NTSB investigations: Cessna 172N, 1998
37 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\") = 1998
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") = 1998
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 CHI99LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · Evansville, INThe pilot's improper flare and improper recovery from a bounced landing.NTSB FTW99FA033Accident · 2 fatalField investigationFinal reportCessna 172N · Bacliff, TXThe pilot's inadvertent VFR flight into instrument meteorological conditions and his inability to maintain adequate altitude/clearance from the wire. Contributing to the accident were the fog, low ceilings and his lack of instrument time.NTSB ATL99FA020Accident · Serious injuriesField investigationFinal reportCessna 172N · Concord, NCThe pilot's improper in-flight decision and his failure to maintain clearance during approach that resulted in collision with utility lines. Related factors were dark night, trees and low ceilings.NTSB LAX99LA031Accident · No injuriesLimited investigationFinal reportCessna 172N · Lancaster, CAThe failure of the pilot to maintain directional control of the aircraft.NTSB LAX99LA030Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZThe failure of the flight instructor to provide adequate supervision of the student pilot during a simulated emergency landing.NTSB ATL99LA013Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lima, SCThe flight instructor's intentional flight into Instrument Meteorological Conditions. Factors were trees and mountainous terrain.NTSB MIA99LA030Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Lauderdale, FLThe failure of the pilot-in-command to note that the flaps did not retract while the pilot-rated student performed a touch-and-go landing on a 6,001 foot-long runway. Factors in the accident were the total failure of the flap system for undetermined reasons…NTSB NYC99FA015Accident · 1 fatalField investigationFinal reportCessna 172N · Linden, NJThe pilot's failure to maintain clearance from the power lines. A factor was sunglare.NTSB MIA99LA013Accident · No injuriesLimited investigationFinal reportCessna 172N · Lawrenceville, GAA fire from an undetermined origin.NTSB SEA99LA002Accident · No injuriesLimited investigationFinal reportCessna 172N · Buhl, IDThe pilot's failure to follow the aircraft's recommended balked landing procedure, resulting in a stall. Factors include the pilot's failure to maintain directional control during the landing flare, the pilot's lack of total experience, and insufficient…NTSB MIA99LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Venice, FLThe pilot's improper flare and improper recovery from a bounced landing.NTSB FTW98LA417Accident · No injuriesLimited investigationFinal reportCessna 172N · Gallup, NMThe pilot's inadequate landing flare. Factors were his misjudgement of altitude and his excessive airspeed.NTSB CHI98LA335Accident · No injuriesLimited investigationFinal reportCessna 172 · Harrisburg, ILthe loss of engine power for undetermined reasons.NTSB FTW98FA399Accident · 1 fatalField investigationFinal reportCessna 172N · Montezuma Crk, UTThe pilot's attempted aerobatic maneuver and the subsequent inadvertent stall/spin. A factor was his intentional low altitude flight.NTSB CHI98LA331Accident · No injuriesLimited investigationFinal reportCessna 172N · Detroit Lakes, MNAn inadequate preflight inspection by the pilot which resulted in fuel exhaustion and subsequent loss of engine power.NTSB LAX98LA269Accident · No injuriesLimited investigationFinal reportCessna 172N · Chandler, AZFuel exhaustion due to the pilot's inadequate preflight planning and in-flight monitoring of the aircraft's fuel consumption.NTSB FTW98FA358Accident · 1 fatalField investigationFinal reportCessna 172N · Cord, ARThe pilot's performance of low altitude flight and his failure to maintain obstacle clearance.NTSB CHI98LA340Accident · No injuriesLimited investigationFinal reportCessna 172N · Traverse City, MIthe inadvertent stall/mush. Factors contributing to this accident were the pilot's improper compensation for the wind conditions, and his excessively high flare.NTSB IAD98LA087Accident · No injuriesLimited investigationFinal reportCessna 172N · Lebanon, OHThe pilot's delay in aborting the landing, which resulted in inadequate obstacle (car) clearance during initial takeoff climb. A contributing factor is the pilot's decision to perform a tailwind landing.NTSB CHI98LA255Accident · Minor injuriesLimited investigationFinal reportCessna 172N · New Lenox, ILLoss of engine power for undetermined reasons.NTSB FTW98LA314Accident · No injuriesLimited investigationFinal reportCessna 172N · Broomfield, COThe pilot's improper landing flare which resulted in a hard landing.NTSB FTW98FA307Accident · Serious injuriesField investigationFinal reportCessna 172N · Lincoln, TXThe #3 cylinder exhaust valve rocker arm fulcrum retaining stud backing out of its stud-tapped hole due to the improper tapping of the stud hole by unknown maintenance personnel. Contributing factors were the transmission wire, sign and gasoline pump.NTSB ATL98LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Olive Branch, MSthe student pilot's failure to maintain directional control of the airplane during takeoff.NTSB CHI98LA228Accident · No injuriesLimited investigationFinal reportCessna 172N · Stone Lake, WIthe lack of effective braking due to hydroplaning. Contributing factors to the accident were the trees off the end of the runway that made a go-around not possible and the ditch off the end of the runway.NTSB IAD98FA070Accident · 1 fatalField investigationFinal reportCessna 172N · Ocean City, MDThe pilot's failure to maintain control of the aircraft due to spatial disorientation. Contributing factors wer fog, dark night conditions, lack of recent experience, inadequate preflight planning, and flight into known adverse weather.NTSB SEA98FA088Accident · 3 fatalField investigationFinal reportCessna 172N · Prindle, WAThe pilot-in-command's failure to maintain control of the aircraft during attempted flight into instrument meteorological conditions. Factors contributing to the accident were clouds, dark night conditions, spatial disorientation, and drug impairment.NTSB CHI98LA147Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hannibal, MOa loss of engine power due to undetermined reasons. A factor was the rough field in which the forced landing was made.NTSB MIA98LA153Accident · No injuriesLimited investigationFinal reportCessna 172N · West Palm Beach, FLthe dual student's failure to use carburetor heat while circling at a reduced power setting, and the flight instructor's failure to properly supervise the student.NTSB LAX98FA152Accident · 4 fatalField investigationFinal reportCessna 172N · Avalon, CAThe pilot's failure to maintain adequate altitude/clearance in a Blind/Box Canyon. A related factor was the mountainous/hilly terrain.NTSB SEA98LA070Accident · No injuriesLimited investigationFinal reportCessna 172N · Enumclaw, WAThe pilot's continued VFR flight into IMC conditions and his failure to maintain clearance from terrain. Clouds and mountainous terrain were a factor.NTSB FTW98LA198Accident · No injuriesLimited investigationFinal reportCessna 172N · Parker, COa fractured #1 exhaust valve rocker arm stud, which subsequently resulted in loss of engine power and a forced landing. The lack of suitable terrain in the forced landing area was a related factor.NTSB IAD98LA045Accident · No injuriesLimited investigationFinal reportCessna 172N · Stevensville, MDthe pilot's improper flare, improper recover from a bounced landing, and failure to maintain directional control.NTSB LAX98LA201Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Barbara, CAThe pilot's misjudging the landing flare and subsequent hard landing.NTSB ATL98FA060Accident · 5 fatalField investigationFinal reportCessna 525 · Marietta, GAThe failure of both pilots to see and avoid conflicting traffic, and the failure of the 172 pilot to operate the transponder as required by current regulations. Factors were the controller's failure to observe the traffic conflict, the lack of radar conflict…NTSB MIA98LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Titusville, FLloss of engine power for undetermined reason(s), which resulted in a forced landing. Factors relating to the accident were: the lack of suitable terrain and obstructions in the emergency landing area.NTSB IAD98LA030Accident · No injuriesLimited investigationFinal reportCessna 172 · Rutland, VTthe pilot's improper in-flight planning/decision, which resulted in fuel exhaustion, loss of engine power, and a forced landing. Related factors were: unfavorable (headwind) conditions, and brush/small trees in the forced landing area.NTSB MIA98LA063Accident · No injuriesLimited investigationFinal reportCessna 172N · Valdosta, GAThe failure of the student to recover (pull-up) from the intentional maneuver resulting in the in-flight collision with terrain. Contributing to the accident was the ostentatious display by the student.