# Accident 20170314003049A: Mcdonnell Douglas Heli Co 369FF, Chalmers, IN, March 14, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 14, 2017, 15:46 local time
- Place: Chalmers, IN
- Damage: Destroyed
- Phase of flight: Other, Specify
- Operating rules: Rotorcraft external load (Part 133)
- Operator: CUCL
- Location: 40.6486° N, 86.8433° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.6486&lon=-86.8433&mi=10
- Aircraft: N530KD, a cancelled registration (https://openairdocs.org/deregistered/N530KD-2017-07-14) (OpenAirDocs)
- Registry model: Mcdonnell Douglas Heli 369FF (registry code 3027371, https://openairdocs.org/model/mcdonnell-douglas-heli-369ff) (OpenAirDocs)
- Reported make and model: MCDONNELL DOUGLAS HELI CO 369FF
- People aboard: 1
- Fatal injuries: 1
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 15,640 total
- NTSB investigation: [NTSB CEN17FA127](https://openairdocs.org/ntsb/CEN17FA127) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170314003049A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON MARCH 14, 2017, AT 1546 EASTERN DAYLIGHT TIME, AN MD HELICOPTERS MODEL 369FF HELICOPTER, REGISTRATION NUMBER N530KD, IMPACTED TERRAIN DURING A POWER LINE CONSTRUCTION FLIGHT. THE PILOT WAS FATALLY INJURED AND THE HELICOPTER WAS DESTROYED. THE HELICOPTER WAS REGISTERED TO ^ROBIN M ROGERS^ AND OPERATED BY ROGERS HELICOPTERS, INC., UNDER THE PROVISIONS OF 14 CFR PART 133 AS AN EXTERNAL LOAD OPERATION. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT AND NO FLIGHT PLAN WAS FILED.

THE WHITE COUNTY AIRPORT (MCX) RECORDED AT 1535: WIND FROM 350 AT 12 KNOTS GUSTING TO 19 KNOTS, 7 STATUTE MILES VISIBILITY WITH LIGHT SNOW, BROKEN CLOUDS AT 3,500 FT, OVERCAST CLOUD LAYER AT 4,800 FT, TEMPERATURE 27F, DEW POINT 16F, AND ALTIMETER SETTING 30.25 INCHES OF MERCURY. THREE WITNESSES INDEPENDENTLY REPORTED GUSTING WIND AT THE TIME OF THE ACCIDENT. A COMPANY CREWMEMBER SITTING IN A VEHICLE WITH WINDOWS OPEN STATED THAT AT THE TIME OF THE ACCIDENT HE FELT THE WIND PAUSE MOMENTARILY, FOLLOWED BY A GUST.

THE PURPOSE OF THE FLIGHT WAS TO THREAD A CABLE THROUGH A SERIES OF TOWERS. USING GROUND EQUIPMENT, THE CABLE WOULD BE USED TO PULL A LARGER CABLE, WHICH IN TURN WOULD THEN PULL A FINAL SET OF 6 CABLES. THE TERM SOCK LINE IS THE NOMENCLATURE APPLIED TO THE SINGLE CABLE BEING THREADED BY THE HELICOPTER.

AT THE TIME OF THE ACCIDENT, THE SOCK LINE WAS FED FROM A TRUCK-MOUNTED REEL NINE TOWERS AWAY, APPROXIMATELY 11,000 FEET AWAY. A LONG METAL BAR (NEEDLE) WAS USED TO THREAD THE SOCK LINE THROUGH THE TOWERS. THE NEEDLE HAS 2 EYES WELDED TO IT, ONE NEAR THE CENTER AND THE OTHER AT THE END DISTAL FROM THE SOCK LINE ATTACHMENT. BOTH EYES HAVE A PROJECTION, OR BARB, POINTING IN THE DIRECTION OF THE SOCK LINE. THIS BARB IS USED TO HOOK THE NEEDLE TO THE TOWER.

THE HELICOPTER PULLED THE SOCK LINE FROM ONE TOWER TO THE NEXT, THREADING IT THROUGH EACH TOWER, UNWINDING THE REEL. WHEN THE HELICOPTER ARRIVED AT THE NEXT TOWER AND CEASED PULLING, A BRAKEMAN AT THE REEL STOPPED IT FROM UNWINDING. THE PILOT AND THE BRAKEMAN WERE IN RADIO CONTACT, AND COORDINATED THE UNWINDING ACTION.

THE HELICOPTER WAS EQUIPPED WITH A SIDE PULL HOOK ASSEMBLY AND A CARGO HOOK. THE CARGO HOOK WAS ATTACHED TO A 50 FOOT LONG LINE WITH A GRAPPLING HOOK (GRAPPLE). THE PILOT HOOKED THE GRAPPLE TO THE NEEDLE USING THE CENTER EYE OF THE NEEDLE.

A WITNESS PROVIDED A VIDEO RECORDING OF THE ACCIDENT FLIGHT. THE VIDEO SHOWED THE PILOT ATTEMPT TO HOOK THE NEEDLE TO THE TOWER STRUCTURE.  THE HELICOPTER SEEMED TO STRUGGLE TO STRETCH THE SOCK LINE TO THE TOWER. THE FIRST ATTEMPT FAILED.  A SECOND ATTEMPT APPEARED TO MISS THE DESIRED CONTACT POINT.  THE HELICOPTER'S ALTITUDE AND ATTITUDE VARIED PRESUMABLY DUE TO WIND GUSTS. THE ATTITUDE OF THE HELICOPTER BECAME MORE VARIABLE. THE NOSE PITCHED UP, AND THE HELICOPTER BEGAN MOVING DOWNWIND. THIS ACTION MOVED THE NEEDLE TOWARD THE TOWER. THE NEEDLE CONTACTED THE LADDER RUNG ASSEMBLY ON THE TOWER.  THE LADDER IS NEAR THE INTENDED NEEDLE PLACEMENT POINT.  THE HELICOPTER CONTINUED MOVING DOWNWIND WHILE THE NEEDLE BECAME ANCHORED TO THE TOWER. THE HELICOPTER BECAME TETHERED TO THE TOWER AND LOST CONTROL. THE LONGITUDINAL AXIS OF THE HELICOPTER BECAME NEARLY VERTICAL, NOSE UP, WHILE STILL TETHERED TO THE TOWER. THE NEEDLE EYE THAT THE GRAPPLE WAS ATTACHED TO BROKE FREE FROM THE NEEDLE, WHIPPING THE 50 FOOT LINE AND GRAPPLE AWAY FROM THE TOWER, SENDING THE LINE UNDER THE HELICOPTER.  FREE OF THE TETHER, THE PILOT APPEARED TO HAVE LEVELLED THE HELICOPTER WHILE DESCENDING, HOWEVER THE HELICOPTER DESCENDED INTO THE LINE. THE LINE TANGLED WITH THE MAIN AND TAIL ROTORS, SHEARING THE BLADES, RESULTING IN THE HELICOPTER FALLING APPROXIMATELY 50 FEET TO THE GROUND.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN17FA127](https://openairdocs.org/ntsb/CEN17FA127), Mar 14, 2017: Mcdonnell Douglas Heli 369FF (N530KD), Chalmers, IN, destroyed, 1 fatal. Probable cause: The pilot's failure to ensure that the needle did not entangle with the tower's vertical lattice as he moved the helicopter rearward, which resulted in the helicopter becoming tethered to the tower…

## Other reports on N530KD (1)

Matched to the same aircraft by N-number and date.

- [Accident 20120930022589A](https://openairdocs.org/incident/20120930022589A), Sep 30, 2012: Mcdonnell Douglas Heli Co 369FF (N530KD), Decorah, IA, Substantial damage. N530KD departed kfod with a destination of kdeh. 58 minutes into the flight the low fuel caution light eluminated, 2-3 minutes later the engine flamed out and…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.
