NTSB investigations: Cessna 172, 1999
9 cases on aircraft the registry lists as Cessna 172. 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
| 1964 | 80 |
|---|---|
| 1965 | 77 |
| 1966 | 84 |
| 1967 | 85 |
| 1968 | 65 |
| 1969 | 35 |
| 1970 | 32 |
| 1971 | 37 |
| 1972 | 40 |
| 1973 | 35 |
| 1974 | 35 |
| 1975 | 15 |
| 1976 | 29 |
| 1977 | 25 |
| 1978 | 27 |
| 1979 | 15 |
| 1980 | 21 |
| 1981 | 27 |
| 1982 | 11 |
| 1983 | 6 |
| 1984 | 8 |
| 1985 | 13 |
| 1986 | 8 |
| 1987 | 13 |
| 1988 | 21 |
| 1989 | 15 |
| 1990 | 6 |
| 1991 | 11 |
| 1992 | 12 |
| 1993 | 10 |
| 1994 | 10 |
| 1995 | 9 |
| 1996 | 12 |
| 1997 | 4 |
| 1998 | 13 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 9 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 11 |
| 2006 | 4 |
| 2007 | 9 |
| 2008 | 8 |
| 2009 | 3 |
| 2010 | 4 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 7 |
| 2014 | 3 |
| 2015 | 5 |
| 2016 | 3 |
| 2017 | 6 |
| 2018 | 6 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 8 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 3 |
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 ('2072402'))
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 ('2072402'))
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 DEN99LA170Accident · No injuriesLimited investigationFinal reportCessna 172 · Panguitch, UTInadequate preflight planning and preparation by the pilot in command. Factors were high velocity gusty winds, high-density altitude, and unsuitable terrain for a forced landing.NTSB IAD99LA067Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Honeoye Falls, NYthe pilot's loss of directional control after landing. A factor in the accident were ruts in the turf runway that were hidden from view.NTSB LAX99LA217Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Needles, CAThe pilot's inadequate compensation for the gusty crosswind condition and subsequent failure to maintain alignment with the road used for takeoff, which resulted in a collision with a construction sign during the initial climb.NTSB MIA99FA150Accident · 1 fatalField investigationFinal reportCessna 172 · Fontana, NCthe pilot continued visual flight into know weather conditions which resulted in reduced visibility, and the subsequent in-flight collision with rising terrain. Factors in this accidents were clouds and low ceiling in the accident area.NTSB ATL99FA074Accident · 1 fatalField investigationFinal reportCessna 172 · Savannah, GAThe pilot's selection of the wrong runway for landing and his delayed go-around, which resulted in the collision with trees. A factor was the tailwind on landing.NTSB FTW99LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Sheridan, ARThe pilot's excessive landing approach speed and his failure to attain the proper touchdown point which resulted in a runway overrun.NTSB ATL99LA059Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Florala, ALThe pilot's inadequate preflight inspection, which resulted in a loss of engine power due to fuel system contamination with water.NTSB DEN99FA051Accident · 2 fatalField investigationFinal reportCessna 172 · Gill, COThe pilot's intentional maneuvering at an unwarranted low altitude resulting in a collision with the ground. Factors were the pilot's ostentatious behavioral display and reduced lighting (dusk) conditions.NTSB ATL99LA041Accident · No injuriesLimited investigationFinal reportCessna 172 · Centre, ALThe pilot's inadequate in-flight planning and his failure to attain the proper touchdown point on the runway. Factors were the tailwind weather condition, and the wet sod runway.