Operations Personas

PlaneConnection’s Flight Operations module serves six distinct user personas. Each persona has different responsibilities, regulatory obligations, interaction frequency, and success metrics. Understanding these personas helps you configure the right user roles and tailor the platform experience to your team.

​

Persona Overview

---

​

Director of Operations

​

How They Use PlaneConnection

The DO starts each day on the Command Center dashboard, scanning the KPI strip for active aircraft count, today’s flights, OTP percentage, fleet utilization, and open squawks. The AI anomaly banner highlights any statistical outliers that need attention. For monthly management meetings, the DO uses the Reports hub to pull fleet performance data — annual utilization, operating costs, and fleet totals — and exports them as PDF or Excel packages.

​

Typical Workflows

The DO’s daily engagement centers on the morning operational review — scanning KPIs, fleet status, the flight timeline, open squawks, and the financial snapshot. Monthly management meetings drive fleet performance reviews where utilization, operating costs, and fleet totals are pulled into presentation-ready reports. The most consequential workflow is the fleet change decision, where per-aircraft P&L data, utilization trends, and maintenance forecasts inform whether to add, remove, or reposition an aircraft. For detailed task guidance, see Run Reports.

---

​

Chief Pilot

​

How They Use PlaneConnection

The Chief Pilot relies on the Crew Roster and Currency Matrix to confirm every crew member assigned to today’s flights is qualified and current. Color-coded dots (green, yellow, red) make it instant to spot issues. When a currency is expiring, the Chief Pilot schedules training directly from the crew detail page. For FRAT oversight, any flight scoring Medium or High triggers an alert. The Chief Pilot reviews the risk factors, assesses mitigations, and either approves or requests changes before departure.

​

Typical Workflows

The Chief Pilot’s daily engagement centers on the crew readiness check — scanning the currency matrix, verifying today’s assigned crews, and resolving any yellow or red flags. Monthly SmartScore reviews identify pilots who may benefit from additional training or recognition based on data-driven safety scoring. Pre-flight FRAT oversight ensures that elevated-risk flights receive Chief Pilot review and sign-off before departure. For detailed guidance, see Conduct a FRAT.

---

​

Dispatcher

​

How They Use PlaneConnection

The Dispatcher lives on the Dispatch Board throughout the day. The board shows aircraft availability, today’s trip queue, weather conditions, and crew duty status in a single view. Drag-and-drop assignment makes trip-to-aircraft pairing fast, and the system automatically detects conflicts (aircraft maintenance, crew duty limits, scheduling overlaps). For active flights, the In-Flight Display provides a live map with aircraft positions, route projections, and destination weather updates. When diversions are needed, the dispatcher coordinates ground services and notifies all affected parties from one screen.

​

Typical Workflows

The dispatcher’s day begins with the morning dispatch setup — confirming aircraft, crew, weather, and NOTAMs for today’s flights and generating flight releases. Throughout the day, live flight monitoring provides real-time tracking with the ability to respond to delays and coordinate diversions. Trip scheduling with conflict resolution handles the combinatorial challenge of matching new trips against available aircraft and crew while respecting duty limits and maintenance windows.

---

​

Line Pilot (PIC/SIC)

​

How They Use PlaneConnection

The Line Pilot’s primary view is My Cockpit — a personal dashboard showing upcoming trips, currency status, duty time gauge, and recent logbook entries. Before each flight, the pilot reviews the flight release, checks weather, inspects aircraft status, and completes the FRAT assessment. After landing, the pilot enters flight times, fuel burn, landings, approach types, and any discrepancies — all from a single post-flight form. The system automatically updates the logbook, aircraft hours, and duty time calculations.

​

Typical Workflows

The pilot’s engagement with PlaneConnection concentrates around two key moments: pre-flight preparation (reviewing currency, duty time, flight release, weather, aircraft status, and completing the FRAT) and post-flight logging (recording flight times, fuel, landings, approaches, discrepancies, and expenses). Between flights, personal currency management ensures all certifications remain current with renewals scheduled before expiration.

