NTSB investigations, MD
28 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 5 |
|---|---|
| 1983 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 2 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 2 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 2 |
| 2006 | 1 |
| 2007 | 1 |
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 c.\"eventStateOrRegion\" = 'MD' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'MD' AND c."eventCountry" = 'USA' 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 MIA07CA115Accident · No injuriesData collectionFinal reportMooney M20R · Mitchellville, MDThe pilot's failure to attain the proper touchdown point for landing and his failure to initiate a go-around when he realized the airplane would touchdown past the intended point.NTSB NYC07CA004Accident · No injuriesData collectionFinal reportBeech BE-58 · Annapolis, MDThe pilot's improper in-flight decision to attempt to land on the wet runway, which resulted in an overrun. Factors in the accident were rain, and the gusty wind conditions.NTSB NYC02LA119Accident · Serious injuriesLimited investigationFinal reportMooney M20 · Hagerstown, MDThe pilot's failure to perform a go-around and obtain the proper touchdown point, which resulted in an overrun. A factor in the accident was the crosswind condition.NTSB IAD02FA047Accident · No injuriesField investigationFinal reportBeech 400A · Baltimore, MDThe captain's failure to go around. Factors included the captain's preoccupation with the flight management system, the crew's failure to adhere to company standard operating procedures, and the lack of proper crew coordination.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 IAD00LA058Accident · Serious injuriesLimited investigationFinal reportCessna 206 · Annapolis, MDThe pilot's failure to attain the proper touchdown point, and his failure to perform a go-around.NTSB NYC99LA101Accident · Serious injuriesLimited investigationFinal reportBeech BE-C23 · Annappolis, MDThe pilot's failure to perform a go-around and he landed long resulting in an overrun. A factor in the accident was the night light conditions.NTSB NYC99LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Cumberland, MDThe pilot's decision to land, instead of performing a go-around.NTSB NYC98LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · Westminster, MDthe pilot's misjudgment of distance and speed during the approach/landing, and his delay in initiating a go-around. The quartering tailwind was a related factor.NTSB IAD97LA072Accident · No injuriesLimited investigationFinal reportCessna 172H · Westminister, MDThe pilot misjudged landing distance on the runway and his failure to perform a go-around.NTSB IAD96LA146Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-235 · Westminster, MDthe pilot's misjudgement of his speed and distance, his failure to attain the proper touchdown point during the landing, and his delay in executing a go-around (aborted landing), which resulted in an overrun.NTSB BFO96LA002Accident · No injuriesLimited investigationFinal reportBeech 95-B55 · Annapolis, MDthe pilot's improper planning/decision, and/or failure to go around while there sufficient airspeed and runway remaining during the approach/landing. Factors relating to the accident were: standing water on the runway, and resultant hydroplaning conditions.NTSB BFO91LA045Accident · No injuriesLimited investigationFinal reportGrumman AA5B · College Park, MDThe pilot's failure to maintain aircraft control. Related factors were: hydroplaning conditions on the wet runway and the pilot's lack of recent experience.NTSB BFO91LA041Accident · No injuriesLimited investigationFinal reportCessna 172P · College Park, MDThe pilot misjudged altitude and distance which resulted in an overrun of the runway.NTSB NYC91LA037Accident · No injuriesLimited investigationFinal reportCessna 152 · Indian Head, MDThe flight instructors decision to land with insufficient runway remaining to stop the airplane which resulted in an overrun.NTSB BFO90LA049Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Lusby, MDThe pilot misjudged the distance needed to touchdown and stop his aircraft before running off the end of the runway. The pilot failed to use all of the available runway during the landing sequence.NTSB BFO90LA044Accident · No injuriesLimited investigationFinal reportCessna 172A · Pocomoke, MDThe pilot's misjudgement of distance and speed during the approach to land, and his failure to attain the proper touchdowwn point during the landing. The ditch was a related factor.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 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 BFO87LA069Accident · No injuriesLimited investigationFinal reportMooney M20E · Pocomoke City, MDWhile on final apch, the plt realized his touchdown point was farther down the rwy than usual, but he believed there was sufficient rwy & elected to cont the lndg. After touchdown, he applied brakes, but was unable to stop on the remaining rwy. Subsequently,…NTSB BFO86FA036Accident · Serious injuriesField investigationFinal reportPiper PA-28-160 · Michellville, MDAfter circling around the airport, trying to raise somebody on UNICOM to find out wind conditions at the field, the pilot noted the lighted windsock indicator and elected to land to the north. The aircraft was observed to land long on the 2420 foot runway,…NTSB BFO86LA001Accident · No injuriesLimited investigationFinal reportCessna 172N · Annapolis, MDThe plt crossed mid-field, and entered a left down wind for rwy 30. He then checked wind direction, completed a base leg, and entered final apch. After reducing his airspeed, the acft 'floated' prior to touching down aprx 600 ft short of mid-fld. The plt…NTSB ATL83LA231Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Cambridge, MDThe owner/student plt & his instructor (CFI) were on a dual instructional flt & proceed to an arpt with a wet grass rwy to practice landings. The rwy was 2200 ft long & had 50 to 60 ft trees at the apch end that had been cut to aprx 25 ft AGL. The 1st apch…NTSB ATL83FIG01Accident · No injuriesFinal reportCessna 172N · Mitchellville, MDThe aircraft was landed with 20 degrees flaps at 67 mph. It continued off the end of the 2,150 foot runway, went through a fence and came to rest at the edge of highway route 50. The handbook recommended 40 degrees of flaps and a 61 mph approach speed.NTSB ATL82DA193Accident · Minor injuriesFinal reportPiper PA-32-300 · Westminster, MDWhile on a cross-country flight, the pilot elected to make an unscheduled stop at a unfamiliar airport to check the en route weather. He circled the airport and thought the wind indicated favored runway 31, but later, he found that the wind was calm. No…NTSB ATL82DA135Accident · Minor injuriesFinal reportBeech C23 · Churchville, MDThe pilot stated that he lowered the nose of the aircraft during the approach to expedite his touchdown. He also stated that he did not apply brakes immediately because the aircraft was not firmly on the ground. When he realized he would be unable to stop on…NTSB ATL82DA130Accident · Minor injuriesFinal reportPiper PA-28-161 · Mitchellville, MDThe pilot took off on a dark night to an airport that he had never landed at before. While en route, he became disoriented and called a flight service station for help. A military helicopter pilot rendezvoused with the lost pilot and provided vectors to the…NTSB ATL82DA124Accident · No injuriesFinal reportCessna A150 · Leonardtown, MDThe pilot reported that his speed was fast on base leg and final approach. After touchdown he bounced back into the air and added power for a go-around, however, he failed to return the carburetor heat control to the cold position and the aircraft did not…