HR & CRM

Threat and Error Management: Pilot Interview Examples

Define threats, errors and undesired aircraft states, then build a clear TEM answer from a worked runway-change scenario.

Written by Lucas 7 min read Updated
Read the guide
Threat and Error Management: Pilot Interview Examples

Threat and error management (TEM) is a way to recognise operational threats, detect crew errors and recover from undesired aircraft states. In a pilot interview, show how a specific barrier protected safety margins, then explain what you did when prevention or detection was no longer enough.

For a competency question, use an event you experienced. The worked runway-change case below is a teaching scenario, with crew calls and recovery actions governed by the aircraft and operator procedures.

Threat and error management definitions

The following definitions paraphrase EASA Aircrew, GM1 to Appendix 5, paragraph (o):

  • Threat: an event or error outside the crew's influence that makes the operation more complex and requires management to preserve safety margins.
  • Error: something the crew does, or fails to do, that produces a departure from the organisation's or crew's intended or expected result.
  • Undesired aircraft state (UAS): a crew-induced deviation in aircraft position or speed, incorrect use of controls, or wrong system configuration that reduces safety margins. Recovery can restore those margins; an ineffective response can introduce another error or progress to an incident or accident.

A windshear encounter is a threat; a crew-induced high, fast approach is an undesired aircraft state. An undesired state is a condition from which recovery remains possible, rather than the accident or incident outcome itself.

A 30-second answer to “What is TEM?”

“TEM helps me anticipate threats, trap errors and recover safety margins. A late runway change is a threat; entering the wrong transition in the flight management system (FMS) is a crew error. If that leaves us high and fast, we have an undesired aircraft state. Briefing, task sharing and cross-checks are barriers. Once the aircraft state is the problem, I prioritise recovering the flight path, then review the original mistake.”

Record a 60-second TEM answer in the AI video interview simulator, then listen for a clear distinction between the threat, error and aircraft state.

Follow a runway change through the model

In this fictional two-pilot simulator scenario, a late runway change increases workload. The pilot flying (PF) flies the cleared flight path while the pilot monitoring (PM) loads the revised approach. The PM selects the wrong transition and the crew misses the cross-check. The shorter-than-expected path leaves less distance to descend and slow down. The crew is still high and fast at the operator's stabilisation gate, so they go around.

Element in this example What to discuss
Threat The late change and the extra workload it creates.
Crew error Wrong FMS transition: aircraft handling (automation) error. Missed cross-check: procedural error.
Undesired aircraft state The aircraft is high and fast at the stabilisation gate.
Recovery Go around, monitor the flight path, communicate intentions and reassess before another attempt.

The classification follows the crew's interaction: an incorrect automation input is a handling error; omitting a required cross-check is procedural. Dan Maurino's TEM paper uses a comparable wrong-approach FMS example to show why crews must shift their attention from correcting an entry to managing the aircraft state.

Several threats and errors can interact. A simple chain helps explain this case, but an actual event may not follow one neat sequence.

Compare prevention, detection and recovery

These barriers are often taught as avoid, trap, mitigate, as in Transport Canada AC 700-042, Appendix A. Before changing the setup, the PF maintains the cleared flight path and the PM loads the revision when workload permits, under the operator's procedures. Cross-check the runway, approach and transition in the FMS against the ATC clearance and current chart before following the revised route.

The first countermeasure to a late runway change is time: request extra track miles or delaying action and slow down early where appropriate. If the change cannot be absorbed safely, tell ATC you are unable, in line with your operator's policy. Airbus's approach guidance supports early energy management, requesting track miles and telling ATC when a request cannot be met. These are preparation principles, rather than a universal speed or manoeuvre.

If the crew can see early that the approach cannot be stabilised, discontinue it using the applicable procedure. If the aircraft is high and fast at the stabilisation gate, go around. Do not let both pilots become absorbed in reprogramming the FMS while the flight path deteriorates. The unstable-approach interview guide develops the distinction between an earlier discontinued approach and a go-around when the required criteria are not met.

