NTSB investigations: Cessna 170B, 2006

14 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, 2006 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\") = 2006
    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 SEA07LA020Accident · No injuriesLimited investigationFinal reportCessna 170B · Billings, MTThe flight instructor's inadequate remedial action to maintain directional control, which resulted in a ground loop/swerve during takeoff roll. A factor was the failure of the pilot who was receiving instruction to maintain directional control.Nov 18, 2006 · N2619D · Substantial damageNTSB NYC06LA216Accident · Serious injuriesLimited investigationFinal reportCessna 170B · Hampton, NHThe pilot's failure to maintain directional control during takeoff.Sep 4, 2006 · N1857C · Substantial damageNTSB LAX06CA219Accident · Minor injuriesData collectionFinal reportCessna 170B · Vacaville, CAthe pilot's failure to maintain directional control. A contributing factor was pilot fatigue.Jun 28, 2006 · N2924D · Substantial damageNTSB SEA06CA106Accident · No injuriesData collectionFinal reportCessna 170B · West Glacier, MTThe pilot's failure to attain sufficient airspeed for flight, his attempt to abort the takeoff, and the airplane's subsequent departure off the end of the runway. Contributing factors were the impacted fence and vegetation, and his total lack of experience in…May 21, 2006 · N3477C · Substantial damageNTSB ANC06CA050Accident · No injuriesData collectionFinal reportCessna 170B · Chickaloon, AKThe pilot's selection of unsuitable terrain for landing, which resulted in a nose over during the landing roll. A factor associated with the accident was the snow on the runway.May 7, 2006 · N2396D · Substantial damageNTSB MIA06CA100Accident · No injuriesData collectionFinal reportCessna 170B · Fort Pierce, FLThe failure of the pilot-in-command to maintain directional control during the landing roll.Apr 28, 2006 · N2891C · Substantial damageNTSB LAX06CA145Accident · No injuriesData collectionFinal reportCessna 170B · Redlands, CAthe student's inadequate compensation for the crosswind gust and failure to maintain directional control. Also causal was the flight instructor's inadequate supervision of the flight, and his failure to maintain directional control. A factor was control…Apr 23, 2006 · N3190A · Substantial damageNTSB ANC06FA048Accident · 5 fatalField investigationFinal reportCessna 170B · Chugiak, AKThe inadequate visual lookout by the pilots of both airplanes during cruise flight, which resulted in their failure to see-and-avoid each other, and a subsequent midair collision.Apr 23, 2006 · N4488B · 2 aircraft · DestroyedNTSB SEA06CA078Accident · No injuriesData collectionFinal reportCessna 170B · Shelton, WAThe main landing gear wheel failure during the takeoff ground roll. A related factor was directional control of the aircraft was not possible after the wheel failure.Apr 18, 2006 · N2886C · Substantial damageNTSB SEA06LA077Accident · Serious injuriesLimited investigationFinal reportCessna 170B · Clark Fork, IDThe pilot's failure to maintain aircraft control during a go-around. A quartering tailwind was a factor.Apr 17, 2006 · N2288D · Substantial damageNTSB SEA06CA073Accident · No injuriesData collectionFinal reportCessna 170B · Havre, MTThe pilot's improper starting procedures in attempting to hand-prop the airplane's engine. Contributing factors were the discharged battery, the failure of the right parking brake and the hangar which the aircraft collided with.Apr 10, 2006 · N2831C · Substantial damageNTSB DEN06CA054Accident · No injuriesData collectionFinal reportCessna 170B · Benton, KSthe pilot's failure to maintain directional control of the airplane resulting in a ground loop. Contributing factors include the inadequate preflight inspection, the pilot's failure to properly latch the cowling, and the pilot's diverted attention to the open…Mar 31, 2006 · N2359J · Substantial damageNTSB ANC06CA040Accident · No injuriesData collectionFinal reportCessna 170B · Palmer, AKThe pilot's selection of unsuitable terrain for landing, which resulted in the airplane nosing over during the landing roll. A factor associated with the accident was the snow covered terrain.Mar 27, 2006 · N2947D · Substantial damageNTSB DEN06CA032Accident · Minor injuriesData collectionFinal reportCessna 170B · Ulysses, KSthe pilot's failure to maintain directional control during the landing, resulting in a ground loop.Jan 7, 2006 · N2912D · Substantial damage