NTSB investigations: Cessna 177B, OK
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
| 1976 | 1 |
|---|---|
| 1977 | 1 |
| 1980 | 1 |
| 1981 | 1 |
| 1985 | 1 |
| 1989 | 1 |
| 1993 | 1 |
| 2010 | 1 |
Where
Latest 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\" = 'OK' 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" = 'OK' 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 CEN10FA385Accident · 3 fatalField investigationFinal reportCessna 177B · Owasso, OKThe pilot’s failure to maintain adequate airspeed during an engine-out approach to the runway, resulting in an aerodynamic stall and spin. Contributing to the accident was the pilot’s inadequate preflight planning, which resulted in a loss of engine power due…NTSB FTW93LA204Accident · No injuriesLimited investigationFinal reportCessna 177B · Shawnee, OKFuel system exhaustion induced power loss for undetermined reasons. A factor was a lack of suitable terrain.NTSB FTW89LA094Accident · No injuriesLimited investigationFinal reportCessna 177B · Harrah, OKFailure of the pilot to maintain directional control during the landing, which resulted in an inadvertent ground swerve; and his improper planning/decision (indecision) concerning an attempted go-around. The pilot's lack of experience in the type of aircraft…NTSB FTW85LA290Accident · Minor injuriesLimited investigationFinal reportCessna 177B · Guthrie, OKThe plt stated he lost eng power shortly after takeoff and during initial climb. He elected to go into the trees due to lack of altitude to allow a more suitable landing area. An eng examination disclosed that the no. four exhaust valve was stuck open due to…NTSB FTW81FPM22Accident · No injuriesClosedCessna 177B · Tulsa, OKNTSB FTW80FPJ26Accident · Minor injuriesClosedCessna 177 · Watonga, OKNTSB FTW77DPJ33Accident · Minor injuriesClosedCessna 177D · Waynoka, OKNTSB FTW77FA009Accident · 1 fatalClosedCessna 177B · Oklahoma City, OK