MIA01LA049 · Robinson R-22 BETA
Robinson R-22 BETA · Accident: hard landing
From TSIG · San Juan, PR to an unrecorded destination
Event
- NTSB case
- MIA01LA049
- 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
- 0
- 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 R-22 BETA
- Aircraft type
- Robinson R-22
- 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
- N195HC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From TSIG · San Juan, PRTo 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Flightcrew › Collective, improper use of
- Flightcrew › Procedures/directives, not followed
Approximate · Estimated position: the centre of Ciales, the place the record names. Not the accident site.
NTSB narrative
The flight instructor stated that he and the student had been performing autorotation landings in an open field, and when power was required by him to affect the recovery, the engine did not produce enough power. The instructor further stated that the helicopter landed hard and the main rotor hit the tail boom, separating half of it from the rest of the helicopter. An FAA inspector and an FAA licensed company mechanic examined the accident helicopter, and performed a static power test on the engine. According to the inspector, the static check was conducted for about 15 minutes, with the engine operating at idle and at full power, and no abnormalities were observed. In addition, the inspector stated that examination of the fuel filter revealed no evidence of fuel contamination.
Probable cause
the flight crew's failure to follow procedures for a straight-in autorotation with power recovery that resulted in their improper use of collective resulting in a hard landing and substantial damage to the helicopter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA049
- Event ID
- 20010103X00008
- Case number
- MIA01LA049
- 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: d44564d32d7ac791402e5c2f521200e76ac6d600cad57a66b15784010a68b78f; retrieved 2026-09-22T12:15:49.463Z.