NTSB investigations: Cessna 172P, 1996
24 cases on aircraft the registry lists as Cessna 172P. 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
| 1969 | 1 |
|---|---|
| 1973 | 1 |
| 1980 | 2 |
| 1981 | 9 |
| 1982 | 30 |
| 1983 | 34 |
| 1984 | 36 |
| 1985 | 32 |
| 1986 | 24 |
| 1987 | 42 |
| 1988 | 39 |
| 1989 | 27 |
| 1990 | 28 |
| 1991 | 39 |
| 1992 | 36 |
| 1993 | 26 |
| 1994 | 22 |
| 1995 | 19 |
| 1996 | 24 |
| 1997 | 25 |
| 1998 | 19 |
| 1999 | 24 |
| 2000 | 21 |
| 2001 | 16 |
| 2002 | 16 |
| 2003 | 25 |
| 2004 | 18 |
| 2005 | 17 |
| 2006 | 9 |
| 2007 | 10 |
| 2008 | 13 |
| 2009 | 9 |
| 2010 | 16 |
| 2011 | 14 |
| 2012 | 12 |
| 2013 | 6 |
| 2014 | 6 |
| 2015 | 12 |
| 2016 | 9 |
| 2017 | 7 |
| 2018 | 10 |
| 2019 | 4 |
| 2020 | 5 |
| 2021 | 7 |
| 2022 | 10 |
| 2023 | 7 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 9 |
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\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072436'))
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") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072436'))
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 MIA97LA051Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Atlanta, GAfailure of the pilot to initiate an immediate climb (go-around or missed approach) after encountering fog, while on final approach to land. Darkness and fog at the end of the runway were related factors.NTSB LAX97LA053Accident · No injuriesLimited investigationFinal reportCessna 172P · Van Nuys, CAimproper flare by the pilot during the landing, and his improper recovery from a bounced landing, which resulted in a hard landing, dragged wing tip, and a collapsed main gear.NTSB CHI97LA026Accident · No injuriesLimited investigationFinal reportCessna 172P · Waukegan, ILthe pilot's improper recovery from a bounced landing. A factor was the pilot's misjudging the flare.NTSB MIA97FA013Accident · 3 fatalField investigationFinal reportCessna 172P · St. Croixthe pilot's failure to maintain airspeed.NTSB LAX97LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Kingsburg, CAthe student pilot's use of an excessively lean mixture, which led to engine overheating, detonation, subsequent failure of the number 2 piston, and a forced landing.NTSB CHI96LA326Accident · No injuriesLimited investigationFinal reportCessna 172 · Chicago, ILthe pilot's improper flare and improper recovery from a bounced landing. A factor relating to the accident was: the pilot's lack of experience (or lack of training) in recovery from bounced landings.NTSB IAD96FA132Accident · 3 fatalField investigationFinal reportCessna 172P · Summersville, WVThe pilot's improper flare, his delay in aborting a landing, and his failure to maintain adequate airspeed, which resulted in a bounced landing and a stall during climb out in an attempt to avoid collision with trees.NTSB NYC96LA149Accident · No injuriesLimited investigationFinal reportCessna 172P · Fairfield, NJthe pilot's improper aborted takeoff by extending full flaps which resulted in a porpoise. Subsequently, the airplane veered off the runway and the nose gear collapsed.NTSB FTW96LA300Accident · No injuriesLimited investigationFinal reportCessna 172P · Owasso, OKInadequate maintenance by maintenance personnel resulting in inoperative brake system during an aborted takeoff. A factor was the downhill runway condition.NTSB LAX96LA250Accident · No injuriesLimited investigationFinal reportCessna 172 · Camarillo, CAthe student pilot misjudged the landing flare resulting in a hard landing. A factor in the accident was high airspeed.NTSB ATL96LA086Accident · No injuriesLimited investigationFinal reportCessna 172 · Winston-Salem, NCThe pilot's improper use of the elevator in response to a bounced landing.NTSB NYC96LA093Accident · No injuriesLimited investigationFinal reportCessna 172P · Rutland, VTthe pilot's improper flare and recovery from a bounced landing. A contributing factor was his lack of recent flight experience.NTSB FTW96LA191Accident · No injuriesLimited investigationFinal reportCessna 172P · Denton, TXthe student pilot's delayed landing flare and his improper bounced landing recovery technique.NTSB FTW96LA179Accident · No injuriesLimited investigationFinal reportCessna 172P · Colorado Spgs, COthe student pilot'S failure to maintain control of the aircraft during a go-around.NTSB LAX96LA157Accident · No injuriesLimited investigationFinal reportCessna 172 · Sedona, AZthe pilot misjudged the flare.NTSB SEA96LA077Accident · No injuriesLimited investigationFinal reportCessna 172P · Friday Harbor, WAthe pilot's misjudgment of the aircraft's altitude above the runway and failure to flare for landing. Darkness (bright night) was a related factor.NTSB LAX96LA148Accident · No injuriesLimited investigationFinal reportCessna 172P · Fullerton, CAthe student pilot's inadequate compensation for the encounter with wake turbulence from a preceding small aircraft, and his improper bounced landing recovery technique.NTSB CHI96LA097Accident · No injuriesLimited investigationFinal reportCessna 172P · West Chicago, ILthe student pilot's misjudging the flare. A factor was the gusts.NTSB FTW96LA128Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Iowa, LAthe pilot's selection of the wrong runway for landing, his delay in initiating a go-around (aborted landing), and his failure to maintain clearance from the transmission lines. Factors relating to the accident were: the pilot's improper weather evaluation,…NTSB LAX96LA117Accident · No injuriesLimited investigationFinal reportCessna 172P · Raymond, CAThe pilot's failure to verify the quantity of fuel onboard the aircraft prior to departure, which resulted in fuel exhaustion.NTSB SEA96LA056Accident · No injuriesLimited investigationFinal reportCessna 172P · Cashmere, WAthe pilot's selection of the wrong runway for landing, by not observing a procedure to land uphill during calm wind conditions, and his subsequent failure to retract the flaps during landing roll, as recommended by the airplane's short-field landing…NTSB SEA96LA055Accident · No injuriesLimited investigationFinal reportCessna 172P · Salmon, IDfailure of the pilot to maintain directional control during the landing, which resulted in a ground swerve. A factor relating to the accident was: the rock pile to the left of the runway.NTSB ATL96LA038Accident · No injuriesLimited investigationFinal reportCessna 172 · Sanford, FLthe pilot-in-command's excessive taxi speed and his failure to maintain adequate clearance from obstacles.NTSB MIA96WA058Accident · 5 fatalForeign investigationCessna 172 · Nassau, Bahamas