NTSB investigations: Cessna 177, MS
10 cases on aircraft the registry lists as Cessna 177. 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
| 1968 | 1 |
|---|---|
| 1972 | 2 |
| 1973 | 1 |
| 1974 | 1 |
| 1987 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1996 | 1 |
| 2008 | 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\" = 'MS' 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 ('2073704'))
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" = 'MS' 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 ('2073704'))
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 DFW08CA063Accident · No injuriesData collectionFinal reportCessna 177 · Picayune, MSThe pilot's misjudgement of the landing flare resulting in a hard landing.NTSB ATL96LA126Accident · No injuriesLimited investigationFinal reportCessna 177 · Lyon, MSthe student pilot's failure to maintain directional control of the airplane during a touch-and-go landing, which resulted in a ground swerve. The gusty crosswind condition was a related factor.NTSB MIA90LA169Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Greenville, MSThe partial loss of engine power for an unknown reason.NTSB MIA89LA238Accident · No injuriesLimited investigationFinal reportCessna 177 · Woodville, MSImproper planning/decision by the pilot, which resulted in fuel exhaustion, due to an inadequate supply of fuel. Factors related to the accident were: darkness and the ditch.NTSB MIA87LA143Accident · No injuriesLimited investigationFinal reportCessna 177 · Pickens, MSThe plt reported that during cruise flt the eng RPM began to drop. He then applied carb heat, however, the eng then quit. A forced landing was made in a pasture. During the landing roll, the acft collided with barbed wire and a fence post. Post crash…NTSB MIA75DLT01Accident · No injuriesClosedCessna 177 · Coldwater, MSNTSB MIA73DKQ26Accident · No injuriesClosedCessna 177 · Clarksdale, MSNTSB MIA73AM045Accident · 1 fatalClosedCessna 177 · Natchez, MSNTSB MIA73AM015Accident · 1 fatalClosedCessna 177 · Jackson, MSNTSB FTW69D0078Accident · No injuriesClosedCessna 177 · Gulfport, MS