NTSB investigations: Cessna 172F, 1998

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, 1998 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\") = 1998
    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 CHI99FA042Accident · 2 fatalField investigationFinal reportCessna 172F · Coleman, WIpilot's failure to maintain clearance from the trees and his intentional flight into IMC conditions. Factors contributing to this accident were the pilot's lack of instrument certification, his becoming lost in the poor weather, his inadequate preparation for…Nov 29, 1998 · N72RE · DestroyedNTSB ATL99LA001Accident · No injuriesLimited investigationFinal reportCessna C-172F · Ball Ground, GAThe pilots failure to maintain directional control of the airplane on take-off, during gusty conditions, resulting in a collision with a tree.Oct 1, 1998 · N5588R · Substantial damageNTSB LAX98LA301Accident · No injuriesLimited investigationFinal reportCessna 172F · Long Beach, CAThe pilot's misjudging the flare point and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing. A contributing factor was the dark night conditions.Sep 21, 1998 · N8761U · Substantial damageNTSB MIA98LA233Accident · No injuriesLimited investigationFinal reportCessna 172F · Spring Hill, FLThe pilot's misjudgment of distance and his delay in initiating a go around. Contributing was the pilot's improper landing flare.Aug 30, 1998 · N7832U · Substantial damageNTSB MIA98LA216Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Tuskegee, ALThe pilot's failure to attain adequate airspeed, and his failure to abort the takeoff.Aug 2, 1998 · N7884U · Substantial damageNTSB MIA98WA203Accident · Serious injuriesForeign investigationCessna 172F · Grand Turk, United KingdomJul 18, 1998 · N5682R · No damageNTSB FTW98LA166Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Collins, COthe pilot's improper in flight planning/decision in electing to land with a known 30 knot tailwind. Factors were high winds and a tailwind.Mar 31, 1998 · N7894U · Substantial damage