NTSB investigations: Cessna 172N, 2006
23 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
| 1965 | 1 |
|---|---|
| 1966 | 2 |
| 1967 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 26 |
| 1978 | 62 |
| 1979 | 81 |
| 1980 | 107 |
| 1981 | 86 |
| 1982 | 91 |
| 1983 | 53 |
| 1984 | 55 |
| 1985 | 40 |
| 1986 | 44 |
| 1987 | 42 |
| 1988 | 47 |
| 1989 | 45 |
| 1990 | 46 |
| 1991 | 57 |
| 1992 | 40 |
| 1993 | 51 |
| 1994 | 43 |
| 1995 | 48 |
| 1996 | 37 |
| 1997 | 40 |
| 1998 | 37 |
| 1999 | 46 |
| 2000 | 35 |
| 2001 | 32 |
| 2002 | 43 |
| 2003 | 32 |
| 2004 | 38 |
| 2005 | 26 |
| 2006 | 23 |
| 2007 | 21 |
| 2008 | 21 |
| 2009 | 20 |
| 2010 | 23 |
| 2011 | 22 |
| 2012 | 14 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 10 |
| 2016 | 24 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 16 |
| 2020 | 25 |
| 2021 | 15 |
| 2022 | 16 |
| 2023 | 20 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 11 |
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\") = 2006
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 year(c."eventDate") = 2006
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 DEN07CA043Accident · No injuriesData collectionFinal reportCessna 172N · Cottonwood Fall, KSthe pilot's failure to maintain clearance from the fence. Contributing to the accident was the pilot's inability to properly identify the runway environment, and the improper in-flight decision to initiate a go-around.NTSB ATL07CA022Accident · No injuriesData collectionFinal reportCessna 172N · Reidsville, NCThe pilot's failure to maintain directional control of the airplane during landing roll, which resulted in an on ground collision with trees.NTSB DFW07CA028Accident · No injuriesData collectionFinal reportCessna 172N · Spring, TXLoss of directional control for undetermined reasons.NTSB NYC07CA014Accident · No injuriesData collectionFinal reportCessna 172N · Morgantown, WVThe student pilot's failure to maintain directional control and the flight instructor's improper planning and supervision of the student's solo cross country flight. A contributing factor was the wind gusts.NTSB CHI07CA006Accident · No injuriesData collectionFinal reportCessna 172N · Grand Rapids, MNThe student pilot's misjudged landing flare and improper recovery from the bounced landing which led to the failure of the nose landing gear. The overload failure of the nose landing gear was a factor.NTSB CHI07CA004Accident · No injuriesData collectionFinal reportCessna 172N · St Charles, MOThe pilot's failure to properly judge the landing flare and his inadequate recovery from the resulting bounced landing. A contributing factor was the inadvertent pilot induced oscillation (porpoise) after initial runway contact.NTSB MIA06CA134Accident · Minor injuriesData collectionFinal reportCessna 172N · Pensacola, FLThe student pilot's failure to raise the wing flaps for a go-around resulting in the airplane not climbing and an in-flight collision with trees.NTSB NYC06CA196Accident · No injuriesData collectionFinal reportCessna 172N · Windsor, NHThe pilot's delay in aborting the takeoff, which resulted in an overrun and subsequent collision with trees. A factor in the accident was the tailwind.NTSB ANC06LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Anchorage, AKThe possible loss of engine power during takeoff/initial climb for an unknown reason, which resulted in a forced landing in rough terrain and a nose over.NTSB CHI06CA204Accident · Minor injuriesData collectionFinal reportCessna 172N · Wadsworth, OHThe pilot used an improper aborted takeoff procedure in that she failed to reduce the engine power. Factors associated with the accident were the tailwind, the wrong runway selection, the pilot's lack of experience, the guard rail, and the embankment.NTSB DFW06FA187Accident · 2 fatalField investigationFinal reportCessna 172N · Petal, MSThe pilot's improper use of flaps, which resulted in an impact with trees during takeoff-initial climb.NTSB NYC06LA179Accident · 1 fatalLimited investigationFinal reportCessna 172N · Pompton Lakes, NJImproper maintenance of the throttle shaft, which resulted in a partial loss of engine power during cruise flight, and subsequent impact with trees during a forced landing.NTSB NYC06FA154Accident · 4 fatalField investigationFinal reportCessna 172N · Newry, METhe flight instructor's failure to maintain altitude/clearance while maneuvering, which resulted in an impact with trees.NTSB CHI06CA151Accident · No injuriesData collectionFinal reportCessna 172N · Athens, OHThe student pilot's inadequate compensation for the wind conditions. Factors associated with the accident were the gusty crosswind, and the ditch.NTSB NYC06LA124Accident · Minor injuriesLimited investigationFinal reportCessna C-172N · Vineyard Haven, MAThe pilot's improper preflight planning and improper fuel consumption calculations, which resulted in fuel exhaustion and a subsequent loss of engine power.NTSB MIA06CA101Accident · No injuriesData collectionFinal reportCessna 172N · Miami, FLThe improper flare by the pilot resulting in a hard landing and substantial damage to the airplane.NTSB SEA06CA098Accident · No injuriesData collectionFinal reportCessna 172N · Billings, MTThe pilot's failure to maintain clearance from a sign while taxiing to parking.NTSB MIA06CA088Accident · No injuriesData collectionFinal reportCessna 172N · Daytona Beach, FLThe pilot's improper landing flare/touchdown, which resulted in the airplane porpoising and incurring damage.NTSB LAX06CA125Accident · Minor injuriesData collectionFinal reportCessna 172N · Compton, CAcontrol interference by the student pilot during a go-around that resulted in an in-flight collision with power lines.NTSB CHI06LA084Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Muncie, INThe loss of engine power during the final approach to land for an undetermined reason.NTSB CHI06CA083Accident · No injuriesData collectionFinal reportCessna 172N · New Hudson, MIThe solo student pilot's failure to properly compensate for the crosswind, resulting in his failure to maintain directional control during landing. Factors were the crosswind and the snow bank.NTSB LAX06LA108Accident · No injuriesLimited investigationFinal reportCessna 172N · Sacramento, CAthe failure of the pilot of the other airplane to maintain an adequate clearance from obstacles while taxiing.NTSB SEA06LA049Accident · No injuriesLimited investigationFinal reportCessna 172N · Snohomish, WACarburetor heat was not used during the initial climb in probable serious carburetor icing conditions during cruise power. Carburetor icing conditions and wet terrain were factors.