Fatal NTSB investigations: Cessna 425
12 cases on aircraft the registry lists as Cessna 425. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1981 | 1 |
|---|---|
| 1983 | 1 |
| 1986 | 1 |
| 1988 | 1 |
| 1992 | 2 |
| 1996 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2005 | 2 |
| 2019 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076018', '207601A'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076018', '207601A'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB CEN19FA161Accident · 1 fatalClass 3 · FieldFinal reportCessna 425 · Butler, MOThe pilot’s loss of airplane control during a descent to a diversion airport with only the left engine operating. Contributing to the accident was a malfunction of the right engine throttle, the cause of which could not be determined.NTSB SEA06FA022Accident · 1 fatalField investigationFinal reportCessna 425 · Belgrade, MTThe pilot's failure to maintain airspeed during the approach which resulted in an inadvertent stall. Factors associated with the accident were dark night conditions, clouds, icing conditions, low visibility and snow.NTSB DEN05FA126Accident · 4 fatalField investigationFinal reportCessna 425 · Lone Tree, COThe pilot's failure to properly execute the published instrument approach procedure, which resulted in controlled flight into terrain.NTSB LAX02FA101Accident · 3 fatalField investigationFinal reportCessna 425 · San Jose, CAthe pilot's loss of control and resulting exceedence of the design stress limits of the aircraft, which led to an in-flight structural failure. The pilot's loss of control was due in part to the loss of primary airspeed reference resulting from pitot tube…NTSB SEA01FA017Accident · 2 fatalField investigationFinal reportCessna 425 · Idaho Falls, IDThe pilot-in-command's failure to maintain adequate airspeed with an asymmetric thrust condition, resulting in a loss of aircraft control. A factor was an asymmetric engine thrust condition, which was present for undetermined reasons.NTSB NYC97FA030Accident · 3 fatalField investigationFinal reportCessna 425 · Bohemia, NYthe pilot's early descent to decision height and his failure to perform the missed approach procedure. A factor was the failure of air traffic control to issue a safety advisory.NTSB MIA92FA085Accident · 1 fatalField investigationFinal reportCessna 425 · Lakeland, FLLoss of control in flight by the pilot for undetermined reasons.NTSB LAX92FA090Accident · 7 fatalField investigationFinal reportCessna 425 · Las Vegas, NVThe pilot's failure to maintain aircraft control due to spatial disorientation. Factors in this accident were: 1) the pilot's failure to obtain a preflight weather briefing and to properly evaluate the existing weather conditions prior to flight, and 2)…NTSB MIA88FA105Accident · 1 fatalField investigationFinal reportCessna 425 · Sanford, FLThe flt was cleared for a night ILS apch & advised that twr at dest had closed. Twr had rptd at closing that fog was forming & the flt was advised of the fog. The acft was located on a remote part of the arpt the next morning. The ELT had activated but the…NTSB DEN86MA061Accident · 5 fatalMajor investigationFinal reportCessna 425 · Granby, CODrg arrival, the plt advised ARTCC that the destination arpt appeared to be covered with fog. She then canceled her IFR flt plan. According to ground witnesses, the acft made several passes over the arpt. Witnesses also rprtd that the horizontal visibility…NTSB NYC84FA052Accident · 1 fatalField investigationFinal reportCessna 425 · Newburgh, NYDuring arrival, there were indefinite delays at white plains, NY, so the plt diverted to Newburgh, NY. He was vectored for an ILS rwy 9 apch. While en route, the plt requested & was given the ILS freq, mins for the apch, the arpt elevation(491 ft MSL), the…NTSB ATL82FA018Accident · 1 fatalClosedCessna 425 · Natchez, MS