NTSB investigations: Cessna 172I
4 cases on aircraft the registry lists as Cessna 172I, 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
| 1987 | 1 |
|---|---|
| 1993 | 1 |
| 2000 | 1 |
| 2007 | 1 |
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 ('2072426')
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 ('2072426')
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 CHI07CA134Accident · Minor injuriesData collectionFinal reportCessna 172I · Shelby, OHThe pilot's failure to properly achieve the correct touch down point which resulted in a runway over run and subsequent nose over into a ditch. Other factors were the pilot's improper decision to land with a tailwind and the ditch.NTSB SEA00LA125Accident · No injuriesLimited investigationFinal reportCessna 172I · Sandy, ORThe pilot's failure to attain the proper touchdown point for landing, and his failure to go around from the improperly executed approach. Factors included the pilot's failure to attain the proper glidepath on the approach, a short landing runway, and…NTSB CHI94LA033Accident · Minor injuriesLimited investigationFinal reportCessna 172I · Moberly, MOthe failure of the pilot-in-command to use all of the available runway.NTSB ATL87LA206Accident · No injuriesLimited investigationFinal reportCessna 172I · Goodway, ALThe plt rprtd that he lndd long on a 2500 ft grass strip which was wet due to hvy dew. Drg the apch, he had an airspeed of 75 to 80 KTS with 30 deg of flaps. Subsequently, the acft slid off the departure end & struck a pecan tree. The recommended final apch…