FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05CA263 · Hughes 369D

8 Aug 2005 · North Las Vegas, NV, United States

Hughes 369D · Accident: in flight collision with terrain/water during landing

From North Las Vegas Airport (VGT) to North Las Vegas Airport (VGT)

Report a problem

Event

NTSB case
LAX05CA263
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
N58431
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Las Vegas Airport (VGT), North Las Vegas, NVTo North Las Vegas Airport (VGT), North Las Vegas, NV
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
Landing · flare/touchdown
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 terrain/water
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 › Cyclic, improper use of
  • Pilot in command(cfi) › Supervision, 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 tail rotor and stinger were damaged during a full touchdown practice autorotation. During a 120-day recurrent training, the instructor pilot and commercial pilot were performing their fifth full-down autorotation. Both pilots were on the controls during the maneuver and the instructor pilot advised the commercial pilot to push the cyclic forward during the deceleration flare; however, the commercial pilot did not move it far enough and stinger impacted the ground, followed by the tail rotor. The tail rotor was substantially damaged and had to be replaced. No mechanical problems were reported with the helicopter prior to the accident.

Probable cause

the pilot's improper use of the cyclic flight control and the flight instructor's inadequate supervision of the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05CA263
Event ID
20050908X01418
Case number
LAX05CA263
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: 12b435430e35d62c2647f0860e44a2f9fe9b328ba146995bae5423d51fb7a5a8; retrieved 2026-09-22T05:31:13.104Z.