NTSB investigations: Cessna 170B, 1995

8 cases on aircraft the registry lists as Cessna 170B. 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 170B, 1995 per year, 1964–2026: 1,115 cases
196477
196567
196661
196746
196848
196931
197036
197144
197235
197332
197435
197535
197627
197722
197828
197922
198012
198116
198215
198313
198416
198515
198615
198717
198811
198911
199010
199112
19927
199313
19945
19958
199617
199715
199812
199911
200010
20019
200211
200310
200412
20059
200614
20075
20083
200913
20109
20114
20126
201312
201411
20159
20163
20177
20188
20197
20207
20217
20224
20236
20248
20258
20266

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 ('2072306', '2072307'))
  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 SEA96LA030Accident · No injuriesLimited investigationFinal reportCessna 170B · John Day, ORThe pilot's failure to maintain a proper glidepath.Dec 16, 1995 · N3171B · Substantial damageNTSB FTW96LA038Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Reklaw, TXThe loss of engine power for undetermined reasons. A factor was the lack of suitable terrain for the forced landing.Oct 29, 1995 · N3152A · Substantial damageNTSB CHI96LA016Accident · Minor injuriesLimited investigationFinal reportCessna 170B · Oconomowoc, WIa loss of engine power for undetermined reasons. A factor associated with the accident was the unsuitable terrain on which to make the forced landing.Oct 25, 1995 · N4555C · Substantial damageNTSB ATL95LA166Accident · No injuriesLimited investigationFinal reportCessna 170 · Hartwell, GAThe pilot's failure to maintain directional control during the takeoff roll and failure to take appropriate remedial action. A factor was trees.Sep 9, 1995 · N8233E · Substantial damageNTSB MIA95LA198Accident · No injuriesLimited investigationFinal reportCessna 170B · Titusville, FLLoss of directional control during the landing roll. Contributing to the accident was the pilot's limited experience in the make and model airplane.Aug 9, 1995 · N2715D · Substantial damageNTSB SEA95LA150Accident · No injuriesLimited investigationFinal reportCessna 170B · Afton, WYDirectional control was not maintained. Factors to the accident were: inadequate remedial action and a stall not identified.Jul 17, 1995 · N3165B · Substantial damageNTSB ANC95LA076Accident · No injuriesLimited investigationFinal reportCessna 170B · Gulkana, AKThe pilot's failure to maintain directional control during the landing roll.Jun 15, 1995 · N4512C · Substantial damageNTSB ANC95LA053Accident · No injuriesLimited investigationFinal reportCessna 170B · Chickaloon, AKThe fracture of the crankshaft resulting in separation of the propeller and propeller flange in-flight. A factor associated with the accident was the lack of suitable terrain for an emergency landing.May 12, 1995 · N4366B · Substantial damage