LAX96TA186 · Hughes 369
Hughes 369 · Accident: in flight collision with object while maneuvering
From Yuma International Airport / Marine Corps Air Station Yuma (YUM) to an unrecorded destination
Event
- NTSB case
- LAX96TA186
- 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
Hughes 369
- Aircraft type
- Hughes 369
- 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
- N5062Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yuma International Airport / Marine Corps Air Station Yuma (YUM)To 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 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
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was on a night visual surveillance operation in an area that was familiar to him. During a turn to the right at low altitude, the helicopter collided with transmission power lines. No visual or mechanical problems were reported to have occurred before the accident.
Probable cause
failure of the pilot to maintain altitude and/or clearance from obstacles, while maneuvering a low altitude at night. Factors relating to the accident were: darkness and the lack of visual cues.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96TA186
- Event ID
- 20001208X05627
- Case number
- LAX96TA186
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-05-01.
- API snapshot SHA-256: 5cde4d15f85fc15008d3820a13ddd09af17bbce3eb7763889dc345c723beac38; retrieved 2026-09-22T22:33:22.698Z.