NTSB investigations: Cessna 172S

9 cases on aircraft the registry lists as Cessna 172S, where the first occurrence was “In flight collision with terrain/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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

20002026

NTSB investigations: Cessna 172S per year, 2000–2026: 9 cases
2000	2
2002	2
2003	1
2004	1
2005	2
2006	1

Where

Open the map

Latest cases

Query with SQL

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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442') 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" = 230)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442')
      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\" = 230))
  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.

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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442')
    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" = 230))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB DFW07FA019Accident · 2 fatalField investigationFinal reportCessna 172S · Hominy, OKThe pilot's continued cruise flight into adverse weather conditions, and his failure to maintain clearance from terrain. Contributing factors were the dark night conditions, and the low ceilings.Nov 5, 2006 · N53443 · Destroyed NTSB LAX06FA059Accident · 1 fatalField investigationFinal reportCessna 172S · Hana, HICollision with mountainous terrain for undetermined reasons.Dec 16, 2005 · N542SP · Substantial damage NTSB LAX05CA137Accident · No injuriesData collectionFinal reportCessna 172S · Gallup, NMthe pilot's premature liftoff and inadequate remedial action, which resulted in the airplane inadvertently recontacting the runway.Apr 12, 2005 · N520ER · Substantial damage NTSB FTW04CA224Accident · Minor injuriesData collectionFinal reportCessna 172S · Leakey, TXThe pilot's failure to maintain clearance with terrain. A contributing factor was the high density altitude.Aug 28, 2004 · N2477E · Substantial damage NTSB LAX04LA054Accident · No injuriesLimited investigationFinal reportCessna 172S · Wikieup, AZThe pilot's selection of an en route altitude that did not provide adequate terrain clearance, and resulted in the in-flight collision with terrain. The rising terrain and the blind/box canyon were contributing factors.Nov 29, 2003 · N518ER · Substantial damage NTSB SEA02FA185Accident · 2 fatalField investigationFinal reportCessna 172S · Medford, ORTerrain clearance was not maintained during cruise flight. Dark night and mountainous terrain were factors.Sep 30, 2002 · N514SP · Substantial damage NTSB FTW02LA068Accident · No injuriesLimited investigationFinal reportCessna 172S · Sugar Land, TXthe student pilot's failure to maintain directional control during landing.Jan 12, 2002 · N497SJ · Substantial damage NTSB ANC00FA082Accident · 1 fatalField investigationFinal reportCessna 172S · Whittier, AKSuicide.Jul 4, 2000 · N862SP · Destroyed NTSB CHI00LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Near Muskegon, MIthe pilot failed to maintain altitude after inadvertently flying to instrument meteorological conditions. Factors associated with the accident were the low ceilings and visibility, the pilot became disoriented after inadvertently flying into IMC, and the…Apr 15, 2000 · N560SP · Substantial damage