FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW03LA099 · Robinson R22 Beta II

18 Feb 2003 · Kent, TX, United States

Robinson Helicopters Robinson R22 Beta II · Accident: airframe, component or system failure en route

From T27 · El Paso, TX to Fort Stockton Pecos County Airport (FST)

Report a problem

Event

NTSB case
FTW03LA099
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 Beta II

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
N54TR
Onboard fatalities
Unknown
Route
From T27 · El Paso, TXTo Fort Stockton Pecos County Airport (FST), Fort Stockton, TX
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
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
Airframe, component or system failure
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 › Separation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While ferrying a helicopter to its new owner/operator, the 1,351-hour pilot experienced a loss of main rotor drive. The pilot reported that the helicopter was in level cruise flight at an altitude of 700 to 900 feet AGL at an indicated airspeed of 70 to 75 knots, when they heard a loud "thump" coming from the area behind the cabin, immediately followed by the activation of the clutch light and accompanied with a change in engine and rotor noise. Within a couple of seconds, the pilot reported hearing another "thump" and, subsequently, the engine RPM started to increase as the rotor RPM was decreasing. The pilot initiated a 180-degree turn to position the helicopter into the wind while maintaining 70 knots as he entered an autorotation into rolling rough and uneven terrain. The helicopter came to rest in an upright position. Examination of the wreckage by the FAA inspectors, who traveled to the accident site, revealed that both main rotor blades were damaged and the tailboom was severed from the helicopter and broken into several pieces consistent with the main rotor contacting the tailboom during the landing. The engine showed evidence of an overspeed greater than about 110%. One of the two drive belts was missing and the remaining belt was off of the upper sheave and showed considerable damage. The wreckage was recovered to the Robinson Helicopter Company facility in Torrance, California, for a detailed examination. No discrepancies were noted, apart from impact related damage, in the assembly, installation or alignment of the engine, clutch assembly or actuator assembly. No evidence of pre-impact damage to the flight and powerplant controls was found. The failed belt was found separated between the vees with only a 5-inch section still intact.

Probable cause

The loss of main rotor drive due to a drive belt separation resulting in a forced landing. 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 FTW03LA099
Event ID
20030220X00240
Case number
FTW03LA099
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, coordinates. 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: 0cc44c2d05d96a8720035038d42fa26b64a4787ea22fd1c4b1fa30c059ee1536; retrieved 2026-09-21T19:32:22.325Z.