Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 7, 2025 · Hughes 369D · N173AL

West Alton, MO

Overview

Report Status
Factual report
Event Type
Accident
Date
August 7, 2025
Injury Outcomes
2 injuries (2 fatalities)
Location
West Alton, MO
Aircraft
Hughes 369D (1976)
Tail Number
N173AL
Operator
Excel Helicopters
Injuries
Fatal
Aircraft Damage
Destroyed
NTSB Number
CEN25FA307

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

Full 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

Flight

Event TypeAccident
Event Time10:59 CDT
Nearest AirportN/A (0nm)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftHughes 369D
Tail NumberN173AL
Aircraft CategoryHeli
DamageDestroyed
OperatorExcel Helicopters
Operating RulePart 133
Engines1
Seats4

People & Injuries

Injury Summary2 injuries (2 fatalities)
Fatal2
Serious0
Minor0
Uninjured0
Total2

Conditions

ConditionsVMC
LightDaylight
Wind5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point70 F
Altimeter30.19 inHg
Observation Time10:50
Weather SourceWFAC

Appendix: Source Data