NTSB investigations, CT
16 cases where NTSB found Descent/approach/glide path.
Cases per year
| 2008 | 2 |
|---|---|
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 2 |
| 2013 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 1 |
| 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '01062040'))
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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '01062040')) 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 ERA24LA168Accident · No injuriesClass 4 · LimitedFinal reportCessna 208 · Ellington, CTThe pilot’s failure to maintain a proper glidepath to the runway, which resulted in a runway undershoot and collision with terrain.NTSB ERA21LA276Accident · Minor injuriesClass 4 · LimitedFinal reportSchweizer SGS 1-26E · Willimantic, CTThe failure of the student to achieve the proper touchdown point resulting in landing undershoot.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 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 GAA18CA529Accident · No injuriesData collectionFinal reportPiper PA46 · Hartford, CTThe pilot’s unstabilized approach and hard landing, which resulted in a nose landing gear collapse.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 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 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.NTSB ERA12FA483Accident · 1 fatalField investigationFinal reportCessna 172P · Plainville, CTThe pilot's failure to maintain the proper glidepath during final approach in visual meteorological conditions, resulting in collision with a berm.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 ERA12FA030Accident · 1 fatalField investigationFinal reportCirrus Design SR22 · Danbury, CTThe pilot did not maintain clearance from a lighted tower during final approach in night visual conditions.NTSB ERA10LA113Accident · 1 fatalLimited investigationFinal reportFoster John Glasair III · Oxford, CTThe pilot's failure to maintain a proper approach path during visual conditions at dusk, which resulted in an in-flight collision with power lines.NTSB ERA09LA064Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Groton, CTThe student pilot’s failure to maintain a proper descent profile to avoid trees during the night visual approach and the flight instructor’s inadequate oversight.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.