Train-the-Trainer by DataHomeLab
Concept

Line operations safety audit

A LOSA is a structured, non-intrusive observation of normal line flights by trained observers. The goal is not to assess named individuals for enforcement or check credit; it is to sample how crews actually manage threats, errors, and undesired aircraft states in everyday operations under protections that keep the data usable for organisational learning. For EBT, LOSA-class flight-deck observation is one of the primary operations-evidence streams that show which threats are real on the line and which competencies fail when they are mismanaged.

How it works

Observation sits on the jump seat (or equivalent) during normal revenue or non-jeopardy line flying. Observers use a coded taxonomy (historically TEM) to record:

  • threats present in the operation (weather, ATC, aircraft, cabin, operational pressure);
  • errors crews commit or inherit;
  • undesired aircraft states if they develop;
  • countermeasures used (including successful recoveries);
  • contextual factors (time pressure, weather, fatigue signals) that FDA alone cannot explain.

Results are aggregated at fleet or operation level. They are not correlated back to punish individuals. Classic LOSA is a time-bounded "snapshot" campaign; related normal-operations monitoring can run more continuously. Doc 9995 groups LOSA under flight-deck observation: high human-resource cost and high training value because it captures the "whys and hows" that flight data analysis (FDA) trends cannot.

Why EBT needs it

FDA can show unstable-approach rates, go-around rates, or exceedance trends; it rarely shows whether the crew lost situation awareness, failed to assert as PM, or mismanaged workload. Confidential safety reports add narrative but are voluntary and biased by what people choose to file. LOSA fills the gap: anonymous structured observation of normal operations, not only accident aftermath.

In the EBT Data Report lineage, "LOSA for EBT" is an explicit source used to build generation-level training priorities. Operator-level LOSA (or equivalent) feeds enhanced programmes: route- and destination-specific threats, real TEM patterns, and competency weaknesses that should appear in scenario design. Doc 9995 notes that for training enhancement, flight-deck observation may be the most valuable single information source.

Relationship to just culture and SMS

LOSA only works if crews believe observation is non-jeopardy and data protection is real. That requires a just culture posture and procedures consistent with Annex 19 data-protection principles: observation notes are for system improvement, not for individual discipline. Outputs should enter the safety management system (SMS) and the training–safety liaison Doc 9995 describes, not sit in a training silo.

Instructor use

  • You are usually a consumer of LOSA findings, not the audit designer. Use fleet briefings and training needs products that translate LOSA themes into module design.
  • In debrief, connect a scenario to line evidence: "Observers see crews miss this callout under gate pressure" is more credible than inventing risk.
  • Do not turn informal jump-seat riding into a pseudo-LOSA of a named crew; that breaks the method and the trust model.
  • When grading PM and TEM-related competencies, remember LOSA-type data often shows monitoring and intervention failures that pure PF handling grades miss; balance attention to both seats in EVAL and SBT.
  • If your airline has no LOSA, treat FDA, reports, and training metrics as partial substitutes and be honest about the blind spot.
  • When designing scenarios from LOSA themes, keep the threat realistic and the training objective competency-clear; do not recreate a news story for drama alone.

Connections

Sources