ATL87LA023 · Hughes 269C
Hughes 269C · Accident: total loss of engine power (non-mechanical) on approach
From Smith Reynolds Airport (INT) to Boone Inc Airport (NC14)
Event
- NTSB case
- ATL87LA023
- 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
- N9665F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Smith Reynolds Airport (INT), Winston-Salem, NCTo Boone Inc Airport (NC14), Eden, 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
- Approach · VFR pattern base
- 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel starvation; Wire, transmission
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel consumption calculations, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PILOT RELATED THAT HE HAD PLACED THE HELICOPTER AT TRIAD FOR A 50 HOUR INSPECTION. AIRCRAFT REPORTEDLY DEFUELED TO DRY TANK. SIX DAYS LATER FUEL TRUCK LOG SHOWS AIRCRAFT REFUELED WITH 23.2 GALLONS AS PAYBACK. ACCORDING TO INFORMATION FURNISHED BY OWNER AND TRIAD, THE HELICOPTER WAS OPERATED FOR A TOTAL OF 1 HOUR AND 25 MINUTES AT VARIOUS POWER SETTINGS. OWNER/PILOT STATED THAT WHILE ON BASE LEG THE ENGINE SHUT OFF LIKE TURNING SWITCH OFF. DURING AUTROROTATION, HAD TO BLEED OFF ROTOR ENERGY TO CLEAR TREES. AFTER CLEARING TREES SAW ABANDONED POWER LINES. THOUGHT HAD HIT LINES WITH BOTTOM OF SKID. TOUCHED DOWN IN PLOWED FIELD AND ROLLED OVER. PILOT DID NOT VISUALLY CHECK FUEL AFTER LANDING BUT SAW NO LEAKS. FAA INSPECTOR ADDED 5 GALLONS OF FUEL TO DRY TANKS AFTER RECOVERY AND RAN ENGINE FOR ABOUT 30 SECONDS. SHUT DOWN DUE TO CRACK IN FUEL LINE WHICH WAS CRIMPED. INSPECTOR INDICATED CRIMP WAS IMPACT DAMAGE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL87LA023
- Event ID
- 20001213X35099
- Case number
- ATL87LA023
- 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: a36fde67382af5bc878acdc2a37c9de6ecd7d884059db095d2bed9e33118945f; retrieved 2026-09-23T13:43:40.123Z.