NTSB investigations: Cessna 172N, OR

5 cases on aircraft the registry lists as Cessna 172N, where the first occurrence was “In flight collision with object”. 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 172N, OR per year, 1982–2026: 5 cases
19821
19841
19951
19971
20021

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 c.\"eventStateOrRegion\" = 'OR' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072434')
      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\" = 220))
  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 SEA02FA125Accident · 2 fatalField investigationFinal reportCessna 172N · Otis, ORThe pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines.Jul 6, 2002 · N738QT · DestroyedNTSB SEA97LA059Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Madras, ORThe pilot's inadvertent visual flight rules (VFR) flight into instrument meteorological conditions (IMC). Factors include the pilot's improper decision to fly under a low ceiling while in mountainous/hilly terrain, and his encounter with fog and low clouds…Feb 7, 1997 · N5618J · Substantial damageNTSB SEA96LA035Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacific City, ORThe pilot's delay in aborting the landing, which resulted in his failure to clear the perimeter fence. Factors relating to the accident were: the tailwind, and the pilot's failure to land at the proper touchdown point.Dec 24, 1995 · N738ME · Substantial damageNTSB SEA84FYK01Accident · Serious injuriesFinal reportCessna 172N · Creswell, ORThe acft collided with wires during an attempted go-around. The plt stated that he had made one go-around and on the 2NDLANDING attempt he landed hard in gusty wind & bounced. During the 2nd go-around he collided with wires & crashed.Aug 11, 1984 · N3278E · DestroyedNTSB SEA82FYM24Accident · 2 fatalFinal reportCessna 172P · 3nm Se Scappoos, ORThe acft struck & severed power lines strung between two 90-foot towers located about 1500 feet apart. The power lines were about 50 to 60 feet above the water at the lowest point of the line sag.Sep 15, 1982 · N7335F · Destroyed