U-2 Spy Plane Pilot Battles Hypoxiat 70000 feet “i’m not feeling very well”

Advertisement

At extreme altitude, a problem with the pilot's oxygen supply is an immediate flight-control problem as well as a medical emergency. That was the situation described in the radio traffic involving U.S. Air Force U-2 aircraft Rook 07 during a mission from RAF Alconbury.

Timeline
Mission phase —
Rook 07 was conducting a U-2 mission from RAF Alconbury.
1.
High-altitude emergency —
The pilot reported feeling unwell and suspected an oxygen problem.
2.
Emergency oxygen —
The pilot activated the U-2 emergency oxygen supply known as the “green apple.”
3.
Coordination —
The pilot contacted Scully Ops through London Military while the aircraft's altitude and recovery plan were coordinated.
4.
Recovery —
The aircraft descended in a planned spiral and returned toward its base.
5.
After landing —
The pilot provided a report of the emergency.
6.

The pilot reported symptoms consistent with hypoxia and suspected a problem with the oxygen supply. He activated the emergency oxygen system known as the “green apple,” a backup source intended to provide oxygen when the primary system is unavailable or compromised. The flight was operating at altitudes approaching 70,000 feet, where loss of adequate oxygen can rapidly impair judgment, coordination and consciousness.

The pilot's condition was communicated through London Military and later through Scully Ops. Rather than treating the radio exchange as an isolated cockpit problem, the controllers had to manage the aircraft while its pilot was reporting that he was not feeling well. The available account says the aircraft was brought to a safer altitude and transferred to Eastern Radar as the situation developed.

Once the pilot reported improvement, the recovery became a controlled descent rather than an immediate return from the original altitude. The source describes a spiral descent, with the pilot planning the descent profile before returning toward base. That sequence matters because the U-2's operating environment is fundamentally different from that of an ordinary general-aviation aircraft: altitude, oxygen availability and descent planning all have unusually large consequences.

The available source material does not identify a final technical determination that the oxygen system itself had failed. It records the pilot's suspicion of contaminated oxygen and his use of the emergency supply. That distinction should be preserved. A symptom report and emergency action establish what the pilot experienced and did; they do not by themselves establish the mechanical origin of the oxygen problem.

The event ended without an accident. The pilot was able to coordinate the descent, return to Scully Ops and provide a report. The radio traffic shows a situation in which the controller's role was to support a pilot whose physiological condition was becoming a factor in the flight, while the pilot remained responsible for flying the aircraft.

The U-2's operating environment makes the radio exchange especially consequential. The aircraft's mission profile places the pilot in a pressure-suit and life-support environment in which physiological problems can rapidly become aviation problems. The pilot therefore had to communicate his condition while simultaneously maintaining control and managing the aircraft's descent. The use of the emergency oxygen system was an immediate response to the perceived loss or degradation of the normal oxygen supply, but the documented record does not establish that a confirmed oxygen-system failure was the final diagnosis.

A useful distinction is between the symptoms reported over the radio and a later medical or engineering determination. The pilot said he was not feeling well and suspected an oxygen-related problem. That is evidence of what the crew experienced at the time. It is not, on its own, evidence that a specific component failed. Keeping that distinction intact prevents the radio recording from being turned into a mechanical finding that the available record does not support.

The recovery also depended on reducing workload. A high-altitude emergency involving a U-2 cannot be handled like a routine diversion: the pilot must control the aircraft, manage oxygen and pressure considerations, descend through a very different atmospheric environment and coordinate with controllers while physiological capacity may be deteriorating. The successful outcome therefore came from the combination of the pilot's actions and ATC coordination, not from a single dramatic radio instruction.

Accident Facts

Category
Emergency, Military
Reconstruction
4:44

Sources

Video source: https://www.youtube.com/watch?v=oXjN2sgYG8Y

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident