NTSB investigations: Cessna 172S
5 cases on aircraft the registry lists as Cessna 172S, 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
| 1999 | 1 |
|---|---|
| 2000 | 1 |
| 2001 | 1 |
| 2003 | 2 |
Where
Open the mapLatest 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 ('2072439', '2072442')
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 ('2072439', '2072442')
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 SEA03LA201Accident · No injuriesLimited investigationFinal reportCessna 172S · Anacortes, WAThe pilot attempting to taxi the airplane with a known system deficiency. Factors include worn wheel brakes and a drainage ditch.NTSB ATL03FA064Accident · 2 fatalField investigationFinal reportCessna 172S · Monroe, GAThe pilot’s exceedence of the design limits of the airplane, which resulted in the overload failure of the horizontal stabilizers, followed by the overload separation of the right wing and subsequent loss of control.NTSB ATL02LA013Accident · No injuriesLimited investigationFinal reportCessna 172S · Sarasota, FLThe operators failure to ensure adequate training had been provided to the student pilot in autopilot operations, and the student pilot's failure to comply/ follow written instructions (Federal Regulations/172 Skyhawk Information Manual) pertaining to the…NTSB CHI01IA047Incident · No injuriesIncident investigationFinal reportCessna 172S · St. Cloud, MNthe fatigue failure of the propeller blade during the initial takeoff climb. The failure was a result of a material defect, which occurred during the manufacturing process and the manufacturers failure to detect the defect.NTSB CHI99LA092Accident · No injuriesLimited investigationFinal reportCessna 172RG · Lawrenceville, ILthe fatigue fracture of the landing gear actuator.