OpenAirDocs.org

NTSB investigations: Cessna 182L

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

Cases per year

19822026

Where

Open the map

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

NTSB ATL06CA109Accident · No injuriesData collectionFinal reportCessna 182L · Eatonton, GAThe CFI's failure to initiate a go-around when he noticed the flight was high during approach resulting in the flight landing long, overrunning the runway , and colliding with trees. Factors in the accident were a wet runway and a tailwind for landing.Jul 22, 2006 · N3415R · Substantial damageNTSB CHI03LA169Accident · Minor injuriesLimited investigationFinal reportCessna 182L · Atchison, KSThe pilot's inadequate inflight decision, which resulted in a landing with a tailwind and an overrun of the runway. Factors contributing to the accident were the tailwind encountered on landing rollout, the variable, gusty winds encountered while in the…Jun 19, 2003 · N42713 · Substantial damageNTSB CHI98LA246Accident · No injuriesLimited investigationFinal reportCessna 182L · Mackinac Island, MIThe pilot's failure to attain a stabilized approach and a touchdown point. The factors contributing to the accident were the pilot in command's improper use of flaps and his not performing a go-around. An additional factor was the pilot in command not using…Jul 10, 1998 · N42184 · Substantial damageNTSB ATL91LA151Accident · No injuriesLimited investigationFinal reportCessna 182L · Macon, NCThe pilot's failure to accurately judge the distance required to stop the airplane. A factor in the accident was the wet, grass runway surface at the time of the accident.Aug 2, 1991 · N3146R · Substantial damageNTSB LAX86LA257Accident · No injuriesLimited investigationFinal reportCessna 182L · Lodi, CAA acft collided with a gravel pile after overrunning the 2,070 ft asphalt rwy. The plt indicated that the wind sock at the arpt was indicating a variable wind direction from 200 deg to 230 deg. The plt elected to land on rwy 12. He stated he would have had…Jun 14, 1986 · N3496R · Substantial damageNTSB ATL83LA258Accident · No injuriesLimited investigationFinal reportCessna 182L · Charlotte, NCThe acft ran off the departure end of the rwy during landing. The wind was light and variable to calm. The plt used aerodynamic braking until it was too late to go around. When he applied the brakes he found that they were spongy and ineffectual. An after…Jul 7, 1983 · N70517 · Substantial damageNTSB ATL82DA045Accident · No injuriesFinal reportCessna 182L · Conyers, GAThe destination airport is a private strip that is oriented on a 150/330 degree heading. The northwest end is enclosed by tall trees. Accordingly, most landings are made toward the northwest regardless of wind direction. The pilot landed on runway 33 which…Jan 30, 1982 · N42042 · Substantial damage