CEN25FA307 · Hughes 369D
Hughes 369D · Accident while maneuvering
From Alton, IL (private airstrip) to Alton, IL (private airstrip)
Event
- NTSB case
- CEN25FA307
- 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
- Ongoing
- API-reported fatalities
- 2 · 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
- N173AL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Alton, IL (private airstrip)To Alton, IL (private airstrip)
- Aircraft age
- About 49 years (built 1976)
- 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 133: Rotorcraft Ext. Load
- 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
- Defining eventThe 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
- Miscellaneous/other
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On August 7, 2025, about 1059 central daylight time, a Hughes (MD Helicopters) 369D helicopter, N173AL, was destroyed when it was involved in an accident near West Alton, Missouri. The pilot and crewmember were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 external load flight. According to the available Automatic Dependent Surveillance – Broadcast (ADS-B) data for the helicopter, the pilot departed from the north bank of the river about 1025. He appeared to make three trips to the powerline support tower on the south bank of the river and then return to the original position on the north bank. The final ADS-B data point was recorded at 1035. No further ADS-B data was recorded. A witness located on the tow vessel reported that the helicopter pilot and lineman appeared to be attempting to attach a safety marker (orange ball) to one of the power lines. The lineman appeared to be standing on the left skid, wearing a safety harness. On the second attempt, as the pilot brought the helicopter closer to the power lines at which time the tail of the helicopter struck the line. From the witness’ vantage point, it appeared that the tailboom partially separated from the airframe with a portion of it “dangling.” The helicopter then pivoted, and the cockpit hit the line which caused sparks similar to when an electrical transformer fails. The helicopter then fell onto the barge deck and a postimpact fire ensued. The witness did not recall seeing the helicopter on fire during flight, only the sparks when the fuselage struck the line. The crew moved the tow vessel alongside the barge and used its pilothouse fire station to extinguish the fire. A subsequent inspection of the barge did not reveal any structural damage or any release of the barge contents. The helicopter main wreckage consisted of the fuselage, engine, main rotor transmission, main rotor hub, and forward portion of the tail boom (fragmented into two sections). One main rotor blade was located about 150 ft from the main wreckage. A 7-foot segment of a second main rotor blade was located about 176 ft from the main wreckage. Finally, a main rotor blade tip, about 6-inches in length, was located about 26 ft from the main wreckage. The remaining main rotor blades and the aft portion of the tail boom, including the tail rotor and horizontal stabilizer, were not present with the wreckage and presumed to have landed in the river. The video data recorder onboard the tow vessel was retained for examination and download. A search of the river bottom in the vicinity of the accident site using side-scan sonar equipment is planned. The helicopter wreckage was retained for possible further examination.
Figure 1 – Accident Site with Powerline Support Tower
Figure 2 – Main Wreckage on Barge Deck
Figure 3 – Main Wreckage on Barge Deck
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN25FA307
- Event ID
- 20250807200732
- Case number
- CEN25FA307
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: d6f9ed6b439db457f0bb0a91b663743bc3c9fa994fc63fc271d901a4eaddf0a6; retrieved 2026-09-15T09:07:47.280Z.