NTSB investigations: Cessna 177B, 1995
11 cases on aircraft the registry lists as Cessna 177B. 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
| 1970 | 2 |
|---|---|
| 1971 | 2 |
| 1972 | 5 |
| 1973 | 11 |
| 1974 | 9 |
| 1975 | 11 |
| 1976 | 15 |
| 1977 | 15 |
| 1978 | 23 |
| 1979 | 17 |
| 1980 | 10 |
| 1981 | 11 |
| 1982 | 8 |
| 1983 | 5 |
| 1984 | 8 |
| 1985 | 11 |
| 1986 | 8 |
| 1987 | 1 |
| 1988 | 5 |
| 1989 | 7 |
| 1990 | 10 |
| 1991 | 4 |
| 1992 | 11 |
| 1993 | 8 |
| 1994 | 1 |
| 1995 | 11 |
| 1996 | 5 |
| 1997 | 4 |
| 1998 | 2 |
| 1999 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 6 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 3 |
| 2010 | 6 |
| 2011 | 2 |
| 2012 | 6 |
| 2013 | 1 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 4 |
| 2019 | 1 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 4 |
| 2023 | 4 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 7 |
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\") = 1995
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073708'))
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") = 1995
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073708'))
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 SEA95LA187Accident · No injuriesLimited investigationFinal reportCessna 177B · Yamhill, ORThe pilot's failure to maintain a proper glidepath. A factor contributing to the accident was the sunglare.NTSB SEA95LA182Accident · No injuriesLimited investigationFinal reportCessna 177B · Seattle, WALoss of engine power for undetermined reason(s).NTSB CHI95LA208Accident · No injuriesLimited investigationFinal reportCessna 177B · Nappanee, INThe failure of the pilot to do adequate preflight planning and failure to refuel when he had the opportunity. A factor in the accident was the soft field due to recent rains.NTSB SEA95LA122Accident · No injuriesLimited investigationFinal reportCessna 177B · Seattle, WAThe pilot's inadequate remedial action when he encountered porpoising after landing on the nosewheel.NTSB LAX95LA206Accident · Minor injuriesLimited investigationFinal reportCessna 177B · Lebec, CAFuel exhaustion due to the pilot's lack of familiarity with the airplane's fuel sysytem and his failure to maintain an adequate supply of fuel to complete the flight.NTSB NYC95LA120Accident · No injuriesLimited investigationFinal reportCessna 177B · Allentown, PAthe pilot misjudged the flare, resulting in a hard, bounced landing and impact with the runway. A factor in this accident was an improper recovery from a bounced landing.NTSB FTW95LA194Accident · Serious injuriesLimited investigationFinal reportCessna 177B · Casa, ARThe pilot's failure to maintain obstacle clearance.NTSB CHI95FA148Accident · 1 fatalField investigationFinal reportCessna 177B · Nappanee, INairplane control was not maintained by the pilot during the his turn to an emergency landing area. Factors associated with this accident were the pilot not complying with the manufacturer's mandatory service bulletin, and an excessive fuel flow caused by the…NTSB ATL95LA061Accident · Serious injuriesLimited investigationFinal reportCessna 177B · Collegedale, TNThe mechanic's failure to follow approved engine overhaul procedures which resulted in the separation of the oil return line, and the complete loss of engine power.NTSB FTW95LA118Accident · No injuriesLimited investigationFinal reportCessna 177B · Terlingua, TXThe pilot's failure to maintain directional control. Factors were his decision to land on the unlit runway and the dusk light conditions.NTSB FTW95LA079Accident · No injuriesLimited investigationFinal reportCessna 177B · Torreon, NMThe pilot's failure to attain proper liftoff speed resulting in an inadvertent stall and the failure to remove frost from the wing. A factor was fatigue.