NTSB investigations: Cessna 172S
7 cases on aircraft the registry lists as Cessna 172S, where the first occurrence was “Overrun”. 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
| 2000 | 1 |
|---|---|
| 2002 | 2 |
| 2004 | 1 |
| 2006 | 3 |
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\" = 340))
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" = 340))
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 NYC06CA159Accident · No injuriesData collectionFinal reportCessna 172S · White Plains, NYThe pilot's misjudged speed/distance which resulted in an overrun.NTSB SEA06CA081Accident · No injuriesData collectionFinal reportCessna 172 S · Malad City, IDThe private pilot's improper touchdown point during landing and the certified flight instructors delayed remedial action. Ditches and fences were factors in the accident.NTSB NYC06CA077Accident · No injuriesData collectionFinal reportCessna 172S · Atlantic City, NJThe pilot's failure to obtain a proper touchdown point, which resulted in an overrun of the runway.NTSB LAX04CA288Accident · No injuriesData collectionFinal reportCessna 172S · Chandler, AZthe student pilot's failure to abort the takeoff. A contributing factor was the pilot's failure to maintain directional control.NTSB MIA02LA112Accident · No injuriesLimited investigationFinal reportCessna 172S · Kill Devil Hill, NCthe pilot's failure to maintain control of the airplane after an attempted aborted landing, and while braking during the landing roll, which resulted in the airplane departing the end of the runway and impacting with a ditch.NTSB LAX02LA092Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Santa Paula, CAThe pilot's selection of the wrong landing runway due to his failure to correctly interpret wind indicators, which resulted in his landing with a tailwind.NTSB NYC00LA243Accident · No injuriesLimited investigationFinal reportCessna 172 · Dunkirk, NYThe pilot's improper recovery from a bounced landing.