NTSB investigations, CT
16 cases where the first occurrence was “Airframe/component/system failure/malfunction”.
Cases per year
| 1983 | 3 |
|---|---|
| 1984 | 2 |
| 1985 | 1 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 1998 | 1 |
| 1999 | 2 |
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\" = 130)
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" = 130) 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 NYC99LA139Accident · No injuriesLimited investigationFinal reportAero Commander 500S · Windsor Locks, CTHydraulic system contamination which prevented normal landing gear extension. A factor was the misjudged landing flare by the flying pilot.NTSB NYC99LA102Accident · Minor injuriesLimited investigationFinal reportGlaser-Dirks DG-400 · New Milford, CTThe manufacturer's use of inadequate adhesive material which resulted in the de-bonding and subsequent failure of the wing spar pin-lock assembly.NTSB NYC98FA062Accident · Minor injuriesField investigationFinal reportAerospatiale ATR-42-320 · Windsor Locks, CTThe improper overhaul of lug holes on the fuel/oil heat exchanger. A factor was the lack of direction contained in the manufacturer's overhaul manual for working with the lug holes.NTSB BFO93LA067Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Willimantic, CTFailure of the pilot to follow emergency procedures to ensure that the gear was locked. A factor related to the accident was the total electrical failure and the construction site located beside the runway.NTSB NYC91FA125Accident · No injuriesField investigationFinal reportBoeing 727-100QC · Windsor Locks, CTA catastrophic and uncontained failure of the no.3 engine which resulted in a fuel fed fire.NTSB NYC90LA095Accident · No injuriesLimited investigationFinal reportBeech Baron 58 · Danbury, CTPilot factor in that the pilot elected to abort the takeoff with insufficient r/w remaining to stop the aircraft on the runway and collided with a fence, car & van.NTSB NYC88LA130Accident · No injuriesLimited investigationFinal reportBeech 35 · New Haven, CTDuring engine start the throttle jammed in the full forward position and could not be pulled back to the idle position to retard the power. The aircraft started rolling and collided with an unoccupied parked aircraft. Examination of the throttle control…NTSB NYC87FA250Accident · 1 fatalField investigationFinal reportPiper PA-28-236 · Gaylordsville, CTThe pilot of the Piper PA-28-236 was cruising at 6000 ft at night when he reported a failure of his vacuum pump followed by loss of his attitude indicator and directional gyro. The aircraft was observed to make a 360 degree turn on the radar scope. The air…NTSB NYC86LA208Accident · Serious injuriesLimited investigationFinal reportBeech C24R · Hartford, CTThe Beech 24R pilot noticed a build-up of a substance on the windshield. He also experienced a problem controlling the propeller. He said upon landing he could not judge forward visibility and flared high (30-40 ft). The pilot reported that the aircraft…NTSB NYC86LA190Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTWhen the plt checked the airspeed indicator on takeoff, he saw no indication of speed & aborted the takeoff, but was unable to stop on the remaining rwy. The acft contd off the departure end, when down an embankment & became inverted. An exam revealed the…NTSB NYC85IA062Incident · No injuriesIncident investigationFinal reportBeech BE-99 · Putnam, CTPlt stated that during tkf the acft started to yaw & roll in a manner consistent with wake turbulence encounter. He applied full opposite rudder & aileron. Normal directional was regained between 50-75 ft above the gnd. The acft was leveled for cruise at 5000…NTSB NYC84LA134Accident · No injuriesLimited investigationFinal reportHughes 269A · Danbury, CTWhile in flt, the helicopter yawed & the eng RPM increased. The plt retarded the throttle to idle, lowered the collective & initiate an autorotation. While attempting to reach a suitable landing area, the plt kept his speed up to avoid buildings. However,…NTSB NYC84LA124Accident · No injuriesLimited investigationFinal reportBeech B19 · Simsbury, CTDuring an instructional flt, a landing was made during which control of the acft was lost and the acft collided with a snow bank hard enough to shear off one of the main landing gear. The other main gear collapsed but the nose gear did not. The instructor…NTSB NYC83FA122Accident · Serious injuriesField investigationFinal reportCessna 172N · N. Stonington, CTThe acft collided with a tree during a go-around at night following a downwind precautionary landing. During the flt the plt had noted the fuel gauges at low readings and said he suspected a 'fuel leak'. He made radio calls to try to go to an arpt before fuel…NTSB NYC83FA121Accident · 1 fatalField investigationFinal reportMooney M-20K · Old Lyme, CTThe acft collided with the ground in IMC after the plt reported he lost his vacuum instruments. The flt originated at mattituck, NY with a destination of lebanon, NH. After departure the plt was cleared to climb to 7000 ft. the instrumentrated pilot was on an…NTSB NYC83FA086Accident · No injuriesField investigationFinal reportCessna 210L · Avon, CTThe acft collided with a tree and broke the nose landing gear during an emergency landing after electrical failure. After the failure, using matches and a flashlight, the plt tried to land but could not find the arpt. The weather was deteriorating so when a…