Flight Eighteen-Thirty: Fatigue, a Missing Observer, and One More Orbit
It is the tenth flight of a 12-hour day: up at 0430, seven flights before noon, two more after a 40-minute lunch, and now 1830 local with about 25 minutes of usable daylight left. Your visual observer called in sick, so you are alone. The client is on site with his phone and wants "one more orbit" for a promotional video. Wind has been gusting since 1800. One battery reads 38% and has a slightly puffy case. You have a headache and notice you have re-read the same checklist line twice. Six workers are still on site and a delivery van keeps crossing the far edge of the area you would be flying over.
1. Identify the human factors at work and explain how they interact.
Read the worked answer
None of these is decisive alone; the risk is in the combination.
- Fatigue. Twelve hours, ten flights, a 40-minute break: attention, vigilance, and error-detection are all degraded. Re-reading the same checklist line twice is a concrete symptom of an attention lapse, not a charming quirk - you are the error-detection system, and it is currently unreliable.
- Stress and motivation. The client is standing next to you with a phone. That is social pressure plus commercial pressure, and it biases judgement toward the answer the client wants.
- Plan-continuation / sunk-cost bias. Ten flights and a long day create a strong pull to finish the job rather than write off the day. "One more orbit" is exactly the request this bias produces.
- Complacency from routine. Flight ten of a familiar job feels low-risk precisely because nothing has gone wrong yet.
- Loss of redundancy. A single pilot with no observer has no independent set of eyes - no second check on airspace, on the aircraft's position against the boundary, or on your own state. The observer is the crew-resource-management layer.
- Physical state. Headache suggests dehydration, missed food, or glare exposure; all degrade performance and all are easy to dismiss.
- Equipment flag. A puffy, warm battery is a thermal-runaway risk indicator, not a low-fuel warning. It is a remove-from-service item.
Interaction: fatigue reduces the chance you notice the gust, the van, or your own headache, while the client's request supplies the justification for not noticing.
2. What is the decision, and how do you communicate it? Include single-pilot mitigations.
Read the worked answer
Decision: stop flying for the day. Pack up.
Why it is not a close call:
- Wind gusting since 1800 with no observer means the drift-correction task falls entirely on you at the worst time of your attention cycle.
- Fading light plus 25 minutes of usable daylight is a hard boundary, not a soft one; the flight you would launch now finishes in the dark.
- A degraded battery is a fire risk on the aircraft and in your hand.
How to say it. Give the operational reason, not the personal one. "We're done for today: no observer, wind above our launch limit, and that pack is coming out of service. I'll fly it at 0900 tomorrow with a full crew." Then stop the conversation, put the aircraft down, and separate the pack. Do not negotiate the limit on site - a limit you can be talked out of is not a limit.
Single-pilot mitigations to have in place before this ever happens:
- A written, pre-agreed go/no-go card with hard numbers (maximum gust, minimum light, minimum crew, minimum battery state) that you check aloud before each flight.
- Geofence and altitude limits set in the app so a momentary lapse cannot become an airspace or traffic incident.
- A self-check (illness, medication, stress, alcohol, fatigue, eating) at the start of each flight, not just the first of the day.
- A rule that any flight with an unresolved equipment flag requires a second person's sign-off, or a 24-hour wait.
- A chief pilot or colleague you are expected to phone for an independent read when you are unsure - the single-pilot equivalent of an observer.
3. If the flight went ahead anyway, which failure chain worries you most, and how does the missing observer change the risk?
Read the worked answer
The chain: fatigue plus gusts plus a low-power pack → drift that is not detected quickly → the aircraft crosses the site boundary toward the delivery van's path and the six workers → either a collision or a lost-link/autoland in an area with people in it. Each link is ordinary; the chain is the accident.
Why the absent observer is the pivot. The observer's job is not to watch the drone - it is to watch the airspace and the ground while the pilot watches the aircraft and the screen, and to call drift, traffic, and people entering the operating area. Removing them:
- Removes the second opinion that would catch a misjudged boundary in the first two seconds.
- Forces the pilot to split attention between aircraft, screen, and surroundings - the classic route to loss of visual line of sight and to unnoticed drift.
- Removes the person who would say "the van's coming through again" before the pilot has to notice it.
If a flight is ever conducted solo, the compensating measures must be built in, not improvised: keep the aircraft closer and lower, fly over the surveyed area only, keep people and vehicle routes outside the geofence with margin, set a hard flight-time limit, and stop at the first gust above the card limit. That is a stricter operation than the one crewed - never a looser one. Tonight, none of it is available.