NTSB investigations, CT
27 cases where the first occurrence was “Overrun”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 4 |
| 1986 | 1 |
| 1987 | 2 |
| 1989 | 2 |
| 1990 | 1 |
| 1992 | 3 |
| 1993 | 3 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 2 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2006 | 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\" = 'CT' 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" = 'CT' 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 NYC06CA108Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Chester, CTThe pilot's delayed decision to abort the takeoff, which resulted in an overrun. A factor in the accident was the pilot's inadequate preflight planning.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 IAD00LA017Accident · No injuriesLimited investigationFinal reportCessna T310R · Plainville, CTThe pilot's improper decision to attempt to close the pilot's door during the takeoff roll, which delayed the aborted takeoff and resulted in the overrun. A factor in the accident was the snow-covered runway.NTSB NYC98LA120Accident · No injuriesLimited investigationFinal reportCessna 140 · Madison, CTThe pilot's improper in-flight decision to continue the landing and his delayed go-around attempt. A factor in this accident was the pilot's diverted attention.NTSB NYC98LA036Accident · No injuriesLimited investigationFinal reportCessna 310R · Hartford, CTThe pilot's improper in-flight decision to land on the departure end of the runway and not perform a go-around.NTSB IAD97LA098Accident · No injuriesLimited investigationFinal reportCessna 182K · Ellington, CTThe pilot's misjudgment of speed and distance and his failure to execute a go around.NTSB IAD96LA110Accident · No injuriesLimited investigationFinal reportMooney M20M · Hartford, CTthe pilot's inadequate control of the airplane during the approach to landing/landing roll. A related factor is the pilot's inadequate remedial action (attempted go-around).NTSB NYC96LA015Accident · No injuriesLimited investigationFinal reportCessna 172RG · Chester, CTThe pilot's failure to attain adequate airspeed, and his delay in aborting the takeoff, which resulted in a runway overrun and collision with trees. Factors relating to the accident were: the wet runway and hydroplaning conditions.NTSB DCA94MA053Accident · 8 fatalClass 1 · MajorFinal reportPiper PA31 · Stratford, CTThe failure of the captain to use the available ILS glideslope, his failure to execute a go-around when conditions were not suitable for landing, and his failure to land the airplane at a point sufficient to allow for a safe stopping distance; the fatalities…NTSB BFO93LA143Accident · Serious injuriesLimited investigationFinal reportCessna 150L · Danielson, CTUndetermined.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB BFO93LA072Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Simsbury, CTLack of braking action from the right brake. The pilot's failure to attain the proper touchdown point was a related factor.NTSB NYC93LA047Accident · No injuriesLimited investigationFinal reportBeech C-24R · Meriden, CTThe pilot's improper airplane preflight, resulting in no airspeed indication during takeoff, and the subsequent abort with insufficient runway available to stop prior to a collision with the terrain.NTSB BFO93LA007Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Griswold, CTThe pilot's improper planning or decision, by not either using all available runway or making a go around. The wet grass condition of the airstrip was a related factor.NTSB BFO92LA080Accident · No injuriesLimited investigationFinal reportPiper PA-60-602P · Danbury, CTThe national transportation safety board determines the probable cause of the accident was the pilot misjudged distance and altitude which resulted in an overrun of the runway.NTSB NYC91LA017Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Bridgeport, CTThe pilot used excessive airspeed on the approach and landed long. The airplane went off the runway and struck a fence.NTSB NYC90LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Simsbury, CTThe pilot's misjudgement of airspeed and distance during landing resulting in an overshoot and swerve off the runway. The dusk light conditions, snow, and frozen terrain were contributing factors to the accident.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 NYC88LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Windham, CTThe flight departed groton, Connecticut enroute to willimantic, Connecticut in unlimited visibility. However at Windham airport, the runway was partially obscured by patchy fog according to the pilot. The pilot landed long due to carrying additional speed in…NTSB NYC87LA153Accident · No injuriesLimited investigationFinal reportCessna 182 · Ellington, CTThe pilot stated that while making a standard left traffic pattern, the wind at the north end of the airport shifted from the southeast to the northwest. The acft touched down with excessive ground speed, ran off the end of the rwy and came to rest on a…NTSB NYC86LA089Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Danbury, CTPilot touched down long on 3135 foot runway, exceeding the braking action of the aircraft, ran off end of runway into a ditch causing substantial damage to the aircraft. The pilot, the sole occupant received no injuries.NTSB NYC85LA036Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Meriden, CTWhile in cruise, plt heard an abnormal sound from the left side of the engine compartment and having had previous problems with the newly-installed engine, elected to make a precautionary landing at a nearby arpt to investigate. Plt stated he landed long and…NTSB NYC85LA021Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Oxford, CTAfter entering the traffic pattern for the selected runway, plt was informed of surface wind conditions and elected to continue and execute a downwind landing. Upon touchdown, plt raised flaps to assist braking action. During roll-out the plt decided…NTSB NYC84LA272Accident · No injuriesLimited investigationFinal reportCessna 152II · E. Windsor, CTPlt failed to note inoperative airspeed indicator until well into takeoff run. When the defect was noted, takeoff abort procedures were performed but the acft continued beyond the airport boundary into a rough field and nosed over. Investigation revealed the…NTSB NYC84LA288Accident · No injuriesLimited investigationFinal reportCessna 172PII · Madison, CTPlt stated groundspeed was fast during the flare and an abrupt touchdown was made 'fairly far' down the rwy. Plt reported, 'braking had not sufficiently slowed or stopped the plane as the plane neared the end of the runway, and it veered off to the right of…NTSB NYC84LA051Accident · No injuriesLimited investigationFinal reportCessna C172N · Meriden, CTThe acft collided with a dirt pile and nosed over during landing. According to the plt, he landed too FAR down the rwy, attempting an abort and the acft flipped over.NTSB NYC82DA171Accident · No injuriesFinal reportGrumman AA-5B · Madison, CTThe pilot stated that he experienced a sudden wind shift when over the runway threshold. The aircraft was landed to the right of the runway after an attempted go-around was aborted because of trees and buildings at the departure end/left side of the runway.