NTSB investigations: Cessna 172F
6 cases on aircraft the registry lists as Cessna 172F, 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
| 1985 | 1 |
|---|---|
| 1986 | 1 |
| 1988 | 2 |
| 1989 | 1 |
| 1998 | 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 ('2072414')
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 ('2072414')
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 MIA98LA233Accident · No injuriesLimited investigationFinal reportCessna 172F · Spring Hill, FLThe pilot's misjudgment of distance and his delay in initiating a go around. Contributing was the pilot's improper landing flare.NTSB FTW89LA060Accident · No injuriesLimited investigationFinal reportCessna 172 · Jacksboro, TXFailure of the pilot to go around, when she did not attain the proper touchdown point (landed long) and had excessive airspeed to stop on the runway. A factor related to the accident was the unfavorable wind condition (sudden wind shift).NTSB ATL88LA182Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Shellman, GAThe plt was making a personal flt to a pvt uncharted airstrip on a coastal island. Approaching his destination, the plt cancelled his VFR flt plan with fss. The plt stated that he approached the soft 2500 foot strip high and ballooned at touchdown. He landed…NTSB CHI88LA065Accident · No injuriesLimited investigationFinal reportCessna 172F · Brighton, MINTSB MKC86LA090Accident · No injuriesLimited investigationFinal reportCessna 172D · Garden Grove, IAThe plt stated that he was attempting a no-flap takeoff from his pvt strip when the wheels hit a wet spot. He said that the acft slowed down but he extended flaps and continued the takeoff. When he saw that he was running out of rwy, he aborted the takeoff…NTSB CHI86LA003Accident · No injuriesLimited investigationFinal reportCessna 172F · Canton, OHThe acft overran the rwy and collided with wires and a pole during landing. The student plt stated that he was too fast and landed long during the calm wind landing. He also stated he should have used more flaps.