NTSB CAROL · Event
Event LAX04LA314
Aircraft involved
Probable cause & findings
The certified flight instructor's misjudged flare and delayed recovery from the practice autorotation.
Factual narrative
On September 5, 2004, at 0820 Pacific daylight time, a Robinson R22 Beta, N994RW, made a hard landing and rolled over at the North Las Vegas Airport, North Las Vegas, Nevada. The helicopter was substantially damaged. The commercial pilot held a certified flight instructor (CFI) certificate, and he sustained minor injuries. The pilot who was receiving dual flight instruction (student pilot) held a private pilot certificate, with a rotorcraft-helicopter rating, and he was seriously injured. Visual meteorological conditions prevailed at the time of the instructional flight, and no flight plan had been filed. Silver State Helicopter was operating the flight under the provisions of 14 CFR Part 91, and it commenced from the airport at 0803. According to the Federal Aviation Administration's (FAA) Western-Pacific Quality Assurance staff (AWP-505), immediately prior to the accident the pilot had performed a series of left-hand closed traffic patterns to runway 12L. The accident occurred during the 7th approach to the runway. An on-duty air traffic controller observed the helicopter perform what he described as a very steep approach to the runway. The helicopter's descent rate did not appear to significantly decrease, whereupon it impacted the ground and rolled over. The FAA reported that radio transmissions from the helicopter's crew sounded normal, and no tones were heard in the background. According to responding airport operation and management officials, the helicopter's initial point of impact (IPI) was in a dirt infield area approximately 20 feet east of the left side of runway 12L, and about 400 feet south of intersecting runway 07. They observed an estimated 90-foot-long debris field between the IPI and the main wreckage, which came to rest on runway 12L. The CFI reported to the National Transportation Safety Board investigator that during the flying lesson he was training his student in autorotations, and his student was working toward obtaining a commercial pilot certificate. The student had performed a series of six or seven 180-degree autorotations to the runway. The CFI stated that both he and his student were on the controls at the time of the accident. The CFI provided the Safety Board investigator with a written statement, dated September 8, 2004, in which he described the accident flight. In pertinent part, the CFI indicated that the mishap occurred on the 4th practice 180-degree autorotation. After the student improperly initiated the autorotation, the CFI told his student that he had the controls. The student let go of the controls, and the CFI commenced the 180-degree turn toward the runway. The CFI intended to complete the maneuver by performing a power recovery and a go-around. The CFI reported the following sequence of events then occurred: "As I rolled out of the turn and attempted the power recovery, I realized through the turn I had accumulated a huge descent rate that did not seem to stabilize after leveling out at approximately 15 ft AGL. We were still descending very fast. I pulled aft cyclic as quick as I could and attempted to roll the throttle on and raise the collective, but before I could initiate a flare, we hit the ground. After that we slid for approximately 200 to 300 ft, and rolled." The helicopter hit the ground hard during a practice autorotation and rolled over. The accident occurred during the 7th approach to the runway. An on-duty air traffic controller observed the helicopter perform what he described as a very steep approach to the runway. The helicopter's descent rate did not appear to significantly decrease, whereupon it impacted the ground and rolled over. The instructor said that after the student improperly initiated the autorotation, he told his student that he had the controls. The student let go of the controls, and the instructor commenced the 180-degree turn toward the runway. The instructor said he intended to complete the maneuver by performing a power recovery and a go-around. The instructor said that as he rolled out of the turn and attempted the power recovery, he realized that he had accumulated a huge descent rate that did not seem to stabilize after leveling out at approximately 15 feet above ground level (agl). The helicopter was still descending very fast when he pulled aft cyclic and attempted to roll the throttle on and raise the collective, but before he could complete the flare, the helicopter hit the ground, slid for approximately 200 to 300 feet, and rolled over. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_LAX04LA314.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 ↗