NTSB investigations: Cessna 172P, 1995
19 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\") = 1995
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") = 1995
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 FTW96FA058Accident · 3 fatalField investigationFinal reportCessna 172P · Hallett, OKThe flight instructor's intentional low altitude flight maneuver. Factors were the static wire and the bright night condition.NTSB LAX96LA043Accident · No injuriesLimited investigationFinal reportCessna 172 · Santa Ana, CAThe pilot's failure to maintain directional control which resulted in an inadvertent ground loop. The pilot's diverted attention while raising the flaps and pushing in the carburetor heat control was a factor in this accident.NTSB MIA95LA216Accident · No injuriesLimited investigationFinal reportCessna 172 · Atlantic Ocean (Atlantic Ocean)The failure of the oil lubrication system for undetermined reasons. Contributing to the accident was the lack of suitable terrain for a forced landing.NTSB ANC95LA149Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Soldotna, AKThe pilot's improper in-flight planning/decision, and his failure to maintain sufficient altitude to assure clearance from obstructions. The downdraft was a related factor.NTSB CHI95LA290Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Port Washington, WIthe failure of the #2 cylinder due to fatigue cracking. A factor was the soft terrain.NTSB LAX95LA296Accident · No injuriesLimited investigationFinal reportCessna 172P · Hesperia, CAThe failure of the connecting rod due to the rod bolt backing off, and the pilot's misjudging the distance and altitude.NTSB NYC95LA172Accident · No injuriesLimited investigationFinal reportCessna 172P · Teterboro, NJthe student pilot's improper flare which resulted in the airplane porpoising and the subsequent buckling of the firewall.NTSB LAX95LA267Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Reno, NVthe pilot's loss of directional control during a crosswind landing using full flaps and the lack of familiarity with the crosswind landing component chart for the aircraft.NTSB CHI95LA235Accident · No injuriesLimited investigationFinal reportCessna 172 · Springfield, MOimproper in-flight planning/decision by the pilot, and his continued flight into adverse weather conditions, which resulted in an uncontrolled altitude deviation and collision with terrain. Factors relating to the accident were: the adverse weather conditions.NTSB CHI95LA233Accident · No injuriesLimited investigationFinal reportCessna 172 · Motley, MNthe pilot's failure to maintain control of the airplane during a soft field takeoff.NTSB SEA95LA155Accident · No injuriesLimited investigationFinal reportCessna 172P · Vashon, WAThe loss of engine power due to connecting rod bolt overload failure. The rough, uneven terrain in the emergency landing area was a factor.NTSB MIA95LA165Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Lake Placid, FLTotal failure of the fuel vent system resulting in the total loss of engine power during cruise flight. Contributing to the accident was the inadequate inspection of the airplane during the last annual inspection for failure of the mechanic to identify that…NTSB ATL95LA113Accident · No injuriesLimited investigationFinal reportCessna 172 · Brownsville, TNThe pilot's improper in-flight decision to land on the wet, sod runway, and his failure to use all of the available runway for landing.NTSB MIA95LA122Accident · No injuriesLimited investigationFinal reportCessna 172P · Clearwater, FLThe pilot-in-command's improper remedial action after the aircraft porpoised during the landing flare and touchdown.NTSB FTW95LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Mountain Home, ARThe pilot's failure to compensate for the gusty crosswind. A factor was gusting crosswinds.NTSB NYC95FA080Accident · 1 fatalField investigationFinal reportCessna 172P · Naples, NYThe pilot's continued VFR flight into instrument meteorological conditions. Factors contributing to the accident were: the night conditions, fog, low ceiling, and hilly terrain.NTSB NYC95LA081Accident · No injuriesLimited investigationFinal reportCessna 172 · Mitchellville, MDThe pilot's failure to maintain directional control and the instructor's inadequate supervision. Related factors: high winds, and a crosswind.NTSB CHI95LA108Accident · No injuriesLimited investigationFinal reportCessna 172 · Alma, MIthe flight instructor's inadequate remedial action during the approach to landing/landing roll. Related factors are the flight instructor's inadequate supervision, the dual student's wrong runway selection, the tailwind, and the dual student's failure to…NTSB LAX95LA133Accident · No injuriesLimited investigationFinal reportCessna 172P · Redlands, CAthe pilot's use of an excessive approach speed and glidepath angle and his improper bounced landing recovery technique.