Bell 206L-3 accident near Owenton, Kentucky, October 7, 2024
On October 7, 2024 at about 9:35 pm local time, a 1990 Bell 206L-3 (helicopter), registered N230AE, was destroyed in an accident during maneuvering (low-alt flying) near Owenton, Kentucky. It was a business flight under charter and air-taxi rules (Part 135). 3 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 7, 2024 · about 9:35 pm local time
- Place
- Owenton, Kentucky · map
- Type
- Accident
- Injuries
- 3 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Bell 206L-3, built 1990 · all 206L-3s on the register
- Registration
- N230AE · no longer on the register · serial 51331
- Damage
- Destroyed
- Flight
- Business flight · charter and air-taxi rules (Part 135)
The NTSB's narrative preliminary · quoted from the NTSB record
On October 7, 2024, at 1730 eastern daylight time, a Bell 206L3+, N230AE, was destroyed when it was involved in an accident in Owenton, Kentucky. The pilot, a flight nurse, and a flight medic were fatally injured. The helicopter was operated by Air Evac Life Team as a Title 14 Code of Federal Regulations Part 135 air medical flight. Communication records from the Kentucky State Police (KSP) revealed that the flight was requested at 1714, and three minutes later, the flight was confirmed with a 14-minute estimated time of arrival. Coordination between the landing zone (LZ), adjacent to a local high school, and the accident helicopter continued for several minutes while the helicopter was enroute and the LZ was properly staffed and equipped for the helicopter’s arrival. At 1724, the helicopter was advised that the requisite fire units had yet to arrive, and the pilot advised that he would “circle” the LZ until it was prepared for the landing. At 1729, the pilot advised that the high school was in sight, that they would perform “a couple of recons, and then head down.” At 1731, county fire units reported a helicopter accident over their radios. Several witnesses described that the helicopter approached from the north at “low altitude” with no unusual sounds or movements. A guyed television signal transmission tower, with a height of 601 ft above ground level (1,559 ft mean sea level) was located on the high school campus adjacent to the LZ. The witnesses saw the helicopter strike one of the guy wires supporting the tower before it descended to ground contact. Several detailed written statements described watching the helicopter strike the wire, watching the wire “move,” and “pieces”; more specifically, the main rotor, separate from the helicopter, before the helicopter and the main rotor system descended separately to the ground. ADS-B track data revealed that the helicopter approached the tower from the northeast on an approximate ground track of 210° magnetic at an altitude of about 1,300 ft msl. At the time, the sun was 18° above the horizon on an azimuth of 246°. Figure 1 shows the area of the accident site including the helicopter’s ADS-B ground track, the guyed tower, and the LZ. Figure 1 - Aerial image with the helicopter’s ground track, as well as positions of the accident site, select pieces of wreckage, the tower and guy anchors, and the LZ annotated. The pilot held an airline transport pilot certificate with ratings for airplane multiengine land and rotorcraft-helicopter, with multiple type ratings. He held commercial pilot privileges for airplane single-engine land. The operator reported that the pilot had accrued 19,638 total hours of flight experience, of which 7,791 hours were in the accident helicopter make and model. According to FAA and maintenance records, the helicopter was manufactured in 1990 and was powered by a Rolls-Royce M250-C30P, 650-horsepower turboshaft engine. The helicopter’s most recent inspection was completed on September 16, 2024, at 12,401 total aircraft hours. The helicopter was equipped with a two-axis autopilot, a Garmin 650 GPS, a Garmin 500txi cockpit display, synthetic vision, and a Helicopter Terrain Awareness and Warning System (HTAWS). These systems provided both visual and aural terrain and obstacle advisories to the pilot and crew. Figure 2 shows an exemplar instrument panel including terrain and obstacle awareness displays. Figure 2 - Exemplar of instrument panel as configured in accident helicopter. The wreckage was examined at the accident site on and all major components of the helicopter were accounted for at the scene. The fuselage came to rest on its left side about 670 ft beyond the base of the tower on an approximate azimuth of 220° and was destroyed by impact and fire. The tailboom remained attached but was deformed by impact and fire. The tailrotor and tailrotor gearbox were separated from the airframe as a unit and found entangled in the wreckage. One blade was separated from its grip and damaged by fire. All flight controls displayed fractures with features consistent with overload separation, and the hydraulic servos were present but displayed overload bending and fractures. The cockpit instruments and avionics components were destroyed by impact and fire. The transmission lord mounts and pylon assemblies were connected to the upper fuselage deck and to the main transmission, with severe bending of link assemblies noted. The main rotor mast was fractured at its base near the top of the transmission case, and the fracture exhibited features consistent with overload separation. The KAflex main driveshaft was attached at the transmission but could not be rotated due to surrounding damage. The driveshaft displayed severe rotational scoring. The engine was still attached in its general mounted position, with the left and right mounts fractured, and the KAflex driveshaft partially fractured at that engine-driven end. The compressor remained in position and exhibited impact damage around the airframe bellmouth area. About five impeller blades exhibited bending along the leading edges near the tips in the direction opposite of blade rotation. All five inlet guide vanes exhibited trailing edge impact damage deflection in the direction of blade rotation. The compressor damage was consistent with engine operation during and ingestion of material during the impact sequence. The main rotor hub and blade assembly with main rotor mast attached was located about 300 ft past the base of the tower on a 192° azimuth. The swashplate was not located. The “white” main rotor blade was accounted for in its entirety where the system came to rest, as the separated outboard section of the blade was found embedded in the ground adjacent to fractured end of the same blade. The “silver” blade was fractured about mid-span, and the outboard approximate 5 ft of the blade was found about 525 ft from the base of the tower on an azimuth of about 335°. Its chordwise separation fracture displayed features consistent with overload. Measurements of the severely damaged trailing edge and other fragments accounted for a complete silver blade before impact and overload separations. Both blades displayed similar leading-edge gouges and striations similar in dimension to the strands of the guy wire cabling. A structural engineering firm performed an inspection of the tower immediately after the accident and submitted a report to the tower operator. According to the report, “The crew inspected each guy anchor, measured guy wire tensions, checked tower plumb, flew a drone up each tower face as well as along the entire length of the top northwest guy wire, and climbed the tower in order to check for possible damage to the tower… The lower hardware for the top northwest guy wire was found to be damaged. The guy wire tensioning rods were bent and the vibration dampers were broken off. No additional tower damage was observed during the inspection. An exact impact location could not be identified.”
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Collision with terrain or object (not controlled flight into terrain) during maneuvering (low-alt flying) defining event
The aircraft
- Airframe total time: 12,401.7 hours
- Last inspection: approved inspection programme, September 16, 2024; 79.5 hours since
- Maximum gross weight: 4,450 lb
- Seats: 4
- Landing gear: fixed
- Fire on the ground
The flight
- Departed from: AE13 Williamstown KY
Weather at the time
- Light: daylight
- Wind: from 030° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 45°F (7°C)
- Altimeter: 30.03 inHg
- Observation at 5:53 pm from KFFT, 21 miles away
Weather report (METAR): KFFT 072153Z AUTO 03006KT 10SM CLR 21/07 A3003 RMK AO2 SLP164 T02060067
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 2 | |||
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
