FTW01LA124 · Robinson R22
Robinson R22 · Accident: rotor failure/malfunction while maneuvering
From Raymondville, TX (no airport) to an unrecorded destination
Event
- NTSB case
- FTW01LA124
- 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
- 0 · 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
Robinson R22
- Aircraft type
- Robinson R22
- 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
- N7087X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Raymondville, TX (no airport)To not recorded
- 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
- Maneuvering · turn to reverse direction
- First occurrenceThe 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
- Rotor failure/malfunction
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Rotor drive system, main rotor drive belt › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter had been in flight for approximately 5 minutes when the main rotor rpm began to decrease. The "clutch light" illuminated and the "low rotor horn sounded." The pilot initiated an autorotation to an open field; however, he did "not have enough altitude" to clear some trees. The helicopter contacted the trees and impacted the ground "hard." The main rotor drive belts were found separated from the drive wheels. An examination of the helicopter by an aircraft mechanic and an FAA inspector revealed that the drive belts were "frayed and ripped." No anomalies were noted with the rest of the drive system. The helicopter was issued an airworthiness certificate on May 27, 1998. Review of the helicopter's maintenance records revealed that it had undergone its last annual inspection on February 10, 2001, at an aircraft total time of 409.2 hours. There was no record of the drive belts being replaced during the life of the helicopter. According to the helicopter manufacturer, the drive belts are to be changed on condition, and there is no life limit on the belts; however, the belts usually get replaced during the helicopter's 2,200-hour overhaul. At the time of the accident, the helicopter had accumulated a total of 488 hours.
Probable cause
the failure of the main rotor drive belts while maneuvering which resulted in a loss of main rotor drive. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA124
- Event ID
- 20010522X00987
- Case number
- FTW01LA124
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 82183c1b78b0f5c0095953d8d41531c6317ff4811edda4f9803759f770c4893a; retrieved 2026-09-22T11:57:14.406Z.