NTSB investigations: Cessna 170A, 1989

6 cases on aircraft the registry lists as Cessna 170A. 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 170A, 1989 per year, 1964–2026: 457 cases
196422
196518
196620
196728
196822
196921
197018
197115
197213
197317
197419
197515
19766
197713
197813
197911
19807
19818
19826
19838
19842
19857
19863
19879
19885
19896
19907
19914
19925
19932
19944
19952
19964
19975
19987
19993
20001
20014
20023
20037
20043
20051
20063
20076
20083
20093
20102
20115
20123
20132
20141
20154
20164
20176
20181
20203
20215
20222
20232
20245
20252
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 ('2072304'))
  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 MIA90FA031Accident · 2 fatalField investigationFinal reportCessna 170A · Rogersville, TNContinued flight into instrument meteorological conditions by a non-instrument rated pilot resulting in spatial disorientation and a loss of aircraft control. Factors contributing to the accident were: the pilot's overconfidence in his ability to fly in…Nov 26, 1989 · N9192A · DestroyedNTSB ATL90LA004Accident · No injuriesLimited investigationFinal reportCessna 170 · Mooresville, NCImproper in-flight planning/decision by the pilot, which resulted in his failure to attain the proper toughdown point on the unidirectional runway. Factors related to the accident were: the unfavorable wind and terrain conditions.Oct 8, 1989 · N11575 · Substantial damageNTSB CHI89LA159Accident · No injuriesLimited investigationFinal reportCessna 170A · Brookfield, WIThe pilot-in-command's failure to take proper corrective action after encountering a wind gust on landing.Aug 4, 1989 · N9762A · Substantial damageNTSB DEN89LA111Accident · No injuriesLimited investigationFinal reportCessna 170A · Kalispell, MTThe pilot's failure to maintain control of the airplane during the landing flare and rollout. Contributing to the accident was the pilot's lack of proficiency with only 4 hours of flight time in the preceding 90 day period.Apr 19, 1989 · N5414C · Substantial damageNTSB BFO89LA025Accident · No injuriesLimited investigationFinal reportCessna 170A · Ravenswood, WVThe pilots decision to land with a tailwind and inadequately compensating for the wind conditions.Mar 23, 1989 · N9187A · Substantial damageNTSB NYC89LA060Accident · Minor injuriesLimited investigationFinal reportCessna 170A · Speculator, NYInaccurate inflight planning and decisions by the pilot who inadvertently flew his aircraft from VFR into instrument meteorological conditions while making a descent at night.Jan 1, 1989 · N1432D · Destroyed