ATL82DKM07 · Hughes 269C
US Helicopters Hughes 269C · Accident: hard landing
From Marshville, NC to Marshville, NC
Event
- NTSB case
- ATL82DKM07
- 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 269C
- Aircraft type
- Hughes 269
- 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
- N9575F
- Operator
- U.S. Helicopters
- Onboard fatalities
- Unknown
- Route
- From Marshville, NCTo Marshville, NC
- 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
- Hard 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
- Pilot in command(cfi) › Level off, improper
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Estimated position: the centre of Marshville, NC, the place the record names. Not the accident site.
NTSB narrative
THE INSTRUCTOR PILOT (IP) AND THE STUDENT (A PRIVATE, SINGLE ENGINE LAND, PILOT) WERE ON A DUAL INSTRUCTIONAL FLIGHT. AFTER COMPLETING SEVERAL HOVER AUTOROTATIONS AND HOVERING PATTERNS, THE IP TOOK CONTROL. HE POSITIONED THE HELICOPTER FOR AN AUTOROTATION FROM 500 FT AGL WITH A POWER RECOVERY. WHEN ENTERING THE AUTOROTATION, THERE WAS A MISUNDERSTANDING CONCERNING WHO WAS TO FLY AND WHO WAS TO FOLLOW THROUGH ON THE CONTROLS. THE STUDENT THOUGHT HE WAS TO FOLLOW THROUGH, BUT REPORTEDLY, THE IP THOUGHT THE STUDENT HAD ASSUMED CONTROL. AS THE HELICOPTER APPROACHED THE GROUND, THE IP TOOK CONTROL AND FLARED; HOWEVER, DURING TOUCHDOWN, THE TAIL ROTOR STRUCK THE GROUND. THE STUDENT STATED THAT PREVIOUSLY, THE MICROPHONE SYSTEM HAD AN INTERMITTENT PROBLEM WHICH WAS THOUGHT TO HAVE BEEN REPAIRED. HE BELIEVED THE PROBLEM OCCURRED AGAIN AND CONTRIBUTED TO THE MISUNDERSTANDING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DKM07
- Event ID
- 20020917X04274
- Case number
- ATL82DKM07
- 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: 5663b987ead9179e62a3976ebb8ccdce82accdb79faa3923eab9a33cb4213069; retrieved 2026-09-24T00:51:52.558Z.