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 |
|---|---|---|
| Pilot | Text | Search by the pilot's name, e-mail, or callsign (partial match) |
| Flight Number | Text | Search by flight number or callsign |
| Status | Select | Filter by flight status |
| 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 |
| Airline | Select (searchable) | Filter by airline |
| 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 |
| Date from / Date 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.
The top of the page is a summary card: the route, pilot, aircraft and stands, then a row of headline figures — landing rate, touchdown G, touchdown distance, centreline offset, block/air time and the flight score. A thin strip across the top of the card carries the flight's status colour. Landing rate and touchdown G are coloured by band, with the band named underneath:
| Figure | Bands |
|---|---|
| Landing rate | Butter up to 100 fpm, Good up to 200 fpm, Firm up to 400 fpm, Hard above 400 fpm — the same scale the live-flight and replay pages use |
| Touchdown G | Smooth up to 1.2 G, Normal up to 1.5 G, Hard up to 2.0 G, Dangerous above 2.0 G — the LANDING_G_FORCE template's default bands |
| Score | Coloured by its Gold / Silver / Bronze tier |
Landing rate is the vertical speed on the last position report before the wheels touch. Touchdown G is the peak G-force in the moment the gear takes the aircraft's weight — the highest reading from that last airborne report through the first 1.5 seconds on the ground — because the load builds after contact rather than before it.
These bands are for display only. An airline that customised its FDM profile's landing bands is still scored on its own bands, and those FDM events remain the record of truth.
For a staff reviewer, the Review card opens the row of airport cards, above the tabs — so a decision never requires scrolling past a chart first. It shows the current status (with who set it, the system's auto-review or staff, and how long ago), three checks drawn from the flight's own data (FDM warnings and violations, the FDM event count, and the score and tier), the decisions the current status allows (Accept, Warn, Reject), and the Reprocess and Delete Flight actions.
Below that, the page is organized into seven tabs. The current tab is carried in the page's URL, so a tab can be linked or bookmarked directly. The Log tab shows how many entries it holds.
| Tab | What it shows |
|---|---|
| Overview | The flight map, flight details, the score with a bar per category, and the FDM events list |
| Landing | The runway diagram, the landing performance report and touchdown wind, the flare charts, the approach profiles, and the stabilized-approach gate |
| Takeoff | The runway diagram, the takeoff performance report, and the takeoff-roll and climb charts |
| Telemetry | Synced telemetry tracks, plus the full zoomable chart of every channel |
| Score | The score breakdown and the Flight Points panel |
| Log | The activity log — staff only; pilots viewing their own flight do not see this tab |
| Notes | The notes thread between the pilot and staff, including any appeal — see Notes and Appeals |
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) |
Airport Weather
The departure and arrival airport cards show the raw METAR observed around blocks-off and blocks-on, with a flight-category badge (VFR / MVFR / IFR / LIFR) next to the airport name.
This is captured once, at the time the flight happened, and stored on the flight record — it is not a live weather lookup. Flights flown before this feature shipped have no stored observation and show no weather block at all; there is no backfill for them. If the weather provider was unreachable at the time, the same applies: the card simply omits the weather block.
Landing Performance Report
Shown in the Landing tab. When a flight's arrival runway (derived automatically from the aircraft's own ACARS position reports) matches a seeded runway record for the arrival airport, the flight page shows a landing performance report alongside landing rate and G-force:
| Field | Description |
|---|---|
| Touchdown Distance | Distance from the runway threshold to the touchdown point, in metres. Negative means the aircraft touched down short of the threshold |
| Centreline Offset | Lateral distance from the runway centreline at touchdown, left or right |
| Touchdown Ground Speed / Airspeed | Ground speed and indicated airspeed at the moment of touchdown, in knots. Shown for reference only — not scored, since a safe touchdown speed depends on aircraft type and flap setting |
| Runway Used | Distance from the threshold to the end of the landing roll, in metres and as a percentage of the runway's landing length |
This report needs a reported arrival runway and the aircraft's own reported runway geometry for it — both ends of the runway, sent by the ACARS client (most current clients do). No airport database record needs to be seeded at all: the runway's threshold, heading and length all come from what the aircraft reported, not from a seeded coordinate. A stable client that never reports the runway ends, or a payload too implausible to trust, does not produce this report; it renders nothing rather than a misleading number. A bounced landing still gets the report: the runway ends reported after a brief bounce count, but those reported after a touch-and-go or go-around do not. See FDM Profiles for the TOUCHDOWN_CENTRELINE_OFFSET and RUNWAY_DISTANCE_USED triggers that can score the centreline offset and runway usage per tenant.
Approach and Ground Track Diagrams
The Landing tab also draws the approach and touchdown from the same position data, so staff and pilots can see how the approach got there, not just the final numbers:
- Runway diagram — opens the tab. The runway drawn to scale lengthwise, with the approach over the threshold (dashed) and the ground track from touchdown to the end of the landing roll (solid) overlaid, and the touchdown point and rollout end marked. Every runway is drawn at the same proportions, so the lateral (left/right) axis is deliberately exaggerated compared to the runway's true length — a real runway is a 50:1+ sliver at true scale, which would make a few metres of deviation invisible. The footer states the exaggeration factor for that runway (negative offsets are left of the centreline, which plots above it), so the exaggerated geometry is never mistaken for a to-scale plan. When the touchdown position reported a wind and the landing runway's magnetic heading is on file, a windsock stands at the far end's corner, streaming downwind relative to the runway as drawn (a headwind trails it back toward the threshold), labelled with the wind and its headwind/tailwind and crosswind components — the same numbers as the Wind at Touchdown card beside the landing performance report. A calm wind shows the pole with no sock.
- Vertical speed · flare and G-force · touchdown — the ten seconds before touchdown and two after, from the flight's own position reports. Each chart's touchdown marker sits on the reading its figure was taken from: the last airborne report for vertical speed, the post-touchdown peak for G-force.
- Approach profile · height above threshold and Approach profile · lateral offset — height above the runway threshold's elevation, and lateral offset from the extended centreline, against distance to the threshold. They cover the final approach only: from where the aircraft turned onto the runway's axis (within 10 NM) down to touchdown, so a downwind leg, a pass over the field or an earlier missed approach is not drawn. The height chart is drawn against a nominal 3° reference glidepath — a fixed assumption this application uses for display only, not the airport's actual published glidepath angle (Airspace does not store that per runway) — and, when the stabilized-approach rule is enabled, the gate height.
The diagrams need the same arrival runway and reported runway geometry as the landing performance report above, plus a usable position history for the flight — they render nothing (no placeholder) when positions have been archived or there are too few samples to plot. Like the numbers above them, these diagrams are display only: no FDM trigger or score is derived from glidepath or centreline deviation shown here.
Takeoff Performance Report
Shown in the Takeoff tab. The departure mirror of the landing performance report. When a flight's departure runway (also derived automatically from ACARS position reports) has the same reported runway geometry available, the flight page shows a takeoff performance report alongside it:
| Field | Description |
|---|---|
| Liftoff Distance | Distance from the runway threshold to the point where the aircraft left the ground, in metres. Negative means the aircraft lifted off before the threshold |
| Takeoff Roll | Distance from the start of the takeoff roll to the liftoff point, in metres |
| Centreline Offset | Lateral distance from the runway centreline at liftoff, left or right |
| Liftoff Ground Speed / Airspeed | Ground speed and indicated airspeed at the moment of liftoff, in knots. Shown for reference only — not scored |
| Runway Used | Percentage of the runway's takeoff length used before liftoff |
Same requirements as the landing performance report: a reported departure runway and the aircraft's own reported runway geometry for it. See FDM Profiles for the TAKEOFF_RUNWAY_USED_PERCENT trigger that can score takeoff runway usage per tenant.
When the flight's position history is still available, the tab also draws the takeoff itself — the same liftoff point and runway geometry the report above was computed from:
- Runway diagram — the actual ground track from the start of the takeoff roll to liftoff (solid) and on to the runway end (dashed), with the line-up and liftoff marked. Without a usable position history it falls back to a straight line between the line-up and liftoff points from the report. As on the landing side, a windsock at the far end's corner shows the wind on the liftoff sample against the departure runway, when that sample reported a wind and the runway's magnetic heading is on file.
- Lateral profile · takeoff roll — the offset from the centreline along the runway.
- Climb profile — altitude and groundspeed over the first 15 nm flown after liftoff, with the climb gradient over the first 5 nm.
FDM Events
Shown in the Overview tab. All FDM trigger events generated during the flight are displayed in a list, with a count per severity above it (zero counts included):
| 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.
Staff who can review flights see a Waive button (×) on each event — see Waive an FDM Event.
Flight Points
Shown in the Score tab, alongside the score breakdown. This panel shows all point transactions connected to the flight, aggregating 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 at the top of the Overview tab, 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.
The Telemetry tab shows synced tracks: one strip per series — altitude, speed, vertical speed, attitude, configuration, engines, fuel and wind — on a shared time axis, with the flight phases along the top and the FDM events marked. A single cursor rests on touchdown; hovering moves it, and every strip shows its reading at the cursor. The pill toggles above choose which strips (and the event markers) are shown.
Below the tracks, All channels · zoomable chart (collapsed by default) holds the full telemetry graph, adding autopilot, throttle, controls, lights, weight, sim rate 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 — including any event staff had waived, which may be detected again. 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.
Waive an FDM Event
Staff who can review flights can waive any FDM event — a warning, a violation, or an information event — when it should not stand: a simulator glitch, a false positive, or a deviation that was approved. Click the × at the end of the event's row in the Overview tab's Events list, give a reason, and confirm.
Waiving removes the event from the flight:
- It no longer counts anywhere events are counted: the Review card's checks, the event tallies, the flight's safety score, the pilot's safety rating, and the Safety Dashboard.
- Any FDM points the event awarded or deducted are reversed — the transaction is removed from the pilot's points, as if the event had never fired.
- If the flight was already accepted, the pilot's performance rating and the flight's stored score are recalculated.
- The flight's activity log records what was removed (the event, its severity, time and trigger), who removed it, the reason, and the points reversed. When points were reversed, the pilot's own activity log records it too.
Waiving does not change the flight's review status. A flight held for review because of the waived violation stays pending — decide it with Accept, Warn, or Reject as usual.
Waiving cannot be undone from the flight page. Reprocessing the flight re-runs the FDM analysis from the telemetry and may detect the same event again, with its points.
Notify Support
Real sim flights sometimes show behaviour that never comes up in testing — an automated review, FDM event, or score that doesn't match what actually happened in the cockpit. The Notify support button on the flight detail page sends the flight straight to the Airspace team so it can be investigated.
Clicking it opens a dialog asking What happened? Describe what you expected and what the system did instead (at least 10 characters). On send, the Airspace team receives:
- Your description.
- The airline, flight number, route, aircraft, current status, and pilot.
- Your name and email, so the team can follow up with you.
- A link to the flight detail page.
The button is available to staff who can review flights (the same permission as Reprocess). A flight can be reported up to three times per hour; further attempts show a message with how long to wait.
Flag a Diversion
A diversion normally reaches the flight when the pilot declares it in flight (the vOCC declares the alternate when the captain says they are diverting or returning). When that never happened, the flight is filed to its planned destination even though the aircraft landed somewhere else. The Flag diversion button on the flight detail page corrects it.
The dialog asks for the airport the flight landed at (search by ICAO or name; the planned arrival is not offered) and a reason. On submit:
- The flight's arrival airport becomes the chosen airport, and the flight is marked as a diversion, like a declared alternate. The planned arrival stand is cleared and the distance is re-measured from the departure airport (a return to the departure airport measures 0 NM).
- The aircraft and the pilot are moved to that airport too, but only if they are still at the planned arrival and have not been booked or flown since. Otherwise they are left where they are. The confirmation says which of them moved.
- A ferry, repositioning, charter or tour leg the flight completed is corrected (see below).
- The flight's activity log records who flagged it, the planned and actual arrival, the reason, and what was moved, alongside the before/after values of the changed fields, plus one entry per corrected leg. Aircraft and pilot moves are also logged on the aircraft and the pilot.
What happens to the flight's leg
Tour, charter, ferry and repositioning legs are completed when the flight is submitted, before any review, so by the time staff flag the diversion the leg already counts as flown to the planned arrival and its points are paid. Flagging corrects it the way a declared alternate would have left it. In the examples, the leg was planned A → B and the flight landed at C.
| Leg | What flagging does |
|---|---|
| Ferry | The leg's points are reversed and it is shown as Diverted, planned B (A → C). If the aircraft was moved to C, a leg C → B is added right after it for the same pilot, with a fresh window, and booked for them if they were moved too. The leg after it waits again, and its pilot is told their window is delayed. A completed ferry goes back in progress. If the aircraft has been booked or flown since, no leg back is added and staff sort the ferry out by hand. |
| Repositioning | The leg's points are reversed. If the aircraft was moved to C, the leg and its bounty are cancelled, and a new bounty C → B is posted when no schedule the aircraft can fly leaves C. If the aircraft has been booked or flown since, the leg stays completed so the rest of the bounty can carry on. |
| Charter | The leg is reopened to be flown again, with a new window of the same length starting now (the original has usually closed by review time). The pilot is told the leg is open. If the leg had completed the contract, the contract goes back in progress and its points are reversed. A contract that has failed or been cancelled since is left as it is. |
| Tour | The leg is reopened and the tour steps back to it, so the pilot books and flies it again. A later leg they had already booked is unbooked. If the leg had finished the tour, the tour award and its bonus points are revoked. If the pilot has flown a later leg of the tour since, the tour is left as it is. |
A leg the pilot already diverted by declaring an alternate in flight is left as it is.
The button is available to staff who can review flights (the same permission as Reprocess), and only while the flight has never been approved. Approval adds hours and starts maintenance waiting at the aircraft's base when the flight arrived there, so flag the diversion before deciding the flight. A rejected flight that was never approved can still be flagged. Reprocessing a flagged flight keeps the diversion and holds it for staff review.
Notes and Appeals
Every flight has a Notes tab: a thread the pilot who flew it and staff share. The pilot reads every note staff leave and can add their own; staff see the same thread from the backoffice. Each note shows its author, a Pilot or Staff badge, and when it was written. Other pilots never see a flight's notes. The tab shows how many notes it holds.
Who can read, add, or delete notes follows the notes abilities.
Appeals
When a flight is rejected or accepted with a warning, its pilot sees a call-out on their flight page with an Appeal to staff button. The pilot writes why the decision should be reviewed (at least 20 characters), and on sending:
- the message is added to the flight's notes, marked Appeal;
- the flight goes back to PENDING_STAFF, so it reappears in the Flight Review queue;
- the appeal is recorded in the flight's activity log.
Each flight can be appealed once — after staff decide it again, the button does not come back. Only the pilot who flew the flight can appeal it.
When staff open a flight under appeal — from the Flight Review queue or the flight page — a dialog opens with the pilot's message, and a banner above the flight keeps it one click away (Read appeal). The banner disappears once staff decide the flight again.
The next decision on the flight — Accept, Warn or Reject — answers the appeal. The answer is added to the flight's notes, marked Appeal decision and signed by the staff member who decided (or System when a reprocess decided it), so the pilot reads it right under their appeal: it states whether the flight was accepted, accepted with a warning, or rejected, followed by the reason staff gave for a warning or rejection, written in the pilot's language where Airspace has it. The pilot is also notified of the result: in the notification bell and by email, in the pilot's language where Airspace has it. The notification says whether the flight was accepted, accepted with a warning, or rejected, includes the reason staff gave for a warning or rejection, and links to the flight. An appeal stays open while the flight is reprocessed, so if the reprocess decides the flight automatically, that decision answers the appeal instead. Only the decision that answers the appeal adds the note and sends a notification; later decisions on the same flight, or a reprocess that sends it back to review, do not reopen it.
Re-approving a flight that had already been approved before (approved, then warned or rejected, then reinstated) does not add its hours, cycles or part wear to the aircraft a second time.
Pilot Record During Review
While reviewing a flight — on the flight page or in the Flight Review queue — staff with view-notes on users see a Pilot record button. It opens the pilot's staff-only record beside the flight, with the number of notes on the button, and lets staff add to it without leaving the review.
Activity Log
Shown in the Log tab, visible to staff only. It 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, waived FDM events with their reason, flagged diversions with the planned and actual arrival and their reason).
- 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).