CEN24FA049

NTSB accident investigation · MD Helicopters 600 · Sterling City, TX · November 29, 2023

Accident · FatalClass 3 · FieldFinal report
Date
November 29, 2023, 14:30 local (20:30 UTC)
Place
Sterling City, TX · Open field between two sets of power lines on private property
Injuries
2 fatal
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N745MBMD Helicopters 600
Defining event
Maneuvering-low-alt flying: Low altitude operation/event
Weather
Visual (VMC) · Day
Status
Completed · report January 14, 2026
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Central Region
Parties
Brim Aviation, FAA Lubbock FSDO, MD Helicopters, Rolls-Royce
FAA report
20231129016729A
Case key
193451

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s failure to maintain clearance from a power line pole’s static arm during forecasted gusting wind conditions, un-forecasted light turbulence, and un-forecasted low-level wind shear conditions, resulting in main rotor blade contact with the static arm and a subsequent loss of control and impact with terrain.

Findings · 8

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedMD Helicopters 600N: 1 caseAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotMD Helicopters 600N: 1 caseAll aircraft: 9,295 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Effect on operationMD Helicopters 600N: 1 caseAll aircraft: 1,199 casesProbable cause
Turbulence: clear air turbulenceEnvironmental issues › Conditions/weather/phenomena · Effect on operationMD Helicopters 600N: 1 caseAll aircraft: 78 casesProbable cause
Wind: windshearEnvironmental issues › Conditions/weather/phenomena · Effect on operationMD Helicopters 600N: 1 caseAll aircraft: 90 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Awareness of conditionMD Helicopters 600N: 1 caseAll aircraft: 1,199 casesProbable cause
Turbulence: clear air turbulenceEnvironmental issues › Conditions/weather/phenomena · Awareness of conditionMD Helicopters 600N: 1 caseAll aircraft: 78 casesProbable cause
Wind: windshearEnvironmental issues › Conditions/weather/phenomena · Awareness of conditionMD Helicopters 600N: 1 caseAll aircraft: 90 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The helicopter departed from the remote landing zone with the pilot and an aerial lineman to conduct aerial power line system work. ADS-B data showed that the helicopter approached the target powerline pole from the west. The helicopter maneuvered around the pole, and the data subsequently terminated at the pole. Various impact marks were observed on a static arm, about 12 ft long, at the top of the pole. The impact marks were located about 4 ft from the base of the static arm. The pole and attached wires were all found intact. The helicopter came to rest on its left side, about 103 ft away from the pole on a flat grass field. The helicopter sustained substantial damage to the main rotor system, fuselage, and empennage. Postaccident examination of the airframe and the engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. A review of meteorological data showed that the helicopter likely encountered gusting wind conditions to 26 kts, light turbulence, and low-level wind shear (LLWS) conditions at the time of the accident. The weather forecast for the accident time did not forecast turbulence or LLWS and there were no PIREPs or other information indicative of turbulent conditions or LLWS within 100 miles of the accident site. The closest terminal aerodrome forecast, 42 miles southeast of the accident site, did include gusting wind conditions. The actual wind conditions for the accident site were likely below the operator’s published wind limitations. A search of archived information indicated that the pilot did not request weather information from Leidos Flight Service or through ForeFlight. The pilot did have an account through ForeFlight but only updated route strings on the accident day. It is unknown what weather information, if any, the pilot checked or received before or during the accident flight. Based on the available evidence, it is likely the pilot failed to maintain clearance from the power line pole’s static arm during forecasted gusting wind conditions, un-forecasted light turbulence, and un-forecasted LLWS conditions, resulting in main rotor blade contact with the static arm and a subsequent loss of control and impact with terrain.

Factual narrative

