FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA93LA004 · Robinson R22 BETA

5 Oct 1992 · Naples, FL, United States

The London Robinson R22 BETA · Accident: loss of control in flight while maneuvering

From Naples Municipal Airport (APF) to an unrecorded destination

Report a problem

Event

NTSB case
MIA93LA004
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 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
N2321X
Operator
The London
Onboard fatalities
Unknown
Route
From Naples Municipal Airport (APF)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
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Airspeed, inadequate
  • Pilot in command › Altitude, improper
  • Pilot in command › Emergency procedure, not performed

Approximate · Estimated position: the centre of Naples, FL, the place the record names. Not the accident site.

NTSB narrative

THE PLT STATED THAT DURING HIS FIRST PASS WHILE OVER TREES, FOR A PHOTOGRAPHIC RUN, THE HELICOPTER EXPERIENCED A SLIGHT YAWING TENDENCY. DURING THE SECOND PASS AT THE SAME AIRSPEED BUT AT A LOWER ALTITUDE (BETWEEN 25 AND 50 FT ABOVE THE TREES) THE HELICOPTER ENTERED AN UNCOMMANDED RT YAW. HE LOWERED THE COLLECTIVE CONTROL AND PUSHED THE CYCLIC BUT DID NOT ADJUST THE THROTTLE. THE SPINNING DESCENT CONTINUED UNTIL IMPACT WITH THE TREES THEN THE GROUND. EXAM OF THE DAMAGED TAIL ROTOR BLADES BY AN FAA AIRWORTHINESS INSPECTOR INDICATE EVIDENCE OF ROTATION AT IMPACT. THE PLT'S BOSS WAS THE PHOTOGRAPHER.

Probable cause

INCORRECT AIRSPEED, INSUFFICIENT AIRSPEED, AND FAILURE OF THE PILOT IN COMMAND TO PERFORM THE CORRECT EMERGENCY PROCEDURE FOLLOWING THE IN FLIGHT LOSS OF CONTROL. CONTRIBUTING TO THE ACCIDENT WAS SELF INDUCED PRESSURE BY THE PILOT IN COMMAND.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA93LA004
Event ID
20001211X15913
Case number
MIA93LA004
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: 91bcaf63fc0e685915b1398e190104ff7324014325f0a5761e2d5b9c9e9b7010; retrieved 2026-09-21T23:06:29.185Z.