CEN25LA292 · Bell 206B
Sky Copters Bell 206B · Accident: collision with terrain/object (non-CFIT) while maneuvering
Event
- NTSB case
- CEN25LA292
- 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
- 0
- 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 206B
- 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
- N432TV
- Operator
- Sky Copters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 44 years (built 1981)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a telephone interview, the pilot stated that he had been spraying a 300-acre field and had already made about 10 passes with the helicopter. He stated that after each pass he landed near a support vehicle to replenish the hopper. On the final approach to the support vehicle, the pilot did not see the wires and the helicopter struck them with the main rotor blades. The pilot landed the helicopter on an adjacent road without further incident. The helicopter sustained substantial damage to the main rotor blades. The pilot discovered that the driver of the support vehicle had moved the truck about 50 ft closer to the wires than it was previously positioned. He stated that the driver of the support vehicle did not inform him that the truck had been moved. The pilot stated that there were no mechanical problems with the helicopter before striking the wires.
Probable cause
The pilot’s failure to maintain clearance from wires while maneuvering at a low altitude, and the ground crew failure to inform the pilot that the support truck had been moved.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA292
- Event ID
- 20250728200649
- Case number
- CEN25LA292
- 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, cause areas. 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: 4ece3947e1468d596f6f40fe72c062c36bebbf96c1d95f2fd6ff50dcf1e8e686; retrieved 2026-09-16T20:08:41.442Z.