Flights
Overview
The Flights page displays all submitted flight records in the system. In this platform, completed flight submissions are referred to as flights (not PIREPs). Each flight record is created when a pilot completes a flight via ACARS and contains the full telemetry data, FDM analysis results, timing information, and approval status.
Backoffice path: backoffice/flights
Available to roles: System Administrator, Administrator
Flight List
The flights list provides a filterable, sortable, and paginated view of all submitted flight records.
List Columns
| Column | Description |
|---|---|
| Flight Number | The scheduled flight number (e.g., "VA101") |
| Callsign | The radio callsign used for the flight |
| User | The pilot who flew the flight |
| Departure | The departure airport ICAO code |
| Arrival | The arrival airport ICAO code |
| Aircraft | The aircraft registration and fleet name |
| Status | Badge indicating the current flight status (see below) |
| Date | The date the flight was submitted |
Filters
The filter panel (collapsed by default) provides structured filters to narrow down the flight list:
| Filter | Type | Description |
|---|---|---|
| Airline | Select (searchable) | Filter by airline |
| Flight Number | Text | Search by flight number or callsign |
| Departure Airport | Select (searchable) | Filter by departure airport |
| Arrival Airport | Select (searchable) | Filter by arrival airport |
| Departure Country | Select (searchable) | Filter by the country of the departure airport |
| Arrival Country | Select (searchable) | Filter by the country of the arrival airport |
| Fleet | Select (searchable) | Filter by fleet; narrows subfleet and aircraft options |
| Subfleet | Select (searchable) | Filter by subfleet; narrows aircraft options |
| Aircraft | Select (searchable) | Filter by specific aircraft registration |
| From / To | Date | Filter by created date range |
Fleet, Subfleet, and Aircraft form a cascading filter: selecting a Fleet narrows the Subfleet options, and selecting a Subfleet narrows the Aircraft options.
A badge next to the "Filters" heading shows the count of active filters. Use the Clear filters button to reset all filters at once.
Export CSV
The Export CSV button downloads a CSV file containing all flights that match the current filters. The export includes standard flight data (flight number, callsign, airline, user, airports, countries, aircraft, fleet, subfleet, status, times, pax, cargo, distance, landing rate, G-force, network, route) but excludes telemetry position data.
Click any column header to sort the list. The list is paginated for performance.
Flight Statuses
Every flight has a status that indicates its current state in the review process. Statuses are grouped by whether they were set by the system automatically or by a staff member manually.
| Status | Set By | Description |
|---|---|---|
| PENDING_STAFF | System | The flight is awaiting manual review by a staff member. This occurs when FDM analysis detects violations, when warnings are present and auto-accept is disabled, or when the flight involved an alternate diversion |
| ACCEPTED_STAFF | Staff | A staff member manually reviewed and approved the flight |
| ACCEPTED_SYSTEM | System | The flight was automatically approved because it had no FDM warnings or violations and auto-approval is enabled |
| WARNING_STAFF | Staff | A staff member reviewed the flight and accepted it with a warning notation |
| WARNING_SYSTEM | System | The flight had FDM warnings but no violations, and the auto-accept warnings setting is enabled |
| REJECTED_STAFF | Staff | A staff member reviewed and rejected the flight |
| REJECTED_SYSTEM | System | The flight was automatically rejected by the system |
Flight Detail Page
Clicking on a flight in the list opens its detail page, which provides comprehensive information about the flight.
Route and Timing
The detail page displays the planned and actual route along with all recorded times:
| Time | Description |
|---|---|
| Block Off | The time the aircraft left the gate (parking brake released) |
| Takeoff | The time the aircraft became airborne |
| Landing | The time the aircraft touched down |
| Block On | The time the aircraft arrived at the gate (parking brake set) |
Two duration values are calculated from these times:
- Block Time -- Total time from block off to block on (gate-to-gate).
- Flight Time -- Total time from takeoff to landing (wheels-up to wheels-down).
Flight Data
| Field | Description |
|---|---|
| Distance | Total distance flown |
| Passengers (PAX) | Number of passengers carried |
| Cargo | Cargo weight carried |
| Landing Rate | Vertical speed at touchdown (feet per minute) |
FDM Events
All FDM trigger events generated during the flight are displayed in a list, grouped by severity:
| Severity | Description |
|---|---|
| Information | Advisory events, often with positive points for good performance |
| Warning | Operational concerns that may or may not require review |
| Violation | Serious deviations that always require staff review |
Each event shows its label, description, and point value (positive for rewards, negative for penalties). The total points across all events are summed and displayed.
Flight Points
The flight detail page includes a Flight Points panel that shows all point transactions connected to the flight. This panel aggregates two categories of points:
| Source | Description |
|---|---|
| FDM | Points automatically generated by FDM trigger evaluation during flight processing. These are read-only and reflect the configured trigger point values. |
| Staff | Points manually added by staff during flight review. These are linked directly to the flight record. |
Staff with point management permissions can add new point entries from this panel using the Add Points button. Each entry requires a reason and point amount (positive to award, negative to deduct). An optional remarks field is available for additional context.
All point entries are immutable ledger records and cannot be deleted. To reverse a manual entry, add a new entry with the opposite point value.
The total points for the flight are displayed as a summary badge next to the panel heading.
Telemetry Positions
The flight's recorded telemetry positions are displayed on an interactive map, showing the aircraft's track from departure to arrival with altitude-based color coding. This allows staff to visually verify the route flown and identify any deviations.
A telemetry graph is also available, providing time-series charts for altitude, speed, vertical speed, attitude, configuration, engine parameters, fuel, wind, autopilot, throttle, controls, lights, weight, and transponder state. Toggle buttons above the chart control which data groups are visible. The chart supports zoom (scroll/pinch), area zoom (shift+drag), and pan (ctrl+drag).
For long flights with large numbers of position reports, both the map and graph automatically downsample to a maximum of 5,000 data points to ensure the page loads efficiently. Corrupt data points (e.g., simulator glitches where altitude suddenly drops to zero mid-cruise) are automatically filtered out of the telemetry graph.
Payload
The payload section shows the planned versus actual passenger and cargo figures for the flight.
SimBrief Brief
If the flight was dispatched through SimBrief, the original flight plan brief is available for reference. This includes the planned route, fuel calculations, weather data, and any dispatch restriction adjustments that were applied.
Staff Actions
Reprocess Flight
The Reprocess action re-runs the full FDM analysis against a flight's raw ACARS telemetry log as a background job.
Use this action when:
- FDM profiles or triggers have been updated and you want to re-evaluate previously submitted flights under the new rules.
- A flight was processed with an incorrect or missing FDM profile assignment.
- You need to verify that trigger changes produce the expected results on historical flight data.
Reprocessing replaces all existing FDM events for the flight with newly generated events from the current active profiles and triggers. The flight status may change as a result if the new FDM events differ in severity from the original analysis.
Single flight: Use the "Reprocess" option in the dropdown menu on the flights list, or the Reprocess button on the flight detail page.
Bulk reprocess: On the flights list page, use the checkboxes to select multiple flights, then click "Reprocess Selected". A confirmation dialog will appear before queuing all selected flights for reprocessing. The "select all" checkbox in the table header selects all flights on the current page. Selections persist across pages.
Reprocessing runs as a background job. The flight detail page will update once processing is complete. Large flights with extensive telemetry data may take a few moments to reprocess.
Activity Log
The flight detail page includes a paginated activity log that records all lifecycle events for the flight, including:
- Automatic status changes from the processing pipeline (data preparation, finalization, point awards).
- Manual staff actions (approve, warn, reject, reprocess).
- Attribute changes tracked with before/after values.
Each entry shows a timestamp and the staff member who performed the action (or "System" for automated events).