NTSB investigations: Cessna 177B, IN
8 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
| 1978 | 1 |
|---|---|
| 1979 | 2 |
| 1993 | 1 |
| 1995 | 2 |
| 2010 | 1 |
| 2012 | 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 c.\"eventStateOrRegion\" = 'IN' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'IN' AND c."eventCountry" = 'USA'
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 CEN12LA532Accident · No injuriesLimited investigationFinal reportCessna 177B · Evansville, INThe pilot’s loss of control due to an inaccurate attitude reference, which was caused by an impending (“in process”) failure of the bearing in the attitude indicator.NTSB CEN11CA123Accident · No injuriesData collectionFinal reportCessna 177B · Seymour, INThe pilot's failure to maintain directional control while taking off with a gusting wind.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 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 CHI93FA137Accident · 2 fatalField investigationFinal reportCessna 177B · Rensselaer, INThe pilot-in-command's failure to maintain aircraft control. Factors were fog and drizzle, and the pilot-in-command's continuing VFR flight into IMC conditions.NTSB CHI80FA013Accident · 1 fatalClosedCessna 177 · Gary, INNTSB CHI79DA068Accident · 1 fatalClosedCessna 177B · Bloomington, INNTSB CHI78DEX26Accident · No injuriesClosedCessna 177B · French Lick, IN