CEN24FA049 · MD Helicopters Inc 600 N
Brim Equipment Leasing MD Helicopters Inc 600 N · Accident: low altitude operation/event while maneuvering
From Sterling City, TX (no airport) to an unrecorded destination
Event
- NTSB case
- CEN24FA049
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
MD Helicopters Inc 600 N
- Aircraft type
- MD Helicopters 600
- 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
- N745MB
- Operator
- Brim Equipment Leasing
- Onboard fatalities
- Unknown
- Route
- From Sterling City, TX (no airport)To not recorded
- Aircraft age
- About 21 years (built 2002)
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA049
- Event ID
- 20231129193451
- Case number
- CEN24FA049
- 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, cause areas. 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: eec37a07d0c864a41fba995e8ef47496c5173a45255937a18e0180ece8c1a605; retrieved 2026-09-15T08:08:40.966Z.