WPR13FA037 · Cessna 421C
Cessna 421C · Accident en route
From Salinas Municipal Airport (KSNS) to Eppley Airfield (KOMA)
Event
- NTSB case
- WPR13FA037
- 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
- 2 · 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
Cessna 421C
- Aircraft type
- Cessna 421
- 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
- N700EM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salinas Municipal Airport (KSNS), Salinas, CATo Eppley Airfield (KOMA), Omaha, NE
- Aircraft age
- About 32 years (built 1980)
- 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 · cruise
- 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
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft structures
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot departed about 90 minutes after sunset in the high-performance multiengine airplane on the cross-country flight. The climb and level off at cruise altitude were uneventful and, based on the radar data, appeared to have been accomplished with the use of the autopilot. The cruise altitude of 27,000 feet was the highest the airplane had been flown in recent history, and the highest altitude it had been operated at with the pilot flying. The pilot made a routine radio exchange with air traffic control personnel shortly after levelling for cruise. Five minutes later, the airplane, with no further radio transmissions, rolled to the right and rapidly descended 10,000 feet, where it subsequently broke apart.
Both wings, along with the horizontal stabilizer and elevators, separated during the breakup sequence. Analysis of their fracture surfaces, along with the debris field distribution and radar data, revealed that the breakup sequence was most likely inadvertently induced by the pilot, as he attempted to recover control of the airplane during the dive.
The airplane sustained extensive thermal damage after ground impact, and examination of the engine components, surviving primary airframe components, the cabin heater, and the autopilot system remnants did not reveal any mechanical malfunctions or failures that would have precluded normal operation. There was no evidence of bird strike, inflight fire, or that the engine fire extinguisher system had been activated.
The airplane was flying toward an uninhabited mountain range and a largely unpopulated desert area at the time of the upset. The moon had set, and the pilot would have had limited reliable external visual cues should the airplane have experienced a failure of either the flight instruments or autopilot. The pilot was instrument rated, however the majority of his flight experience was garnered in aircraft equipped with modern "glass cockpit" avionics, as opposed to the traditional flight instruments installed in the accident airplane (which he had recently purchased).
The airplane was equipped with a dual vacuum pump system, which drove the primary flight instruments and, in turn, the autopilot. One of the vacuum pumps had failed on the previous flight, and the pilot was unable to get it repaired in time for the accident flight. The dual nature of the vacuum system allowed for flight with a single failed pump, however failure of the remaining pump or associated vacuum system components would have left the pilot to hand fly the airplane, using backup flight instruments, at an altitude perilously close to the limit of the airplane's flight envelope (the maximum altitude was 30,200 feet). Examination revealed that the second pump was most likely operational; however, fire damage precluded an accurate assessment of the operability of the remaining vacuum system components. Although operation of the airplane did not require adherence to a minimum equipment list, the airplane's FAA Master Minimum Equipment List stated that one of the vacuum pumps can be inoperative, provided the airplane is operated under VFR and not operated at night. Given the pilot's overwhelming experience with "glass cockpit" instruments, as opposed to the traditional type in the accident airplane, along with the failure of one of the vacuum pumps, he should have reconsidered making the flight, particularly during night conditions.
The airplane had experienced multiple anomalies with the autopilot and vacuum system prior to the accident flight. Maintenance records indicated that these discrepancies had been resolved; however, damage to the airplane precluded a substantive confirmation of their operation. Additionally, an oversight by an avionics repair facility 1 week before the accident resulted in the airplane's pitot/static system being inadvertently tested and certified to 20,000 feet, rather than the airplane's service ceiling of 30,200 feet. The relevance of this finding, if any, could not be determined.
The airplane was equipped with a supplemental oxygen system; however, maintenance records indicated that the pilot's mask, while operational, had degraded. Additionally, the mask had been relocated to a position behind the pilot's seat, which would have been hard to reach in the event of a rapid decompression. Ultimately, the NTSB was unable to determine the cause of the rapid descent because of the postcrash damage to the airplane systems and components.
Probable cause
The pilot's failure to regain airplane control following a sudden rapid descent during cruise, which resulted in an in-flight breakup. Contributing to the accident was the pilot's decision to make the flight with a failed vacuum pump, particularly at high altitude in night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13FA037
- Event ID
- 20121111X04124
- Case number
- WPR13FA037
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2012-11-11.
- API snapshot SHA-256: 77722be1a5173c7fb3a17302de0eb485df18cb2fefde54dc454c7206c7748927; retrieved 2026-09-14T15:47:59.089Z.