Flight Data Monitoring (FOQA) demo
Validates and explains flight data exceedances and links them to reports, for FOQA analysts 1:35
What the demo shows
Validates and explains flight data exceedances and links them to reports, for FOQA analysts
Each flight data event is replayed as its traces on one axis (height against the approach path, airspeed against the target band, sink rate, tailwind) with the gates and the exceedance moment marked and the agents' plain explanation beneath. A flight data reader decodes every file and seals the crew; an event validator tests every exceedance against both air data computers, both radio altimeters, GPS height, the runway and the schedule and clears data errors with a reason; a validation checker re-checks every Level 3 and says when it disagrees. An event explainer writes the cause chain with every clause cited to the data, the ATIS, the METAR or the clearance; a report linker matches voluntary reports on de-identified features; a trend finder rates airports, runways and fleets against their baselines; a briefing writer drafts the review board submission and the pilot briefing; and an identity guard checks everything that leaves. The FOQA analyst confirms or rejects each event and decides which trends go to the Safety Review Board; only the gatekeeper can link an event to a crew.
Transcript
- flight data monitoring for airline safety teams.
- Agents check and explain every flight event.
- Most unstable approaches, 97 in 100, are landed anyway.
- Overnight, 1,388 flights, 214 events and 26 for a lease.
- Here is CV1910 into Seattle, replayed trace by trace.
- At 500 feet, it was 19 knots fast.
- with an 11 knot tailwind.
- The validator checked both air data computers.
- The event is real.
- The explainer says why, and every clause is cited.
- The trend finder found 11 such night arrivals on 16R.
- Two pilot reports match.
- Nobody learns who wrote them.
- Elise confirms the event with her signature.
- Then she sends the trend to the safety review board.
- Every value cited, every crew anonymous, every decision logged.
- The result, 214 events, 26 decisions by morning.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.