NTSB investigations: Cessna 172N, IA
15 cases on aircraft the registry lists as Cessna 172N. 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
| 1978 | 1 |
|---|---|
| 1979 | 1 |
| 1981 | 1 |
| 1982 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2010 | 1 |
| 2019 | 1 |
| 2021 | 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.\"eventStateOrRegion\" = 'IA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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."eventStateOrRegion" = 'IA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434'))
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 CEN21LA433Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Council Bluffs, IAThe student pilot’s failure to maintain directional control during a touch and go landing.NTSB CEN20LA014Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Swea City, IAThe pilot's failure to replace the oil filler cap during his preflight inspection, which resulted in oil starvation and a subsequent total loss of engine power.NTSB CEN10CA178Accident · No injuriesData collectionFinal reportCessna 172N · Ankeny, IAA total loss of engine power due to fuel exhaustion as a result of the pilot's inadequate in-flight fuel monitoring.NTSB CHI02LA076Accident · No injuriesLimited investigationFinal reportCessna 172N · Ottumwa, IAthe student pilot failed to maintain directional control during takeoff. A contributing factor was the snowbank.NTSB CHI01LA303Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sheldon, IAthe in-flight planning/decision and proper touchdown point not attained by the pilot. Contributing factors were the ingested exhaust valve and lack of experience of the pilot.NTSB CHI99LA348Accident · No injuriesLimited investigationFinal reportCessna 172N · Des Moines, IAthe pilot's improper in-flight planning and decisions which led to fuel exhaustion. A factor relating to this accident was the telephone pole.NTSB CHI97LA214Accident · No injuriesLimited investigationFinal reportCessna 172 · Ottumwa, IAthe improper flare performed by the student and the inadequate recovery from the bounced landing. A factor related to the accident was the student lack of experience.NTSB CHI94LA322Accident · No injuriesLimited investigationFinal reportCessna 172N · Boone, IAthe failure of both pilots to adequately monitor radio communications during an exceptionally busy period. Factors related to the accident were the high vegetation and the failure of airport personnel to recognize and correct a hazardous situation.NTSB CHI93LA022Accident · No injuriesLimited investigationFinal reportCessna 172N · Ankeny, IAThe pilot's improper recovery for a bounced landing.NTSB MKC89LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Cresco, IAFailure of the pilot to maintain control of the airplane during the landing on a closed runway.NTSB MKC88FA058Accident · 4 fatalField investigationFinal reportCessna 172N · Oxford, IAWitnesses stated that the aircraft appeared to be in trouble immediatley after takeoff, as the wings were rapidly rocking while it was struggling to stay airborne. The aircraft turned sharply left, where it then barely cleared a row of trees. The airplane…NTSB MKC82DA103Accident · No injuriesFinal reportCessna 172N · Marion, IAThe pilot reported that he took off, stayed in the traffic pattern, and made a normal approach with one notch of flaps at about 75 mph. He stated that on final approach, the wind shifted from 350 to almost 180 degrees. He landed long and was unable to stop on…NTSB MKC82FA006Accident · 1 fatalClosedCessna 172N · Prairie City, IANTSB MKC79FCD18Accident · No injuriesClosedCessna 172 · Fort Dodge, IANTSB MKC78FCD52Accident · Serious injuriesClosedCessna 172N · Clinton, IA