FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04LA131 · Robinson R22 Beta

4 Sept 2004 · St. Thomas, United States

Robinson R22 Beta · Accident: loss of control in flight during initial climb

From St. Thomas to an unrecorded destination

Report a problem

Event

NTSB case
MIA04LA131
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

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
N176FM
Operator
Aviane
Onboard fatalities
Unknown
Route
From St. ThomasTo 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
Initial climb
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
Loss of control in flight
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

  • Pilot in command › Performance data, not followed
  • Pilot in command › Remedial action, not performed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that the helicopter was parked on a dock at the Crown Bay Marina in a northeasterly heading. After starting the engine, he performed a pedal turn to the right, and brought the helicopter to a 4 foot hover with all engine indications in the green. He commenced a southeasterly takeoff profile into the 10-15 knot wind while maintaining a steadily climb at 30 to 40 knots. When the flight was at approximately 20 foot, the helicopter yawed to the right "sharply." He stopped the climb and was able to correct back to the original heading with left anti-torque pedal input. When the helicopter attained the original heading, it started spinning to the right "uncontrollably." He then entered an autorotation into the water where he and the passenger evacuated the helicopter before it sank approximately 60 yards from the dock. The pilot stated he maintained a southerly heading from the point of hovering to the autorotation and he did not contact any object during the entire flight. Examination of the tail rotor conducted by a Federal Aviation Administration (FAA) inspector revealed that the tailrotor drive shaft was fractured approximately six inches aft of the tailrotor drive shaft damper assembly. NTSB review of pictures provided by FAA revealed both ends of the fracture surfaces of the tailrotor drive shaft exhibited evidence of torsional twisting. The tailrotor blades were found to be fractured approximately 8 inches from the center of rotation. The FAA Rotorcraft Flying Handbook (FAA-H-8083-21) states that unanticipated yaw, also referred to as loss of tail rotor effectiveness (LTE), may occur in all single-rotor helicopters at airspeeds less than 30 knots, and occurs to the right in helicopters with a counter-clockwise rotating main rotor (Robinson 22). It is the result of the tail rotor not providing adequate thrust to maintain directional control. The suggested recovery technique of a sudden unanticipated right yaw is to apply full left pedal while simultaneously moving cyclic control forward to increase speed. As recovery is effected, adjust controls for normal forward flight. Collective pitch reduction aids in arresting the yaw rate but may cause an excessive rate of descent. Any large, rapid increase in collective to prevent ground or obstacle contact may further increase the yaw rate and decrease rotor revolution per minute (RPM). NTSB review of the Robinson R22 Beta Pilot's Operating Handbook revealed that the recommended takeoff profile, from a hover, is to maintain 5 feet until reaching 40 knots. This is where a steady climb may be commenced while accelerating to 60 knots.

Probable cause

The failure of the pilot-in-command to comply with performance data related to the recommended takeoff profile and his failure to perform remedial action following reduced tailrotor effectiveness, resulting in subsequent initiation of an autorotation and ditching.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04LA131
Event ID
20040930X01542
Case number
MIA04LA131
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: 2e26056f1e64053bb855b71f32d504444e3a08d57d2fe0dd85c4bec8a4db87d1; retrieved 2026-09-22T06:46:23.388Z.