NTSB investigations, CT
8 cases where the sequence of events included Landing area overshoot.
Cases per year
| 2013 | 1 |
|---|---|
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 2 |
| 2017 | 1 |
| 2018 | 1 |
| 2021 | 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\" = '380' 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" = '380' 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 ERA22LA016Accident · Serious injuriesClass 3 · LimitedFinal reportKitfox IV · North Canaan, CTThe pilot's mismanagement of the airplane's altitude, airspeed, and course during a forced landing following a partial loss of engine power, which resulted in collision with trees and terrain. Contributing was the pilot’s inadvertent omission of stowing the…NTSB WPR18LA173Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 28-140 · Hartford, CTA loss of engine power for undetermined reasons because postaccident examination of the engine and fuel system did not reveal any anomalies that would have precluded normal operation, which led to the pilot’s forced landing and subsequent runway overshoot and…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 GAA16CA514Accident · No injuriesData collectionFinal reportCessna 205 · Ellington, CTThe pilot's exceedance of the airplane's critical angle-of-attack during the initial climb after an attempted go-around, which resulted in an aerodynamic stall.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 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 ERA15LA053Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Clinton, CTThe pilot's inadequate fuel planning and improper fuel management, which resulted in a total loss of engine power due to fuel starvation. Contributing to the accident was the pilot's failure to follow proper procedures in response to the loss of engine power.NTSB ERA13LA276Accident · No injuriesLimited investigationFinal reportCessna 170 · Plainville, CTThe pilot’s overflight of the landing runway during a forced landing after a loss of engine power. Contributing to the accident was the pilot’s inadequate preflight which resulted in his failure to detect water contamination of the fuel system.