Eurocopter Deutschland Gmbh EC135T2 N405TJ accident near Philadelphia, Pennsylvania

Probable cause

The sUAS operator’s failure to see and avoid a helicopter, resulting in a midair collision between the helicopter and the sUAS.

NTSB analysis

The purpose of the helicopter flight was a medical resupply for a local hospital. According to the pilot of the helicopter, while on final approach to the hospital’s helipad, he heard and felt something impact the upper portion of the helicopter. After the impact sound, the pilot reported seeing a small black object fall down the right side of the windscreen. The pilot continued the approach to the helipad and landed uneventfully. After landing, an inspection of the helicopter revealed one of the main rotor blades sustained substantial damage. The pilot reported that there were no signs of bird snarge or feathers to indicate the impact was with a bird.

After the accident, small unmanned aircraft system (sUAS) operator, who had been operating a sUAS in the area of the accident flight, reported to a Federal Aviation (FAA) office that he had heard a helicopter and attempted to land his sUAS. After the helicopter flew by, he reported that his control station lost contact with the sUAS. An FAA inspector and the sUAS operator were unsuccessful in their subsequent search for the sUAS. Multiple follow up attempts to interview the sUAS operator and to retrieve the flight controller’s datalog were unsuccessful. Based on the available information, the object that impacted the helicopter was likely the operator’s sUAS.

Text from the NTSB. Open the NTSB docket for ERA25LA129 for the full record.