NTSB investigations: Cessna 172M, 1999
22 cases on aircraft the registry lists as Cessna 172M. 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
| 1972 | 3 |
|---|---|
| 1973 | 24 |
| 1974 | 59 |
| 1975 | 82 |
| 1976 | 104 |
| 1977 | 99 |
| 1978 | 92 |
| 1979 | 80 |
| 1980 | 59 |
| 1981 | 50 |
| 1982 | 53 |
| 1983 | 34 |
| 1984 | 35 |
| 1985 | 34 |
| 1986 | 38 |
| 1987 | 29 |
| 1988 | 28 |
| 1989 | 38 |
| 1990 | 37 |
| 1991 | 36 |
| 1992 | 31 |
| 1993 | 37 |
| 1994 | 24 |
| 1995 | 29 |
| 1996 | 23 |
| 1997 | 35 |
| 1998 | 30 |
| 1999 | 22 |
| 2000 | 22 |
| 2001 | 30 |
| 2002 | 26 |
| 2003 | 24 |
| 2004 | 18 |
| 2005 | 16 |
| 2006 | 18 |
| 2007 | 16 |
| 2008 | 24 |
| 2009 | 14 |
| 2010 | 15 |
| 2011 | 13 |
| 2012 | 18 |
| 2013 | 20 |
| 2014 | 20 |
| 2015 | 9 |
| 2016 | 10 |
| 2017 | 19 |
| 2018 | 14 |
| 2019 | 13 |
| 2020 | 16 |
| 2021 | 8 |
| 2022 | 24 |
| 2023 | 12 |
| 2024 | 14 |
| 2025 | 12 |
| 2026 | 8 |
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 ('2072418'))
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 ('2072418'))
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 MIA00LA046Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Pikeville, NCThe inadequate supervision of the private-rated pilot by the certified flight instructor for allowing the airplane to impact terrain during a simulated forced landing procedure to an open field.NTSB CHI00LA036Accident · No injuriesLimited investigationFinal reportCessna 172M · Ava, MOthe improper in-flight decision made by the pilot. Factors to the accident were the charts/other manuals depicting the incorrect frequency, the dirt bank, and the rocks.NTSB SEA00LA010Accident · No injuriesLimited investigationFinal reportCessna 172M · Mackay, IDThe pilot's failure to land at the proper touchdown point. Factors include a wind gust, a grass runway, and a drop-off into rough terrain at the end of the runway.NTSB SEA99LA160Accident · No injuriesLimited investigationFinal reportCessna 172M · Tahola, WAThe pilot's inadequate directional control and his failure to maintain clearance from trees along the side of the landing area. Factors include a landing area surrounded by tall trees.NTSB CHI99LA336Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Daleville, INA loss of engine power for undetermined reasons.NTSB CHI99LA312Accident · No injuriesLimited investigationFinal reportCessna 172M · Bloomington, ILthe pilot's inadequate visual lookout and not performing a maneuver to avoid obstructions. A factor was the road signs.NTSB MIA99LA207Accident · No injuriesLimited investigationFinal reportCessna 172M · Pierson, FLthe flight instructor's (pilot in command) failure to achieve the proper touch down point, his improper decision to continue the touch and go, and failure to abort the takeoff in sufficient time, resulting in the aircraft overrunning the runway and colliding…NTSB NYC99LA174Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Hamburg, NYThe pilot's improper recovery from a bounced landing. A related factor was the lack of experience in make and model.NTSB LAX99LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · Fresno, CAThe pilot's misjudged landing flare and inadequate recovery procedures from the subsequent bounced landing.NTSB LAX99LA221Accident · Serious injuriesLimited investigationFinal reportCessna 172M · San Diego, CAThe mechanic's improper installation of nonapproved automotive electrical system parts, and his failure to ensure that all electrical connections were secure during the reinstallation, which resulted in the failure of the electrical system. The pilot's…NTSB NYC99LA152Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Fayetteville, WVThe pilot's failure to maintain directional control during the aborted landing. A factor in this accident was the crosswind condition.NTSB SEA99LA062Accident · No injuriesLimited investigationFinal reportCessna 172M · Omak, WAThe pilot's failure to properly secure the aircraft before hand-propping.NTSB ATL99LA090Accident · No injuriesLimited investigationFinal reportCessna 172M · Double Springs, ALThe pilot's failure to maintain directional control of the aircraft during landing. A factor was the pilot's lack of experience.NTSB FTW99LA133Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Lancaster, TXThe pilot's inadequate preflight inspection which resulted in fuel exhaustion and the subsequent total loss of engine power.NTSB CHI99LA148Accident · No injuriesLimited investigationFinal reportCessna 172 · Blair, NEThe pilot's misjudged landing flare.NTSB CHI99LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Mayview, MOthe pilot's selection of unsuitable terrain for the attempted precautionary landing. Factors to the accident were the overcast weather condition, inadequate preflight planning by the pilot, the inadvertent flight into instrument meteorological conditions, and…NTSB NYC99LA094Accident · No injuriesLimited investigationFinal reportCessna 172M · Lumberton, NJThe pilot's misjudgment of altitude and distance which resulted in a runway overrun.NTSB FTW99LA108Accident · No injuriesLimited investigationFinal reportCessna 172M · Midlothian, TXThe pilot's failure to maintain clearance with the powerlines. Factors were the low ceilings and the dusk light illumination.NTSB CHI99LA118Accident · No injuriesLimited investigationFinal reportCessna 172M · New Hudson, MIThe pilot's misjudgment of speed and distance and his failure to execute a go-around. A related factor was the crosswind.NTSB LAX99LA123Accident · No injuriesLimited investigationFinal reportCessna 172M · Reno, NVThe pilot's inadequate compensation for the crosswind condition and his failure to maintain runway alignment during the crosswind landing.NTSB MIA99WA082Accident · No injuriesForeign investigationCessna 172M · Rum Cay, BahamasNTSB FTW99LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Midlothian, TXThe student pilot's failure to compensate for a crosswind resulting in a loss of control. Factors were the gusty high winds and the flight instructor's improper decision to allow the student to solo during high winds.