- Date
- July 2, 2009, 21:00 local (Jul 3, 2009, 01:00 UTC)
- Place
- Loris, SC
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N53963Eurocopter AS 350 B2
- Defining event
- Approach: Collision during takeoff/land
- Weather
- Visual (VMC) · Night
- Status
- Completed · report March 3, 2010
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20090702047879A
- Case key
- 74191
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The crew's failure to see and avoid a steel pole during a nighttime approach to the helipad.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot was performing a visual nighttime approach to a hospital heliport to pick up a patient for transport. The pilot flew the final approach west, into the wind. As the helicopter approached the helipad the two onboard clinicians were calling out obstructions, such as trees and light poles. About 5 feet above the helipad the tailrotor struck a short steel pole adjacent to the helipad. The helicopter shuttered and vibrated, but the pilot was able to continue the landing. Although all three crewmembers had been to the heliport before, they forgot about the short steel poles aligned adjacent to the helipad. The recorded weather at an airport approximately 15 miles northeast of the accident site, about the time of the accident, included calm wind, clear skies, and visibility of 10 miles. After the accident, the hospital removed the short steel poles adjacent to the helipad and the Federal Aviation Administration initiated research into the crew training, operations specifications, and the history of the poles being erected near the helipad. Additionally, the operator’s regional safety manager stated that all pilots have begun additional training to position aircraft in such a manner to ensure that all components of the aircraft are clear of all hazards on the periphery or boundaries of marked landing zones/heliports, rather than attempting to place the center of the aircraft at the center of the landing zone/heliport. The operator also initiated a reassessment of hazards at landing zones/heliports within each of their regions’ normal operating area, and reported that the information from the reassessments will be added as part of normal preflight briefings and risk assessments.
Factual narrative
On July 2, 2009, about 2100 eastern daylight time, a Eurocopter AS 350 B2 helicopter, N53963, operated by Omniflight Helicopters Inc., was substantially damaged while landing at Loris Community Hospital Heliport (5SC5), Loris, South Carolina. The certificated commercial pilot and two clinicians were not injured. Night visual meteorological conditions prevailed and a company flight plan was filed for the medical positioning flight conducted under the provisions of 14 Code of Federal Regulations Part 91. The flight originated from Conway-Horry County Airport (HYW), Conway, South Carolina, at 2040. According to the pilot, the purpose of the flight was to pick up a patient at 5SC5 for transport. The pilot initiated an approach to 5SC5, to the west, into the wind. As the helicopter approached the helipad, the clinicians were "call(ing)" clear of obstructions, such as trees and light poles. About 5 feet above the helipad, the helicopter shuttered and vibrated. The pilot continued the landing and performed an emergency engine shutdown. A Federal Aviation Administration (FAA) inspector subsequently interviewed the pilot and clinicians. The FAA inspector stated that although all three persons had been to the heliport before, they simply forgot about several steel poles aligned adjacent to the helipad. Just prior to landing, the tailrotor struck one of the steel poles, and the helicopter came to rest on the helipad. Two of the four steel poles were about 2 feet high and 4 inches in diameter, and the other two were about 3 feet high and 6 inches in diameter. The poles were placed along one side of the helipad along the perimeter line that separated the helipad from a road. According to the operator's Vice President of Clinical Services, all clinicians are trained with the pilots in Air Medical Resource Management (AMRAM). Through that training, the clinicians are taught to point out obstacles and hazards to flight. Examination of the helicopter by the FAA inspector revealed damage to the tailboom, tailrotor, tailrotor gearbox, tailrotor drive shaft, main rotor, and horizontal stabilizer. The recorded weather at an airport approximately 15 miles northeast of the accident site, at 2058, included calm wind, clear skies, and visibility 10 miles. The pilot had accumulated 2,587 total flight hours in rotorcraft, including 501 hours as pilot-in-command in the Eurocopter AS 350 B2 helicopters. The pilot logged 46, 19, and 2 flight hours in the previous 90, 30, and 1 days respectively. Subsequent to the accident, the hospital removed the short steel poles adjacent to the helipad. The FAA inspector stated that the FAA will research the crew training, ops specs, and the history of the poles being erected near the helipad. The Eastern Region Safety Manager for Omniflight stated the following in the “Recommendation” section of the NTSB Pilot/Operator Report form: “The conclusion of the Pilot involved and the Company Chief Pilot was that the incident could have beenaverted if the landing to the landing zone had been made further into the landing zone as to prevent the tail rotor from impacting any obstruction in the vicinity of the edge of the landing zone. Initial and immediate action has been to indoctrinate all pilots flying into medium to small sized landing zones / heliports to position aircraft in such a manner to ensure that all components of the aircraft are clear of all hazards on the periphery and or confines/boundaries of marked landing zones/heliports rather than attempting to place the center of the aircraft at the center of the landing zone / heliport. Corporate wide reassessment of hazards at landing zones/heliports within each regions normal operating area is underway and will be added/updated as needed and posted as part of normal preflight briefings / risk assessments.” [ This Report was modified on December 21, 2009 ]
Aircraft
- Registration
- N53963
- Reported as
- Eurocopter AS 350 B2
- Category
- Helicopter
- Serial number
- 3963
- Airframe hours
- 2,377
- Engine
- Turbomeca ARRIEL 1D1, 625 horsepower, turbo shaft
- Damage
- Substantial damage
- Flight
- Positioning · Part 91
- Operator
- Omniflight Helicopter Inc.
- Registered owner
- US Bancorp Equipment Finance Inc
- Airworthiness certificate
- Standard, Normal
- Last inspection
- AAIP · June 29, 2009 · 7 hours before
- Departed
- HYW · Conway, SC
- Destination
- 5SC5 · Loris, SC
- Flight plan
- Company VFR
- Airport
- 5SC5 · Loris Community Hospital Helip
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 43
- Injuries
- None
- Certificates
- Private, Commercial
- Airplane ratings
- Single-engine land
- Instrument ratings
- Helicopter
- Medical
- Class 2, With waivers/limitations
- Last flight review
- December 15, 2008
- Seat
- Right
- Flight hours
- 2,701 total · 501 in this make and model · 1,901 as pilot in command · 46 in the last 90 days · 19 in the last 30 days · 2 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Night
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 79 °F, dew point 64 °F
- Altimeter
- 29.87 inHg
- Observed at
- CPC, 15 nm away
Docket · 5
The files NTSB released with the investigation on August 21, 2009, on NTSB’s docket system: statements, records, photos and specialists’ reports. 14.3 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.