The Vertical Aviation International published the Utilities, Patrol, and Construction Working Group Safety Guide for Helicopter Operators on July 10, 2020. This document provides exemplary aviation job hazard analyses for power line construction and maintenance operators to utilize. One of the hazards listed that can be encountered during this mission profile is a loss of control due to gusty winds. A review of the FAA-Approved MD Helicopters MD600N Rotorcraft Flight Manual (RFM) found that with a takeoff weight of 3,548 pounds and a density altitude of 3,278 ft, the helicopter would be operating within the controllability envelope for crosswind conditions. The RFM states in part: Hover in ground effect operation in winds in excess of 17 kts has been demonstrated for all azimuths. The Brim Aviation General Operation Manual lists a maximum wind speed of 40 kts and a gust spread of 15 kts for flight operations. The helicopter was not equipped with a crashworthy voice or data recorder, nor was it required to be. On November 29, 2023, about 1430 central standard time, a MD Helicopters Inc. MD600N helicopter, N745MB, sustained substantial damage when it was involved in an accident near Sterling City, Texas. The commercial pilot and the aerial lineman sustained fatal injuries. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 rotorcraft external load flight. The purpose of the flight was to perform aerial work on a power line system. The helicopter was operated by Brim Aviation. There were no known witnesses to the accident sequence. Prior to the flight, the pilot completed the operator’s flight risk assessment tool. The helicopter arrived at the remote landing zone (LZ) to perform the work about 1240. Between 1245 and 1310 the helicopter was configured for the work, and a safety meeting was held. From 1315 to 1340, a pre-work scouting flight was performed. At 1340, the helicopter arrived back at the LZ to prepare for the work and another briefing was held. A review of ADS-B data showed that the helicopter departed from the LZ about 1415. The helicopter then approached the target power line pole (a steel mono pole that was about 133 ft tall) from the west. The helicopter maneuvered around the pole, and the data subsequently terminated at the pole about 1429. At 1440, the helicopter was overdue, and the operator began multiple communication attempts and then started searching for the helicopter. At 1551, the operator arrived at the accident site and discovered the wreckage of the helicopter. A private forensic pathologist performed the pilot’s autopsy at the request of the Justice of the Peace of Sterling County, Texas. According to the pilot’s autopsy report, his cause of death was multiple blunt impact injuries. A private forensic pathologist performed the aerial lineman’s autopsy at the request of the Justice of the Peace of Sterling County, Texas. According to the aerial lineman’s autopsy report, his cause of death wasmultiple blunt impact injuries. The aerial lineman’s postmortem toxicological testing by the FAA Forensic Sciences Laboratory detected delta-8-tetrahydrocannabinol (delta-8-THC) in cavity blood, at a low level. Delta-8-THC was not detected in urine. Carboxy-delta-8-THC was identified in cavity blood at 5.5 ng/mL and detected in urine at 56.5 ng/mL. Carboxy-delta-9-THC was detected in cavity blood and detected in urine at 1.8 ng/mL. Vilazodone was detected in cavity blood at 230 ng/mL and in urine at 173 ng/mL. Delta-8-THC is a psychoactive cannabinoid chemical. Very little delta-8-THC occurs naturally in the cannabis plant, and delta-8-THC used in consumer products typically is chemically manufactured from cannabidiol (CBD), another chemical in the cannabis plant. Delta-8-THC is available in a variety of over-the-counter products for oral consumption, smoking, and inhalation. Delta-8-THC has psychoactive and intoxicating effects that can impair motor coordination, reaction time, decision making, problem solving, and vigilance. The potency of delta-8-THC varies widely in consumer products. Delta-8-THC products may also contain impurities including delta-9-THC. Carboxy-delta-8-THC is a non-psychoactive metabolite of delta-8-THC. Carboxy-delta-9-THC is a non-psychoactive metabolite of delta-9-THC, the primary psychoactive substance in cannabis. Delta-9-THC was not detected in this case. Delta-9-THC may be inhaled or ingested recreationally by users seeking mind-altering effects. It may also be used medicinally, such as to treat illness-associated nausea and appetite loss. Psychoactive effects of delta-9-THC vary depending on the user, dose, and route of administration, and may impair motor coordination, reaction time, decision making, problem solving, and vigilance. Carboxy-delta-9-HC may be detected in urine for days or weeks after last cannabis use, well beyond the expected window of acute psychoactive effects. Vilazodone is a prescription medication commonly used to treat major depression. Use of vilazodone may impair coordination, worsen reaction time and judgement. Vilazodone generally carries a warning that patients should not drive a car or operate machinery until they know how this medication affects them. The aerial lineman was not required to hold a FAA medical certificate. A review of meteorological data showed that a mid-level trough was located west of the accident site and provided mid-level support for cloud development. In addition, cloud cover and increasing surface moisture were moving across the accident site from the south as evidence by the surface analysis chart for 1500. Based on the Aviation Routine Weather Reports (METARs) and High-Resolution Rapid Refresh (HRRR) sounding, the cloud cover base was likely somewhere between 2,000 and 3,000 ft agl with no precipitation noted below the cloud base. The surface winds were gusting as high as 26 kts, which was supported by the HRRR sounding and confirmed by wind farm wind sensorinformation. Wind speed information from a wind turbine located 900 ft west-northwest of the accident site was retrieved. The wind speed sensor was located on a wind turbine tower around 262 ft agl with the wind speed reported in meters per second (m/s). The wind speed around the accident time ranged from 18 kts to 22 kts. There was a range of 10 to 15 kts between the sustained and gusting wind speeds. In addition, the GOES-16 visible satellite information confirmed transverse banding in the lower-level cloud cover, typically indicative of turbulent conditions. The HRRR sounding also indicated a density altitude of 3,278 ft. The weather forecast information applicable for the accident time indicated no forecast information for turbulence or low-level wind shear (LLWS) and there were no Pilot Reports (PIREPs) or other information indicative of turbulent conditions or LLWS within 100 miles of the accident site. The closest terminal aerodrome forecast, located 42 miles southeast of the accident site, had wind gusts to 21 kts. FAA Advisory Circular (AC) 91-92 “Pilot’s Guide to a Preflight Planning” (dated March 15, 2021) provided pilot guidance on preflight self-briefings, including planning, weather interpretation, and risk identification/mitigation skills. The AC further stated in part: Pilots adopting these guidelines will be better prepared to interpret and utilize real-time weather information before departure and en route, in the cockpit, via technology like Automatic Dependent Surveillance-Broadcast (ADS-B) and via third-party providers. A search of archived information indicated that the pilot did not request weather information from Leidos Flight Service or through ForeFlight. The pilot did have an account through ForeFlight, but only updated route strings on the accident day. It is unknown what weather information, if any, the pilot checked or received before or during the accident flight. The pilot was employed by the operator and was signed off by the operator to perform Part 133 work two days before the accident. The aerial lineman was employed by Source Utility Services, Georgetown, Texas, and was signed off by Source Utility Services to perform aerial lineman work on October 23, 2022. The aerial lineman, who would be standing on the left skid during his work, was secured to the cabin with two personal restraint lanyards. Various impact marks were observed on a static arm, about 12 ft long, at the top of the pole. The static arm supported optical ground wire. The impact marks were located about 4 ft from the base of the static arm. The pole and attached wires were all found intact. The helicopter came to rest on its left side, about 103 ft away from the pole on a flat grass field. The remote field, used for cattle grazing, was located on private property, and was surrounded by wind turbines. The fuselage sustained extensive crushing damage. The NOTAR (no tail rotor) system was found separated, about 30 ft away from the fuselage. Allmajor structural items from the fuselage and empennage were observed at the accident site. The helicopter sustained substantial damage to the main rotor system, fuselage, and empennage. All six main rotor blades exhibited significant deformation, fractures, and fragmentation of their outboard ends. All fractures observed exhibited signatures consistent with overload. The leading edges of two main rotor blades exhibited blue paint transfer that was a close color match to the paint scheme of the tail boom. Flight control continuity was established for the airframe. The annunciator panel was radiographed by the NTSB Materials Laboratory to determine the filament status of the individual bulbs within the annunciator lights. Each individual annunciator light contained 4 bulbs. None of the bulbs exhibited hot coil stretching in any filaments. The cockpit light panel was submitted to the NTSB Materials Laboratory for examination. The panel was submitted to determine the status of the filaments in the light bulbs for each annunciator light. The panel was x-rayed to determine the status of each filament. There were 20 lights in the panel. The radiographs of the light bulbs showed no hot filament stretching in any of the filaments. In addition, all the filaments were intact. An external examination of the engine revealed no uncontainment or fire damage. The disassembly and examination revealed rotational scoring in the compressor impeller and shroud as well as presence of metal spray in the turbine section, consistent with engine operation during impact. Postaccident examination of the airframe and the engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.

