NTSB investigations: Cessna 177
12 cases on aircraft the registry lists as Cessna 177, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 1 |
|---|---|
| 1985 | 1 |
| 1989 | 2 |
| 1991 | 1 |
| 1993 | 1 |
| 1996 | 2 |
| 1998 | 1 |
| 1999 | 1 |
| 2002 | 1 |
| 2004 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073704')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073704')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 230))
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 NYC04CA200Accident · No injuriesData collectionFinal reportCessna 177 · Warrenton, VAThe pilot's incorrect aborted landing procedure, which resulted in a collision with terrain.NTSB FTW02LA081Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Pond Creek, OKThe pilot's failure to maintain altitude due to falling asleep while performing pipeline patrol activities.NTSB FTW99LA057Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Marietta, OKThe failure of the pilot-in-command to maintain clearance with terrain. Factors were the short runway and the dark night light condition.NTSB SEA98FA161Accident · 1 fatalField investigationFinal reportCessna 177 · Red Lodge, MTThe pilot's failure to maintain adequate altitude over, or clearance with, mountainous terrain during night visual flight rules flight. Factors included night lighting conditions and mountainous terrain.NTSB NYC96FA178Accident · 1 fatalField investigationFinal reportCessna 177 · Youngstown, OHthe pilot's delay in aborting the landing, and his failure to attain adequate airspeed to fly out of ground effect, which resulted in a stall/mush and collision with the ground. Factors relating to the accident were: the pilot's improper recovery from a…NTSB LAX96LA107Accident · No injuriesLimited investigationFinal reportCessna 177 · Corona, CAimproper planning/decision by the pilot-in-command (PIC), and his failure to ensure that adequate airspeed was obtain and/or maintain during lift-off/initial climb. A factor relating to the accident was: the PIC allowed the airplane's maximum gross weight…NTSB BFO93LA099Accident · No injuriesLimited investigationFinal reportCessna 177 · Newport, NHThe pilot's failure to properly recover from a bounced landing, and his failure to maintain directional control during the aborted landing.NTSB DEN91FA110Accident · 1 fatalField investigationFinal reportCessna 177 · Hygiene, COSuicide. A factor related to the accident was: the pilot's other psychological condition.NTSB LAX89LA219Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Banning, CAInadequate preflight planning/preparation by the pilot.NTSB LAX89LA116Accident · No injuriesLimited investigationFinal reportCessna 177 · Yuba City, CAInadequate supervision by the instructor (CFI) which resulted in a delayed go-around, inadequate airspeed, and a stall/mush into the ground. A poor approach by the student pilot was a contributing factor.NTSB CHI86LA040Accident · No injuriesLimited investigationFinal reportCessna 177 · Crookston, MNWhile doing a 270 degree turn on base leg for runway realignment the pilot permitted the acft to fly into the ground.NTSB NYC82FHJ06Accident · 3 fatalFinal reportCessna 177 · Larchmont, NYThe aircraft was on a flight to take pictures of a home that was recently constructed on the shore of long island sound. While in flight, pictures were also taken of boats. A witness on a boat stated taht after the pilot made several passes over boats, the…