NTSB investigations: Cessna 172G
8 cases on aircraft the registry lists as Cessna 172G, where the first occurrence was “On ground/water collision with object”. 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
| 1986 | 1 |
|---|---|
| 1992 | 3 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 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 ('2072420')
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\" = 310))
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 ('2072420')
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" = 310))
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 NYC01LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Steubenville, OHThe pilot's failure to maintain directional control while landing with a crosswind. Factors in the accident were the pilot's lack of familiarity in the make and model airplane, and the crosswind conditions.NTSB CHI99LA201Accident · No injuriesLimited investigationFinal reportCessna 172G · Union, INThe pilot's failure to maintain clearance with the sign. Factors associated with the accident were the low ceilings and the sign which was contacted.NTSB MIA98LA234Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Leesburg, FLThe pilot's decision to leave the engine running with no one at the controls as he exited the aircraft to check for wheel chocks in place. This resulted in the aircraft moving uncontrolled and eventually colliding with a fence.NTSB CHI97LA298Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Chicago, ILthe pilot's selection of the wrong taxi route (service road) and not maintaining clearance between his airplane's wing and a bus.NTSB NYC92LA182Accident · No injuriesLimited investigationFinal reportCessna 172H · New Cumberland, WVThe pilot's improper takeoff procedures and his lack of understanding of airplane performance which resulted in an aborted takeoff with insufficient runway to stop and the subsequent collision with a fence. Factors related to the accident were; the pilot's…NTSB LAX92LA286Accident · No injuriesLimited investigationFinal reportCessna 172G · Tonopah, NVThe failure of the pilot to adequately identify and compensate for the existing tailwind conditions, and, his failure to initiate a go around when he became aware of being high with a fast ground speed.NTSB LAX92LA248Accident · No injuriesLimited investigationFinal reportCessna 172L · Safford, AZThe airplane colliding with animals which ran on to the runway during the pilot's takeoff roll. A factor in this accident was the pilot not being able to take remedial action and avoid the animals.NTSB ATL87LA056Accident · No injuriesLimited investigationFinal reportCessna 172G · New Philadelphi, OHThe acft right wing tip struck a hangar door while taxiing. The plt reported that he initially estimated the damage to be limited to the fiberglass wing tip fairing. He subsequently flew the aircraft back to his original departure point. Further examination…