FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL00LA034 · Hughes 369D

6 Mar 2000 · Dallas, NC, United States

Hughes 369D · Accident: airframe, component or system failure while maneuvering

From Charlotte Douglas International Airport (CLT) to NC (no airport)

Report a problem

Event

NTSB case
ATL00LA034
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 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
N303BT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Charlotte Douglas International Airport (CLT), Charlotte, NCTo NC (no airport)
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 out of 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
Airframe, component or system failure
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 › Flight controls, improper use of

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was performing an out-of-ground effect (OGE) hover at 500 agl while performing aerial photography for a live news broadcast. While hovering OGE on a heading of 195 degrees with the winds were from 030 degrees at 10 knots, the helicopter experienced several unanticipated right yaw excursions. The pilot made the decision to perform an autorotation landing. He stretched the landing to clear power lines and upon impact with the ground, the helicopter rolled onto its right side. According to the pilot, he previously experienced a tail rotor failure in the same model helicopter, and believed the helicopter was possibly experiencing a similar malfunction. Advisory Circular 90-95 (Unanticipated Right Yaw in Helicopters) instructs the pilot to avoid tailwinds while maneuvering between hover and 30 knots and to be aware of wind direction and velocity when hovering in winds of 8-10 knots, especially OGE. A recommended recovery technique is to adjust the controls for normal forward flight. A postaccident examination of the helicopter revealed no engine or airframe abnormalities.

Probable cause

The pilot's improper use of flight controls during an emergency landing. Factors were an encounter with a loss of tail rotor effectiveness (LTE) during an out-of-ground effect hover, the pilot's inadequate weather evaluation, and his failure to follow proper procedures for LTE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL00LA034
Event ID
20001212X20585
Case number
ATL00LA034
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. 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: 6e3c92b90de22e15962c06ad370506007aa8669979dd7c623104596290a07a32; retrieved 2026-09-22T13:04:58.924Z.