NTSB investigations: Cessna 175

8 cases on aircraft the registry lists as Cessna 175, where the first occurrence was “Overrun”. 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

19822026

NTSB investigations: Cessna 175 per year, 1982–2026: 8 cases
1982	1
1983	1
1984	1
1987	1
1995	1
1996	1
1998	1
2004	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 ('2072502') 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" = 340)) 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 ('2072502')
      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\" = 340))
  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 ('2072502')
    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" = 340))
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 CHI04LA137Accident · Minor injuriesLimited investigationFinal reportCessna 175 · Blissfield, MIThe pilot selected the wrong runway on which to land which resulted in exceeding the proper touchdown point during landing. Factors associated with the accident were the tailwind condition and the drainage ditch which the airplane contacted.Jun 4, 2004 · N9401B · Substantial damage NTSB SEA98LA041Accident · No injuriesLimited investigationFinal reportCessna 175 · Port Townsend, WAThe pilot's misjudged distance and speed during landing. A factor was the wet grass runway.Feb 26, 1998 · N7620M · Substantial damage NTSB ATL97LA019Accident · Minor injuriesLimited investigationFinal reportCessna 175 · Soperton, GAfailure of the pilot either to attain the proper touch down point for landing or to abort the landing while there was sufficient runway remaining. The terrain (ditch) at the end of the runway was a related factor.Nov 26, 1996 · N7582M · Substantial damage NTSB FTW96LA032Accident · No injuriesLimited investigationFinal reportCessna 175 · Deer, ARThe pilot's selection of a downwind runway for landing. Factors were the tailwind and the pilot's misinterpretation of the wind conditions.Oct 22, 1995 · N7421M · Substantial damage NTSB ATL87LA196Accident · Serious injuriesLimited investigationFinal reportCessna 175 · Sebring, OHPlt and his two pax had spent most of the day at barber apt preparing for the fireman's bbq to be held later. In late afternoon, they decided to take a flt around the area. During the flt, it was decided to land at the tri-city apt. Witnesses reptd that the…Jul 3, 1987 · N7659M · Substantial damage NTSB SEA85LA033Accident · No injuriesLimited investigationFinal reportCessna 175 · Indian Meadows, IDLanded long and acft slid off end of rwy on compact snow and ice contacting a snow berm near end of rwy.Nov 17, 1984 · N7380M · Substantial damage NTSB MIA84LA008Accident · No injuriesLimited investigationFinal reportCessna 175 · Ft. Mccoy, FLAbout 10 min after departing ft Mccoy, FL, the plt realized he had forgotten his flt bag, so he returned to land at the airstrip. During the landing, the acft floated, & after touching down, there was insufficient rwy remaining to safely stop or go around.…Oct 8, 1983 · N6511E · Substantial damage NTSB CHI82DA103Accident · Minor injuriesFinal reportCessna 175 · Tuscola, ILA landing was made on runway 27 just prior to sunset. The pilot reported that he realized he was not slowing fast enough, but due to the low altitude of the setting sun, he misjudged the length of the runway. He initiated a go-around, but did not obtain…Mar 27, 1982 · N7452M · Destroyed