NTSB investigations: Cessna 177, 2003
4 cases on aircraft the registry lists as Cessna 177. 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 |
|---|---|
| 1967 | 5 |
| 1968 | 104 |
| 1969 | 103 |
| 1970 | 69 |
| 1971 | 43 |
| 1972 | 42 |
| 1973 | 28 |
| 1974 | 29 |
| 1975 | 30 |
| 1976 | 24 |
| 1977 | 20 |
| 1978 | 17 |
| 1979 | 18 |
| 1980 | 15 |
| 1981 | 13 |
| 1982 | 13 |
| 1983 | 6 |
| 1984 | 3 |
| 1985 | 10 |
| 1986 | 9 |
| 1987 | 6 |
| 1988 | 9 |
| 1989 | 14 |
| 1990 | 10 |
| 1991 | 10 |
| 1992 | 12 |
| 1993 | 6 |
| 1994 | 2 |
| 1995 | 5 |
| 1996 | 6 |
| 1997 | 9 |
| 1998 | 9 |
| 1999 | 11 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 8 |
| 2003 | 4 |
| 2004 | 5 |
| 2006 | 3 |
| 2007 | 6 |
| 2008 | 7 |
| 2009 | 4 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 3 |
| 2013 | 1 |
| 2014 | 3 |
| 2015 | 4 |
| 2016 | 1 |
| 2017 | 4 |
| 2018 | 3 |
| 2019 | 4 |
| 2020 | 3 |
| 2021 | 4 |
| 2022 | 2 |
| 2023 | 2 |
| 2024 | 1 |
| 2025 | 1 |
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\") = 2003
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073704'))
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") = 2003
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073704'))
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 DEN04LA011Accident · No injuriesLimited investigationFinal reportCessna 177 · Nageezi, NMthe pilot's inadequate preflight planning, inadequate fuel consumption calculations, and improper fuel management. Contributing factors include fuel exhaustion resulting in the loss of power, the lack of suitable terrain for a forced landing and the tree.NTSB CHI03LA226Accident · No injuriesLimited investigationFinal reportCessna 177 · Murdock, NEThe pilot's inadequate preflight planning/preparation which led to fuel exhaustion and subsequent loss of engine power. Contributing to the accident were the trees and unsuitable terrain.NTSB SEA03CA112Accident · No injuriesData collectionFinal reportCessna 177 · Woodland, WAThe pilot's premature liftoff and his failure to maintain/obtain airspeed and directional control during takeoff.NTSB ATL03FA061Accident · 3 fatalField investigationFinal reportCessna 177 · Old Fort, NCThe pilot's decision to continue VFR flight into IMC and his failure to maintain terrain clearance which resulted in an in-flight collision with mountainous terrain.