NTSB investigations: Cessna 172K

8 cases on aircraft the registry lists as Cessna 172K, where the first occurrence was “Airframe/component/system failure/malfunction”. 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

19832026

NTSB investigations: Cessna 172K per year, 1983–2026: 8 cases
1983	1
1985	1
1988	1
1993	1
1996	1
2000	1
2007	2

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 ('2072430') 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" = 130)) 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 ('2072430')
      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\" = 130))
  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 ('2072430')
    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" = 130))
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 DFW07LA130Accident · No injuriesLimited investigationFinal reportCessna 172K · Amarillo, TXThe failure of the left main landing gear spring assembly as a result of an unapproved repair by an unknown person(s), which resulted in a loss of directional control during the landing roll.Jun 7, 2007 · N7370G · Substantial damage NTSB ATL07CA058Accident · No injuriesData collectionFinal reportCessna 172K · Cornelia, GAThe failure of the owner/operator to repair or replace a known leaking brake system components resulting in a total loss of brakes while taxing and an on-ground collision with trees.Mar 22, 2007 · N46567 · Substantial damage NTSB SEA00LA194Accident · No injuriesLimited investigationFinal reportCessna 172K · Burns, ORThe separation of a portion of one propeller blade as a result of a fatigue crack that initiated at the site of foreign object damage to the blade.Sep 28, 2000 · N84034 · Substantial damage NTSB ATL96LA059Accident · No injuriesLimited investigationFinal reportCessna 172K · Asheville, NCfailure of the brake on the right main landing gear as a result of water (ice) in the brake fluid, which resulted in a loss of braking control.Mar 9, 1996 · N79058 · Substantial damage NTSB FTW94LA013Accident · No injuriesLimited investigationFinal reportCessna 172K · Jacksonville, TXThe pilot's failure to follow proper emergency procedures to troubleshoot the electrical system. A factor was an electrical system irregularity of an undetermined nature.Oct 16, 1993 · N7825T · Substantial damage NTSB ATL88LA115Accident · No injuriesLimited investigationFinal reportCessna 172K · Butler, ALThe plt rptd that he observed the engine oil pressure indication drop to zero during a low-level pipeline patrol flight. He attempted to increase engine pwr and initiate a climb, but the engine began to run rough. He subsequently landed on the pipeline…Mar 15, 1988 · N78840 · Substantial damage NTSB NYC86LA043Accident · Minor injuriesLimited investigationFinal reportCessna 172K · Bloomsburg, PAThe acft was on an IFR flt en route to allegheny county arpt at 6000 ft when an electrical failure occurred. The plt executed a precautionary landing in a muddy fld. The nose wheel caught in mud and the acft nosed over. Examination of the electrical system…Nov 28, 1985 · N7506G · Substantial damage NTSB ATL83LA384Accident · No injuriesLimited investigationFinal reportCessna 172K · Brundidge, ALWhile cruising at 2,000 ft the plt smelled fuel fumes & elected to make a precautionary landing. When within gliding distance of the arpt, he secured the eng with the mixture control & made an uneventful deadstick landing. After exiting the acft he noticed…Sep 29, 1983 · N79025 · Destroyed