NTSB investigations, MA
34 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 2 |
| 1985 | 3 |
| 1987 | 1 |
| 1988 | 4 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1993 | 3 |
| 1994 | 2 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 2 |
| 1998 | 1 |
| 2000 | 4 |
| 2002 | 2 |
| 2004 | 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\" = 'MA' 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" = 'MA' 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 NYC04CA066Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Grt. Barrington, MAThe pilot's misjudgment of the airplane's distance/speed and failure to obtain the proper touchdown point, which resulted in an overrun. A factor was the cross wind.NTSB NYC02LA143Accident · No injuriesLimited investigationFinal reportBeech 58 · Provincetown, MAThe pilot's failure to initiate a timely go-around, which resulted in his landing the airplane long and fast. Factors included low ceilings and the airplane's initial misalignment with the runway.NTSB NYC02LA052Accident · No injuriesLimited investigationFinal reportSocata TB-9 · Marlborough, MAThe pilot's failure to achieve a proper touchdown point on the runway which resulted in an overrun. A factor was the pilot's lack of experience in short field operations.NTSB NYC00LA212Accident · Minor injuriesLimited investigationFinal reportPiper PA-46 · Chatham, MAThe pilot's delayed use of the brakes, which resulted in a runway overrun. Factors in the accident were the pilot's improper decision to land with a right quartering tailwind.NTSB IAD00LA046Accident · No injuriesLimited investigationFinal reportSchweizer SGS 2-33A · Sterling, MAThe pilot's failure to attain a proper touchdown point.NTSB NYC00LA109Accident · No injuriesLimited investigationFinal reportCessna 172 · North Adams, MAThe pilot's failure to obtain the proper touchdown point. A factor was a tailwind.NTSB NYC00FA092Accident · Minor injuriesField investigationFinal reportDassault DA-900 · Hyannis, MAThe flightcrew's inadequate coordination and improper weather evaluation. Also causal was the captain's improper decision to continue the approach to a runway with insufficient length and his failure to obtain the proper touch down point on the runway.…NTSB NYC98LA126Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Taunton, MAa delayed decision by the pilot to abort the takeoff, which resulted in an overrun. A factor was false reading from the airspeed indicator.NTSB NYC98LA004Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Edgartown, MAThe pilot's inadequate evaluation of the wind direction and his failure to initiate a go-around. Contributing factors were the tailwind, wet runway, and utility pole.NTSB IAD97IA045Incident · No injuriesIncident investigationFinal reportCessna 402C · Provincetown, MAthe pilot's inadequate inflight planning/decision, and his misjudgment of speed and distance. Related factors were: fog, tailwind, and soft terrain on the overrun area at the end of the runway.NTSB NYC96LA185Accident · No injuriesLimited investigationFinal reportCessna 182 · Stow, MAthe pilot's misjudgment of speed and distance during the landing, and his failure to go around while there was sufficient runway remaining, which resulted in a runway overrun and an encounter with a soft terrain at the edge of a pond. Wet grass on the runway…NTSB NYC96LA124Accident · No injuriesLimited investigationFinal reportCessna 172 · Gardner, MAthe pilot 's misjudgment of speed and distance during landing.NTSB NYC95LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Norfolk, MAThe pilot's misjudgement of speed and distance during the landing, which resulted in a runway overrun. Factors relating to the accident were: heavy rain, wet runway, and hydroplaning conditions.NTSB NYC95LA044Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Gr. Barrington, MAThe pilot landed with excessive airspeed which resulted in a long landing, runway overrun, and collision with trees.NTSB NYC94LA181Accident · No injuriesLimited investigationFinal reportCessna 172P · Sterling, MAThe pilot misjudged landing distance, which resulted in an overrun of the runway. A factor is the pilot's failure to do a go-around.NTSB NYC94LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-301T · Norwood, MAThe pilot's delay in aborting the takeoff which resulted in a overrun of the runway. Factors were a snow covered runway, takeoff speed not attained, brakes not used, and a ditch.NTSB NYC94LA015Accident · Minor injuriesLimited investigationFinal reportCessna 310L · Tewksbury, MAwas an improperly planned approach, and excessive compensation for the winds by the pilot which resulted in an overrun, and on ground collision with a fence and vehicle. A factor was the gusty crosswinds.NTSB NYC93LA131Accident · Minor injuriesLimited investigationFinal reportPiper PA-32 · Spencer, MAThe pilot's inadequate preflight planning for the high density altitude departure and the delay in aborting the takeoff roll, with insufficient runway remaining, resulting in a collision with treesNTSB BFO92LA108Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Marston Mills, MAThe pilot's inadequate preflight preparation. Contributing was the pilot's failure to use all available runway and overconfidence in his own abilities.NTSB NYC91LA088Accident · No injuriesLimited investigationFinal reportPiper PA28-400 · Fall River, MAAn improper flare and touchdown point which resulted in an overrun of the runway during the landing roll.NTSB NYC90LA196Accident · No injuriesLimited investigationFinal reportGrumman AA5B · Stow, MAThe pilot's failure to properly plan the approach which resulted in the pilot misjudging the touch down point and landed long.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 NYC89LA046Accident · No injuriesLimited investigationFinal reportBeech 24R · Oxford, MAFailure of the pilot to stop the aircraft on the available runway due to a long landing.NTSB NYC88DNA02Accident · Serious injuriesFinal reportDillinger Long E-Z · Lawrence, MAThe plt depd provincetown on a rtrn flt to his home arpt at aprx 0230 EDT & arrived at his destn about 1 hr later. He rprtd he was unable to activate the plt-ctld rwy lights. He checked the lighted wind sock & decided the night was bright & clear enough to…NTSB NYC88LA091Accident · No injuriesLimited investigationFinal reportCessna 303 · Hyannis, MAThe Cessna 303 broke out of the clouds and made a long landing on a 5567 ft runway. Tire marks showed that the aircraft touched down with less than 2000 ft of runway remaining. The landing runway was 24 and the winds were from 360 degrees at 8 KTS. The runway…NTSB NYC88LA075Accident · No injuriesLimited investigationFinal reportCessna 402C · Provincetown, MAThe Cessna 402C was being positioned for a scheduled commuter flight with only a pilot on board. The pilot made an ILS approach to runway 7 with winds from 220 degrees at 14 knots, the runway wet and light rain falling. The aircraft slid off the end of the…NTSB NYC87LA237Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Stow, MAThe pilot was on takeoff roll when he decided to abort. He stated that he felt the engine was not developing adequate power and the airspeed was not up to required takeoff speed. The aircraft continued off the end of the runway and inverted in swampy soil.NTSB NYC85LA170Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Provincetown, MADuring arrival, the acft was vectored for an ILS rwy 7 apch which was made with a tail wind. On his 1st attempt, the plt made a missed apch & was vectored for another ILS. After making a 2nd apch, he landed. The plt stated that while he was landing, he…NTSB NYC85LA167Accident · Minor injuriesLimited investigationFinal reportPiper PA28-151 · Chatham, MADuring the final approach to runway 24, the aircraft was too high and fast. The pilot decided to land on the runway instead of going around. According to the pilot, the aircraft landed too FAR down the runway and went over the end.NTSB NYC85LA085Accident · No injuriesLimited investigationFinal reportBoeing JB-75 · Marston Mills, MAThe acft nosed over after contacting an utility pole during an overrun landing. The acft touched down aprx 1/2 way down the rwy and the plt applied brakes, however, braking action was poor because of the wet grass rwy. The acft skidded off the end of the rwy…NTSB NYC85LA040Accident · No injuriesLimited investigationFinal reportBeech 58TC · Norwood, MATouchdown made 1/3 the way down the wet rwy. Brakes were ineffective on wet pavement. Plt raised flaps and reapplied brakes with no positive result. Acft continued onto 60 ft overrun area where some braking action was effective however, acft continued down an…NTSB NYC84LA094Accident · No injuriesLimited investigationFinal reportCessna 500 · Fitchburg, MAThe plt landed on a slushy rwy. He was unable to stop on the rwy and angled off the end into marshy ground. The stoppingdistance on a dry rwy was figured at 2355 ft. on a slushy rwy the stopping distance was about 4004 ft. the landing rwy was 4500 ft long.…NTSB NYC83LA180Accident · No injuriesLimited investigationFinal reportCessna 172 · Haverhill, MAThe acft overran the departure end of the 2100 ft rwy 32 during landing. The wind was from 320 degrees at 10 KTS. The pilot stated he made one go-around because he was high. He reported that the 2nd approach was flown at 65 mph with the touchdown accomplished…NTSB DCA82AA013Accident · 2 fatalFinal reportMcdonnell Douglas DC-10-30 · Boston, MADrg arr, plt ackd rcpt of ATIS info & fld cond rprt, both in dcg braking action "fair to poor." He was not adzd of 3 pltrprts of braking action "poor to nil" or "poor." Acft was clrd for vor/dme apch to rwy 15R. Due to psbl wnd shear, 35 deg of flaps (instead…