WPR18FA091 · Piper PA34 200T
Piper PA34 200T · Accident: aircraft structural failure en route
From Meadows Field (BFL) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- WPR18FA091
- 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
Piper PA34 200T
- Aircraft type
- Piper PA34
- 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
- N14GQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Meadows Field (BFL), Bakersfield, CATo Minden-Tahoe Airport (MEV), Minden, NV
- Aircraft age
- About 40 years (built 1978)
- 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
- En route · descent
- 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
- Aircraft structural failure
- 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 › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The instrument-rated airline transport pilot was maneuvering the airplane from about 14,500 ft mean sea level (msl) while descending to the destination airport. Throughout the flight, the pilot was communicating with his son via text messaging to ask about the weather conditions at the destination airport, near where his son was located. The pilot's son described a broken cloud layer and advised the pilot that, if the airplane stayed above the clouds, he could then "drop in over the valley." About 2 minutes before the accident, the pilot told an air traffic controller, "I'm going to orbit here to the south…south over the airport I can see it, maneuvering through a hole," GPS data showed that, as the airplane continued to turn to the right, its airspeed increased rapidly, and the right turn tightened.
After completing a full revolution, the airplane exceeded its maximum structural cruising speed and never-exceed speed. The airplane's flight load increased throughout the turn, exceeding the airplane's maximum flight load factor. Immediately afterward, the flight data became unreliable; this point was likely when an in-flight breakup occurred. The location of the separated components in the debris field and the damage to the components were consistent with a tail-first in-flight breakup.
The airplane flight path before the in-flight breakup were consistent with a graveyard spiral caused by spatial disorientation. The pilot's statement to the controller regarding his intent to maneuver through a hole in the cloud layer indicated operation near instrument meteorological conditions (IMC). The airplane's excessive bank, pitch, and load factor coincided with the height of the reported cloud tops (13,000 ft), further indicating that the pilot was likely flying in and out of the clouds as he was attempting to spiral down to the airport. Given the reports of ceilings at 9,500 feet, the in-flight breakup likely occurred in IMC or within seconds of the airplane exiting IMC, precluding the pilot from taking recovery action upon reentering visual meteorological conditions.
The investigation could not determine whether the pilot was using supplemental oxygen while operating the airplane above 14,000 ft msl, as required by federal regulations. However, the communications between the controller and the pilot revealed that the pilot had no appreciable change in speech rate, coherence, or response time, indicating that the pilot was not experiencing hypoxia while in contact with air traffic control.
Although the pilot's coronary artery disease placed him at an increased risk for a sudden cardiac event, no evidence indicated that such an event occurred. Toxicology testing identified diphenhydramine, a sedating antihistamine, in the pilot's cavity blood and liver specimens.
Because experienced instrument-rated pilots should be able to identify spatial disorientation, the pilot's use of diphenhydramine likely contributed to this accident by degrading his judgment and slowing his responses.
Probable cause
The pilot's loss of airplane control due to spatial disorientation while maneuvering in instrument meteorological conditions. Contributing to the accident was the pilot's impairment from the use of a sedating antihistamine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18FA091
- Event ID
- 20180220X11813
- Case number
- WPR18FA091
- 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: 3f1ebd2fb565744a4e5e57bd3632c73f31bb9432b70cb6cf5435e38b87326dd8; retrieved 2026-09-15T06:33:53.436Z.