NTSB investigations: Cessna 177, 2002

8 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, 2002 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\") = 2002
    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 IAD02LA093Accident · No injuriesLimited investigationFinal reportCessna 177 · Dayton, OHThe pilot's failure to maintain adequate airspeed, resulting in a stall.Sep 13, 2002 · N2916X · Substantial damageNTSB LAX02FA227Accident · 4 fatalField investigationFinal reportCessna 177 · Hana, HIThe pilot's failure to maintain an adequate airspeed while maneuvering, which resulted in a stall.Jul 14, 2002 · N306DJ · Substantial damageNTSB NYC02LA137Accident · No injuriesLimited investigationFinal reportCessna 177 · Millville, NJThe pilot's improper bounced landing recovery. A factor was the dark night conditions.Jul 5, 2002 · N29321 · Substantial damageNTSB SEA02LA113Accident · No injuriesLimited investigationFinal reportCessna 177 · Mt. Vernon, WAThe pilot's failure to accurately determine the amount of fuel onboard. Factors included trees, and a portable restroom.Jun 26, 2002 · N29441 · Substantial damageNTSB FTW02LA175Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Sherman, TXThe hard landing as result of the pilot's failure to maintain aircraft control during landing. A contributing factor was the gusty crosswinds.Jun 9, 2002 · N2282Y · Substantial damageNTSB ATL02LA090Accident · No injuriesLimited investigationFinal reportCessna 177 · Locust Grove, GAThe pilot improper flare during an aborted takeoff, followed by an subsequent hard landing.Apr 29, 2002 · N2809X · Substantial damageNTSB FTW02LA081Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Pond Creek, OKThe pilot's failure to maintain altitude due to falling asleep while performing pipeline patrol activities.Feb 18, 2002 · N3402T · Substantial damageNTSB FTW02FA072Accident · 1 fatalField investigationFinal reportCessna 177 · Farmington, NMthe pilot's inadequate in-flight planning decision which resulted in fuel exhaustion while in the traffic pattern at the destination airport.Jan 22, 2002 · N29406 · Substantial damage