LOFT (Line Oriented Flight Training)

Line Oriented Flight Training emerged directly from the accident-investigation findings of the late 1960s and 1970s. A NASA/United Airlines research program, led by psychologist Robert Helmreich and the NASA Ames Human Factors group, analyzed the accident record and determined that the dominant causal chain was not deficient stick-and-rudder skill but failures in crew coordination, communication, and cockpit decision-making — the behavioral domain now codified as Crew Resource Management (CRM). The NTSB investigation of United Airlines Flight 173 (Portland, Oregon, December 1978 — fuel exhaustion while crew troubleshot a landing-gear anomaly) and Eastern Air Lines Flight 401 (Miami, December 1972 — crew distraction while troubleshooting a cockpit indicator light) became the foundational case studies that drove FAA acceptance of LOFT as a training methodology. The FAA codified LOFT requirements for Part 121 operators in 14 CFR §121.409, which specifies that approved training programs must include LOFT conducted in a simulator qualified under §121.407. For training centers operating under Part 142, §142.55 requires that the training program approved for air carrier use integrate LOFT alongside maneuver-based simulator training.

LOFT is defined by three structural properties that distinguish it from conventional simulator training. First, the scenario runs in real time without instructor pause or replay — the crew experiences the operational scenario as it would unfold on a revenue flight, with time pressure, realistic ATC communications, weather evolution, and accumulated minor and major events. Second, the scenario design replicates an actual line operation: specific routing, realistic dispatch information (fuel load, weather package, NOTAMs, ATIS), and a time-of-day that matches the operational environment for which the crew is being trained. Third, the debrief focuses exclusively on behavioral performance — crew communication, decision logic, threat recognition, task management — not on maneuver precision. The LOFT instructor's role during the scenario is observational, not interventional.

Three formal LOFT variants are recognized in the regulatory and training literature. A Full LOFT is the pure form: one uninterrupted scenario, typically 2–3 hours of flight time, with one or more injected events (ranging from distractions and degraded systems to weather deviations and emergencies requiring diversion). A Line Operational Evaluation (LOE) is a Full LOFT used for proficiency evaluation rather than training — conducted under a 14 CFR §142.59 checking framework, with the crew's performance rated against defined behavioral standards. The LOE is increasingly used by Part 121 operators as a component of their Advanced Qualification Program (AQP), which the FAA codified under 14 CFR Part 121, Subpart Y. A Line Operational Simulation (LOS) was the research tool from which LOSA (Line Operations Safety Audit) evolved — structured observations of normal line operations without the training or evaluation objectives that define LOFT and LOE.

Modern LOFT scenario design is data-driven. ICAO Doc 9995 (Manual of Evidence-Based Training, 2nd ed.) integrates LOFT scenario design explicitly into the EBT framework: the threats and errors injected into LOFT scenarios should derive from FOQA/FDM exceedance data, ASAP/ASRS reports, and LOSA observations of the operator's actual line operations. This evidence pipeline is the mechanism by which EBT becomes operationally meaningful — the crew is trained against the specific threat-and-error combinations that actually occur in their fleet and route network, not against a scenario rotation designed in 1995. EASA Part-ORO ORO.FC.230 and AMC1 ORO.FC.230 mandate that recurrent training for multi-pilot aircraft include scenarios with realistic operational complexity, which in practice means LOFT-format scenarios even for operators who have not formally adopted EBT.

LOFT is not a substitute for maneuver-based training — it is a complement to it. Type rating initial training still requires individual maneuver validation: engine failure at V1, single-engine ILS approach to minimums, rejected takeoff, TCAS RA response. What LOFT provides is the integration environment: the crew must manage a degraded system while simultaneously managing ATC, passenger considerations, fuel state, destination weather, and crew workload. The integration is precisely what maneuver-based training cannot replicate, and it is precisely what the accident record shows was missing.

The most common failure mode in LOFT implementation is instructor intervention. When an instructor freezes the simulator to correct a procedural error or re-brief a maneuver, the LOFT becomes a conventional training session with a realistic scenario wrapper. The crew no longer experiences time pressure, accumulated decision burden, or the consequence cascade that follows an uncorrected error — which is precisely the operational reality LOFT is designed to develop. FAA guidance in AC 120-35D (Line Operational Simulations, 2016) addresses this directly, specifying that LOFT scenarios should be designed with enough margin that the crew can recover from minor errors without instructor intervention, and that instructors must be specifically trained to withhold intervention unless safety of training requires it.

For combined ATO and AOC operators, LOFT presents a program-design challenge: the ATO is training ab-initio students in maneuver-based syllabi while the AOC is running LOFT for line pilots. The scenarios, data infrastructure, and debrief methodology are operationally different. However, a school that introduces LOFT-format exercises at the MCC phase — before a student transitions to an AOC type rating course — builds the CRM and threat-management habits that LOFT recurrent training then reinforces throughout the pilot's line career. The behavioral continuity between early LOFT exposure and mature EBT recurrent training is a competitive differentiator for integrated operator-training organizations.

Aviatize's training management module supports LOFT scenario tracking as a distinct training record type. Each LOFT session is logged with scenario identifier, crew pairing, aircraft type, injected events, and the competency domains assessed during the post-LOFT debrief — using the same nine ICAO core competency taxonomy that governs all CBTA and EBT grading in the platform. The ground training and checking module tracks LOFT completion for recurrent currency purposes, ensuring that Part 121 and Part-ORO recurrent program requirements are met and audit-ready without manual spreadsheet reconciliation.

For operators implementing EBT, the KPI reporting and dashboards module aggregates LOFT debrief outcomes across the pilot population, surfacing which competency domains degrade under the threat profiles most commonly injected in scenarios. This fleet-wide behavioral data is the evidence input that drives the next recurrent cycle's scenario selection — closing the evidence loop that ICAO Doc 9995 defines as the distinguishing feature of mature EBT implementation, and that regulators increasingly test during SMS and training program audits.