NTSB investigations, CT
31 cases where the first occurrence was “In flight collision with object”.
Cases per year
| 1984 | 3 |
|---|---|
| 1985 | 2 |
| 1986 | 1 |
| 1988 | 2 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 4 |
| 2002 | 2 |
| 2004 | 3 |
| 2005 | 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\" = 220)
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" = 220) 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 NYC06CA056Accident · Serious injuriesData collectionFinal reportPiper PA-28-140 · East Killingly, CTThe flight instructor's delayed decision to discontinue the simulated forced landing, which resulted in a collision with trees.NTSB IAD05LA050Accident · No injuriesLimited investigationFinal reportPiper PA-31P-350 · Ridgefield, CTThe pilot's improper IFR procedure by flying below the minimum descent altitude, which resulted in the airplane striking trees.NTSB NYC05LA040Accident · No injuriesLimited investigationFinal reportPiper PA-46-350P · Hartford, CTThe pilot's failure to maintain adequate clearance from trees during the approach to the runway. A factor related to the accident was the nighttime conditions.NTSB IAD04FA025Accident · 2 fatalField investigationFinal reportRobinson R-44 · Killingly, CTThe pilot in command's intentional flight into instrument meteorological flight conditions, and his failure to maintain obstacle clearance which resulted in a controlled descent into trees. Factors included the pilot's inadequate weather evaluation, low cloud…NTSB NYC04FA127Accident · 1 fatalField investigationFinal reportMooney M20J · Oxford, CTThe pilot's failure to maintain altitude/clearance during an instrument approach, which resulted in a collision with trees prior to the runway. Factors were nighttime conditions and cloud cover.NTSB IAD02LA068Accident · No injuriesLimited investigationFinal reportCessna 150 · Griswold, CTthe pilot's improper pre-flight planning and decision to depart a field with insufficient runway. Factors were the rough/uneven terrain, high obstructions and the tailwind.NTSB IAD02FA043Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Oxford, CTThe pilot's failure to follow the published instrument approach procedure. Factors were the night and low ceiling conditions.NTSB NYC02FA009Accident · 1 fatalField investigationFinal reportCessna 152 · Middlefield, CTThe pilot's failure to maintain sufficient altitude while maneuvering, which resulted in a collision with terrain. Factors in the accident were the dark night, rising terrain, and clouds.NTSB IAD01LA106Accident · Serious injuriesLimited investigationFinal reportDigimas Starduster Too · Watertown, CTthe student pilot's inattention while maneuvering at low altitude, which resulted in collision with trees. A factor in the accident was the student pilot's intentional low-altitude maneuvering.NTSB IAD01FA070Accident · 1 fatalField investigationFinal reportPiper PA-32R-301 · Greenwich, CTThe pilot's failure to maintain control of the airplane while maneuvering in instrument meteorological conditions, due to spatial disorientation. Factors in the accident were the fog, and the pilot's use of a sedating medication.NTSB NYC01LA121Accident · Minor injuriesLimited investigationFinal reportSchweizer SGS 1-26E · New Milford, CTthe student pilot's improper decision to fly northeast of the airport with winds from the southwest, and his subsequent diverted attention to the glider's proximity to the airport while he searched for thermals, which resulted in an off airport landing.NTSB NYC00LA221Accident · Minor injuriesLimited investigationFinal reportPiper PA28-235 · Chester, CTThe CFI's delayed remedial action.NTSB NYC00FA057Accident · 1 fatalField investigationFinal reportCessna 152 · N. Stonington, CTThe pilot's failure to maintain aircraft control while landing. A factor in this accident was the pilot's lack of recent flight experience.NTSB NYC00FA004Accident · 1 fatalField investigationFinal reportCessna 182R · Killingworth, CTThe pilot's failure follow the published instrument approach procedure. A factor in the accident was the low cloud ceiling.NTSB NYC98LA192Accident · Minor injuriesLimited investigationFinal reportCessna 140 · Watertown, CTWas the pilot's misjudged altitude of the airplane prior to performing a stall, and which resulted in the main landing gear contacting a rock wall.NTSB NYC95LA087Accident · 1 fatalLimited investigationFinal reportPiper PA-60-602P · Danbury, CTThe pilot's delay in initiating a go-around (aborted landing) and failure to assure that the flaps were properly reset for the go-around. Factors relating to the accident were: the pilot's failure to achieve the proper touchdown point for landing, the wet…NTSB BFO93FA128Accident · 1 fatalField investigationFinal reportTaylorcraft BC12-65 · Danbury, CTUndetermined.NTSB NYC92FA123Accident · 1 fatalField investigationFinal reportMBB BK-117 · Middletown, CTA wire strike after the pilot made a decision to continue the approach into an area of hazards. Factors related to the accident were the failure of the pilot and the hospital communicator to request all available information about the landing area and…NTSB NYC92LA020Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Groton, CTThe pilot's failure to maintain the minimum descent altitude during the approach. A factor was pilot fatigue.NTSB NYC91FA095Accident · 2 fatalField investigationFinal reportCessna 120 · Simsbury, CTThe pilot's intentional flight into terrain. Contributing to the accident were psychological conditions.NTSB NYC90FA063Accident · 1 fatalField investigationFinal reportPiper PA-28-181 · Fairfield, CTThe intoxicated pilot's failure to attain/maintain a safe altitude to provide clearance from the tree.NTSB NYC90FA011Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Glastonbury, CTThe pilot-in-command's failure to maintain adequate altitude control during maneuvering flight. Contributing to the accident was the failure of the airplane's electrical system and the pilot's operation at night, without emergency lighting (flashlight).NTSB NYC89LA197Accident · No injuriesLimited investigationFinal reportSchweizer SGS-2-32 · Plymouth, CTImproper compensation for wind conditions by the pilot. A factor related to the accidetn was: the downdraft.NTSB NYC89LA034Accident · Serious injuriesLimited investigationFinal reportCessna 340 · Oxford, CTCollision with trees and terrain due to the pilot exceeding approach minimum altitude during an ILS approach.NTSB NYC88LA240Accident · Minor injuriesLimited investigationFinal reportCessna 150 · Burlington, CTThe plt was attempting to land at the mountain arpt. Patwas indicated the winds were from the north at 15 KTS. Gusts were not reported. The plt made her apch at 70 mph IAS and with 20 deg of flaps deployed. As she flared the acft, she encountered a gust of…NTSB NYC87DNE01Accident · Serious injuriesFinal reportKosch Whitehead #21 · Stratford, CTThe experimental aircraft was making taxi tests on an abandoned taxiway when it became airborne. A photographer rushed out from a marked safety area directly in the flight path of the aircraft and was struck by the aircraft receiving a broken arm. The…NTSB NYC86LA055Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Ellington, CTWhile on apch for landing, about 50 ft from the rwy, the landing gear contacted a bridge and the acft bounced into the air. Pwr was added at this time and again the acft bounced. The acft was then landed on the rwy and it skidded to a stop. The plt stated she…NTSB NYC86FA037Accident · 2 fatalField investigationFinal reportBell 206B · Cheshire, CTThe helicopter was flying at or near the base of the overcast when it contacted a tree and descended to ground impact. Witnesses reported hearing the eng operating during the accident sequence and the area was covered with heavy fog. No mechanical malfunction…NTSB NYC85LA023Accident · No injuriesLimited investigationFinal reportBeech BE-55E · Groton, CTAs the acft broke out of the 300 overcast layer the plt saw birds flying off of the rwy threshold. Due to IFR conditions and low altitude the plt elected not to go around. The tower advised the plt of the birds on 2 mile final on the ILS apch.NTSB NYC84FA307Accident · 4 fatalField investigationFinal reportBell 206B · Wallingford, CTThe acft collided with wires after the plt announced by radio that he was going to make a low pass over the site of an outdoor event that he had just attended. Some witnesses saw the helicopter flying extremely low. It appeared that one of the landing skid…NTSB NYC84LA232Accident · No injuriesLimited investigationFinal reportRobinson R22 · Ellington, CTAfter being directed to do so by the arpt mgr the pilot was air taxiing to parking when the main rotor blades contacted one main rotor blade of a parked bell 206. The pilot related that he assumed he would clear the 206 since he was watching the airport mgr…