Why engine failure is a useful speaking scenario
This article supports TELCAP preparation. It does not teach a flight procedure and must never replace the aircraft flight manual, quick-reference handbook, checklist, operator policy or training. Engine failures are a useful language scenario because the speaker must set priorities, report a developing situation and explain decisions without losing the operational sequence.
An engine problem is not always a complete failure. A crew may see abnormal vibration, oil pressure, temperature, thrust response, noise, smoke or an engine warning. The first question is not “How can we fix it?” but “What is the aircraft condition and which procedure applies?” The answer depends on aircraft type, phase of flight and available performance.
In an English assessment, a strong candidate avoids dramatic assumptions. “We have an abnormal engine indication and are following the QRH” is more credible than declaring both engines failed from one warning light. Facts, priorities and clear intentions matter more than advanced vocabulary.
Aviate, navigate and communicate
The traditional priority remains useful: fly the aircraft, navigate toward a safe option and communicate when workload permits. During an immediate failure after take-off, keeping control and following the aircraft-specific memory items or procedure comes before a detailed radio report. One pilot flies and monitors the flight path; the other completes applicable checklists and coordinates.
Task sharing is not rigid. In a single-pilot operation, the pilot must protect control and use short, essential messages. In a multi-crew operation, duties are divided but both pilots maintain situational awareness. A long troubleshooting discussion while neither pilot monitors altitude, airspeed or terrain is dangerous.
Navigation means more than turning toward the nearest visible airport. The crew considers altitude, terrain, weather, runway, aircraft weight, emergency services, fuel and the likely condition of the remaining systems. In a total loss of thrust, glide capability and available landing areas may dominate the decision. With one engine remaining, the appropriate airport may be farther away but better equipped.
Recognising the type of problem
Useful reports distinguish an indication from a confirmed condition. “We have severe vibration on the left engine” identifies the observed problem. “We shut down the left engine in accordance with the checklist” explains a completed action. “We are unable to maintain the assigned level” tells ATC the operational consequence.
The crew should not diagnose the cause over the radio. The cause may be mechanical, fuel-related, bird ingestion, weather damage or a sensor failure. Maintenance and investigation determine the cause later. At the time, ATC needs to know what assistance the aircraft needs and what performance limitations exist.
Cabin effects also matter. An engine failure may require a diversion, a return to the departure airport or preparation for an abnormal landing. Cabin crew need a concise briefing when workload allows: what happened, expected landing time, whether a rapid cabin preparation is needed and whether there are special instructions. Passengers need calm, accurate information rather than technical speculation.
Declaring an emergency and working with ATC
The crew uses applicable emergency phraseology and company procedures. If immediate help or priority is required, the initial call should identify the aircraft, nature of emergency, position or altitude, intention and requested assistance. It may be impossible to include every detail in the first transmission; the crew can give essential information first and update later.
For example: “MAYDAY, MAYDAY, MAYDAY, ABC123, engine failure, maintaining three thousand feet, returning to the departure airport, request priority vectors and emergency services.” The exact wording can change with the event. The important qualities are clarity and a stated need.
ATC can provide vectors, priority, runway information, traffic separation, weather and coordination with rescue services. Controllers may ask for souls on board, fuel remaining, dangerous goods and assistance requested when workload permits. These facts help airport response, but they should not delay immediate aircraft control.
If a crew needs to stop communication temporarily, it can say “stand by.” This is professional task management, not a failure to cooperate. When able, the crew reports its current position, altitude, route and any change in capability.
Selecting a landing option
Airport selection is a risk decision. The departure airport may offer familiar procedures and emergency services, but weather, runway direction or aircraft position may make another airport safer. The destination may be suitable if it is close and the aircraft remains fully capable of reaching it. A crew must continually compare options as conditions change.
For an off-airport landing scenario, the language should remain disciplined. The pilot selects the most suitable reachable area, follows the aircraft procedure and focuses on control. It is unsafe to promise a particular landing site until the aircraft can reach it. A candidate can explain the factors: wind, terrain, obstacles, surface, people, rescue access and remaining energy.
After landing, the aircraft may require evacuation, inspection or a controlled stop on the runway. Crew follow the checklist and commands from the operator or emergency services. The priority is occupants and aircraft safety, not minimising delay or preserving a schedule.
Communication after the immediate event
Once the workload decreases, the crew gives a fuller report. It should identify the engine involved, actions already completed, current aircraft performance, fuel, persons on board, weather concerns and the requested airport support. ATC then has a common operational picture and can coordinate the approach.
Controllers should avoid unnecessary questions during a high-workload phase. Clearances must be concise and realistic for the aircraft's capability. If traffic or weather makes the first plan unsuitable, the controller and crew discuss another option without assuming the original plan remains valid.
After the flight, flight crew and maintenance personnel document indications, timing, engine parameters and actions. A factual report supports troubleshooting and safety learning. It should distinguish what was observed, what the checklist required and what the crew inferred.
Common language mistakes
Candidates often say “we would land immediately.” In aviation, immediate landing may be impossible or less safe than a controlled approach. A better answer identifies a suitable landing option and explains why. Another mistake is saying that one pilot flies while the other “fixes the engine.” Crews follow approved procedures; they do not repair an engine in flight.
Avoid mixing up distress and urgency language without explaining the operational condition. When unsure, state the problem plainly and request the required priority. Also avoid giving exact performance figures for an aircraft type you do not operate. General, correct reasoning is better than memorised data used incorrectly.
Practise a scenario in stages: an abnormal indication, a confirmed shutdown, a weather complication and an ATC question. This requires listening, paraphrasing and adapting an answer—skills central to TELCAP.
Key vocabulary
- engine failure — loss of normal engine power or safe engine operation
- abnormal indication — instrument value or warning outside the expected range
- thrust — force produced by an engine to move the aircraft forward
- QRH — quick-reference handbook used for approved abnormal and emergency procedures
- single-engine operation — flight after one engine is unavailable in a multi-engine aircraft
- return — flight back to the departure airport after an abnormal event
- emergency services — rescue, fire and medical support prepared for an aircraft arrival
- souls on board — number of people on the aircraft, used for emergency coordination
- glide — descent without engine thrust while using the aircraft's remaining energy
- aircraft capability — performance and systems available after a failure
Discussion questions
- Why must aircraft control come before a detailed radio call?
- Which facts should a crew report to ATC after the immediate procedure?
- Why is the nearest airport not automatically the safest choice?
- How does task sharing change the response in a two-pilot crew?
- Which information helps airport emergency services prepare for arrival?
- Why should a crew avoid diagnosing the technical cause over the radio?