NTSB investigations: Cessna 170B, 2002

6 cases on aircraft the registry lists as Cessna 170B, where the first occurrence was “Loss of control - on ground/water”. 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

19822026
NTSB investigations: Cessna 170B, 2002 per year, 1982–2026: 125 cases
19827
19838
19848
19856
19865
19876
19884
19893
19905
19914
19923
19938
19941
19952
19966
19974
19986
19995
20005
20012
20026
20033
20044
20056
20066
20072

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\") = 2002
    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')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 260))
  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 LAX03LA042Accident · No injuriesLimited investigationFinal reportCessna 170B · Mobile, AZthe pilot's improper compensation for the crosswind conditions at touchdown and failure to maintain proper alignment of the tail wheel equipped airplane during landing, which resulted in a ground loop. The crosswind was a contributory factor.Nov 28, 2002 · N4465B · Substantial damageNTSB ANC02LA096Accident · No injuriesLimited investigationFinal reportCessna 170 · Soldotna, AKThe pilot's inadequate recovery from a bounced landing, and his failure to maintain directional control of the airplane. A factor contributing to the accident was the pilot's excessive braking which resulted in a nose over.Aug 15, 2002 · N2558D · Substantial damageNTSB LAX02LA245Accident · No injuriesLimited investigationFinal reportCessna 170B · St. Johns, AZthe pilot's selection of the wrong runway for the existing crosswind condition and his subsequent inadequate compensation for the winds, which led to a failure to maintain directional control and a ground loop.Aug 1, 2002 · N2233D · Substantial damageNTSB ANC02LA032Accident · No injuriesLimited investigationFinal reportCessna 170B · Anchorage, AKThe failure of the pilot to maintain directional control during takeoff. A factor associated with the accident was an inadvertent ground loop.May 12, 2002 · N7608B · Substantial damageNTSB LAX02LA159Accident · No injuriesLimited investigationFinal reportCessna 170B · San Diego, CAThe failure of the dual student to maintain directional control of the airplane and the instructor's delayed the remedial action, which resulted in a ground loop. A factor in the accident was the gusting crosswind conditions.May 11, 2002 · N3462C · Substantial damageNTSB ATL02LA080Accident · No injuriesLimited investigationFinal reportCessna 170B · Ocala, FLThe pilot's failure to maintain directional control on landing roll, resulting in a loss of control/ground loop.Apr 8, 2002 · N3470C · Substantial damage