- Date
- May 10, 2013, 18:42 local (23:42 UTC)
- Place
- Hartford, KY
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N94PHBell 206B
- Defining event
- Maneuvering-low-alt flying: Miscellaneous/other
- Weather
- Visual (VMC) · Day
- Status
- Completed · report August 29, 2013
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20130510024819A
- Case key
- 86863
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 pilot’s failure to avoid a powerline that crossed a field that he was spraying. Contributing to the collision was the company’s failure to specifically mention that flight hazards be identified during a pre-work conference.
Findings · 4
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
Before spraying a tract, the pilot circled it three times to look for lines, obstructions, houses, and people and to develop a plan to spray the field. He completed two spray passes, and during the third spray pass, he heard a “pop” sound and saw “the lines” as they contacted the windscreen. The helicopter was controllable for a “brief moment,” but it then yawed slowly to the right and slightly down at which point all control was lost. The helicopter continued to rotate clockwise and veered to the right, then impacted the ground on the left side. The pilot reported that there was no preimpact mechanical failure or malfunction with the helicopter or its systems, and that during his three orbits of the tract, he did not identify the power line that he subsequently contacted. While the company policy and procedures manual specified that the pilot identify potential problem areas or miscommunications, it did not specify that flight hazards be identified during the pre-work conference. Postaccident, the operator changed its policy and procedures manual and specifically stated that flight hazards be identified during the pre-work conference before spraying a tract.
Factual narrative
On May 10, 2013, about 1842 central daylight time, a Bell 206B, N94PH, registered to and operated by Provine Helicopter Service, Inc., collided with a powerline then the ground during an aerial application flight near Hartford, Kentucky. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 137 flight. The helicopter sustained substantial damage and the commercial pilot, the sole occupant, was not injured. The flight originated about 5 minutes earlier from a location immediately adjacent to the accident site. The pilot stated that he took the final load of chemical to complete the current tract, or field. He circled over it 3 times looking for lines, obstructions, houses and people and to develop a plan to spray the field. He completed 2 spray passes and during the 3rd spray pass, he heard a “pop” sound and saw “…the lines” as they contacted the windscreen. The helicopter was controllable for a, “brief moment” but it then yawed slowly to the right and slightly down at which point all control was lost. The helicopter continued to rotate clockwise and veered to the right, then impacted the ground on the left side. He reported there was no preimpact mechanical failure or malfunction with the helicopter or its systems. The company Policy and Procedures Manual in effect at the time of the accident specifies major duties and responsibilities of the pilot, which included information that a pre-work conference be conducted before application to each tract being sprayed. The pre-work conference specifies that the tract representative, “turn key”, ground crew, and pilot agree on and understand the weather conditions, locations of the tract and boundaries, products being applied and their rates, landing zones, adjacent landowners, and potential problem area or miscommunication. However, nowhere in the duties and responsibilities is it spelled out specifically that potential flight hazards be identified during the pre-work conference. Postaccident, the operator changed the Policy and Procedures Manual to specify that all involved personnel involved identify flight hazards during the pre-work conference.
Aircraft
- Registration
- N94PH
- Reported as
- Bell 206B
- Category
- Helicopter
- Serial number
- 2809
- Airframe hours
- 13,635
- Engine
- Rolls-Royce 250-C20, 317 hp, turbo shaft
- Damage
- Substantial damage
- Flight
- Aerial application · Part 137
- Operator
- Provine Helicopter Service Inc
- Registered owner
- Provine Helicopter Service Inc
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · May 3, 2013
- Departed
- Hartford, KY
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
- 24
- Injuries
- None
- Certificates
- Flight instructor, Commercial
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Helicopter, Airplane
- Medical
- Class 1, With waivers/limitations
- Last flight review
- July 8, 2012
- Seat
- Right
- Flight hours
- 2,000 total · 320 in this make and model · 1,870 as pilot in command · 120 in the last 90 days · 35 in the last 30 days · 7 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 190° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 72 °F, dew point 66 °F
- Altimeter
- 29.85 inHg
- Observed at
- OWB, 16 nm away
Docket · 9
The files NTSB released with the investigation on June 3, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.8 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.