NTSB investigations, 2001
36 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 131 |
|---|---|
| 1983 | 132 |
| 1984 | 124 |
| 1985 | 86 |
| 1986 | 59 |
| 1987 | 77 |
| 1988 | 65 |
| 1989 | 62 |
| 1990 | 66 |
| 1991 | 51 |
| 1992 | 69 |
| 1993 | 70 |
| 1994 | 62 |
| 1995 | 75 |
| 1996 | 60 |
| 1997 | 52 |
| 1998 | 46 |
| 1999 | 50 |
| 2000 | 42 |
| 2001 | 36 |
| 2002 | 46 |
| 2003 | 53 |
| 2004 | 48 |
| 2005 | 47 |
| 2006 | 41 |
| 2007 | 31 |
Where
Open the mapLatest 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\") = 2001
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE 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 year(c."eventDate") = 2001 AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE 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 IAD02LA021Accident · No injuriesLimited investigationFinal reportCessna 208B · Lewiston, METhe pilot's failure to adequately ensure the wings were free of contamination prior to departure. Factors included the operator's inadequate de-icing procedures and the snowy weather conditions.NTSB CHI02LA054Accident · No injuriesLimited investigationFinal reportCessna 182K · Nashville, MIthe pilot exceeding the proper touchdown point on the runway during the landing and his improper in-flight planning and decision. Factors relating to the accident were the pilot misjudging his speed and distance during the landing and the ditch.NTSB LAX02FA028Accident · 2 fatalField investigationFinal reportCessna 340A · Santa Monica, CAThe pilot's failure to remove the control gust lock prior to takeoff and his failure to abort the takeoff with sufficient runway remaining to stop the airplane on the runway.NTSB CHI02LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · New Ulm, MNThe student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student not attaining the proper touchdown point and the plowed…NTSB ATL02LA002Accident · Minor injuriesLimited investigationFinal reportBeech 19 · St Clair Spring, ALThe pilot misjudged the touchdown point that resulted in the runway overrun.NTSB CHI01LA315Accident · No injuriesLimited investigationFinal reportCessna 182M · Marshall, WIThe pilot misjudged his altitude and airspeed and landed long. A factor was the wet grass.NTSB NYC01LA225Accident · No injuriesLimited investigationFinal reportSchweizer SGS 1-35 · Cumberland, MDThe pilot misjudged distance and altitude. A factor was the pilot's lack of familiarity with the glider.NTSB ANC01LA133Accident · No injuriesLimited investigationFinal reportPiper PA-12 · Tok, AKThe pilot's failure to abort the landing. Factors associated with the accident were the pilot's selection of an unsuitable landing area, and his failure to attain a proper touchdown point. An additional factor was a ditch.NTSB IAD01LA103Accident · No injuriesLimited investigationFinal reportCessna U206G · Millersburg, OHThe pilot's misjudgment of speed and distance, which resulted in an overrun during landing. Factors were the short, wet, grass runway, and his failure to do a go-around.NTSB CHI01LA299Accident · No injuriesLimited investigationFinal reportBeech 58P · Theodosia, MODiminished braking action due to standing water on the runway. A factor associated with the accident was the ditch which the airplane contacted.NTSB NYC01LA216Accident · No injuriesLimited investigationFinal reportCessna 182R · Elizabethtown, KYThe pilot's improper decision to fly the airplane with a known deficiency, and his inflight decision to land with a quartering tailwind. A factor was the wing maintenance officer's concurrence to fly the airplane with the known deficiency.NTSB ANC01LA126Accident · No injuriesLimited investigationFinal reportFreeman Glastar · Glennallen, AKThe pilot's failure to abort the landing. Factors associated with the accident were the pilot's selection of an unsuitable landing area, and his failure to attain a proper touchdown point. An additional factor was a tailwind.NTSB ANC01LA108Accident · No injuriesLimited investigationFinal reportCessna 207 · Akiachak, AKThe pilot's selection of a the wrong runway, which resulted in a tailwind for the takeoff attempt. Factors associated with the accident are a short takeoff area, a tailwind, and the pilot's inadequate evaluation of the weather conditions.NTSB FTW01LA174Accident · No injuriesLimited investigationFinal reportCessna 152 · Denison, TXthe pilot's delay in aborting the takeoff, which resulted in a runway overrun.NTSB CHI01LA266Accident · No injuriesLimited investigationFinal reportGrumman AA-5B · Beaver Island, MIThe pilot misjudged the approach and landing, and his failure to abort the landing. Factors associated with the accident were the trees at the approach end of the runway and the sand/gravel pit that the airplane traveled into.NTSB ANC01LA094Accident · No injuriesLimited investigationFinal reportCessna U206 · McCarthy, AKThe pilot's decision to not abort the takeoff. Factors associated with the accident are a short and rising runway.NTSB CHI01LA226Accident · No injuriesLimited investigationFinal reportCessna 182T · Fowlerville, MIThe student pilot's failure to maintain aircraft control during landing. Factors relating to this accident were the misjudged flare, the exceeded proper touchdown point, the delayed go-around, the student pilot's improper in-flight decisions, and the pond.NTSB NYC01LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Mattituck, NYThe pilot's failure to attain a proper touchdown point. A factor was the tailwind.NTSB NYC01LA180Accident · Minor injuriesLimited investigationFinal reportCessna TU206G · Garrettsville, OHThe airstrip owner/pilot's failure to use all of the available runway. Factors were a tailwind condition and a contaminated runway.NTSB ANC01LA085Accident · No injuriesLimited investigationFinal reportCessna 172K · Wasilla, AKThe pilot's delay in aborting the takeoff roll.NTSB ANC01LA088Accident · No injuriesLimited investigationFinal reportCessna 185 · Cantwell, AKThe student pilot's failure to abort a landing resulting in an overrun. Factors in the accident were the pilot's diverted attention, and gusty wind conditions.NTSB CHI01LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Brooklyn, MIThe proper touchdown point exceeded, all of the available runway not used, and aircraft control not being maintained by the pilot during the landing. Factors to the accident were the pilot mistaking the taxiway for the runway, the pilot not performing a…NTSB LAX01LA210Accident · No injuriesLimited investigationFinal reportCessna A185F · Ash Fork, AZThe pilot's misjudged touchdown location on a short runway. Contributing factors were the presence of a tailwind and the proximity of trees.NTSB NYC01LA143Accident · No injuriesLimited investigationFinal reportYakovlev 52 · Fredericksburg, VAThe pilot's failure to obtain the proper touchdown point, which resulted in an overrun.NTSB MIA01LA156Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Bennettsville, SCThe pilot failure to obtain the proper touchdown point on the runway resulting in the airplane landing long, over running the runway, colliding with a telephone pole separating the right wing, and coming to rest in the parking lot of a restaurant.NTSB CHI01LA144Accident · No injuriesLimited investigationFinal reportCessna 152 · Roscommon, MIThe failure of the pilot to maintain clearance from the tree line. Factors to the accident were the tailwind, the aircraft being near gross weight, the high density altitude, the rough runway condition, and the tree line. An additional factor to the accident…NTSB ATL01LA055Accident · No injuriesLimited investigationFinal reportAir Tractor AT-602 · Dunlap, TNThe pilot's failure to obtain liftoff airspeed for undetermined reasons. A factor was tree stumps on the departure end of the takeoff area.NTSB IAD01LA054Accident · No injuriesLimited investigationFinal reportPiper PA-32-301 · Factoryville, PAThe pilot's failure to reach the proper touchdown point, and his subsequent failure to abort the landing.NTSB MIA01LA120Accident · 1 fatalLimited investigationFinal reportHenry Pelican · Lakeland, FLThe pilot's delay in aborting the takeoff in a downwind condition resulting in an overrun and subsequent collision with a ditch. Contributing to the accident was the pilot's failure to conduct performance planning for the flight.NTSB LAX01LA114Accident · No injuriesLimited investigationFinal reportAir Tractor AT-802 A · Maricopa, AZInadequate selection of landing facilities and improper placement of vehicles near the runway. An additional factor was the use of a runway which resulted in a downwind landing.NTSB NYC01FA084Accident · No injuriesField investigationFinal reportHawker Siddeley HS-125-3A · Bridgeport, CTThe pilot-in-commands inadequate preflight planning resulting in an approach to a runway with insufficient length. A factor related to the accident was the slush covered runway which resulted in a hydroplaning condition.NTSB LAX01IA109Incident · No injuriesIncident investigationFinal reportBoeing 737-3H4 · Phoenix, AZthe pilot's misjudgment of distance, which resulted in a runway overrun. A factor in the incident was the failure of the flightcrew to conduct a briefing for the approach to runway eight.NTSB ANC01LA040Accident · No injuriesLimited investigationFinal reportTaylorcraft 19 · Salcha, AKThe pilot's failure to compensate for a tailwind during takeoff, and his delay in aborting the takeoff. Factors in the accident were a tailwind, and snow-covered terrain.NTSB CHI01LA094Accident · No injuriesLimited investigationFinal reportCessna 500 · Sault Ste Marie, MIThe pilot exceeding the available runway distance during landing and the pilot's delay in executing a go-around. Factors relating to the accident were, the pilots improper in-flight planning/decision, the pilot disregarding the NOTAMS for the airport, the…NTSB SEA01TA050Accident · No injuriesFinal reportBeech 200 · Olympia, WAThe pilot's failure to attain the proper touchdown point for landing. A factor was weather conditions below published approach minimums.NTSB IAD01LA022Accident · No injuriesLimited investigationFinal reportLearjet 35 · Schenectady, NYThe pilot's improper trim setting, which resulted in a runway overrun and impact with a fence.