FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA367 · Bell 206 B

19 Jul 2010 · Roseville, PA, United States Narrative disagrees

Helicopter Applicators Bell 206 B · Accident while maneuvering

From Penn Valley Airport (SEG) to Penn Valley Airport (SEG)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA10CA367
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bell 206 B

Aircraft type
Bell 206
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N302MG
Onboard fatalities
Unknown
Route
From Penn Valley Airport (SEG), Selinsgrove, PATo Penn Valley Airport (SEG), Selinsgrove, PA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 137: Agricultural
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering · low-altitude flying
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Physical

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot of the helicopter stated that he was conducting an aerial application flight over a river. He completed a site survey, noted wires in close proximity to the site, and began application at an altitude of 40 feet. The pilot stated that approximately three quarters of the way across the river, he "momentarily lost sight" of the power lines. The main rotor blades struck the power lines, and the pilot maneuvered the helicopter over a shallow water area. The helicopter lost anti-torque control and the pilot performed a hovering autorotation to the river, where it impacted rocks and rolled to the right. The helicopter sustained substantial damage to the main rotor system, fuselage and tail boom. The pilot stated that there were no preexisting mechanical malfunctions or anomalies with the helicopter, and that the accident could have been prevented with a more thorough examination of the spray site and adjustment of the spray pattern.

Probable cause

The pilot's failure to maintain clearance from a known wire hazard.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA367
Event ID
20100719X10927
Case number
ERA10CA367
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 0dbce8457091dc141c3d043fb4ac76c8be9839cbcfd1bbd836b9558db04169e5; retrieved 2026-09-15T14:43:07.363Z.