LAX06CA227 · Hughes 369D
Hughes 369D · Accident: in flight collision with object while maneuvering
From OGGA · Kahului, HI to Kahului International Airport (OGG)
Event
- NTSB case
- LAX06CA227
- 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
Hughes 369D
- 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
- N611WA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From OGGA · Kahului, HITo Kahului International Airport (OGG)
- 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 · hover in ground effect
- 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
- Tree(s)
- 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
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's main rotor blades struck a tree while in a hover. The purpose of the flight was to conduct animal control. Once the animal had been identified and neutralized, the pilot was directed to remove the animal. He landed the helicopter near the animal, which was in a confined area with rolling terrain, thick low trees, high grass, and lava rock outcroppings. About 15 feet above the ground, the main rotor blades contacted a tree off to the right rear side of the helicopter. The pilot repositioned the helicopter about 100 feet to another landing site and landed normally. He reported the main rotor "blades strike" to the company and waited for the Director of Maintenance (DOM) to arrive and assess the damage to the main rotor blades. The DOM determined that the helicopter could be flown back to home base. After the helicopter returned to base, maintenance personnel removed and inspected the main rotor blades. All five of the main rotor blades sustained substantial structural damage. Maintenance personnel referenced the maintenance manual and determined that the dents/depressions in the main rotor blades were beyond serviceable limits and could not be repaired.
Probable cause
the pilot's failure to maintain an adequate clearance from obstructions, which led to a main rotor blade strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06CA227
- Event ID
- 20060817X01191
- Case number
- LAX06CA227
- 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: 4b73bba75f24ec9cd70642baa01bf228385e376c5f584e651250d68a7881508a; retrieved 2026-09-22T04:41:41.135Z.