---

​

Maintenance Controller

​

How They Use PlaneConnection

The Maintenance Controller starts each day on the Due Items page, reviewing the fleet health matrix. The color-coded grid (rows = aircraft, columns = inspection categories) makes it instant to identify what needs attention. When a due item is approaching, the controller coordinates a maintenance window with dispatch, and the system checks for trip conflicts automatically. For discrepancies, the controller assesses severity, decides whether to defer under MEL or ground for repair, creates work orders, and tracks resolution through to closure — all with a complete audit trail.

​

Typical Workflows

The Maintenance Controller’s daily fleet health review covers fleet availability, the due items matrix, and open discrepancies. AD/SB compliance reviews verify that all Airworthiness Directives and Service Bulletins are compliant across the fleet. The squawk resolution workflow tracks discrepancies from pilot report through assessment, deferral or repair decision, and final resolution with a complete audit trail.

---

​

Owner / Client

​

How They Use PlaneConnection

The Owner accesses a simplified portal focused on trip requests, financial transparency, and real-time trip tracking. The trip request form uses plain language (airport names instead of ICAO codes, calendar pickers instead of UTC times) and provides a cost estimate within hours. The monthly financial review shows usage hours, revenue from charter, itemized expenses (fuel, maintenance, crew, insurance, hangar), and net position — all downloadable as a professional owner statement PDF.

​

Typical Workflows

The owner’s primary interactions are requesting trips (submitting origin, destination, date, passengers, and special requests, then reviewing and approving the estimate), monthly financial reviews (examining usage, revenue, expenses, net position, and payout status), and tracking upcoming trips (checking details, passenger manifests, ground transport, weather, and live flight position on travel day).

---

​

Cross-Role Interactions

These personas do not work in isolation. The reason PlaneConnection is a single integrated platform rather than separate tools for each role is that aviation operations are inherently collaborative — every trip, every safety event, and every crew currency change touches multiple personas.

​

Trip Lifecycle

A trip is the clearest example of cross-role collaboration. It begins when an owner submits a request, passes through the dispatcher for availability checking and estimation, returns to the owner for approval, and then flows into the operational pipeline. The dispatcher assigns aircraft and crew, the Chief Pilot verifies qualifications and duty compliance, and the Maintenance Controller confirms airworthiness — all before the line pilot ever sees the flight release. After the flight, the pilot’s post-flight log feeds data back to maintenance (discrepancies), accounting (expenses), and the owner (trip summary and invoice). Each persona acts on the same underlying trip record from their own perspective, ensuring consistency without manual data transfer between systems.

​

Safety Event Flow

When an operational event has safety implications, the cross-role flow extends beyond operations into the SMS module. A discrepancy reported by a line pilot post-flight is assessed by the Maintenance Controller for its technical root cause, potentially flagged by a dispatcher as safety-relevant, and then elevated to the Safety Manager for formal investigation. The investigation team conducts root cause analysis, and the Safety Board reviews findings and assigns corrective actions. The reason this flow is built into the platform rather than handled through separate safety reporting systems is that the operational context — aircraft status, crew duty time, weather conditions, maintenance history — is already captured in the ops data and should inform the safety investigation without requiring re-entry.

​

Crew Currency Expiration

Currency management illustrates how the platform automates cross-role coordination. When the system detects a currency expiring within 60 days, the Chief Pilot receives an alert and schedules training. The line pilot receives the training assignment and completes it. The dispatcher immediately sees the updated currency status, making the pilot available for dispatch. If a currency lapses before renewal, the system automatically blocks the pilot from flight assignments until renewed — a safeguard that operates independently of any individual persona’s attention, preventing the scheduling errors that can occur when currency tracking depends on manual spreadsheet checks.

---

​

RBAC Mapping

Each persona maps to one or more platform user roles:

​

Related