NTSB investigations, CT
17 cases where the first occurrence was “In flight collision with terrain/water”.
Cases per year
| 1982 | 2 |
|---|---|
| 1984 | 2 |
| 1985 | 1 |
| 1986 | 3 |
| 1988 | 2 |
| 1992 | 2 |
| 1993 | 1 |
| 1997 | 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\" = 230)
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" = 230) 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 NYC06FA137Accident · 2 fatalField investigationFinal reportGates Learjet 35A · Groton, CTThe crew's failure to properly monitor the airplane's altitude, which resulted in the captain's inadvertent descent of the airplane into water. Contributing to the accident were the foggy weather conditions, and the captain's decision to descend below the…NTSB IAD02FA024Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Milford, CTThe pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.NTSB NYC00LA111Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301 · East Haddam, CTThe private pilots failure to obtain the proper touchdown point and the CFI's delay in remedial action.NTSB IAD97LA120Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-180 · Danbury, CTThe pilot's improper planning/decision to not use actual occupant weights and compute takeoff data, which resulted in an overweight takeoff towards rising terrain.NTSB NYC93FA159Accident · 2 fatalField investigationFinal reportSwearingen SA-226-TC · Hartford, CTFailure of the copilot (second-in-command) to follow the checklist, assure the gear was extended for landing and attain or maintain adequate airspeed (VMC); and failure of the pilot-in-command (PIC) to properly supervise the flight and take sufficient…NTSB BFO92FA141Accident · 1 fatalField investigationFinal reportChampion 7KCAB · East Haddam, CTThe pilot's decision to attempt an aerobatic maneuver without adequate altitude for recovery.NTSB BFO92LA123Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Windham, CTThe pilot's improper IFR operation. Contributing was the pilot's instrument flight inexperience.NTSB NYC89FA059Accident · 1 fatalField investigationFinal reportBeech A36 · Bridgeport, CTTwice prior to being established on final the pilot was asked if he was getting proper indications for the approach to land. Contact was subsequently lost while the pilot was attempting to make an ILS approach to runway 06 at Bridgeport. The aircraft was…NTSB NYC88FA093Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Stratford, CTThe pilot and pilot-rated pax received vectors for multiple ILS approaches in deteriorating conditions. On the first attempt the aircraft passed over witnesses but was off course and not in a position to land. The second attempt was aborted before reaching…NTSB NYC86FA096Accident · 5 fatalField investigationFinal reportPiper PA-24-180 · Somers, CTThe acft, on a night flt, was seen flying about 1 mi west of ellington arpt. A witness saw the acft flying north and just above the 800 ft high terrain. The acft was in a gradual descent and it appeared that it would not clear terrain ahead. Afterwards the…NTSB NYC86FNE02Accident · No injuriesFinal reportFolsom Sonerai II · Middlebury, CTThe plt reported that the acft was slow to climb after takeoff and had reached an alt of only 100' AGL at the end of the 5000' lond rwy. The plt continued to state the acft was unable to clear rising terrain aprx 1/2 mile from the arpt. The acft contacted the…NTSB NYC86FA057Accident · 2 fatalField investigationFinal reportCessna 182L · So.Glastonbury, CTThe acft was on a VOR instrument apch when it collided with 250 ft high terrain approx 6 miles south of the arpt and approx 2 miles north of the vor/faf. Shortly before the accident the pilot notified ATC that he was in turbulence; then reported he was clear…NTSB NYC85FA104Accident · 1 fatalField investigationFinal reportPiper PA-28-180 · East Haddam, CTDuring approach to runway 14 pilot decided to go around. Aircraft turned left about 90 degrees and collided with rising terrain .2 NM east of the runway. The rising terrain parallels runway 14.NTSB NYC85LA002Accident · Minor injuriesLimited investigationFinal reportPiper PA-18-150 · Waterbury, CTAfter liftoff, the plt initiated a turn into the crosswind to maintain runway heading. As he did so, a wind gust tipped the acft in the direction of the turn. Ground contact occurred before corrective control inputs by the plt could take effect.NTSB NYC84FA295Accident · 1 fatalField investigationFinal reportAero Commander 680V · Bridgeport, CTThe acft descended into the water six & 1/2 miles sw of Bridgeport, CT. The acft was on an ILS apch to rwy 06. The acft was in communication with NY TRACON arrvl radar and on his initial call had indicated a desire for a clearance direct tobridgeport. A brief…NTSB NYC82FA188Accident · 1 fatalField investigationFinal reportCessna 310R · Danbury, CTApproaching the destination arpt, the plt was advised to plan a VOR rwy 24 approach & that he would be turned just inside the faf. At 0055, newark a/c identified the acft 3 mi north of the arpt still at 2,000 ft & asked the plt if he was able to execute the…NTSB NYC82FA050Accident · 1 fatalField investigationFinal reportCessna T337C · Bloomfield, CTAt 0630 & 0800 the plt received wx briefing for an IFR flt to bridgeport, CT & was advised of flt precautions for icing, low ceilings & visibilities. The flt departed at 0907. At 1118 the plt diverted to windsor locks for landing at bradley intl arpt because…