Downwind Saturation: Traffic, Tablet Failure and a Chatty Passenger
You are flying a VFR cross-country into a controlled aerodrome and have been cleared to join downwind for runway 27. You are number two behind a slower aircraft. On downwind at 1500 ft, your tablet GPS suddenly shuts down because its battery is flat. The terminal chart is under your thigh. ATC calls traffic at your two o'clock. At the same time your passenger asks about a whistling door seal, and you notice you are 200 ft high and 15 kt fast. You feel your jaw tighten and your scan is jumping between the tablet, the chart, the traffic and the passenger. The runway is in sight and the approach path looks manageable. You have 45 minutes of fuel reserves and the weather is fine.
1. Explain what is happening in workload terms and identify the highest-priority task.
Read the worked answer
This is task saturation with attention tunnelling. Several demands arrive at once: a navigation failure, an ATC traffic call, a passenger question, and degraded energy management. The pilot's jaw tightening is a stress cue, and the jumping scan shows attention is being pulled between sources rather than allocated deliberately. In this state, the risk is not that any one task is difficult, but that the pilot loses the attitude, airspeed or separation while trying to solve all of them simultaneously.
The highest-priority task is to aviate: maintain control of attitude, airspeed and flight path, and manage energy. Everything else is secondary. The tablet failure is not an emergency if the aircraft is under control, and the passenger question can wait. ATC's traffic call requires a response, but a brief acknowledgement or standby is enough until the aircraft is stabilised. The reasoning is simple: an unstable approach or a loss of separation can kill; a flat tablet cannot.
2. Propose a sequence of actions and decide whether to continue the approach.
Read the worked answer
A workable sequence is:
- Stabilise: lower the nose or reduce power as required, trim, and set the aircraft to a known downwind attitude and speed. Confirm the altitude and position visually and by reference to the runway.
- Communicate briefly: acknowledge ATC with a short call, such as traffic in sight or standby, and ask for a delay if workload is high. Do not attempt a long explanation.
- Manage the passenger: tell them clearly that you need quiet for a few minutes and that the door seal is not an immediate problem.
- Restore navigation: retrieve the chart when the aircraft is stable, or use known visual references and the runway. The tablet is not essential.
- Decide on the approach: if the aircraft is stabilised by the appropriate gate, continue; if not, go around. A go-around is low-cost and is the correct choice when high, fast or distracted.
The key reasoning is that continuing is acceptable only if the aircraft is stable and the pilot's attention is back on the flight path. The fact that the approach path looks manageable is not enough; the pilot must also be managing it.
3. What preflight and in-flight strategies would reduce the chance of this happening again?
Read the worked answer
Preflight strategies include charging the tablet and carrying a backup power source, keeping the paper chart accessible rather than under the thigh, and briefing the passenger on sterile cockpit periods during departure, approach and landing. The pilot should also brief the expected approach, radio frequencies and likely traffic before joining the circuit.
In-flight strategies include:
- Using a deliberate prioritisation rule: aviate, navigate, communicate, then administer passenger needs.
- Verbalising energy targets and using callouts for speed and altitude.
- Using the autopilot if available to reduce workload, while still monitoring it.
- Asking ATC for delay or vectors when workload is high rather than trying to absorb everything at once.
- Treating a go-around as a normal, pre-briefed option rather than a failure.
The broader lesson is that distraction is not caused by a single event but by the combination of events at a high-workload phase. Good preflight preparation and a simple prioritisation rule reduce the chance that a minor equipment failure becomes an unstable approach.