LAX03CA250 · Texas Helicopter OH-13E-M74
Texas Helicopter OH-13E-M74 · Accident: in flight collision with object while maneuvering
From Tulare, CA to an unrecorded destination
Event
- NTSB case
- LAX03CA250
- 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
Texas Helicopter OH-13E-M74
- Aircraft type
- Texas OH-13
- 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
- N51852
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulare, CATo not recorded
- 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 · aerial application
- First occurrenceThe 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
- In flight collision with object
- 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, transmission
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter collided with power lines during an aerial application. The pilot was on his nineteenth pass over the field, traveling eastbound. Power lines were located on the east and west side of the road. There was a pole about 75 feet tall, and the top 6 feet contained three wires. The top wire, a black colored insulator wire, was located 3 feet from the top of the pole. The pilot located the outbox on the pole and determined he would fly above the box to clear all of the wires. As he flew over the lines, the helicopter impacted the insulator wire about 1/2 foot above the cockpit floor. The helicopter slid along the wire and then the wire broke from the insulator at the next pole. The poles were placed about 300 feet apart. As the helicopter impacted the ground, the left skid hit first, followed by the main rotor.
Probable cause
the pilot's failure to maintain clearance with the wires due to an inadequate visual lookout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03CA250
- Event ID
- 20030902X01434
- Case number
- LAX03CA250
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 00ec38b47babff55ccd3f4fe6af4871e64081ff0310ba14f062027fb2705d2bf; retrieved 2026-09-21T19:24:16.980Z.