FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA166 · Robinson Robinson R22 Beta

20 Aug 2003 · Odessa, FL, United States

Clearwater Air Park Robinson Robinson R22 Beta · Accident: hard landing

From ORMC Trauma Center Heliport (3FD1) to ORMC Trauma Center Heliport (3FD1)

Report a problem

Event

NTSB case
MIA03LA166
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 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
N129YE
Onboard fatalities
Unknown
Route
From ORMC Trauma Center Heliport (3FD1), Odessa, FLTo ORMC Trauma Center Heliport (3FD1), Odessa, FL
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 › Rotor RPM, not maintained

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

NTSB narrative

The accident flight was the certified flight instructor (CFI) applicants initial CFI checkride. The CFI applicant stated in writing immediately after the accident that after they had exited the helicopter, the designated pilot examiner (DPE) stated to him "...we should say that when the [throttle] was rolled [off] the engine stopped running and to stick to that story." The CFI applicant stated in writing with the NTSB Pilot/Operator Aircraft Accident Report form that after obtaining his commercial pilot certificate with rotorcraft helicopter rating, he attended the Robinson factory in California where he completed the Robinson Safety Course. He also described the events leading up to the checkride and what occurred during the oral examination, the preflight inspection, and the flight portion of the checkride immediately before the accident. Following several autorotative landings which he describes in detail, the DPE then asked him to perform a 180- degree autorotation to a power recovery and entered the maneuver. While flying on the downwind leg with the airspeed and main rotor rpm steady, he looked to his intended spot then back to the gauges. At that time the low main rotor horn came on; the rpm was at 96 percent. He (CFI applicant) said, "rpm is stable" and started the turn knowing the rpm would increase during the turn. The airspeed was 60 knots and the main rotor rpm was steady at 96 percent. About 90 degrees into the 180-degree turn, the DPE advised, "you're too slow" and took the controls. He (CFI applicant) thought the DPE was going to roll on throttle and recover but he continued the descent. The helicopter landed hard, slid across the runway, and came to rest in the grass adjacent to the runway. He indicated on the report that there was no mechanical failure or malfunction. The CFI applicant later stated verbally that the DPE did not apply throttle input when he took the controls. The DPE stated in writing immediately after the accident that, "As I attempted to recover, it seemed as though the engine did not respond. However I am not sure if it stopped since this all happened within 1 second or two." The DPE stated in writing with the NTSB Pilot/Operator Aircraft Accident Report form what he asked during the oral examination. Following that he conducted a preflight briefing with the CFI applicant which included discussion of various procedures they would follow and the guidelines for executing the required maneuvers. Following the preflight inspection of the helicopter, the CFI applicant performed airwork followed by several straight-in autorotations to a power recovery, then one straight-in autorotation to touchdown. He reminded the CFI applicant sometime during the autorotations the main rotor rpm was falling below safe limits and he should keep it closer to the normal limits of 102-104 percent. The CFI applicant responded that he understood but his CFI had taught him that way to avoid any overspeeds during the flare. The DPE then "directed" the applicant to perform a normal takeoff and try a "required" 180-degree autorotation to a power recovery. The flight departed and the CFI applicant entered the autorotation. During the left turn the low main rotor horn came on at approximately 97 percent, and the CFI applicant continued the descending turn until he was between 100-200 feet above ground level, at 40 knots airspeed, and a nose down attitude. When the flight was about 1/2 way into the 180-degree turn he felt the aircraft descending rapidly and he stated, "the rpm is too low" as he observed it descending through 80 percent. He heard a response from the CFI applicant and he took the controls when he observed the main rotor rpm "...decreasing through 80%...." He grabbed the controls and felt the applicant pulling up even further on the collective. He (DPE) simultaneously pushed the collective full down, rolled on full throttle and applied left cyclic control input. He was only able to turn the helicopter 40 degrees and the helicopter contacted the runway near the centerline at about a 40-degree angle while in a level attitude. He estimated the helicopter skidded approximately 125 feet before coming to rest upright. They both exited the helicopter and he asked the CFI applicant if he remembered whether or not the engine was running when he opened full throttle since he did not get the expected response from the engine when he opened full throttle. The CFI applicant responded, "I don't remember what should I say." He advised the CFI applicant to stick to your story about not remembering. He indicated on the report that there was no mechanical failure or malfunction. Review of a document provided by Robinson Helicopter Company pertaining to a flight evaluation by the CFI applicant 6 days before the accident revealed the instructor indicated the CFI applicant was average in all areas, which included 180-degree autorotations. Review of the procedures for practice autorotation with a power recovery revealed, "Keep RPM in green arc and airspeed 60-70 KIAS."

Probable cause

The failure of the pilot to maintain the proper airspeed during the practice 180-degree autorotational landing and his failure to maintain main rotor rpm resulting in a hard landing. A contributing factor in the accident was the delay by the designated pilot examiner to take the controls from the pilot after recognizing that the airspeed and main rotor rpm were low.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA166
Event ID
20030905X01470
Case number
MIA03LA166
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: e19b7eccfc0288006b44280ae2194f4dea9568d53cac448f2469f2e5e8dc1c18; retrieved 2026-09-21T19:23:32.572Z.