NTSB investigations, CT
10 cases where the sequence of events included Abnormal runway contact.
Cases per year
| 2010 | 1 |
|---|---|
| 2011 | 1 |
| 2016 | 1 |
| 2017 | 3 |
| 2019 | 1 |
| 2020 | 1 |
| 2021 | 1 |
| 2024 | 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\" = '090' 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" = '090' 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 ERA24LA089Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-34-200 · Groton, CTThe pilot receiving instruction’s failure to extend the landing gear prior to landing. Also contributing, was the flight instructor’s failure to monitor the airplane’s configuration while on approach to land.NTSB ERA21LA319Accident · No injuriesClass 4 · LimitedFinal reportBeech F33A · Oxford, CTThe inadvertent operation of the landing handle during the landing roll, which resulted in a nose gear retraction and subsequent collision with the runway.NTSB ERA20LA337Accident · No injuriesClass 4 · LimitedFinal reportLancair 235 · Chester, CTThe pilot's unstable approach, which resulted in a hard landing, and the separation of the left main landing gear.NTSB GAA19CA379Accident · No injuriesData collectionFinal reportCirrus SR22 · Grotten, CTThe pilot's improper landing flare and failure to maintain pitch control, which resulted in a porpoised landing.NTSB GAA17CA345Accident · No injuriesData collectionFinal reportPiper PA28 · Hartford, CTThe pilot’s improper landing flare, which resulted in a bounced landing.NTSB GAA17CA325Accident · No injuriesData collectionFinal reportCessna 182 · Ellington, CTThe pilot’s unstabilized approach and failure to go around in rainy, gusting crosswind conditions, which resulted in a runway overrun. Contributing to the accident was the pilot’s self-induced pressure to land due to the deteriorating weather conditions.NTSB ERA17FA167Accident · 1 fatalField investigationFinal reportCirrus Design SR22 · Wallingford, CTThe pilot's unstablilized approach and improper landing flare, which resulted in a bounced landing, and his subsequent failure to maintain control during a go-around. Contributing to the accident was the pilot's lack of experience in the accident airplane…NTSB GAA17CA099Accident · Minor injuriesData collectionFinal reportPiper PA38 · Hartford, CTThe student pilot’s improper landing flare, which resulted in a bounced hard landing.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 ERA11CA017Accident · No injuriesData collectionFinal reportCessna 120 · Falls Village, CTThe pilot’s failure to abort the takeoff, which resulted in an in-flight collision with terrain.