NTSB CAROL · Event
Event CHI97FA149
Aircraft involved
Probable cause & findings
the improper torque meter installation by maintenance personnel, attempting flight with known discrepancies by the pilot-in-command and the check airman, and an improper autorotation by the pilot-in-command with improper oversight of the autorotation maneuver by the check airman.
Factual narrative
HISTORY OF FLIGHT
On May 27, 1997 at 1110 mountain standard time (mst), a Bell 206L3, N35CH, was substantially damaged during an autorotation maneuver. The pilot was executing the maneuver during a Federal Aviation Administration (FAA) FAR Part 135 flight check when the accident occurred. The pilot had just completed two autorotation maneuvers, and this autorotation maneuver was to be a 180 degree reversal autorotation to a predetermined spot landing with a power termination. The pilot executed the maneuver, but during the level off received a low RPM warning horn. The pilot attempted to increase engine power using the throttle on the collective, but was not able to attain maximum engine RPM. The helicopter impacted hard with the taxiway, causing structural skin damage to the tail boom. The airline transport pilot and two FAA inspectors were uninjured in the accident. The 14 CFR Part 91 flight was operating in visual meteorological conditions, and no flight plan had been filed.
TESTS AND RESEARCH
The investigator in charge (IIC) examined the helicopter on May 29, 1997. Prior to the IIC arriving, the helicopter's tail boom and interior had been removed from the helicopter. With the interior removed from the helicopter the collective and throttle controls were moved throughout their full range of travel. With the collective control near its maximum rotor blade angle position the throttle linkage would bind with a nut when it reached the mid throttle position. If the collective was cycled with the throttle in the idle position no binding would occur. The helicopter had been modified to incorporate an external torque meter which was placed on the helicopter in view of the pilot. This torque meter was installed to aid the pilot while conducting external lifting operations. The major repair and alteration paper work (FAA Form 337), indicated an installation date of May 23, 1997. It was a nut from the installation of this torque meter which interfered with the throttle controls when the controls were cycled following the accident.
ADDITIONAL INFORMATION
The pilot in command of the helicopter in a written statement wrote that during the preflight cockpit check she noticed a "... slight lump in the throttle...", and reported that she pointed this out to the FAA examiner. She wrote that both pilots believed it to have been caused by the installation of the dual controls for this flight. The IIC asked the FAA examiner on June 4, 1997 if he remembered the pilot making this comment, and he remembered the pilot making some comment to him about the throttle before the flight, but could not remember the pilot's exact words. Two helicopter instructor pilots were interviewed by the IIC following the accident. Both pilots reported that any time an autorotation was executed they always assume that no engine power will be available during the recovery portion of the maneuver. Federal Aviation Regulation FAR 61.47 states that unless previously agreed upon the FAA examiner is not the pilot in command during a flight check. The pilot was executing an autorotation maneuver for a FAR Part 135 flight check. This autorotation maneuver was to be a 180-degree reversal autorotation to a predetermined spot landing with a power termination. The pilot executed the maneuver, but during the level-off received a low RPM warning horn, and attempted to recover using power. During the attempt to increase power the helicopter's throttle interfered with a nut which had been installed for an external torque meter approximately one week before the accident. The nut on the torque meter installation interfered with the throttle controls in certain positions only. A discrepancy with the helicopter's throttle was noticed by the pilot-in-command, and reported to the FAA examiner before the beginning of the flight check. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_CHI97FA149.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 ↗