NTSB CAROL · Event
Event LAX99LA112
Aircraft involved
Probable cause & findings
The loss of aircraft control due to the pilot's sudden application of collective combined with excessive cyclic inputs.
Factual narrative
On February 27, 1999, at 1256 hours Pacific standard time, an Enstrom F-28F, N5700C, rolled over and crashed during takeoff from the Reid-Hillview Airport, San Jose, California. The aircraft sustained substantial damage. The commercial pilot, who holds private helicopter privileges, and the mechanic were not injured. The aircraft was operated as a maintenance test flight by California In Nice Air, Inc., under 14 CFR Part 91 of Federal Aviation Regulations, and was originating when the accident occurred. Visual meteorological conditions prevailed at the time and no flight plan was filed. The pilot stated that he was in the left seat, applying collective in preparation to liftoff from the pad. As he pulled collective, the aircraft suddenly rose vertically to a height of 4 feet agl. He was surprised because he did not feel at the time that the aircraft had become light enough to hover. As the aircraft ascended, the fuselage began a left and right pendular motion, which then shifted to fore and aft movement as he attempted to recover. As the aircraft pitched forward for the final time, the main rotor blades struck the ground. After the rotor blades struck the ground, the aircraft rolled onto its right side before coming to rest. The pilot exited the aircraft without assistance. The mechanic shut off the master and fuel switches before being assisted through the broken windscreen by several nearby witnesses to the accident. The pilot stated that he has about 147.8 hours in helicopters and 110.3 hours in the F-28F, but had not flown the aircraft in the preceding 90 days. He said he thought he might have initially mispositioned the cyclic before raising the collective, but was also attempting to comply with the mechanic's request to "pull-off before vibration became a problem." He did not clearly recall what occurred or what control inputs he made after becoming airborne. He also did not remember making any sudden or abrupt control movements, but said the controls "felt" differently than he had expected. The mechanic had removed the right cyclic and pedal controls prior to flight. The mechanic, who occupied the right seat, reported the flight was being conducted to verify the main rotor tracking and balancing that had been completed earlier. The aircraft had already been test flown once since the tracking and balancing were completed with no reported abnormalities. The mechanic said there were three targets installed on each main rotor blade and a magnetic pickup on the main rotor mast. Also installed at the time was the associated wiring that connected the Strobex and Chadwick test equipment located in the rear of the aircraft. A Federal Aviation Administration airworthiness inspector checked the aircraft flight controls after the accident and reported that there was no evidence of any preexisting mechanical defects. The pilot and a mechanic were performing a postmaintenance test flight following tracking of the main rotor blades. One test flight had already been accomplished with no discrepancies. The pilot had not flown the helicopter during the preceding 90 days. As the pilot pulled the collective, the aircraft suddenly came to a 4-foot hover with the fuselage swinging side to side and fore and aft below the main rotor. The pilot attempted to recover; however, the aircraft pitched forward, the main rotor blades struck the ground, and the aircraft rolled onto its right side. The pilot said he thought he might have mispositioned the cyclic before raising the collective as he was attempting to comply with the mechanic's request to 'pull-off before vibration became a problem.' He said the controls 'felt' differently than he had expected. A detailed control system inspection found no evidence of preexisting discrepancies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_LAX99LA112.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 (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