NTSB investigations: Cessna 172P, 1997
25 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\") = 1997
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") = 1997
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 SEA98LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Kenmore, WAthe pilot's inadequately planned approach and failure to maintain directional control. The pilot's lack of total experience in kind of aircraft and haze were factors.NTSB NYC98LA040Accident · No injuriesLimited investigationFinal reportCessna 172P · Mitchellville, MDThe pilot's improper recovery from a bounced landing.NTSB LAX98LA030Accident · No injuriesLimited investigationFinal reportCessna 172P · San Diego, CAThe student pilot's failure to maintain adequate clearance from a hangar while taxiing.NTSB FTW98LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · Tooele, UTfailure of the pilot to maintain directional control of the airplane, while landing. Factors related to the accident were: the pilot's improper flare for landing, his delay in attempting to go around (abort the landing), and the encounter with a runway marker…NTSB NYC98LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Pittsfield, MAThe pilot's poor in-flight decision to continue VFR flight in IFR conditions. Factor's in this accident were the pilot's inadequate pre-flight planning, and fog.NTSB MIA98TA011Accident · Minor injuriesFinal reportCessna 172P · Wiggins, MSLoss of engine power for undetermined reasons resulting in a forced landing on unsuitable terrain and the aircraft nosing over during landing roll.NTSB CHI97LA303Accident · No injuriesLimited investigationFinal reportCessna 172P · Yankton, SDThe pilot's failure to maintain control of the aircraft. A factor contributing to the accident was the wind gusts.NTSB IAD97FA122Accident · 1 fatalField investigationFinal reportCessna 172P · Airville, PAThe student pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent collision with terrain.NTSB ATL97LA117Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Rockhill, SCThe pilot's failure to plan and have adequate fuel for the flight.NTSB FTW97LA289Accident · No injuriesLimited investigationFinal reportCessna 172P · La Porte, TXfailure of the pilot to maintain directional control of the airplane during the takeoff roll, as he attempted to close and lock the left cabin window. Factors relating to the accident were: the pilot's failure to follow the before takeoff checklist (secure…NTSB CHI97FA218Accident · 7 fatalField investigationFinal reportCessna 172P · Chicago, ILthe pilots not maintaining visual separation between their airplanes. A factor in this accident was the pilot of the southbound airplane not reporting her position abeam the airport as directed by the ATC controller.NTSB NYC97LA136Accident · No injuriesLimited investigationFinal reportCessna 172P · Wildwood, NJThe pilot's inadequate use of carburetor heat, which resulted in carburetor icing.NTSB NYC97LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Tioga, PAThe pilot's improper inflight decision to land downwind with an inoperative airspeed indicator, and his improper landing flare.NTSB FTW97LA247Accident · No injuriesLimited investigationFinal reportCessna 172P · Fort Worth, TXimproper planning/decision by the flight instructor (CFI), which resulted in his inadvertent encounter with jet blast from a twin jet transport airplane.NTSB CHI97LA189Accident · No injuriesLimited investigationFinal reportCessna 172P · Fowlerville, MIfailure of the pilot to either attain proper touchdown point for landing or go around while he had sufficient airspeed and runway remaining.NTSB NYC97LA090Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Morristown, NJThe flight instructor's inadequate supervision which allowed the student to solo at night with less than one hour of night instruction with a known inoperative landing and taxi light. A Factor was the student pilot's spatial disorientation which resulted in…NTSB FTW97LA175Accident · No injuriesLimited investigationFinal reportCessna 172P · Austin, TXThe pilot's failure to maintain aircraft control. A factor was the pilot's inadequate compensation for the wind conditions.NTSB LAX97LA167Accident · Serious injuriesLimited investigationFinal reportCessna 172P · San Jose, CAThe student pilot's failure to maintain adequate airspeed to preclude stalling following an improper recovery from a bounced landing. Contributing factors were the pilot's premature and excessive flap retraction and misjudged landing flare.NTSB FTW97LA163Accident · No injuriesLimited investigationFinal reportCessna 172P · Mckinney, TXthe student pilot's failure to maintain directional control on the ground after recovery from a bounced landing.NTSB SEA97FA076Accident · 1 fatalField investigationFinal reportCessna 172P · Burlington, WYloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB FTW97LA116Accident · No injuriesLimited investigationFinal reportCessna 172P · Cleveland, OKThe pilot/mechanic's improper installation of the spark plug, resulting in its separation from the engine. A factor was the unsuitable terrain available in the runway's overrun area.NTSB MIA97LA090Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Jackson, TNThe pilot's failure to maintain an adequate visual lookout while taxing. The reduced visibility was a factor.NTSB IAD97LA046Accident · No injuriesLimited investigationFinal reportCessna 172P · Chesapeake, OHthe pilot's failure to maintain proper altitude during the approach at night. Related factors were: darkness, and the pilot's lack of night flying experience.NTSB MIA97LA066Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Fort Lauderdale, FLFailure of other maintenance personnel to properly torque a connecting rod bolt and nut for the No. 3 cylinder during engine overhaul.NTSB CHI97LA054Accident · No injuriesLimited investigationFinal reportCessna 172P · Bloomington, INthe pilot failed to maintain control of the aircraft. Factors included the icy runway and the crosswind.