NTSB investigations: Cessna 421C
10 cases on aircraft the registry lists as Cessna 421C, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1993 | 1 |
|---|---|
| 1994 | 2 |
| 1997 | 1 |
| 1999 | 1 |
| 2002 | 2 |
| 2003 | 1 |
| 2006 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076016', '2076017')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076016', '2076017')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 CHI07CA152Accident · No injuriesData collectionFinal reportCessna 421C · Kokomo, INThe pilot not obtaining proper alignment with the runway during the emergency landing after takeoff, which imparted an excessive side load on the landing gear. Factors contributing to the accident were the unstabilized approach and engine shutdown due to the…NTSB CHI06LA080Accident · No injuriesLimited investigationFinal reportCessna 421C · Indianapolis, INThe main landing gear malfunctioned and failed to extend during the landing approach for an undetermined reason, which resulted in a main gear up landing.NTSB LAX03LA106Accident · No injuriesLimited investigationFinal reportCessna 421C · Crescent City, CAThe separation of the upper and lower right main landing gear scissor links due to improper maintenance, which resulted in a ground loop, and the collapse of the right main landing gear during the landing roll.NTSB MIA02LA089Accident · No injuriesLimited investigationFinal reportCessna 421C · Tampa, FLthe fracture of the landing gear upper barrel due to fatigue cracking, caused by improper machining after the barrel was assembled during the manufacturing process, resulting in damage to the airplane.NTSB SEA02LA046Accident · No injuriesLimited investigationFinal reportCessna 421C · Hailey, IDWater contamination within the aircraft's landing gear hydraulic line(s) which froze and blocked the line(s) preventing extension of the right main gear. A factor was the below freezing environmental conditions which the aircraft was operating in prior to and…NTSB FTW99LA059Accident · Minor injuriesLimited investigationFinal reportCessna 421C · Shelbyville, TXThe total failure of the aircraft's electrical system. Factors were the thunderstorms, the dusk light condition, and the lack of suitable terrain for the precautionary landing.NTSB SEA97LA058Accident · No injuriesLimited investigationFinal reportCessna 421C · Cedar City, UTwater contamination in the hydraulic system, which froze in the (right) main gear hydraulic actuator, and restricted movement of the (right) main gear retraction and extension system.NTSB CHI94MA072Accident · 2 fatalMajor investigationFinal reportCessna 421C · Mccook, NEImproper in-flight planning/decision by the pilot, and the accumulation of airframe ice, which resulted in an inadvertent stall. Factors associated with the accident were: partial failure of both alternators, which resulted in a subsequent electrical system…NTSB MIA94FA057Accident · 3 fatalField investigationFinal reportCessna 421C · Titusville, FLFailure of the pilot-in-command to maintain VMC resulting in the inflight loss of control. Contributing to the accident was the fatigue failure of a section of pipe adjacent to a flange which connects to the turbocharger oil outlet of the left engine assembly.NTSB LAX93FA149Accident · 3 fatalField investigationFinal reportCessna 421C · Eagle Mountain, CAFailure of the left elevator for undetermined reason(s), which resulted in flutter and failure of the empennage, and subsequent uncontrolled collision with the terrain.