Fatal NTSB investigations, CT

12 cases where the first occurrence was “In flight collision with terrain/water”.

Cases per year

19822026
Fatal NTSB investigations, CT per year, 1982–2026: 12 cases
19822
19841
19851
19862
19882
19921
19931
20011
20061

Latest 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.\"highestInjuryLevel\" = 'Fatal'
    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.

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…Jun 2, 2006 · N182K · DestroyedNTSB 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.Dec 30, 2001 · N7427J · Substantial damageNTSB 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…Aug 17, 1993 · N220KC · DestroyedNTSB BFO92FA141Accident · 1 fatalField investigationFinal reportChampion 7KCAB · East Haddam, CTThe pilot's decision to attempt an aerobatic maneuver without adequate altitude for recovery.Sep 14, 1992 · N561EK · DestroyedNTSB 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…Dec 24, 1988 · N262C · DestroyedNTSB 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…Feb 20, 1988 · N2469M · DestroyedNTSB 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…Mar 31, 1986 · N6599P · DestroyedNTSB 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…Jan 3, 1986 · N3349R · DestroyedNTSB 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.Apr 10, 1985 · N55408 · DestroyedNTSB 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…Sep 4, 1984 · N100CT · DestroyedNTSB 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…Aug 9, 1982 · N98841 · DestroyedNTSB 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…Mar 11, 1982 · N7721X · Destroyed