NTSB investigations, CT
31 cases where the sequence of events included Runway excursion.
Cases per year
| 2008 | 4 |
|---|---|
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 1 |
| 2013 | 2 |
| 2015 | 4 |
| 2016 | 2 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 1 |
| 2021 | 2 |
| 2022 | 3 |
| 2023 | 1 |
| 2025 | 2 |
| 2026 | 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 s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
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 s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) 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 ERA26LA229Accident · No injuriesClass 4 · LimitedFinal reportHawker Beechcraft G36 · Danbury, CTThe pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.NTSB ERA26LA015Accident · No injuriesClass 4 · LimitedFinal reportSocata TB 10 · New Milford, CTThe pilot’s decision to depart from an unlit turf runway at night, which resulted in a loss of directional control, and subsequent runway excursion.NTSB ERA25LA279Accident · No injuriesClass 4 · LimitedFinal reportBeech A23-24 · Windham, CTThe pilot’s inadequate preflight planning, which resulted in a rejected takeoff and subsequent runway excursion.NTSB ERA23LA216Accident · No injuriesClass 4 · LimitedFinal reportGilbert R. Ringer GP4 · Stratford, CTA failure of the left main landing gear down locking mechanism, which resulted in a collapse of that landing gear and a subsequent runway excursion.NTSB ERA22LA336Accident · Minor injuriesClass 4 · LimitedFinal reportBellanca 7KCAB · East Haddam, CTThe pilot's failure to maintain directional control during the landing.NTSB ERA22LA253Accident · No injuriesClass 4 · LimitedFinal reportPiper PA28 · Simsbury, CTThe pilot’s delayed decision to abort the landing, which resulted in a runway overrun.NTSB ERA22LA152Accident · No injuriesClass 4 · LimitedFinal reportAmerican Champion 7GCBC · Plainville, CTThe pilot’s failure to maintain directional control during the landing roll.NTSB ERA21FA346Accident · 4 fatalClass 2 · FieldFinal reportCessna 560 · Farmington, CTThe pilot-in-command’s failure to release the parking brake before attempting to initiate the takeoff, which produced an unexpected retarding force and airplane-nose-down pitching moment that prevented the airplane from becoming airborne within the takeoff…NTSB ERA21LA249Accident · No injuriesClass 4 · LimitedFinal reportCessna 172R · Groton, CTThe pilot’s failure to maintain directional control of the airplane during landing, resulting in a runway excursion and collision with an airport sign.NTSB ERA20CA294Accident · No injuriesClass 4 · Data collectionFinal reportSocata TB200 · Simsbury, CTA runway excursion following an aborted takeoff in tailwind conditions.NTSB GAA20CA068Accident · No injuriesData collectionFinal reportIcon A5 · Chester, CTThe pilot's failure to maintain a proper approach angle in dark night conditions, which resulted in a collision with treetops and a subsequent hard landing.NTSB ERA19LA030Accident · Minor injuriesLimited investigationFinal reportPiper PA28 · Simsbury, CTMaintenance personnel's inadequate inspection of the wheel brake system during the airplane's most recent 100-hour inspection, which resulted in a loss of hydraulic fluid and the pilot's inability to control the airplane during the landing.NTSB ERA16CA308Accident · No injuriesData collectionFinal reportBeech C23 · Simsbury, CTThe student pilot’s failure to attain the proper touchdown point, which resulted in a runway overrun.NTSB ERA16LA122Accident · No injuriesLimited investigationFinal reportCessna 152 · Chester, CTThe pilot’s failure to maintain directional control of the airplane during the landing, which resulted in a runway excursion.NTSB ERA15LA356Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Stratford, CTThe pilot's failure to maintain directional control while landing in a crosswind.NTSB ERA15LA322Accident · Minor injuriesLimited investigationFinal reportEclipse EA500 · Danbury, CTThe pilot's failure to attain the proper touchdown point and exceedance of the target touchdown speed, which resulted in a runway overrun.NTSB GAA15CA228Accident · No injuriesData collectionFinal reportCessna 337F · Danbury, CTThe pilot's failure to maintain pitch control during the landing, resulting in a hard landing, nose gear collapse, runway excursion, and collision with terrain.NTSB GAA15CA218Accident · No injuriesData collectionFinal reportCessna 170A · East Haddam, CTThe pilot's failure to maintain directional control during the landing roll, and excessive use of brakes, which resulted in a runway excursion and nose over.NTSB ERA13LA343Accident · No injuriesLimited investigationFinal reportCessna 175 · Willimantic, CTThe pilot’s failure to maintain directional control during the landing roll, which resulted in a ground loop.NTSB ERA13CA233Accident · Minor injuriesData collectionFinal reportHughes Charles R Zodiac 601XL · Meriden, CTThe pilot's decision to land with a tailwind and his failure to maintain aircraft control during landing.NTSB ERA12CA436Accident · No injuriesData collectionFinal reportPiper PA-28-236 · Chester, CTThe pilot’s failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.NTSB ERA11IA521Incident · No injuriesIncident investigationFinal reportBeech V35 · New Haven, CTThe in-flight fatigue failure of the engine’s crankshaft, which resulted in the separation of the forward portion of the crankshaft and the propeller.NTSB ERA11LA264Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Meriden, CTMaintenance personnel's inadequate inspection of the main landing gear, which resulted in a failure of the right main landing gear’s inboard torque link lug due to a fatigue fracture. Contributing to the accident was owner's lack of compliance with a factory…NTSB ERA11CA138Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's loss of directional control during the landing rollout, resulting in a runway excursion.NTSB ERA10CA440Accident · No injuriesData collectionFinal reportBeech P35 · Hartford, CTThe pilot's inadequate compensation for the crosswind, resulting in a loss of directional control during landing.NTSB ERA10CA278Accident · No injuriesData collectionFinal reportCessna 172S · East Haddam, CTThe pilot's delayed decision to attempt a go-around, and his subsequent failure to maintain directional control while landing.NTSB ERA09LA339Accident · No injuriesLimited investigationFinal reportPilatus PC-12/47 · Bridgeport, CTThe flight crew's misjudgment of speed and distance, which resulted in an overrun of the wet runway.NTSB ERA09CA048Accident · No injuriesData collectionFinal reportCessna 172 · Groton, CTThe student pilot's failure to maintain directional control during landing.NTSB ERA09CA034Accident · No injuriesData collectionFinal reportGrumman American Avn. AA-5B · Bridgeport, CTThe pilot's loss of directional control during landing and while suffering symptoms of vertigo.NTSB ERA09CA007Accident · No injuriesData collectionFinal reportCirrus Design SR20 · Chester, CTThe pilot’s failure to obtain the proper touchdown point while landing. Contributing to the accident were the pilot’s inexperience landing at the airport, night conditions, and non-standard runway lighting.NTSB CHI08LA185Accident · No injuriesLimited investigationFinal reportTraxler John N Kitfox · Hartford, CTThe pilot's failure to compensate for crosswinds resulting in a loss of directional control while landing. Contributing to the accident was the pilot's lack of experience and training in tailwheeled airplanes.