FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA244 · Hughes 369HS

5 Apr 2009 · Pacific Ocean, PO, United States

Husa Hughes 369HS · Accident: collision during takeoff/landing

From Pacific Ocean to Pacific Ocean

Report a problem

Event

NTSB case
WPR09LA244
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 369HS

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
N2058X
Operator
Husa
Onboard fatalities
Unknown
Route
From Pacific OceanTo Pacific Ocean
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
Takeoff
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 during takeoff/landing
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A representative of the operator reported that during takeoff from the deck of a fishing vessel, the tail rotor contacted an object on the deck. In his statement, the pilot said that during takeoff for a local fish spotting flight, the helicopter experienced a “violent movement to the right.” Despite the pilot’s input of left pedal, he was unable to regain control of the helicopter. The helicopter landed hard on the deck, resulting in the collapse of the left landing skid. Subsequently the helicopter rolled over and came to rest on its side while remaining on the deck. Examination of the helicopter by the pilot revealed structural damage to the tail boom, tail rotor, and main rotor assembly. The pilot reported no mechanical anomalies with the helicopter or its flight control systems.

Probable cause

The pilot’s failure to maintain clearance from an object during takeoff from the deck of a fishing vessel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA244
Event ID
20090515X70740
Case number
WPR09LA244
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. 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: 3522decc064dd03bf9c071bb8dc752fb8270a741c11ca09d51dcf3d854bb6516; retrieved 2026-09-15T11:03:35.400Z.