NTSB investigations: Cessna 172F, 1989

7 cases on aircraft the registry lists as Cessna 172F. 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

19642026
NTSB investigations: Cessna 172F, 1989 per year, 1964–2026: 563 cases
19642
196560
196657
196747
196824
196914
197024
197123
197221
197319
197410
197516
197615
197715
197810
197910
19803
198113
19826
19836
19847
19855
19867
19875
198810
19897
19903
19924
19936
19947
19958
19967
19974
19987
19993
20001
20015
20024
20034
20043
20055
20064
20072
20083
20092
20101
20114
20122
20133
20143
20153
20163
20172
20181
20197
20202
20213
20224
20231
20242
20253
20261

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\") = 1989
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072414'))
  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 ATL89FA163Accident · 1 fatalField investigationFinal reportCessna 172F · Vernon, ALImproper maintenance of the spark plugs by the pilot/mechanic which resulted in a partial loss of engine power, and the pilot's failure to clear trees during an emergency landing in an open field resulting in an inadvertent stall.Jun 17, 1989 · N7939U · Substantial damageNTSB ATL89LA132Accident · No injuriesLimited investigationFinal reportCessna 172F · Elkin Arpt., NCThe failure of the pilot to properly compensate for the gusty wind conditions during takeoff and the delay in his decision to abort the takeoff before colliding with trees. Contributing to the accident were the gusty wind conditions and the pilot's lack of…Apr 23, 1989 · N7908U · Substantial damageNTSB DEN89LA105Accident · No injuriesLimited investigationFinal reportCessna 172F · Morgan, UTInadequate servicing of the aircraft by the pilot, partial blockage of the fuel line and fuel filter, and fuel starvation. Contributing factors were: the downward sloping runway and a fence.Apr 10, 1989 · N7847U · Substantial damageNTSB NYC89LA102Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Honesdale, PAThe loss of directional control by the pilot during landing.Mar 16, 1989 · N5517R · Substantial damageNTSB FTW89LA060Accident · No injuriesLimited investigationFinal reportCessna 172 · Jacksboro, TXFailure of the pilot to go around, when she did not attain the proper touchdown point (landed long) and had excessive airspeed to stop on the runway. A factor related to the accident was the unfavorable wind condition (sudden wind shift).Feb 26, 1989 · N8643U · Substantial damageNTSB LAX89FA113Accident · 1 fatalField investigationFinal reportCessna 172F · Safford, AZFailure of the pilot to maintain proper airspeed while on final approach resulting in an aerodynamic stall. Contributing to the accident was the pilot's delayed use of wing flaps.Feb 18, 1989 · N8492U · DestroyedNTSB BFO89LA017Accident · Serious injuriesLimited investigationFinal reportCessna 172F · Bruceton Mills, WVThe power loss occurred because of carburetor ice which obstructed airflow to the induction system. Contributing to the accident was the carburetor icing conditions, the highway and the ditch which was contacted.Jan 31, 1989 · N8264U · Destroyed