NTSB investigations: Cessna 177
11 cases on aircraft the registry lists as Cessna 177, where the first occurrence was “In flight collision with object”. 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 | 1 |
| 1990 | 1 |
| 1992 | 3 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2001 | 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\" = 220))
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" = 220))
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 NYC01LA103Accident · No injuriesLimited investigationFinal reportCessna 177 · Hampton, NHThe pilot's inadvertent encounter with a downdraft, which resulted in a collision with trees. A factor related to the accident were the downdraft wind conditions.NTSB CHI98LA126Accident · 1 fatalLimited investigationFinal reportCessna 177 · Ft. Leonardwood, MOThe pilot's failure to maintain adequate obstacle clearance and his inadequate inflight decision which resulted in VFR flight in to instrument meteorological conditions. The pilot's overconfidence in his ability is a contributing factor.NTSB MIA97LA004Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Ringgold, GAThe pilot's failure to see and avoid obstructions during takeoff.NTSB CHI95LA324Accident · No injuriesLimited investigationFinal reportCessna 177 · Camp Lake, WIthe pilot's inadequate compensation for wind conditions, and failure to maintain altitude/clearance from the power line, while on short final approach. The downdraft was a related factor.NTSB CHI92LA192Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Erie, ILThe pilot's failure to maintain a proper glidepath.NTSB CHI92LA186Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Napoleon, MIAn inadvertent stall on takeoff.NTSB MIA92LA136Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Live Oak, FLImproper planning/decision by the pilot, and his improper use of the mixture control, which resulted in his failure to attain sufficient altitude to clear trees near the departure end of the runway. The proximity of trees was a related factor.NTSB CHI90LA241Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Schaumburg, ILThe pilot's failure to attain a proper climb rate after takeoff. Factors related to the accident are misjudgement of the aircraft takeoff weight, and overconfidence in the ability of the aircraft.NTSB LAX89FA241Accident · 3 fatalField investigationFinal reportCessna 177 · Hesperia, CAAn inflight collision with a power line while maneuvering at low altitude shortly after departure on a dark night over an area with few ground reference lights. The reasons for the aircraft's flight path and altitude profile are undetermined. A factor in the…NTSB LAX85FA197Accident · Serious injuriesField investigationFinal reportCessna 177 · Fallbrook, CAAlthough aware of existing IMC conditions and reduced lighting with the setting of the sun, the plt attempted a visual apch to his home arpt which did not have an approved apch. His remarks to mcclellen-palomar twr, regarding the use of the on-board loran…NTSB FTW82DA312Accident · No injuriesFinal reportCessna 177 · Springer, NMWhile en route on a flight from gallup, NM to dalhart, TX, the left fuel tank would not feed. The pilot made a precautionary landing on rough, grassy terrain with no damage. An examination revealed that the tab for the left filler cap was broken and the cap…