NTSB investigations: Cessna 177, 2008

7 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

19652026
NTSB investigations: Cessna 177, 2008 per year, 1965–2026: 800 cases
19651
19675
1968104
1969103
197069
197143
197242
197328
197429
197530
197624
197720
197817
197918
198015
198113
198213
19836
19843
198510
19869
19876
19889
198914
199010
199110
199212
19936
19942
19955
19966
19979
19989
199911
20003
20017
20028
20034
20045
20063
20076
20087
20094
20102
20114
20123
20131
20143
20154
20161
20174
20183
20194
20203
20214
20222
20232
20241
20251

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 year(c.\"eventDate\") = 2008
    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.

NTSB ERA09CA012Accident · Minor injuriesData collectionFinal reportCessna 177 · Bluffton, SCThe pilot's inadequate planning and preflight inspection.Oct 10, 2008 · N3495T · Substantial damageNTSB SEA08CA180Accident · No injuriesData collectionFinal reportCessna 177 · Glendale, AZThe loss of engine power due to vapor lock. Contributing to the accident was the high atmospheric temperature.Aug 17, 2008 · N29304 · Substantial damageNTSB SEA08LA179Accident · 1 fatalLimited investigationFinal reportCessna 177 · St. Johns, AZThe failure of both pilots to abort the takeoff when a suitable climb rate could not be attained. Contributing to the accident was the reduction of available power due to the camshaft lobe and lifter corrosion/wear, the high density altitude, and the CFI’s…Aug 16, 2008 · N3487T · Substantial damageNTSB CHI08CA188Accident · No injuriesData collectionFinal reportCessna 177A · Rhinelander, WIThe loss of engine power for an undetermined reason. A factor was the berm encountered during the forced landing.Jul 1, 2008 · N2295Y · Substantial damageNTSB DFW08CA174Accident · No injuriesData collectionFinal reportCessna 177 · Baldwin City, KSThe pilot's loss of directional control resulting from a hard landing and failure to recover from a bounced landing. Contributing to the accident was the crosswind.Jun 28, 2008 · N3337T · Substantial damageNTSB CHI08CA120Accident · No injuriesData collectionFinal reportCessna 177 · Bellefontaine, OHThe pilot's failure to maintain directional control during the aborted landing. Contributing to the accident was the fence.May 4, 2008 · N29650 · Substantial damageNTSB DFW08CA063Accident · No injuriesData collectionFinal reportCessna 177 · Picayune, MSThe pilot's misjudgement of the landing flare resulting in a hard landing.Jan 28, 2008 · N2905X · Substantial damage