ERA15FA096 · Robinson Helicopter R22 BETA
Vertical Solutions Helicopter Company LL Robinson Helicopter R22 BETA · Accident: loss of control in flight on approach
From Fernando Luis Ribas Dominicci Airport (TJIG) to Fernando Luis Ribas Dominicci Airport (TJIG)
Event
- NTSB case
- ERA15FA096
- 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
- 1 · 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 Helicopter 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
- N348VH
- Onboard fatalities
- Unknown
- Route
- From Fernando Luis Ribas Dominicci Airport (TJIG), San Juan, PRTo Fernando Luis Ribas Dominicci Airport (TJIG), San Juan, PR
- Aircraft age
- About 23 years (built 1992)
- 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
- Approach · VFR pattern downwind
- 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 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student helicopter pilot was on a solo training flight in the airport traffic pattern. He had completed eight approaches via a right downwind approach to the runway, when the air traffic controller advised him that he was number three for his next approach. About 1 minute later, the student pilot requested a left 360-degree turn. The controller then instructed him to hold at his current location and expect to be number four in sequence. During the next 6 minutes, the controller made three attempts to have the student pilot report the traffic to follow on final approach in sight, and the student pilot advised that it was hard for him to hear the controller's instructions due to wind noise. The controller then advised the student pilot to follow an airplane on short final approach, and the student pilot reported the traffic in sight. About 1 minute later, the controller advised the pilot of another airplane to follow the helicopter on the approach. The airplane pilot observed the helicopter ascend in a series of right, 360-degree turns for about 100 to 200 ft. As it climbed, white smoke consistent with a rapid increase in engine rpm and an engine overspeed trailed the helicopter. When the helicopter climbed to an apex of about 800 ft, the ends of both rotor blades coned upward to where the tips were nearly vertical, consistent with a low rotor rpm condition. The helicopter then entered a right, spiraling descent until it impacted the water.
A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures with the helicopter that would have precluded normal operation. The main rotor blade elastomeric teeter stops were missing, consistent with low rotor rpm blade flapping. Although the temperature and dew point were conducive to carburetor icing, its formulation likely would not have allowed the helicopter to climb as high as it did just before the accident. More likely, the student pilot became distracted while he attempted to track other aircraft in the traffic pattern and sequence the helicopter for the approach, which led to his failure to maintain rotor rpm. Toxicological testing performed on specimens from the pilot identified butalbital in liver (1.24 ug/g) and in muscle (0.468 ug/g). Estimated corresponding blood levels were likely below the therapeutic window for butalbital, and unlikely to have been directly impairing at the time of the accident.
Probable cause
The student pilot’s failure to maintain rotor rpm while maneuvering in the airport traffic pattern, which resulted in the helicopter’s uncontrolled descent to the water. Contributing to the accident was the student’s distraction with other aircraft operating in the traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15FA096
- Event ID
- 20150110X10017
- Case number
- ERA15FA096
- 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: d1ac2f080bc50d5fc2c79315960ea26dac4ceddbef0255c3ecd2f974dbc8fac7; retrieved 2026-09-14T17:30:43.218Z.