Cessna 421C accident near Shaver Lake, California, November 11, 2012
On November 11, 2012 at about 3:20 am local time, a 1980 Cessna 421C, registered N700EM, was substantially damaged in an accident during enroute (cruise) near Shaver Lake, California (Salinas Muni airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 11, 2012 · about 3:20 am local time · cases in 2012
- Place
- Shaver Lake, California · Salinas Muni · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 421C, built 1980 · all 421Cs on the register
- Registration
- N700EM · no longer on the register · serial 421C1010
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during enroute (cruise) defining event
- Loss of control in flight during enroute (cruise)
- Attempted remediation/recovery during uncontrolled descent
- Aircraft structural failure during uncontrolled descent
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft structures › (general) › (general) › Capability exceeded other cases naming the airframe structure
- factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Aircraft › Aircraft systems › Vacuum system › (general) › Inoperative other cases naming the heating, ice protection and utility systems
- Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Response/compensation
- Aircraft › Aircraft systems › Indicating/recording systems › (general) › Incorrect service/maintenance other cases naming the instruments and avionics
- Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 637.7 hours in all; 102 in this make and model; 41 in the last 90 days; 14.3 in the last 30 days; 629.2 as pilot in command
- Last flight review: June 13, 2012
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 5,118 hours
- Last inspection: annual inspection, February 8, 2012; 135 hours since
- Maximum gross weight: 7,450 lb
- Seats: 8
- Landing gear: retractable
- Engine 1: Cont Motor GTSIO-520-N (piston); 274 hours total
- Engine 2: Cont Motor GTSIO-520-N (piston); 883 hours total
- Fire on the ground
The flight
- Departed from: KSNS Salinas CA at 2:37 am
- Destination: KOMA Omaha NE
- Flight plan: IFR
- Runway 26, 6,004 ft by 150 ft
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 43°F (6°C), dew point 36°F (2°C)
- Altimeter: 31.17 inHg
- Observation at 2:53 am from KMAE, 42 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
38 documents, released by the NTSB on June 2, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N700EM: not on the register today · the record of its deregistration
- Cessna 421 Golden Eagle 768 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Cont Motor GTSIO-520-N 10 aircraft carry this series today · as the NTSB recorded it
- Engine: Cont Motor GTSIO-520-N 10 aircraft carry this series today · as the NTSB recorded it
- Salinas Municipal · nearest airport
- Salinas Municipal · departed from
- Eppley Airfield · bound for
- Accidents and incidents in California 9,080 since 1982 · 1,093 in the last ten years
- California 28,500 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR13FA037.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