In ground study or a simulator debrief, identify which barrier could have acted and who was responsible. In the arrival briefing, cover what applies to this flight, including the relevant minima, the charted missed-approach path and applicable altitude instructions, under the operator's procedures. If the cross-check catches the entry early enough, the crew has trapped the error before it develops into the undesired state. Keep diagnosis of the original mistake for a safe moment after recovery.

Model answer: describe what you said and what happened

“We communicated well” leaves out the action. Answer as the PM in the scenario above:

“We're high and fast at our stabilisation gate. As PM, I'd call for the go-around using our standard wording. The PF initiates it under our SOP and flies the applicable missed-approach instructions. I monitor the flight path and modes and carry out my assigned calls and actions.

As soon as workload permits, I'd tell ATC ‘XYZ123, GOING AROUND’. We'd check fuel and agree the next option. If we can make another approach, I'd request enough track miles. We'd verify the revised clearance and FMS setup against the chart and brief the new approach before continuing. The lesson on the threat side is to ask for time earlier.

In the debrief, I'd explain that the runway change was the threat, the wrong transition and missed check were our errors, and the high, fast approach was the aircraft state we needed to recover from.”

“GOING AROUND” is the pilot transmission in EASA SERA phraseology, section 1.4.18, consistent with the ICAO phraseology cited in EUROCONTROL's runway-excursion prevention plan. The PM transmits as workload permits while the PF flies the applicable charted procedure or ATC instructions.

Test yourself on free CRM and HR interview questions before reading the model answers.

If the cross-check catches the wrong transition earlier, with time to correct it, a useful challenge is: “The selected transition doesn't match our clearance. Let's compare it with the chart before we continue.” Explain why this earlier detection changes the outcome.

Build a personal example with observable evidence

Select an event you actually experienced. Write down the situation, your role and the specific action you took. Include the other pilot's or team member's response where it matters.

  • What made the task more complex?
  • What did you notice, and what evidence supported your concern?
  • Which action did you personally take?
  • What happened after that action?
  • What changed in your later preparation or behaviour?

“We caught the incorrect setup during the cross-check” is an observable result. If you made the original mistake, take ownership and explain how it was detected. Keep other people anonymous and omit sensitive operational details.

Use the STAR method guide to organise the event. For a challenge involving authority gradient, practise the disagreement-with-your-captain question. Keep this simulator response separate from your own history.

Try the HR and CRM interview questions and human performance topics. Answer first, then compare the structure with the model response.

The sim-check examiner guide also uses a runway-change example to connect preparation with observable crew behaviour. Continue with simulator assessment preparation, or download the existing free 20-question interview workbook for offline practice.

Sources and scope

  1. EASA Easy Access Rules for Aircrew, GM1 to Appendix 5, paragraph (o), gives the TEM definitions and countermeasures.
  2. Dan Maurino, ICAO: Threat and Error Management, CASS 2005: error classification and the transition from error management to aircraft-state recovery.
  3. SKYbrary: Late runway or approach-type change and missed-approach RTF communications, as related reading. EUROCONTROL's prevention plan, Appendix C and aircraft-operator guidance, supports the time, track-mile and phraseology points; Airbus Safety First supports early energy management and ATC cooperation.
  4. Transport Canada: Introduction to Threat and Error Management, as further reading.

Last reviewed: November 2026

Prepare your next answer

Make sure the interviewer can distinguish the threat, your action and the outcome. Record one answer, identify the weakest link and practise it again.

Compare YPI plans for CRM model answers, simulator preparation, A320/B737 practice and video interview attempts. Independent preparation resource, not affiliated with or endorsed by any airline.

Ready to apply? Browse first officer jobs.

About the reviewer

Lucas · Airline pilot & instructor

Airline pilot and instructor with experience in Europe, North America, Africa and the Middle East. Our editorial policy

Browse jobs by location or role