NTSB investigations: Cessna 172K, 1990

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

19672026
NTSB investigations: Cessna 172K, 1990 per year, 1967–2026: 691 cases
19671
19683
196929
197048
197166
197252
197343
197440
197521
197630
197729
197825
197915
198012
198113
198211
19836
19845
19857
19866
198712
19889
19895
19907
199111
19924
19937
199412
19956
199612
19975
19986
19996
200010
20015
20028
200310
20047
20054
20062
20078
20083
20091
20104
20116
20126
20135
20147
20152
20166
20171
20182
20198
20201
20213
20224
20234
20244
20254
20262

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\") = 1990
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
  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 LAX91LA043Accident · No injuriesLimited investigationFinal reportCessna 172 · Tonopah, NVThe airplane's encounter with a wind gust while taxiing from landing. Contributing factors related to the pilot's improper weather evaluation and his lack of experience in making weather evaluations.Nov 26, 1990 · N79551 · Substantial damageNTSB FTW91LA019Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Granbury, TXTotal loss of engine power due to fuel exhaustion. Factors were the pilot's improper fuel consumption calculations, and the darkness of the night.Nov 26, 1990 · N46383 · Substantial damageNTSB DEN90LA163Accident · No injuriesLimited investigationFinal reportCessna 172 · Grants, NMThe pilot's failure to maintain directional control.Jul 16, 1990 · N46593 · Substantial damageNTSB SEA90FA091Accident · 1 fatalField investigationFinal reportCessna 172K · Tacoma, WAThe pilot did not adequately maintain a proper glide path for landing which resulted in an inflight collision with a tree.Jun 3, 1990 · N79931 · DestroyedNTSB MIA90FA118Accident · 2 fatalField investigationFinal reportCessna 172K · Mayaguez, PRThe pilot's failue to conduct proper preflight preparations, resulting in a takeoff at 175 pounds over maximum allowable gross weight, with full flaps extended, and on the improper runway for wind conditions which resulted in the airplane being unable to…May 10, 1990 · N7268G · DestroyedNTSB ANC90FA053Accident · No injuriesField investigationFinal reportCessna 172-K · Anchorage, AKPilot-in-command used poor judgement when he elected to take off on rough & uneven frozen lake which resulted in a failed nose ski.Apr 12, 1990 · N46410 · Substantial damageNTSB ATL90LA085Accident · No injuriesLimited investigationFinal reportCessna 172K · Columbus, OHImproper planning/decision by the pilot. A factor related to the accident was: the adverse wind condition.Mar 22, 1990 · N7275G · Substantial damage