NTSB investigations: Cessna 172L, 1999

7 cases on aircraft the registry lists as Cessna 172L. 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

19702026
NTSB investigations: Cessna 172L, 1999 per year, 1970–2026: 414 cases
19702
197117
197234
197340
197428
197523
197617
197719
197817
19795
19808
19817
19825
19832
19845
19856
19864
19873
198811
19894
19908
19911
19926
19933
19947
19956
19967
19972
19986
19997
20006
20019
20024
20035
20045
20059
20067
20075
20084
20092
20101
20111
20121
20134
20141
20153
20161
20173
20186
20194
20201
20211
20224
20233
20245
20255
20264

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\") = 1999
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072432'))
  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 FTW00LA055Accident · No injuriesLimited investigationFinal reportCessna 172L · New Orleans, LAThe pilot's inadvertent starting of the engine. Factors were the pilot's failure to set the mixture control to the off position, and the intermittent short in the starter switch.Dec 28, 1999 · N172GT · Substantial damageNTSB NYC00LA049Accident · No injuriesLimited investigationFinal reportCessna 172L · Wooster, OHThe pilot's inadvertent taxi onto unsuitable terrain. A factor was the burnt out landing/taxi light.Dec 8, 1999 · N7565G · Substantial damageNTSB CHI99LA237Accident · No injuriesLimited investigationFinal reportCessna 172L · Montezuma, IAthe pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.Jul 14, 1999 · N19752 · Substantial damageNTSB NYC99LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Mattituck, NYThe pilot's failure to maintain control of the airplane, and the flight instructor's inadequate supervision of the solo flight.Jul 8, 1999 · N7164Q · Substantial damageNTSB NYC99LA149Accident · No injuriesLimited investigationFinal reportCessna 172L · Millinocket, METhe total loss of engine power for undetermined reasons.Jun 16, 1999 · N7897G · Substantial damageNTSB DEN99LA085Accident · No injuriesLimited investigationFinal reportCessna 172L · Gunnison, COThe pilot's inadvertent stall/mush immediately after takeoff. Factors were the high density altitude weather condition, and the pilot's total lack of experience in type of operation.May 25, 1999 · N172KB · Substantial damageNTSB LAX99LA082Accident · No injuriesLimited investigationFinal reportCessna 172L · Santa Paula, CAThe instructor pilot's misjudged altitude and speed, which resulted in a failure to attain the proper touchdown point causing an overrun and collision with a block wall. A factor was the wet runway, which may have hindered brake effectiveness.Jan 26, 1999 · N7639G · Substantial damage