FOQA and FDM (Flight Operational Quality Assurance / Flight Data Monitoring)

FOQA and FDM are functionally identical safety programs operating under different acronyms in different regulatory regions. The FAA published Advisory Circular 120-82 in 2004 establishing FOQA as a non-punitive safety data program. EASA codified FDM into Part-ORO.AOC.130 with mandatory implementation for commercial air transport operators flying turbine-powered aircraft above 27,000 kg MTOW (raised over time). ICAO Annex 6 Chapter 3 §3.3.6 makes FDM a mandatory element of the SMS for international commercial air transport operations.

The technical machinery. Modern transport aircraft generate hundreds to thousands of parameters per second — pitch, roll, airspeed, altitude, control inputs, engine parameters, configuration, navigation data, autopilot state — recorded to a Quick Access Recorder (QAR) or transferred via wireless data link. The data is downloaded routinely (daily on most fleets), processed through analytical software (Sagem AGS, Teledyne FDR, Airbus AirFASE, GE Aviation Centrix), and analyzed against pre-defined event triggers. Common FOQA/FDM events: unstable approach (failure to meet stabilized approach criteria at gate altitude), high speed in landing configuration, hard landing (>1.6g touchdown), excessive bank angle, terrain proximity, runway excursion proximity, EGT exceedance.

The protected data principle. FOQA and FDM data is — under both FAA AC 120-82 framework and EASA AMC1 ORO.AOC.130 — non-punitive in nature. Data identifies events for organizational analysis and trend identification, not for disciplining individual pilots. The protections are formalized through agreements between operator, pilot union, and regulator. The protections are essential: without them, pilots avoid behaviors that produce data signatures (e.g., flying conservative profiles to avoid event triggers) and the data quality degrades, defeating the safety purpose.

Integration with the SMS. FOQA/FDM data feeds Hazard Identification (Pillar 2 of SMS), Safety Performance Indicators (Pillar 3 — Safety Assurance), and EBT scenario design (recurrent training informed by actual operational events). The connection is bidirectional: the SMS uses FOQA/FDM to detect hazards; the training department uses FOQA/FDM to design EBT scenarios; the safety department compares FOQA/FDM trends against intervention effectiveness.

For smaller operators not yet equipped for full FOQA/FDM, simplified Operational Quality Assurance Lite (OQA-Lite) programs derive equivalent benefit from a smaller parameter set. Even basic Hobbs-time and squawk-rate data captured in maintenance and dispatch systems contributes to the overall safety picture.

For Part 121 / Part-CAT operators, FOQA/FDM is operationally embedded — every flight produces data, every flight contributes to the analytical baseline, every detected event is reviewed and categorized. Operators with mature programs can answer questions like "how many unstable approaches have we had this month?" with hours of latency rather than weeks; operators with immature programs cannot answer the question at all without manual reconstruction.

The operational pattern that matters most for training organizations: the FOQA/FDM data shows what actually happens in line operations — not the simulator profiles, not the training-department imagination of operations, but the actual approaches actually flown by actual line pilots. EBT recurrent training designed around FOQA/FDM evidence delivers safety value the legacy fixed-syllabus model cannot match.

Aviatize integrates FOQA/FDM data when the operator has a separate FOQA/FDM system in place — accepting event feeds and aggregating them alongside the SMS Safety Performance Indicators, the Compliance Monitoring Function findings, and the training department's competency profile data. The connection turns FOQA/FDM from a standalone safety datastream into an integrated operational signal feeding everything downstream.

For operators not yet equipped for FOQA/FDM, Aviatize captures the basic operational data the platform manages anyway — flight time, stabilized approach grades from training, instructor-detected anomalies, dispatch rejections, maintenance squawk rates per flight — into an OQA-Lite-equivalent framework that delivers measurable safety value at the operator's actual maturity stage.