Aircraft

Registration
N745MB
Reported as
MD Helicopters 600 (N)
Category
Helicopter
Serial number
RN067
Built
2002
Airframe hours
9,053.3
Engine
Rolls-Royce 250-C47M, 650 horsepower, turbo shaft
Damage
Substantial damage
Flight
External load · Part 133
Operator
Brim Equipment Leasing, LLC, doing business as Brim Aviation
Registered owner
Cobra Aviation Services, LLC
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · November 28, 2023 · 3.5 hours before
Departed
None · Sterling City, TX
Equipment
Onboard weather, Satellite tracking device, ADS-B, Handheld GPS, Electronic flight bag or handheld device

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
31
Injuries
Fatal
Certificate
Commercial
Medical
Class 2, Without waivers/limitations
Last flight review
April 30, 2023
Seat
Left
Restraint
4-point
Toxicology
Performed
Flight hours
1,975 total · 74.7 in this make and model · 1,665 as pilot in command · 74.7 in the last 90 days · 58 in the last 30 days · 3.4 in the last 24 hours
Role
Other flight crew
Age
22
Injuries
Fatal
Seat
Rear
Toxicology
Performed

Weather

Conditions
Visual (VMC) · Day
Wind
170° at 15 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
61 °F, dew point 43 °F
Altimeter
30.01 inHg
Turbulence
Light
Observed at
KBPG, 33 nm away
METAR
KBPG 292015Z AUTO 17015KT 10SM CLR 16/06 A3001 RMK AO2 T01620059

