NTSB investigations: Cessna 172G
10 cases on aircraft the registry lists as Cessna 172G, where the first occurrence was “In flight encounter with weather”. 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
| 1982 | 2 |
|---|---|
| 1983 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 2 |
| 1991 | 1 |
| 2002 | 1 |
| 2003 | 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\" = 240))
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" = 240))
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 NYC03LA112Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Ocean City, NJThe pilot's failure to maintain directional control during an aborted landing. A factor was a crosswind.NTSB FTW03LA030Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Fort Stockton, TXThe pilot's decision to conduct VFR flight into IMC and his failure to maintain terrain clearance. Contributing factors were the dark night, clouds, fog, and the lack of suitable terrain.NTSB NYC91FA115Accident · 2 fatalField investigationFinal reportCessna 172G · New Bedford, MAThe pilot's improper planning/decision and failure to maintain proper altitude after encountering adverse weather at low altitude. The adverse weather (fog) was a related factor.NTSB MKC88FA124Accident · 1 fatalField investigationFinal reportCessna 172G · Sarcoxie, MOWitnesses at the acdnt site characterized the wx as having a low ceiling with fog. They rprtd they saw the acft 'appear out of clouds' in a steep descent. The acft then began to 'pull up;' however, during recovery from the dive, the acft struck trees &…NTSB LAX88FA161Accident · 4 fatalField investigationFinal reportCessna 172G · Los Banos, CAFailure of the pilot to maintain control of his aircraft to avert a collision with the ground.NTSB ATL87LA165Accident · No injuriesLimited investigationFinal reportCessna 172G · Steubenville, OHPIC rpted he flew over airport and noted wind direction as 290-300 degrees on wind indicator. He entered downwind for rwy 31 at uncontrolled field. Normal approach flown with full flaps on final with left crosswind correction. About 30-40 feet above rwy, acft…NTSB FTW86LA038Accident · No injuriesLimited investigationFinal reportCessna 172G · Spring, TXThe pilot continued VFR flight into IFR weather conditions which he had encountered near his destination during the last few moments of his approximate four hour, night, cross-country flight. He then turned back to houston intercontinental airport to land. He…NTSB NYC83LA258Accident · No injuriesLimited investigationFinal reportCessna 172G · Woodford, VTAccording to the pilot weather was clear at time of departure with clouds at about 4000-4500 feet but clr above. He entered a break in the clouds and began following a road. As the weather began closing in from above and the road became curvy, the pilot had…NTSB DEN83FTE02Accident · 1 fatalFinal reportCessna 172G · Mack, COWhile on a flt from evanston, WY to glenwood, CO, the plt encountered "cloud to ground" conditins & diverted toward grand junction, CO. He stated that due to a nav problem, he radioed grand junction tower to verify his position. Grand junction had no radar &…NTSB ATL83FID01Accident · 1 fatalFinal reportCessna 172G · Boones Mill, VAThe pilot was trying to approach roanoke in weather that obscured the mountain tops. He crashed into a mountain slope at the 2900 foot level. He had contacted roanoke radio but radar contact had not been established. During his weather briefing VFR flight had…