FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA148 · Robinson R22 BETA II

1 Feb 2013 · Gillett, TX, United States

Robinson R22 BETA II · Accident: loss of tail rotor effectiveness while maneuvering

From Karnes City, TX (no airport) to an unrecorded destination

Report a problem

Event

NTSB case
CEN13LA148
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
N3059Q
Operator
Jams M. Janysek · private individual
Onboard fatalities
Unknown
Route
From Karnes City, 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
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
Loss of tail rotor effectiveness
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot and a passenger were conducting an aerial hunt at low altitude. The pilot said he was about 20 feet above 30-foot-tall trees and flying into the wind slowly when the tail rotor "malfunctioned" and he lost control. The helicopter started spinning to the right, and the pilot initiated an autorotation. The helicopter landed hard and rolled over on its left side. The pilot stated that he thought the helicopter had lost tail rotor authority. Examination of the tail rotor found no evidence of a tail rotor malfunction or defects that would preclude normal operation. The pilot was operating the helicopter in a low airspeed, out of ground effect, high-power-demand flight condition, which was conducive to the development of loss of tail rotor effectiveness.

Probable cause

A loss of tail rotor effectiveness while manuevering at low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA148
Event ID
20130203X53401
Case number
CEN13LA148
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: d32f4249e304ec71c95966a749e783e91ac55b05bcf9625a6ad80e8187048e15; retrieved 2026-09-15T20:53:00.720Z.