NTSB investigations
1,681 cases where the first occurrence was “Overrun”.
Cases, newest first
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 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 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 SEA90LA015Accident · No injuriesLimited investigationFinal reportCessna 182P · Hillsboro, ORFailure of the pilot to attain the proper touchdown point or go around while there was still sufficient runway and speed remaining. The tailwind was a related factor.NTSB ATL90LA011Accident · No injuriesLimited investigationFinal reportCessna 182Q · Cumming, GAA lack of fluid in the brake system and an inadequate annual inspection.NTSB CHI90LA015Accident · No injuriesLimited investigationFinal reportCessna 207 · Dodgeville, WIPilot's improper planning/decision and his delay in deciding to go around. Factors related to the accident were: the unfavorable wind conditions, the pilot's visual perception on the crowned runway, his misjudgement of speed and remaining distance on the…NTSB CHI90LA013Accident · No injuriesLimited investigationFinal reportCessna 172H · Bay City, MIThe pilot's failure to execute a go-around in a timely manner.NTSB ATL90LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Ridgeland, SCThe pilot misjudged the airspeed and failed to attain the proper touchdown point.NTSB MIA90LA006Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Titusville, FLFailure of the pilot to go around after landing long with excessive airspeed.NTSB ANC89LA179Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Kiana Creek, AKImproper planning/decision by the pilot, and the premature lift-off. Factors related to the accident were: the unfavorable wind condition and the pilot's self-induced pressure.NTSB CHI89LA197Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Lebanon, ILFailure of the pilot to use all available runway and his misjudgement of the available distance (runway length) for landing. Contributing factors were: inadequate preflight planning/preparation, and the runway and terrain conditions.NTSB CHI89LA195Accident · No injuriesLimited investigationFinal reportBeech 36 · Princeton, ILThe pilot had excessive airspeed, misjudged the landing distance, and did not go around. The high obstructions (trees),wet runway, ditch, and uneven terrain (roadway) were contributing factors.NTSB CHI89LA194Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Mt. Horeb, WIThe pilot's failure to follow proper procedures for breaking-in new brakes and the excessive touchdown speed. Contributing factors were the worn brakes.NTSB ANC89LA174Accident · No injuriesLimited investigationFinal reportCessna 180 · Redoubt Bay, AKImproper planning/decision by the pilot. Factors related to the accident were: the unfavorable runway and terrain conditions.NTSB CHI89LA189Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Newark, ILThe pilot landed long and failed to make a go around.NTSB ANC89LA165Accident · No injuriesLimited investigationFinal reportCessna U206 · Nondalton, AKFailure of the pilot to attain the proper touchdown point for the landing, his excessive airspeed, and his misjudgement of runway distance remaining. Factors related to the accident were: loose/wet gravel on the runway and the location of the parked aircraft…NTSB NYC89LA214Accident · No injuriesLimited investigationFinal reportCessna 172N · Bayport, NYThe pilot's misjudging speed and distance resulting in his overshooting the landing and running off the end of the runway.NTSB LAX89LA305Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Marble Canyon, AZThe pilot selected the wrong runway and landed downwind.NTSB SEA89LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Alderwood Manor, WAImproper planning/decision by the pilot. The tailwind and high obstructions were related factors.NTSB NYC89LA199Accident · Serious injuriesLimited investigationFinal reportCessna A185F · Deer Isle, METhe pilot's inadequate preflight in determining the adequacy of the takeoff environment under the existing adverse wind conditions.NTSB MIA89LA227Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Pensacola, FLThe pilot's failure to follow the checklist and ensure that the elevator trim tab was adjusted properly for takeoff.NTSB BFO89LA072Accident · No injuriesLimited investigationFinal reportBeech B55 · Orange, VAThe takeoff was rejected when the pilot was startled by the sound from the emergency window exit which was inadvertently opened by a passenger. The pilot was unable to stop the aircraft in time to avoid overrunning the runway.NTSB DEN89LA190Accident · No injuriesLimited investigationFinal reportPiper PA-18-125 · Ekalaka, MTMisjudgement of the proper touchdown point by the pilot, which resulted in an overrun of the landing area and collision with a post. The downhill terrain condition and location of the fence post were related factors.NTSB CHI89LA161Accident · No injuriesLimited investigationFinal reportCessna R172K · Vincennes, INThe pilot had excessive airspeed, misjudged the landing distance, and did not go around. Contributing factors were: the pilot misread wind information and selected the wrong runway. Also, the tailwind and ditch were considered to be contributing factors.NTSB NYC89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Danbury, CTThe pilot's misjudgement of (excessive) airspeed, his failure to attain the proper touchdown point, and failure to make a go-around, while there was sufficient runway remaining. The fence was a related factor.NTSB MIA89LA209Accident · No injuriesLimited investigationFinal reportPiper PA-34 · Ackerman, MSThe pilot's selection of the wrong runway and his improper inflight planning/decision which resulted in a situation from which he could neither go-around nor stop on the remaining runway. The thunderstorms, inoperative (disrepaired) wind sock, and rough…NTSB CHI89IA140Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-10-10 · Chicago, ILHydroplaning attributed to the physical condition of the runway, and the airport personnel's failure to adequately maintain the runway. Contributing factors were: the rain and the wet runway.NTSB DEN89LA171Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Alpine, WYPilot's decision to land at an unlighted airport at night. The aircraft landed long and overran the runway.NTSB DEN89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Salt Lake City, UTThe pilot's improper use of the parking brake and his delay in aborting the takeoff. Factors related to the accident were: the fence & vehicle.NTSB NYC89LA157Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Beverly, MACollision with trees during an aborted landing and attempted go-around with insufficient remaining runway.NTSB LAX89DVG08Accident · No injuriesFinal reportHomebuilt BG 12 B-D · Montague, CAPilot misjudged the airplane's altitude and failed to extend the spoilers.NTSB CHI89LA121Accident · No injuriesLimited investigationFinal reportCessna C172M · Wadsworth, OHPilot's poor planning/decision making during the approach and landing phase of flight, which resulted in a long landing and runway overrun.NTSB BFO89LA046Accident · No injuriesLimited investigationFinal reportCessna 210A · Ocean City, MDFailure of the pilot to go around after landing long & recovering from a bounced landing. Contributing factors were: the pilot's excessive airspeed on the apch, his improper flare for the landing, his failure to attain the proper touchdown point, and the…NTSB DEN89LA135Accident · No injuriesLimited investigationFinal reportCessna 210 · Halls Crossing, UTInadequate aircraft handling by the pilot, resulting in a runway overrun.NTSB MKC89LA125Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Bolivar, MOImproper planning/decision by the pilot and his delay in aborting the takeoff. Contributing factors were the tall grass, inadequate runway maintenance, and trees.NTSB MIA89LA149Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Melbourne, FLThe instructors decision to attempt a takeoff in a high density altitude situation, with a quartering tailwind.NTSB CHI89LA090Accident · No injuriesLimited investigationFinal reportCessna 150 L · Eureka, MIStudent pilot's improper aircraft control during the takeoff roll, and the subsequent aborted takeoff was performed with insufficient runway remaining to successfully stop the aircraft before the departure end of the runway.NTSB MIA89LA143Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Palmetto, FLThe pilot's selection of the wrong runway for landing along with failure to attain a proper point of touchdown and the failure to perform a go-around.NTSB CHI89LA081Accident · No injuriesLimited investigationFinal reportCessna 172D · Ottawa, ILStudent pilot's continuing an approach to landing beyond the point where she could bring the aircraft to a controlled stop on the remaining runway surface.NTSB NYC89LA124Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Dushore, PACollision with trees during a rejected takeoff from a private turf strip due to the pilots failure to take advantage of the existing wind.NTSB BFO89LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Laurel, MDThe pilot's failure to obtain adequate airspeed during the attempted short field takeoff for undetermined reasons.NTSB NYC89LA120Accident · No injuriesLimited investigationFinal reportCessna 172 · So. Bethlehem, NYThe pilots misjudgement of landing distance which resulted in the failure to touchdown at a proper touchdown point. The pilot also failed to perform a go-around.NTSB SEA89LA069Accident · No injuriesLimited investigationFinal reportCessna 182 · Arlington, ORThe student pilot touched down too FAR down the runway to allow him to stop before running into a trailer.NTSB NYC89LA117Accident · No injuriesLimited investigationFinal reportCessna 172M · Palmyra, PAThe pilot misjudged the airspeed and distance during the landing.NTSB NYC89LA115Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Matawan, NJThe pilot's inadequate action after encountering tailwind conditions during landing.NTSB LAX89LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Eureka, CAThe improper in-flight planning by the instructor pilot when he allowed the private pilot student to land long. Additionally, the instructor delayed remedial action until the runway overrun was inevitable.NTSB ATL89LA117Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Timmonsville, SCThe pilot's failure to remain aware of the local wind conditions. Additionally, he executed the approach and landing with excessive speed, combined with a tailwind, which resulted in the runway overrun.NTSB NYC89LA109Accident · No injuriesLimited investigationFinal reportCessna 172XP · Vineland, NJThe pilot's misjudgement of speed & distance during landing which resulted in the proper touchdown point to be exceeded. The runway conditions were contributing factors.NTSB BFO89FA024Accident · No injuriesField investigationFinal reportLearjet 25 · Roanoke, VACo-pilots poorly planned approach which resulted in an overrun landing. A contributing factor was the captains poor supervision of the approach and landing.NTSB MIA89LA105Accident · No injuriesLimited investigationFinal reportCessna 150 · Arcadia, FLThe pilot's delayed to go around after landing long with excessive speed.NTSB FTW89LA062Accident · No injuriesLimited investigationFinal reportCessna 421B · San Antonio, TXThe failure of the pilot to follow the proper procedures/directives by not following the glideslope which resulted in not being able to attain the proper touchdown point.NTSB FTW89LA060Accident · No injuriesLimited investigationFinal reportCessna 172 · Jacksboro, TXFailure of the pilot to go around, when she did not attain the proper touchdown point (landed long) and had excessive airspeed to stop on the runway. A factor related to the accident was the unfavorable wind condition (sudden wind shift).NTSB FTW89LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · Marietta, OKFailure of the pilot to select the proper runway, which resulted in a downwind landing and an overrun of the runway. The gusty tailwind, ditch, and railing (fence) were factors.