FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA074 · Robinson R-22

26 Mar 2002 · Coral Springs, FL, United States

Robinson R-22 · Accident: hard landing

From Pompano Beach Airpark (PMP) to an unrecorded destination

Report a problem

Event

NTSB case
MIA02LA074
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 R-22

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
N7187J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pompano Beach Airpark (PMP), Pompano Beach, FLTo 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

  • Pilot in command(cfi) › Level off, high

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the instructor, he wanted to finish off the rotorcraft instructional flight with a practice forced landing to a power recovery at 500 feet agl. He did not disarm the engine governor, and the student rolled the throttle to the detent and held it there when the instructor announced, "engine failure". When the instructor tried to ease on throttle, he felt resistance and interpreted the condition as a real engine failure and announced, "my controls". The combination of choosing a landing spot with too high grass and uneven, soft terrain, together with the student continuing to handle the collective control resulted in a too high flare and hard touchdown and rollover.

Probable cause

The instructor's too high flare during an autorotational landing, resulting in a hard touchdown and rollover. Factors contributing to the accident were the instructor's nonperformance of a preflight brief concerning procedures and techniques for a simulated engine failure, the student's not removing total rotorcraft control when the instructor announced, "my controls", and the selection of unsuitable terrain for landing by the instructor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA074
Event ID
20020327X00409
Case number
MIA02LA074
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, coordinates. 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: a0d221da15418392fbf93ece9d4855e00d55feee82a099fc0736169629cadfd4; retrieved 2026-09-22T11:03:17.130Z.