NTSB CAROL · Event
Event MIA99LA070
Aircraft involved
Probable cause & findings
The CFI's decision not to follow procedures and directives (initiate a go-around/power recovery) during a simulated 180 autorotation resulting in a hard landing and in flight collision with terrain.
Factual narrative
On January 30, 1999, at about 0841 eastern standard time, a Robinson R22, N4046H, registered to Comprador Helicopter Inc., operated by Heliflite as a 14 CFR Part 91 instructional flight crashed while conducting a 180 autorotation with turn to runway 10 at Pompano Beach Airpark, Pompano Beach, Florida. Visual meteorological conditions prevailed and no flight plan was filed. The helicopter was destroyed. The commercial pilot/certified flight instructor, and commercial pilot receiving instruction sustained serious injuries. The flight originated about 3 minutes before the accident Two witnesses who are Robinson R22 instructor pilots stated they observed the helicopter in right closed traffic for runway 10. They observed the helicopter conduct a 180 autorotation before the accident, which resulted in a termination with power to the numbers on runway 10. They stated the autorotation did not look right, so they decided to watch the helicopter. The helicopter remained in right closed traffic and was at about 500 feet as it was abeam the numbers of runway 10. They entered the auto and turned left about 20 degrees. The helicopter was observed to turn a very steep right turn (90 degrees) with a steep nose low/down attitude (60 degrees). Between 100 to 150 feet they started to roll out of the turn, but not all of the way out. One of the witnesses stated, "the dive looked to steep to recover from." At contact with the ground they appeared to still have had a nose low attitude of 5 to 10 degrees. The helicopter crashed short of the numbers. The pilot stated in an initial interview that he was demonstrating the 180 autorotation to the rated student pilot. He entered the maneuver at 500 feet and 60 knots. He lowered the collective pitch to the full down position, applied right anti torque pedal, reduced the throttle to split the needles, and adjusted his airspeed to a 60 knot attitude, and began a right turn towards his intended touchdown point. The airspeed decreased a little so he lowered the nose. As they were going through 100 feet he started to level off. The rotor was in the green arc, airspeed 60 knots, they were in a high rate of descent, and the airframe started to vibrate. The helicopter collided with the ground in a nose low attitude. When asked why he did not initiate a power recovery when he knew he was in a high rate of descent and would not reach his intended touchdown point, he kept referring to the airframe vibration. When asked if he experienced any low rpm after he went through 100 feet he said no. The pilot stated in the NTSB Pilot/Operator Aircraft Accident Report, "As we came on downwind I took the controls from Mr. Perez and positioned the aircraft abeam the proposed landing spot at +/- 500 AGL and +/- 60 kts Through out the turn rpm was in the green. But as airspeed was a little low (+/- 55 kts) I lowered the nose a little bit to maintain 60 kts. Upon leveling off out of the turn at around 100" AGL I performed the 100' check. As I recall rpm was slightly above the green (106-107% rpm) and airspeed was +/- 60 kts. At that very instant the entire helicopter began vibrating violently and the rate of descent increased dramatically. I can also recall very high control forces as I attempted to pull aft cyclic and up collective. As I recall it took about 3 seconds from the time I came out of the turn and the vibrations started to the time of impact." The commercial pilot receiving instruction stated the CFI stated, "Jasper Blotkamp was in command of the helicopter as he was showing me 180 degree auto rotations when I felt the helicopter vibrate and heard the warning alarm of the low rotor rpm in the cockpit. Immediately after this the helicopter hit the ground." The Robinson R22 Maneuver Guide states the following entry procedures for a 180 (Autorotation) with power recovery: Establish the aircraft on a downwind at 75 KTS and 700 feet AGL. When abeam the intended touchdown point, enter the autorotation by smoothly, but firmly, lowering the collective full down without reducing the throttle. Usually the needles will split establishing an autorotation. If the needles do not split, reduce the throttle slightly. Apply right pedal and aft cyclic to maintain the attitude. Crosscheck attitude, trim, rotor, RPM, and airspeed. It states that the turn should be completed and the helicopter aligned with the intended touchdown area prior to passing through 100 feet AGL. If the collective has been increased to load the rotor during the turn, it may have to be lowered on roll out to prevent a decay in RPM. As the aircraft descends through 100 feet AGL, make an immediate power recovery if the following conditions do not exist: 1. Aircraft aligned with the touchdown point. 2. Rotor RPM in the green. 3. Airspeed 60 to 70 KTS. 4. Rate of descent less than 1500 FPM. The maneuver guide defines the symptoms of low rotor rpm as: 1. A noticeable decrease in engine noise. 2. Aircraft vibration and cyclic stick shake at higher airspeeds. 3. The low rotor RPM warning horn and light at approximately 95% RPM. The CFI was demonstrating a 180 autorotation with turn. The pilot did not meet the parameters listed in the maneuver guide for a touchdown or power recovery while going through 100 feet. The helicopter collided with terrain hard and nosed over end over end. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_MIA99LA070.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