# NTSB investigations, CT: In flight collision with terrain/water NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports. ## Latest cases - [NTSB NYC06FA137](https://openairdocs.org/ntsb/NYC06FA137.md): Gates Learjet 35A · Groton, CT · Accident · 2 fatal · Field investigation · Final report · Jun 2, 2006 · N182K · Destroyed > The 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 IAD02FA024](https://openairdocs.org/ntsb/IAD02FA024.md): Piper PA-28R-180 · Milford, CT · Accident · 1 fatal · Field investigation · Final report · Dec 30, 2001 · N7427J · Substantial damage > The 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 NYC00LA111](https://openairdocs.org/ntsb/NYC00LA111.md): Piper PA-32R-301 · East Haddam, CT · Accident · No injuries · Limited investigation · Final report · Mar 30, 2000 · N8041B · Substantial damage > The private pilots failure to obtain the proper touchdown point and the CFI's delay in remedial action. - [NTSB IAD97LA120](https://openairdocs.org/ntsb/IAD97LA120.md): Piper PA-28R-180 · Danbury, CT · Accident · Serious injuries · Limited investigation · Final report · Sep 18, 1997 · N3102R · Destroyed > The 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 NYC93FA159](https://openairdocs.org/ntsb/NYC93FA159.md): Swearingen SA-226-TC · Hartford, CT · Accident · 2 fatal · Field investigation · Final report · Aug 17, 1993 · N220KC · Destroyed > Failure 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 BFO92FA141](https://openairdocs.org/ntsb/BFO92FA141.md): Champion 7KCAB · East Haddam, CT · Accident · 1 fatal · Field investigation · Final report · Sep 14, 1992 · N561EK · Destroyed > The pilot's decision to attempt an aerobatic maneuver without adequate altitude for recovery. - [NTSB BFO92LA123](https://openairdocs.org/ntsb/BFO92LA123.md): Piper PA-28-180 · Windham, CT · Accident · No injuries · Limited investigation · Final report · Sep 5, 1992 · N3751R · Destroyed > The pilot's improper IFR operation. Contributing was the pilot's instrument flight inexperience. - [NTSB NYC89FA059](https://openairdocs.org/ntsb/NYC89FA059.md): Beech A36 · Bridgeport, CT · Accident · 1 fatal · Field investigation · Final report · Dec 24, 1988 · N262C · Destroyed > Twice 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 NYC88FA093](https://openairdocs.org/ntsb/NYC88FA093.md): Piper PA-34-200T · Stratford, CT · Accident · 2 fatal · Field investigation · Final report · Feb 20, 1988 · N2469M · Destroyed > The 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 NYC86FA096](https://openairdocs.org/ntsb/NYC86FA096.md): Piper PA-24-180 · Somers, CT · Accident · 5 fatal · Field investigation · Final report · Mar 31, 1986 · N6599P · Destroyed > The 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 NYC86FNE02](https://openairdocs.org/ntsb/NYC86FNE02.md): Folsom Sonerai II · Middlebury, CT · Accident · No injuries · Final report · Mar 1, 1986 · N27EF · Substantial damage > The 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 NYC86FA057](https://openairdocs.org/ntsb/NYC86FA057.md): Cessna 182L · So.Glastonbury, CT · Accident · 2 fatal · Field investigation · Final report · Jan 3, 1986 · N3349R · Destroyed > The 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 NYC85FA104](https://openairdocs.org/ntsb/NYC85FA104.md): Piper PA-28-180 · East Haddam, CT · Accident · 1 fatal · Field investigation · Final report · Apr 10, 1985 · N55408 · Destroyed > During 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 NYC85LA002](https://openairdocs.org/ntsb/NYC85LA002.md): Piper PA-18-150 · Waterbury, CT · Accident · Minor injuries · Limited investigation · Final report · Oct 3, 1984 · N83665 · Destroyed > After 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 NYC84FA295](https://openairdocs.org/ntsb/NYC84FA295.md): Aero Commander 680V · Bridgeport, CT · Accident · 1 fatal · Field investigation · Final report · Sep 4, 1984 · N100CT · Destroyed > The 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 NYC82FA188](https://openairdocs.org/ntsb/NYC82FA188.md): Cessna 310R · Danbury, CT · Accident · 1 fatal · Field investigation · Final report · Aug 9, 1982 · N98841 · Destroyed > Approaching 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 NYC82FA050](https://openairdocs.org/ntsb/NYC82FA050.md): Cessna T337C · Bloomfield, CT · Accident · 1 fatal · Field investigation · Final report · Mar 11, 1982 · N7721X · Destroyed > At 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… ## The whole list in SQL Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS: ```sql 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 ``` This list as a web page: https://openairdocs.org/ntsb?occurrence=230&state=CT --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.