CHI08FA269 · Bell 206L-1
Air Evac EMS Bell 206L-1 · Accident: system/component malfunction/failure (non-power) en route
From Burney, IN to Rushville, IN
Event
- NTSB case
- CHI08FA269
- 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
- 3 · 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 206L-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
- N37AE
- Operator
- Air Evac EMS
- Onboard fatalities
- Unknown
- Route
- From Burney, INTo Rushville, IN
- Aircraft age
- Not recorded
- 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 91: General Aviation
- 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
- En route · cruise
- 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
- System/component malfunction/failure (non-power)
- 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
- Aircraft › Aircraft propeller/rotor
- Organizational issues › Development
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The emergency medical services crew had attended a local fundraising event and was returning to the helicopter/crew base when the accident occurred. Witnesses reported that the helicopter made a normal departure. They subsequently reported seeing components separate from the helicopter before it descended and impacted the ground. The helicopter came to rest in a corn field approximately 1.2 miles from the departure point. A postaccident examination of the helicopter revealed that an 8-foot section of one of the main rotor blades separated in-flight rendering the helicopter uncontrollable. Metallurgical examination determined that the blade failed as a result of fatigue cracking. The origin of the fatigue crack coincided with a large void between the blade spar and an internal lead weight. Further investigation determined that the presence of residual stresses in the spar from the manufacturing process, in combination with excessive voids between the spar and the lead weight, likely resulted in the fatigue failure of the blade. The manufacturer issued an alert service bulletin that identified main rotor blades that may have been affected by the combination of residual stresses and excessive voids between the spar and the lead weight. The service bulletin also called for supplemental inspections in order to maintain the continued airworthiness of the affected blades.
Probable cause
The in-flight separation of a main rotor blade due to a fatigue failure of the blade spar, rendering the helicopter uncontrollable, and the manufacturer's production of main rotor blades with latent manufacturing defects, which precipitated the fatigue failure of the blade spar.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08FA269
- Event ID
- 20080909X01417
- Case number
- CHI08FA269
- 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: aa41e9a30359898b0a1a920ebdadd50b948f4ddd30cea2fea789499990a00175; retrieved 2026-09-13T19:25:56.323Z.