FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR14FA182 · Boeing E75

4 May 2014 · Fairfield, CA, United States

Boeing E75 · Accident: low altitude operation/event while maneuvering

From Travis Air Force Base (SUU) to Travis Air Force Base (SUU)

Report a problem

Event

NTSB case
WPR14FA182
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing E75

Aircraft type
Boeing E75
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N68828
Operator
Unknown
Onboard fatalities
Unknown
Route
From Travis Air Force Base (SUU), Fairfield, CATo Travis Air Force Base (SUU), Fairfield, CA
Aircraft age
About 70 years (built 1944)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering · low-altitude flying
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Low altitude operation/event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Physical
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The highly experienced air show pilot was attempting to cut, with the vertical stabilizer of his biplane, a ribbon that was suspended about 20 feet above and across the runway. He was performing the maneuver on the third day of an open house at a United States Air Force (USAF) base and had successfully accomplished the maneuver on the two previous days, as well as at many previous air shows. After the pilot rolled the airplane inverted for the pass, witnesses observed it descend smoothly to the runway and slide to a stop. As the airplane came to a stop, a fire erupted, and the airplane was completely engulfed in flames within about 90 seconds of the fire's start. The first fire suppression vehicle did not reach the airplane until more than 4 minutes after the fire began, and the fire was extinguished soon thereafter.

The investigation did not identify any preimpact mechanical deficiencies or failures of the airplane or any adverse weather conditions that contributed to the abnormal runway contact. Toxicology analysis detected therapeutic amounts of diphenhydramine, an over-the-counter sedating antihistamine, in the pilot's blood, which likely impaired his ability to safely complete the maneuver and resulted in the abnormal runway contact.

The pilot was found lying on the upper panel of the cockpit canopy, and the canopy was found unlatched but in its closed position, indicating that when the airplane came to a stop, the pilot was likely conscious and attempted to exit the airplane; however, he was unsuccessful. The investigation was unable to determine when the pilot released his harness restraint system. If he released his harness before attempting to open the canopy, he would have fallen onto the canopy, which would have significantly increased the difficulty of opening the canopy. Even if the pilot did not release his harness before attempting to open the canopy, airframe damage and the canopy opening geometry would have prevented the full opening of the canopy, limiting the pilot's ability to exit. Further, the canopy was not equipped with any emergency egress provisions, such as quick-release hinge pins. Finally, the pilot's lack of a helmet or any fire protection garments increased his susceptibility to thermal injury and reduced his useful time to effect an exit, particularly given the rapidity of the fire's spread.

Although initially a survivable accident, the combination of pilot egress difficulties, the rapid fire growth, and the more than 4-minute firefighting response time altered the final outcome. The USAF primarily based its Airport Rescue and Fire Fighting (ARFF) plan for the air show on Department of Defense (DoD) and USAF guidance. In preparation for the open house, the USAF show director had attended an International Council of Air Shows (ICAS) trade show and briefing, where he was provided with ICAS guidance material that advocated the highest state of readiness for the ARFF teams. This entailed prepositioning the ARFF equipment, with the ARFF personnel fully suited in their protective gear, ready for immediate travel to and engagement in the rescue and firefighting efforts. For undetermined reasons, either that information was not communicated to the show organizers and ARFF planners or the responsible personnel and departments elected to disregard it. The organizers and planners made the decision to maintain the facility's ARFF readiness state at the DoD-defined "unannounced emergency" level during the air show, instead of the highest state of ARFF readiness advocated by ICAS. Based on the available evidence, if the ARFF teams had been at the highest state of ARFF readiness, the pilot's likelihood of survival would have been significantly increased.

The hazards imposed by low-level inverted flight included inadvertent ground contact, impact damage, and fire. The pilot had multiple strategies available to manage or mitigate the hazards' attendant risks. These included ensuring that he was in appropriate physiological and psychological condition to operate safely, wearing appropriate protective clothing, and ensuring an appropriate level of airplane crashworthiness including occupant escape provisions. The availability of ARFF services represented the final element of the risk management process, necessary only if all the other strategies failed or were otherwise ineffective. In this accident, the pilot either intentionally or unknowingly weakened, defeated, or did not implement several risk mitigation strategies: he was likely impaired by medication, he did not wear any protective clothing, and his airplane was not well-equipped from an occupant-escape perspective. The combination of these factors then resulted in the pilot being fully dependent on the timely arrival of ARFF personnel and equipment for his survival. The failure of the ARFF personnel and equipment to be at their highest level of readiness and to arrive in a timely manner was not the first, but rather the last, failed element of the overall risk-management scheme.

Probable cause

The pilot's failure to maintain clearance from the runway during a low-level aerobatic maneuver due to his impairment by an over-the-counter antihistamine. Contributing to the severity of the pilot's injuries were the pilot's lack of fire protective clothing, his inability to egress the cockpit, the rapid spread of the fire, and the decision of the air show's organizers not to have the airport rescue and firefighting services at their highest level of readiness, which delayed arrival of fire suppression equipment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14FA182
Event ID
20140504X90153
Case number
WPR14FA182
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 0a7e8a149028a23ba737f249307b9b86f1694822dd3a529637c3f425b0b0ff2f; retrieved 2026-09-14T16:14:14.545Z.