NTSB investigations: Cessna 172H, 2003
14 cases on aircraft the registry lists as Cessna 172H. 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
| 1966 | 11 |
|---|---|
| 1967 | 59 |
| 1968 | 48 |
| 1969 | 32 |
| 1970 | 24 |
| 1971 | 28 |
| 1972 | 32 |
| 1973 | 22 |
| 1974 | 12 |
| 1975 | 16 |
| 1976 | 18 |
| 1977 | 18 |
| 1978 | 13 |
| 1979 | 15 |
| 1980 | 8 |
| 1981 | 6 |
| 1982 | 5 |
| 1983 | 7 |
| 1984 | 6 |
| 1985 | 7 |
| 1986 | 9 |
| 1987 | 6 |
| 1988 | 2 |
| 1989 | 9 |
| 1990 | 6 |
| 1991 | 5 |
| 1992 | 10 |
| 1993 | 5 |
| 1994 | 6 |
| 1995 | 9 |
| 1996 | 9 |
| 1997 | 3 |
| 1998 | 4 |
| 1999 | 4 |
| 2000 | 12 |
| 2002 | 6 |
| 2003 | 14 |
| 2004 | 2 |
| 2005 | 6 |
| 2006 | 1 |
| 2007 | 1 |
| 2008 | 4 |
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 3 |
| 2012 | 3 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 2 |
| 2018 | 3 |
| 2019 | 3 |
| 2020 | 5 |
| 2022 | 4 |
| 2023 | 6 |
| 2024 | 2 |
| 2025 | 4 |
| 2026 | 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 year(c.\"eventDate\") = 2003
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072424'))
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 year(c."eventDate") = 2003
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072424'))
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 ANC04LA012Accident · No injuriesLimited investigationFinal reportCessna 172 · Chugiak, AKThe pilot's selection of an unsuitable landing/takeoff area, and his failure to abort the takeoff, which resulted in an in-flight collision with a stump, and subsequent loss of control. Factors associated with the accident were snow-covered terrain and a…NTSB FTW04LA028Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Wichita Falls, TXThe loss of engine power due to an obstruction in the fuel line.NTSB FTW04LA008Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Manvel, TXThe pilot's failure to maintain airspeed during the attempted go-around resulting in an inadvertent stall. A contributing factor was the pilot's failure to maintain directional control during the crosswind landing.NTSB CHI03LA223Accident · No injuriesLimited investigationFinal reportCessna 172H · Red Wing, MNThe pilot's failure to follow the checklist resulting in fuel starvation and subsequent loss of engine power.NTSB CHI03LA216Accident · 1 fatalLimited investigationFinal reportCessna 172H · Isle, MNThe pilot's failure to maintain adequate airspeed which resulted in a stall. The trees, high density altitude, and the soft field were additional factors.NTSB SEA03LA136Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Sullivan Lake, WAThe pilot-in-command's downwind landing. A contributing factor was the tailwind condition.NTSB CHI03LA193Accident · No injuriesLimited investigationFinal reportCessna 172H · Plymouth, INThe collision with a deer during landing.NTSB NYC03LA127Accident · Minor injuriesLimited investigationFinal reportCessna 172H · East Vincent, PAThe pilot's inadequate in-flight planning/preparation which resulted in fuel exhaustion during cruise flight. The pilot's inadequate preflight preparation in which he failed to refuel the airplane is a contributing factor.NTSB SEA03LA097Accident · No injuriesLimited investigationFinal reportCessna 172H · Glasgow, MTA loss of engine power due to carburetor icing. Contributing factors were carburetor icing conditions and the muddy, wet terrain at the landing site.NTSB CHI03LA166Accident · No injuriesLimited investigationFinal reportCessna 172H · Council Bluffs, IAMisjudgment of the landing flare by the pilot in command resulting in a hard landing.NTSB ATL03LA092Accident · No injuriesLimited investigationFinal reportCessna 172H · Somerville, TNThe pilot's misjudged approach airspeed and distance which resulted in an undershoot of the runway and collision with terrain.NTSB CHI03LA105Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Holt, MOThe pilot's inadequate preflight planning/preparation, which resulted in a loss of engine power due to fuel exhaustion. A factor to the accident were the trees.NTSB CHI03LA082Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Callao, MOA loss of engine power due to the erosion of the number 2 piston, resulting in loss of compression on that cylinder. Contributing factors were the tailwind, the muddy runway condition, and the roadway and ditch.NTSB ATL03LA057Accident · No injuriesLimited investigationFinal reportCessna 172 · Camden, SCThe pilot's inadequate preflight planning which resulted in fuel exhaustion, subsequent loss of engine power and an in-flight collision with terrain.