NTSB investigations: Cessna 172N, 2001
32 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\") = 2001
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") = 2001
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 LAX02FA056Accident · 2 fatalField investigationFinal reportCessna 172N · San Clemente, CAa loss of engine power due to a loss of magneto to engine timing resulting from stress corrosion crack induced fracture, and separation of the magneto impulse coupling spring.NTSB DEN02LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Broomfield, COthe pilot's failure to maintain directional control of the airplane while landing. A contributing factor was the crosswind.NTSB SEA02LA017Accident · No injuriesLimited investigationFinal reportCessna 172N · Snohomish, WAThe student pilot misjudged the distance from a fence during taxi. The flight instructors inadequate supervision and the fence were factors.NTSB DEN02LA003Accident · No injuriesLimited investigationFinal reportCessna 172N · Provo, UTThe pilot's improper recovery from a bounced landing. Contributing factors were the pilot's lack of total experience in aircraft, and the pilot's lack of recent experience in kind of aircraft.NTSB NYC02LA011Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Ashland, VAThe line technician's inadvertent contact with the propeller during a hand-propped engine start.NTSB IAD02LA004Accident · No injuriesLimited investigationFinal reportCessna 172 · Perkasie, PAThe pilot's improper flare, which resulted in a hard landing. A factor was the sun glare.NTSB DEN02LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Colo Springs, COthe pilot's inadequate landing flare, which resulted in a hard landing. A contributing factor was the pilot's excessive airspeed on final approach.NTSB CHI02LA004Accident · No injuriesLimited investigationFinal reportCessna 172N · Beaver Island, MIThe pilot not maintaining directional control of the airplane during landing. The gusty crosswind and the berm were factors.NTSB SEA02FA002Accident · 3 fatalField investigationFinal reportCessna 172N · Decatur Island, WAThe pilot's failure to maintain airspeed during a low altitude turn, resulting in a stall. The pilot exceeding the aircraft's maximum gross takeoff weight was a factor.NTSB SEA01LA169Accident · No injuriesLimited investigationFinal reportCessna 172N · Pasco, WAThe DHC-8 maintenance crew's failure to maintain radio contact with the tower during its engine run. Factors included the tower controller not issuing a safety advisory on the DHC-8 engine run to the accident pilot as recommended by FAA guidance, and the…NTSB CHI01LA303Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sheldon, IAthe in-flight planning/decision and proper touchdown point not attained by the pilot. Contributing factors were the ingested exhaust valve and lack of experience of the pilot.NTSB DEN01LA147Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Peyton, COThe pilot's improper go-around procedure and his failure to maintain adequate airspeed which resulted in an inadvertent stall. A factor was the pilot's lack of total experience.NTSB MIA01LA207Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Covington, GAThe flight instructor's improper monitoring of the dual student during a simulated engine out approach and her delayed decision to initiate a go-around resulting in the airplane colliding with trees at the departure end of the runway during the go-around.NTSB MIA01WA203Accident · Minor injuriesForeign investigationCessna 172N · Cojimar, CubaNTSB DEN01LA129Accident · No injuriesLimited investigationFinal reportCessna 172N · Farmington, NMthe pilot's failure to maintain clearance from the powerline while descending for an emergency landing. A contributing factor was the loss of engine power for an undetermined reason.NTSB CHI01LA202Accident · No injuriesLimited investigationFinal reportCessna 172N · West Chicago, ILThe instructor pilot's inadequate recovery from the bounced landing and inadequate supervision of the dual students alignment with the runway. A factor was the student pilot not maintaining proper alignment with the runway during landing.NTSB FTW01LA162Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Caldwell, TXthe solo student pilot's intentional engine shutdown, while practicing emergency landing prodecures. A contributing factor was the lack of suitable terrain for the forced landing.NTSB LAX01LA231Accident · No injuriesLimited investigationFinal reportCessna 172N · Boulder City, NVthe loss of engine power while in cruise flight due to the mechanic's improper magneto timing.NTSB ATL01LA067Accident · No injuriesLimited investigationFinal reportCessna 172N · Colquitt, GAThe student pilot's failure to use the fuel selector valve properly which resulted in fuel starvation and the subsequent loss of engine power, and the pilot's improper flare during landing.NTSB FTW01LA131Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Georgetown, TXthe pilot's failure to refuel the aircraft resulting in fuel exhaustion during cruise flight. A contributing factor was the gusty wind encountered during the forced landing.NTSB IAD01LA056Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Ashland, MEloss of partial engine power due to carburetor icing.NTSB CHI01FA130Accident · 2 fatalField investigationFinal reportCessna 172N · Wichita, KSthe student pilot not maintaining clearance from the tower support wire during the practice emergency landing maneuver and the instructor pilot's inadequate supervision of the student pilot. Factors relating to the accident were the static wire and the low…NTSB FTW01LA112Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Marfa, TXfuel exhaustion resulting in a total loss of engine power in cruise flight due to the pilot's failure to refuel the aircraft. Contributing factors were the lack of suitable terrain for the forced landing, and the dark night condition.NTSB SEA01LA076Accident · Minor injuriesLimited investigationFinal reportCessna 172 N · Sultan, WAThe pilot's failure to maintain adequate clearance from trees and terrain during the airplane's initial climb.NTSB LAX01FA134Accident · 2 fatalField investigationFinal reportCessna 172N · Rialto, CAThe pilot's intentional visual flight into instrument meteorological conditions. Contributing to the accident was the pilot's improper weather evaluation and lack of total experience.NTSB LAX01FA129Accident · 3 fatalField investigationFinal reportCessna 172N · Santa Monica, CAthe pilot's loss of airplane control while maneuvering due to spatial disorientation. Contributing factors were the dark night, the marine cloud layer that restricted the pilot's cruising altitude, and the pilot's lack of familiarity with nighttime flight…NTSB LAX01LA115Accident · No injuriesLimited investigationFinal reportCessna 172N · Show Low, AZThe pilot's failure to maintain directional control resulting in an encounter with terrain and a nose over.NTSB CHI01FA093Accident · 2 fatalField investigationFinal reportCessna 172H · Centralia, ILThe student pilot allowed the airspeed to get too low and inadvertently stalled the airplane, and the CFI delayed in taking remedial action.NTSB LAX01LA102Accident · No injuriesLimited investigationFinal reportCessna 172N · San Diego, CAThe pilot's failure to maintain directional control of the airplane during landing rollout.NTSB LAX01FA101Accident · 4 fatalField investigationFinal reportCessna 152 · Long Beach, CAThe failure of the flight crews of both airplanes to maintain adequate visual lookout for traffic.NTSB LAX01FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172N · Monterey, CAUndetermined.NTSB CHI01LA057Accident · No injuriesLimited investigationFinal reportCessna 172N · Lincoln, ILThe pilot's failure to maintain directional control on the runway. Factors relating to this accident were the aborted takeoff attempt, the pilot's improper in-flight planning/decision, and the snowbank.