NTSB investigations: Cessna 172G
12 cases on aircraft the registry lists as Cessna 172G, where the first occurrence was “In flight 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
| 1983 | 1 |
|---|---|
| 1989 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1995 | 2 |
| 1996 | 2 |
| 1998 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2005 | 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\" = 220))
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" = 220))
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 IAD05CA117Accident · Minor injuriesData collectionFinal reportCessna C-172G · Eustis, METhe pilot's failure to maintain clearance from a bush during the aborted landing.NTSB CHI03LA303Accident · No injuriesLimited investigationFinal reportCessna 172G · Greenville, MIThe pilot's inadequate takeoff procedure with the use of 20 degrees of flaps. Contributing factors were the interrelated effects of high aircraft weight, the density altitude, and the relative humidity. An additional factor was the trees.NTSB NYC03LA025Accident · No injuriesLimited investigationFinal reportCessna 172G · Stow, MAThe pilot's failure to maintain adequate altitude/clearance. A factor in this accident was gusty wind conditions.NTSB IAD98LA096Accident · No injuriesLimited investigationFinal reportCessna 172G · Williamson, NYDirectional control not maintained by one of the pilot's on board the airplane.NTSB SEA96LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Kettle Falls, WAthe pilot's inadequate preflight planning. Factors relating to the accident were: high ambient temperatures; departing from a short, grass runway; and tall trees off the departure end of the airstrip.NTSB CHI96LA193Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Lowell, MIwas inadequate initial training of the pilot and inadequate flight test procedures by the FAA Designated Pilot Examiner when he reportedly had the pilot demonstrate 12 pilot operations from the FAA's practical flight test standards in 35 minutes during the…NTSB BFO95LA088Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Put-In-Bay, OHThe pilot's delay in aborting the landing after selecting the wrong runway. Factors relating to the accident were: garbled radio transmissions on the UNICOM frequency, and the resultant tailwind for landing.NTSB LAX95LA101Accident · 1 fatalLimited investigationFinal reportCessna 172G · Pope Valley, CAthe pilot's poor judgment to buzz the lake and his inadequate visual lookout.NTSB ATL93FA025Accident · 3 fatalField investigationFinal reportCessna 172 · Brownsboro, ALThe pilot failed to evaluate the wind conditions and took off with a tailwind which resulted in the collision with a tree on the departure end of the runway. Factors were dark night and tailwind.NTSB SEA92FA002Accident · 4 fatalField investigationFinal reportCessna 172G · Miltonfreewater, ORInadequate in-flight planning. Factors to the accident were: mountainous terrain, clearance not maintained, lack of total flight experience, and lack of familiarity with geographical area.NTSB SEA89LA078Accident · No injuriesLimited investigationFinal reportCessna 172 · Lynden, WAThe pilot delayed in aborting the landing and failed obtain or maintain sufficient airspeed to keep the aircraft from mushing after lift-off. Factors related to the accident were: obstructions near the approach end of the runway, failure of the pilot to…NTSB SEA83LA074Accident · No injuriesLimited investigationFinal reportCessna 172G · Near Homedale, IDThe flt originated before sunset, but the student plt practiced in the local area until the onset of darkness. While attempting to land on his private strip, he made 2 go-arounds. On the second go-around, the acft collided with an electrical wire, then flew…