NTSB investigations: Cessna 172N, 1999
46 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\") = 1999
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") = 1999
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 ATL00LA022Accident · No injuriesLimited investigationFinal reportCessna 172N · Melbourne, FLThe certified flight instructor's improper touchdown flare that resulted in a hard landing.NTSB LAX00LA054Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Concord, CAthe pilot's failure to use a checklist and remove the control gust lock.NTSB FTW00LA041Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Springhill, LAThe pilot's inadequate compensation for the wind conditions, which resulted in a loss of aircraft control. Factors were the gusty winds, and the pilot's inadequate weather evaluation.NTSB MIA00LA028Accident · No injuriesLimited investigationFinal reportCessna 172N · Defuniak Spgs, FLWas the pilot's failure to obtain a proper weather briefing resulting in his encounter with fog, his having to make a precautionary landing in a field when the aircraft became low on fuel, and the on ground collision with trees during landing roll.NTSB IAD00LA006Accident · No injuriesLimited investigationFinal reportCessna 172N · Hopedale, MAwas the student pilot's improper flare that resulted in a bounced landing and the flight instructor's delay in taking remedial action.NTSB DEN00LA018Accident · No injuriesLimited investigationFinal reportCessna 172N · Rawlins, WYThe pilot's inadequate preflight planning preparation which resulted in fuel exhaustion. Factors in the accident were the unsuitable terrain on which to make a forced landing and the pilot's lack of experience in aircraft type.NTSB FTW00LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Pineville, LAThe student pilot's misjudgment of distance/speed during approach resulting in his failure to attain the proper touchdown point.NTSB CHI00LA021Accident · No injuriesLimited investigationFinal reportCessna 172N · Crandon, WIthe deer that ran out onto the runway and collided with the airplane. A factor associated with the accident was the night lighting conditions.NTSB LAX00LA021Accident · No injuriesLimited investigationFinal reportCessna 172N · Deer Valley, AZFuel exhaustion due to the pilot's inadequate preflight verification of the fuel quantity, and, once he became aware of the critical fuel state, his decision to over-fly two alternate airports in order to continue to his destination.NTSB ANC00LA005Accident · No injuriesLimited investigationFinal reportCessna 172 · Bethel, AKThe failure of the driver of the forklift to maintain an adequate visual outlook.NTSB FTW99LA269Accident · No injuriesLimited investigationFinal reportCessna 172N · Longview, TXThe pilot's improper touchdown technique, which resulted in the airplane porpoising.NTSB CHI99LA348Accident · No injuriesLimited investigationFinal reportCessna 172N · Des Moines, IAthe pilot's improper in-flight planning and decisions which led to fuel exhaustion. A factor relating to this accident was the telephone pole.NTSB LAX99LA321Accident · No injuriesLimited investigationFinal reportCessna 172N · Vacaville, CAThe pilot's inadequate compensation for the existing gusty crosswind condition and his subsequent failure to maintain directional control.NTSB MIA99LA259Accident · No injuriesLimited investigationFinal reportCessna 172N · Moontown, ALThe pilot's decision to land on a runway with a quartering tailwind, his failure to obtain the proper touchdown point on the runway, and his delay in aborting the takeoff phase of a touch and go landing, resulting in the aircraft overrunning the runway,…NTSB LAX99LA313Accident · No injuriesLimited investigationFinal reportCessna 172N · Merced, CAThe pilot's premature retraction of the flaps during an attempted go-around with insufficient airspeed, which led to an inadvertent stall/mush condition.NTSB LAX99LA306Accident · No injuriesLimited investigationFinal reportCessna 172N · San Jose, CAThe pilot's failure to maintain an adequate visual lookout during taxi. Sun glare was a factor in the accident.NTSB LAX99LA309Accident · No injuriesLimited investigationFinal reportCessna 172N · Carlsbad, CAThe pilot's failure to maintain an adequate clearance from obstacles during taxi in a confined space.NTSB MIA99LA247Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeland, FLThe student pilots improper use of brakes on landing rollout resulting in a loss of directional control and subsequent collision with a ditch. Contributing to the accident was the certified flight instructors improper supervision of the student pilot.NTSB NYC99FA213Accident · 3 fatalField investigationFinal reportCessna 172N · Sussex, NJThe pilot's improper decision to takeoff with a tailwind. Factor's in this accident were the tailwind condition and pressure to depart caused by other airplanes performing successful downwind departures.NTSB MIA99LA239Accident · No injuriesLimited investigationFinal reportCessna 172N · Olive Branch, MSthe pilot misjudged the flare, resulting in the nose gear impacting the runway, and a bounced landing.NTSB NYC99FA214Accident · 4 fatalField investigationFinal reportCessna 172N · Dyke, VAThe pilot's inadvertent flight into instrument meteorological conditions, which resulted in his inability to see the rapidly rising terrain. A factor was the pilot's inaccurate evaluation of the weather.NTSB FTW99LA213Accident · No injuriesLimited investigationFinal reportCessna 172N · Hot Springs, ARthe pilot's failure to refuel the airplane which resulted in fuel exhaustion and a total loss of engine power. A factor was the lack of suitable terrain for a forced landing.NTSB DEN99LA135Accident · No injuriesLimited investigationFinal reportCessna 172N · Englewood, COThe unforecasted sudden wind change, and the pilot's failure to maintain aircraft control. A factor was the down sloping terrain next to the runway.NTSB LAX99LA258Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZthe student pilot's premature retraction of the flaps during an aborted landing and his failure to obtain/maintain adequate flying airspeed, which resulted in a stall/mush condition and the airplane settling back onto the ground. The student pilot's failure…NTSB CHI99LA245Accident · No injuriesLimited investigationFinal reportCessna 172N · Greenville, MIthe student pilot's inadequate use of the rudder which resulted in a loss of directional control during an aborted landing. A factor associated with the accident was the student's lack of total experience and the segmented circle which the airplane contacted.NTSB ATL99LA110Accident · No injuriesLimited investigationFinal reportCessna 172N · Kissimmee, FLThe pilot's improper flare and recovery from a bounced landing.NTSB DEN99LA121Accident · No injuriesLimited investigationFinal reportCessna 172N · Englewood, COThe flight instructor's failure maintain aircraft control. A factor was the inadequate supervision by the flight instructor.NTSB CHI99LA224Accident · No injuriesLimited investigationFinal reportCessna 172N · Faribault, MNthe pilot's failure to maintain directional control of the airplane during the takeoff ground run.NTSB CHI99LA211Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Addison, ILThe pilot's improper fuel selector positioning resulting in fuel starvation during cruise.NTSB DEN99LA106Accident · No injuriesLimited investigationFinal reportCessna 172N · Platteville, COThe pilot misjudging the flare altitude, resulting in a hard landing, and his subsequent loss of aircraft control. A factor was overload forces collapsing the nose landing gear assembly.NTSB CHI99LA188Accident · No injuriesLimited investigationFinal reportCessna 172N · Cloquet, MNa fire which initiated from an undetermined origin.NTSB LAX99LA213Accident · No injuriesLimited investigationFinal reportCessna 172 · Weaverville, CAthe pilot's failure to follow prescribed procedures and directives for the particular airport.NTSB NYC99LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172 · West Milford, NJThe flight instructors failure to maintain climb airspeed during the go-around, which degraded climb performance, resulting in an in-flight collision with terrain. Factors in the accident were, delay in executing a go-around, retracting the flaps to 10…NTSB SEA99LA077Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Covington, WAThe student pilot's inadequate recovery from a bounced landing, and his subsequent improper execution of the go-around procedure, resulting in collision with trees off the departure end of the runway. Factors included the student pilot's lack of total…NTSB MIA99LA148Accident · No injuriesLimited investigationFinal reportCessna 172N · Eagleville, TNThe dual's student failure to maintain adequate altitude/clearance from the wire during takeoff/initial climb. Also causal was the certified flight instructor's inadequate supervision.NTSB ATL99FA078Accident · Serious injuriesField investigationFinal reportCessna 172N · Winter Haven, FLThe pilot of the other aircraft's failure to maintain visual lookout. A factor was the other pilot's disregard for VFR Traffic pattern procedures.NTSB DEN99LA067Accident · No injuriesLimited investigationFinal reportCessna 172I · Las Cruces, NMThe pilot of N46204's failure to maintain visual lookout and to identify the other aircraft visually during landing.NTSB SEA99LA049Accident · No injuriesLimited investigationFinal reportCessna 172N · Puyallup, WAThe pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall.NTSB FTW99LA110Accident · No injuriesLimited investigationFinal reportCessna 172N · Turrell, ARThe total loss of engine power as the result of improper maintenance which led to the number one cylinder intake valve rocker assembly stud bolt backing out rendering the valve inoperative. A factor was the lack of suitable terrain for the forced landing.NTSB FTW99LA114Accident · No injuriesLimited investigationFinal reportCessna 172N · Cleburne, TXThe pilot's failure to maintain adequate altitude/ clearance from the wires.NTSB LAX99LA131Accident · No injuriesLimited investigationFinal reportCessna 172N · Scottsdale, AZFailure of the student pilot to maintain directional control of the aircraft while retracting the flaps during a touch-and-go.NTSB FTW99LA090Accident · No injuriesLimited investigationFinal reportCessna 172N · Orange, TXThe student pilot's failure to maintain directional control during landing touchdown. A factor was the muddy drainage ditch.NTSB NYC99LA066Accident · No injuriesLimited investigationFinal reportCessna 172N · Berlin, NJThe pilot in command's failure to obtain the proper touch down point on the runway, and failure to perform a go-around. A factor relating to the accident was a sudden wind shift.NTSB LAX99FA106Accident · Minor injuriesField investigationFinal reportCessna 172N · El Monte, CAAn in-flight fuel fire in the left forward doorpost due to an electrical arc from an adjacent map light switch puncturing a main fuel feed line. The manufacturer's inadequate design in routing the fuel line in close proximity to electrical arc sources in the…NTSB DEN99LA039Accident · No injuriesLimited investigationFinal reportCessna 172N · West Jordan, UTThe pilot's failure to maintain directional control of the aircraft. Factors were his lack of recent flight experience, and his lack of experience in the make and model of aircraft.NTSB LAX99LA099Accident · No injuriesLimited investigationFinal reportCessna 172N · Fort Ord, CAFuel exhaustion due to the pilot's becoming lost and disoriented during multiple attempts at completing an ILS approach.