ERA15FA173 · Bell Helicopter Textron 206 L-1
T & M Aviation Bell Helicopter Textron 206 L-1 · Accident: loss of engine power (total) while maneuvering
From Dean Griffin Memorial Airport (M24) to Dean Griffin Memorial Airport (M24)
Event
- NTSB case
- ERA15FA173
- 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
- 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
Bell Helicopter Textron 206 L-1
- Aircraft type
- Bell 206
- 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
- N50KH
- Operator
- T and M Aviation
- Onboard fatalities
- Unknown
- Route
- From Dean Griffin Memorial Airport (M24), Wiggins, MSTo Dean Griffin Memorial Airport (M24), Wiggins, MS
- Aircraft age
- About 35 years (built 1980)
- 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 137: Agricultural
- 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
- Loss of engine power (total)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was to assist in the scheduled burn of an 800-acre wooded area. The helicopter was under contract with the US Department of Agriculture Forest Service. A Forest Service employee reported that, as the helicopter neared the conclusion of a 61-minute controlled burn mission, he observed it complete a turn to a northerly heading at the southwestern end of the burn area. About 7 seconds later, he heard a sound that resembled an air hose being unplugged from a pressurized air tank. A crewmember, who was the sole survivor, reported that the helicopter was about 20 ft above the tree canopy when the pilot announced that the helicopter had lost power. The helicopter then descended into a group of 80-ft-tall trees in a nose-high attitude and impacted terrain. Witnesses participating in the controlled burn at the time of the accident did not observe any other anomalies with the helicopter before the accident.
The fuel system, fuel pump, and fuel control unit were destroyed by fire, which precluded a complete examination. During the engine examination, light rotational scoring was found in the turbine assembly, consistent with light rotation at impact; however, neither the turbine rotation speed nor the amount of engine power at the time of the accident could be determined. The rotor blade damage and drive shaft rotation signatures indicated that the rotor blades were not under power at the time of the accident. An examination of the helicopter's air tubes revealed that they were impact-damaged; however, they appeared to be secure and properly seated at their fore and aft ends.
On the morning of the accident flight, the helicopter departed on a reconnaissance flight with 600 lbs of JP-5 fuel. The helicopter returned with sufficient fuel for about 133 minutes of flight, and the helicopter was subsequently serviced with an unknown quantity of uncontaminated fuel for the subsequent 60-minute accident flight. Based on the density altitude, temperature, and airplane total weight at the time of the accident, the helicopter was operating within the airplane flight manual's performance limitations.
Most of the cockpit control assemblies were consumed by fire except for the throttle, which was found in the "idle" position. Given the crewmember's report that, after the engine failure, the helicopter entered and maintained a nose-high attitude until it impacted trees and then the ground, it is likely that the pilot initiated an autorotation in accordance with the Pilot's Operating Handbook engine failure and autorotation procedures. A review of the pilot's records revealed that he passed the autorotation emergency procedure portion of his most recent Federal Aviation Administration Part 135 examination, which occurred 1 month before the accident, and this may have aided in his recognition of the engine failure and decision to initiate an emergency descent.
Although a weather study indicated that smoke and particulates were present in the area before, during, and after the accident, witnesses reported an absence of smoke near the area where the helicopter lost power and impacted the ground.
Probable cause
A loss of engine power for reasons that could not be determined due to postaccident fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15FA173
- Event ID
- 20150330X73700
- Case number
- ERA15FA173
- 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. 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: fc249de9a8b0a4037f9cbd7540a796291d725ca270fa9485e390bd9bafecc369; retrieved 2026-09-14T17:34:04.026Z.