WPR19FA079 · Cessna 414 A
Cessna 414 A · Accident: VFR encounter with IMC during initial climb
From Fullerton Municipal Airport (FUL) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- WPR19FA079
- 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
- 5 · all aircraft and ground
- Ground fatalities
- 4
- 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
- Instrument Meteorological Cond
Cessna 414 A
- Aircraft type
- Cessna 414
- 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
- N414RS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fullerton Municipal Airport (FUL), Fullerton, CATo Minden-Tahoe Airport (MEV), Minden, NV
- Aircraft age
- About 38 years (built 1981)
- 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
- Initial climb
- 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
- VFR encounter with IMC
- 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
- Aircraft › Aircraft structures
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot departed for a cross-country, personal flight with no flight plan filed. No evidence was found that the pilot received a preflight weather briefing; therefore, it could not be determined if he checked or received any weather information before or during the accident flight. Visual meteorological conditions existed at the departure airport; however, during the departure climb, the weather transitioned to instrument meteorological conditions (IMC) with precipitation, microburst, and rain showers over the accident area. During the takeoff clearance, the air traffic controller cautioned the pilot about deteriorating weather conditions about 4 miles east of the airport. Radar data showed that, about 5 1/2 minutes after takeoff, the airplane had climbed to about 7,800 ft above ground level before it started a rapid descending right turn and subsequently impacted the ground about 9.6 miles east of the departure airport. Recorded data from the airplane’s Appareo Stratus 2S (portable ADS-B receiver and attitude heading and reference system) revealed that, during the last 15 seconds of the flight, the airplane’s attitude changed erratically with the pitch angle fluctuating between 45° nose-down and 75°nose-up, and the bank angle fluctuating between 170° left and 150° right while descending from 5,500 to 500 ft above ground level, indicative of a loss of airplane control shortly after the airplane entered the clouds. Several witnesses located near the accident site reported seeing the airplane exit the clouds at a high descent rate, followed by airplane parts breaking off. One witness reported that he saw the airplane exit the overcast cloud layer with a nose down pitch of about 60°and remain in that attitude for about 4 to 5 seconds “before initiating a high-speed dive recovery,” at the bottom of which, the airplane began to roll right as the left horizontal stabilizer separated from the airplane, immediately followed by the remaining empennage. He added that the left wing then appeared to shear off near the left engine, followed by the wing igniting. An outdoor home security camera, located about 0.5 mile north-northwest of the accident location, captured the airplane exiting the clouds trailing black smoke and then igniting. Examination of the debris field, airplane component damage patterns, and the fracture surfaces of separated parts revealed that both wings and the one-piece horizontal stabilizer and elevators were separated from the empennage in flight due to overstress, which resulted from excessive air loads. Although the airplane was equipped with an autopilot, the erratic variations in heading and altitude during the last 15 seconds of the flight indicated that the pilot was likely hand-flying the airplane; therefore, he likely induced the excessive air loads while attempting to regain airplane control. Conditions conducive to the development of spatial orientation existed around the time of the in-flight breakup, including restricted visibility and the flight entering IMC. The flight track data was consistent with the known effects of spatial disorientation and a resultant loss of airplane control. Therefore, the pilot likely lost airplane control after inadvertently entering IMC due to spatial disorientation, which resulted in the exceedance of the airplane’s design stress limits and subsequent in-flight breakup. Contributing to accident was the pilot’s improper decision to conduct the flight under visual flight rules despite encountering IMC and continuing the flight when the conditions deteriorated. Toxicology testing on specimens from the pilot detected the presence of delta-9-tetrahydrocanninol (THC) in heart blood, which indicated that the pilot had used marijuana at some point before the flight. Although there is no direct relationship between postmortem blood levels and antemortem effects from THC, it does undergo postmortem redistribution. Therefore, the antemortem THC level was likely lower than detected postmortem level due to postmortem redistribution from use of marijuana days previously, and it is unlikely that the pilot’s use of marijuana contributed to his poor decision-making the day of the accident. The toxicology testing also detected 67 ng/mL of the sedating antihistamine diphenhydramine. Generally, diphenhydramine is expected to cause sedating effects between 25 to 1,120 ng/mL. However, diphenhydramine undergoes postmortem redistribution, and the postmortem heart blood level may increase by about three times. Therefore, the antemortem level of diphenhydramine was likely at or below the lowest level expected to cause significant effects, and thus it is unlikely that the pilot’s use of diphenhydramine contributed to the accident.
Probable cause
The pilot’s failure to maintain airplane control after entering instrument meteorological conditions (IMC) while climbing due to spatial disorientation, which resulted in the exceedance of the airplane’s design stress limits and subsequent in-flight break-up. Contributing to accident was the pilot's improper decision to conduct the flight under visual flight rules and to continue the flight when conditions deteriorated.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA079
- Event ID
- 20190204X12045
- Case number
- WPR19FA079
- 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, coordinates, cause areas. 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: a31cd830ee8d5e1c5e2634d19b68cc9b5ccaa50f3ccb97ac707ae5cad7c526b1; retrieved 2026-09-13T17:58:49.224Z.