Enstrom 280FX accident near Erie, Colorado, January 26, 2015
On January 26, 2015 at about 7:02 pm local time, a Enstrom 280FX (helicopter), registered N86235, was destroyed in an accident near Erie, Colorado (Erie Municipal airport). It was an instructional flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
An in-flight failure of the helicopter's #2 main rotor spindle due to undetected fatigue cracking, which resulted in an in-flight breakup. Contributing to failure were the nonconforming thread root radius of the spindle and the manufacturer's failure to include a bending moment within the spindle threads when performing the fatigue analysis during initial design of the spindle.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 26, 2015 · about 7:02 pm local time · cases in 2015
- Place
- Erie, Colorado · Erie Municipal · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Enstrom 280FX FX · all 280FXs on the register
- Registration
- N86235 · no longer on the register · serial 2002
- Damage
- Destroyed
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The flight instructor and the student pilot were conducting a local instructional flight in the helicopter. The helicopter was on final approach to land when one of the three main rotor blades (#2 blade) separated from the main rotor head. The main transmission and main rotor head (with #1 and #3 blades still attached) then separated from the helicopter, and the helicopter descended to ground impact. Examination of the wreckage revealed that the separation of the #2 blade was due to fracture of the #2 main rotor blade spindle. The #2 spindle fractured at the inboard end of the threads. Metallurgical analysis of the fractured spindle revealed signatures consistent with a fatigue crack initiating from multiple origins that propagated across 92% of the spindle cross-section; the remaining 8% of the fracture surface exhibited signatures consistent with overload. The high percentage of stable fatigue fracture growth versus overload suggested that low loading propagated the crack. Further, corrosion was visible on the fracture surface in the fatigue initiation area, which indicated that the crack had been present and growing for some time. Similar fatigue cracks were observed emanating from thread roots on the #1 and #3 spindles; the crack in the #3 spindle emanated from the inboard-most thread, similar to the crack in the #2 spindle, and the crack in the #1 spindle emanated from the cotter pin hole. Both of these cracks were shorter than the crack in the #2 spindle, and the fatigue on their fracture surfaces had only propagated a small amount through the #1 and #3 spindle cross-sections. The root radii of the threads on all three of the spindles did not meet the thread form specified on the manufacturer's drawing. Cross-sections of the threads from the three spindles showed that the #2 spindle and the #3 spindle had flat-bottomed threads; the #1 spindle did not have flat-bottomed threads but had threads with a sharper than specified root radius. A subsequent finite element analysis determined that the flat-bottomed threads and the sharper than specified root radius threads would result in higher stresses at the threads, which likely contributed to the crack initiation within the threads. Further, the investigation determined that the predicted loads used in the original fatigue analysis during the design of the spindle did not account for a bending load at the spindle threads. The omission of bending loads during design and the flat-bottom quality of the threads led to stresses greater than used in the original fatigue life calculation by the manufacturer. Further, the finite element analysis of the spindle revealed that, once a crack has initiated, the bending loads at the spindle threads would be sufficient to propagate the crack at a rate similar to that of the total time accumulated on the #2 spindle (about 9,300 flight hours). Before the accident, the spindle was not a life-limited part, and there were no recurrent inspections specified for the spindle threads, resulting in a low likelihood of the operator detecting the fatigue fracture within the spindle threads before the accident. Following this accident, the manufacturer released a service directive bulletin and the Federal Aviation Administration released an airworthiness directive that require a magnetic particle inspection of spindles with 1,500 hours or more time in service.
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
- Autorotation Inflight upset defining event
The NTSB's findings
- factor Organizational issues › Development › Manufacture/production › Equipment manufacture › Manufacturer
- Aircraft › Aircraft propeller/rotor › Main rotor system › (general) › Failure
- Aircraft › Aircraft propeller/rotor › Main rotor system › (general) › Design
- Aircraft › Aircraft propeller/rotor › Main rotor system › (general) › Capability exceeded
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
- Flight time: 1,223.3 hours in all; 87 in the last 90 days; 4.9 in the last 30 days
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: rgt
- Injury: fatal
Dual student
- Certificate: student
- Flight time: 65.8 hours in all; 65.8 in this make and model; 29.2 in the last 90 days; 8.5 in the last 30 days
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming HI0-360 SER (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: Erie CO
- Destination: Erie CO
- Flight plan: none
- Runway 15, 4,700 ft by 60 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Temperature: 72°F (22°C), dew point 16°F (-9°C)
- Observation at 6:55 pm from EIK, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
21 documents, released by the NTSB on July 20, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N86235: not on the register today · the record of its deregistration
- Enstrom 280 Shark 66 registered today · the model family and its accident history
- Enstrom 216 aircraft on the register
- Engine: Lycoming HI0-360 SER 390 aircraft carry this series today · as the NTSB recorded it
- Erie Municipal · nearest airport
- Accidents and incidents in Colorado 2,860 since 1982 · 383 in the last ten years
- Colorado 7,486 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN15FA126.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
