The U.S. aircraft register, updated daily
Accidents · NTSB NYC85FA048 · Preliminary: the investigation is not finished

Robinson R-22-A accident near Ellington, Connecticut, December 22, 1984

On December 22, 1984 at about 9:50 pm local time, a Robinson R-22-A (helicopter), registered N84958, was destroyed in an accident near Ellington, Connecticut (Ellington airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 22, 1984 · about 9:50 pm local time
Place
Ellington, Connecticut · Ellington
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Robinson R-22-A · all R-22-As on the register
Registration
N84958 · no longer on the register · serial 407
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

THE NON-INST RATED PLT CONTINUED FLT INTO IMC CONDITIONS IN A HELICOPTER WHICH WAS NOT EQUIPPED FOR FLT ON INSTRUMENTS. THERE IS NO RECORD OR WITNESSES OF THE PLT HAVING RECEIVED A FORMAL WX BRIEFING BUT IT IS REPORTED THAT THE PLT WAS INFORMED OF FOG MOVING TOWARD AND EVENTUALLY 'SOCKING IN' THE ARPT. THE PLTS REPLY TO THE LAST CALL OF A 'SOCKED IN' CONDITION WAS 'I HAVE THE ARPT IN SIGHT'. WITNESSES SAW THE ACFT HEADING AWAY FROM THE ARPT AFTER HAVING HEARD IT FLYING TOWARD THE ARPT. THE ACFT WAS SEEN TO DESCEND AT A STEEP ANGLE TOWARD THE GROUND JUST PRIOR TO IMPACT. THE SIGHTING WAS SHORT (APROX 3 SECONDS) AND MADE MORE DIFFICULT BY THE REDUCED VISIBILITY DUE TO FOG AND FADING DAYLIGHT (DUSK). INVESTIGATION REVEALED NO MECHANICAL OR PHYSICAL REASONS OF A CONTRIBUTORY NATURE.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: commercial pilot
  • Ratings: rotorcraft: helicopter
  • Flight time: 33 in the last 90 days; 9 in the last 30 days; 118 as pilot in command; 117 on instruments
  • Medical certificate: Class 2 (valid medical--no waivers/lim.)
  • Seat: unk

The aircraft

  • Airframe total time: 505 hours
  • Last inspection: 100-hour inspection, December 19, 1984; 5 hours since
  • Maximum gross weight: 1,300 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Avco Lycoming O-320-B2C (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: 7B9 Ellington CT at 8:20 pm
  • Flight plan: none
  • Runway 3, 1,800 ft by 50 ft

Weather at the time

  • Light: dusk
  • Wind: from 030° at 7 knots
  • Temperature: 36°F (2°C), dew point 34°F (1°C)
  • Altimeter: 29.00 inHg
  • Observation at 9:50 pm from BDL, 10 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.