ERA09LA139 · Hughes OH-6A
Charlotte Helicopters Flight Academy Hughes OH-6A · Accident: collision with terrain/object (non-CFIT) while maneuvering
From Charlotte-Monroe Executive Airport (EQY) to Charlotte-Monroe Executive Airport (EQY)
Event
- NTSB case
- ERA09LA139
- 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
- 1 · 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
Hughes OH-6A
- Aircraft type
- Hughes OH-6
- 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
- N4191A
- Onboard fatalities
- Unknown
- Route
- From Charlotte-Monroe Executive Airport (EQY), Monroe, NCTo Charlotte-Monroe Executive Airport (EQY), Monroe, NC
- 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 91: General Aviation
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a flight to "simulate a mission" to examine power lines, the helicopter had been paralleling the west side of transmission lines. While resetting the global position system (GPS), the pilot-in-command (PIC) transferred controls to the pilot-rated-passenger. While the PIC was trying to reduce the sensitivity of the GPS warning system, the helicopter made a right turn of almost 260 degrees of heading change, allowing the helicopter to be on a perpendicular ground track and traveling directly toward the power lines. The helicopter collided with the topmost lines in the set, which were the grounding wires for the transmission line. The helicopter was observed by an eyewitness impacting the power line and descending to the ground. Examination of the wreckage revealed no evidence of any mechanical deficiencies. Several witnesses heard the helicopter and reported that it sounded normal prior to impacting the power lines. The main rotor blade was separated from the main wreckage. The pilot-rated-passenger had a history that he had not revealed to the Federal Aviation Administration of kidney stones, severe knee pain, and regular use of prescription pain medication. This pilot had seen an orthopedic surgeon the day before the accident for continuing knee pain, for which he had requested and received additional pain medication "to help him sleep." Toxicological testing was consistent with the recent use of the potentially impairing narcotic medication that had been prescribed the day before the accident. It is possible that the pilot-rated-passenger was impaired or distracted by knee pain, by the use of narcotic medication for that pain, or by fatigue due to insomnia from the knee pain; however, the investigation could not conclusively determine if impairment or distractions contributed to the accident.
Probable cause
The pilot-rated-passenger’s failure to maintain clearance from a known wire hazard during low-level maneuvering. Contributing to the accident was the pilot-in-command’s inadequate monitoring of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA139
- Event ID
- 20090122X30337
- Case number
- ERA09LA139
- 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. 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: bedc1cc80cbaeda75b138f313d2eb2369cc8954db101c5988d2316391bfd4402; retrieved 2026-09-13T19:55:37.298Z.