NTSB investigations: Cessna 172F, 1995

8 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, 1995 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\") = 1995
    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 CHI96LA006Accident · No injuriesLimited investigationFinal reportCessna 172F · Danbury, WIthe partial failure of the left magneto, the road sign, and the road embankment. A factor relating to this accident is the brush which obscured the road sign.Oct 11, 1995 · N8740U · Substantial damageNTSB LAX95LA295Accident · No injuriesLimited investigationFinal reportCessna 172F · Bradley, CAfuel exhaustion due to the pilot's failure to refuel prior to takeoff and his delayed decision to proceed to his alternate airport. The night light conditions and the lack of a suitable emergency landing area were factors.Aug 15, 1995 · N5563R · Substantial damageNTSB CHI95LA252Accident · No injuriesLimited investigationFinal reportStevens Acro II · Oshkosh, WIthe failure of the pilot of the Acro II, N40LF, to maintain clearance from the Cessna 172, N5542R.Jul 31, 1995 · N40LF · 2 aircraft · Minor damageNTSB CHI95LA230Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Wyandotte, INthe number three intake valve became stuck (seized), which resulted in a loss of engine power. The lack of suitable terrain for a forced landing was a related factor.Jul 22, 1995 · N8599U · Substantial damageNTSB SEA95LA131Accident · No injuriesLimited investigationFinal reportCessna 172F · Homedale, IDThe pilot misjudged distance and altitude during the approach. The downdraft was a factor.Jun 27, 1995 · N4298C · Substantial damageNTSB LAX95LA193Accident · No injuriesLimited investigationFinal reportCessna 172F · Boonville, CAa loss of engine power for undetermined reasons.May 26, 1995 · N5255F · Substantial damageNTSB BFO95FA050Accident · 1 fatalField investigationFinal reportCessna 172F · Tappahanock, VAThe student pilot's misjudgment of distance/speed during the approach to land, and her failure to go around while there was still sufficient runway remaining. Factors related to the accident were: inadequate supervision by the flight instructor, the student's…May 12, 1995 · N5238F · DestroyedNTSB ATL95FA079Accident · 1 fatalField investigationFinal reportCessna 172F · Seneca, SCThe pilot's inadequate visual lookout while maneuvering near utility lines, which resulted in a collision with the wires.Apr 9, 1995 · N8197U · Substantial damage