DFW05LA159 · Hughes 269A
Hughes 269A · Accident: total loss of engine power (non-mechanical) en route
From Shreveport Downtown Airport (DTN) to Rusk, TX
Event
- NTSB case
- DFW05LA159
- 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
- 1 · 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 269A
- 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
- N8768F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Shreveport Downtown Airport (DTN), Shreveport, LATo Rusk, TX
- 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
- En route · cruise
- 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
- Wire, static
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A 450-hour commercial helicopter pilot departed approximately 0615, on the return leg of a personal cross-country flight. About 0805 two witness saw the helicopter following a road. The first witness reported seeing the helicopter following the highway heading north at a "normal" height. They then saw the helicopter "lose altitude very quickly". The second witness, who was heading south, said he saw a helicopter low over the [highway] median heading north, "lower than tree line, 20 to 30 feet". The witness also stated, "the pilot was concentrating on the center gauges, [and] console, [and he] was working the controls fast and vigorous." Both the FAA inspector and Department of Public Safety Trooper noted that the helicopter impacted power lines prior to impacting the ground. The top and forward sections of the left and right landing skids showed evidence of a wire strike. The fuel tank had been breached near the top of the tank, however approximately 3 quarts of fuel was drained from the tank through the gascolator. The blades were absent of leading edge gouges. One blade was bent "upwards", the two other blades were bend "downwards", with one of the blades having scuff and paint marks consistent with the tail rotor boom. The scuffed blade also had slight buckling on the trailing edge. The main rotor drive shaft and housing was broken from the transmission; the main rotor drive shaft was bent about 45 degrees and lacked any "twisting" motion. The tail rotor drive shaft was separated in two, with no twisting motion at the break. The shaft had scuff and paint transfer marks longitudinally along the shaft. The tail rotor blades had numerous impact marks on the sides of the blades, removing paint and leaving small dents in the blades. The leading edges of the blades were absent of leading edge gouges. The mixture control cable clamp, on the fuel servo was metal and had no rubber cushion in it. The clamp had no "holding effect" on the mixture cable and the cable was free to move out of the clamp. The bottom set of sparkplugs were examined and all four were worn out-normal to worn out-severe, and lead fouled. Control continuity through the cyclic and collective has established. However, three bolts connecting the cyclic controls were missing the safety cotter pins. Additionally, one of the castled nuts had had backed off, and was within a few threads of "falling" off. A post-accident engine run was accomplished. The engine was started and run through the operating rpm range, with no noted abnormalities. After shut-down, fuel would "leak" through the servo, and out the induction system, when the mixture was left in the full-rich position. The reason for the lost of engine power could not be determined.
Probable cause
A loss of engine power for undermined reasons, and the subsequent collision with power lines and the ground. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05LA159
- Event ID
- 20050620X00814
- Case number
- DFW05LA159
- 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: 8dd1975a3cf52321f538101ae24e06b606570b2c34e460cedc865c58a8e251b9; retrieved 2026-09-20T18:01:27.904Z.