Docket · 29

The files NTSB released with the investigation on January 14, 2026, on NTSB’s docket system: statements, records, photos and specialists’ reports. 42.6 MB in all.

Pilot/operator aircraft accident report, NTSB form 6120.1Item 1 · PDF · 9 pages · 1.6 MBSterling county sheriff's office - accident reportItem 2 · PDF · 2 pages · 290 KBInvestigation photographsItem 3 · PDF · 11 pages · 3.5 MBMemorandum for record a�� telephone interview, pilot next of kinItem 4 · PDF · 2 pages · 70 KBAccident flight ADS-B data - google earth pro (.kmz file)Item 5 · KMZ · 18 KBAccident flight ADS-B data - microsoft excel (.xlsx file)Item 6 · XLSX · 503 KBWeather factual reportItem 7 · PDF · 24 pages · 1.7 MBWeather attachment 1Item 8 · GIF · 20.2 MBWeather attachment 2Item 9 · PDF · 3 pages · 262 KBOnsite examination reportItem 10 · PDF · 9 pages · 602 KBHelicopter specialist's factual reportItem 11 · PDF · 13 pages · 9 photos · 1.3 MBHelicopter specialist's factual report - attachment 1Item 12 · PDF · 2 pages · 1.4 MBPowerplants factual reportItem 13 · PDF · 21 pages · 4.5 MBElectronic devices - specialist's factual reportItem 14 · PDF · 5 pages · 517 KBAnnunciator panel - email examination reportItem 15 · PDF · 1 page · 81 KBCockpit light panel - email examination reportItem 16 · PDF · 1 page · 81 KBBrim aviation - accident timelineItem 17 · PDF · 1 page · 114 KBBrim aviation - flight risk assessment toolItem 18 · PDF · 1 page · 527 KBBrim aviation - flight releaseItem 19 · PDF · 1 page · 157 KBBrim aviation - general operations manual excerptItem 20 · PDF · 1 page · 203 KBBrim aviation - weight and balance sheetItem 21 · PDF · 1 page · 74 KBBrim aviation - pilot training documents excerptsItem 22 · PDF · 6 pages · 2.1 MBSource utility services - aerial lineman training documents excerptItem 23 · PDF · 4 pages · 178 KBPilot logbook - recent entriesItem 24 · PDF · 2 pages · 1.6 MBToxicological report - pilotItem 25 · PDF · 1 page · 162 KBToxicological report - aerial linemanItem 26 · PDF · 1 page · 190 KBStatement of party representatives to NTSB investigationItem 27 · PDF · 3 pages · 371 KBRelease of aircraft wreckage, NTSB form 6120.15Item 28 · PDF · 2 pages · 159 KBEvidence control formItem 29 · PDF · 1 page · 137 KB

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.