NTSB CAROL · Event
Event CHI97LA266
Registry · N224AM
FAA Aircraft Registry record.
Make / Model
BELL HELICOPTER TEXTRON CANADA 407
Year of manufacture
2011
TCDS
H2SW · BELL HELICOPTER TEXTRON CANADA LTD
Engine
ROLLS-ROYC 250-C47B (650 hp)
Seats / Engines
8 seats · 1 engine
Last airworthiness date
20110606
ADS-B equipped
Yes — Mode-S A1EFE9
Registrant of record
AIR METHODS LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's improper in-flight planning/decision and failure to perform the emergency procedure for shut-down of the right engine. Factors relating to the accident were: the power lever cable became disconnected from the fuel control unit, due to improper maintenance; and reduced directional control of the airplane, when one engine remained at a high power setting.
Factual narrative
On August 19, 1997, at 2221 central daylight time (cdt), a Swearingen SA226TC, N224AM, registered to Superior Aviation, Inc., was substantially damaged following a loss of control during the landing roll on runway 05 (6,501' x 150' asphalt), at the Des Moines International Airport, Des Moines, Iowa. The commercial pilot reported minor injuries. The 14 CFR Part 135 cargo flight was operating in instrument meteorological conditions. An IFR flight plan had been filed. The cargo flight departed from Wichita, Kansas, at 2050 cdt, with an intended destination of Des Moines, Iowa. According to the pilot's written statement, he was on approach to land on runway 05, when it was observed that the right engine control was stuck at the maximum power position. The pilot indicated that it seemed like the right engine was disconnected from the right power lever. Upon breaking out of the clouds the pilot found himself approximately 1 1/2 miles from the runway and too high to make a safe landing so he chose to execute a missed approach. The pilot found the airplane would not maintain altitude with the gear down and one engine at zero thrust. Upon shooting a second localizer approach to runway 05, he found it hard to keep the airplane straight and level because of the power differential between the two engines. The pilot said, "Upon touchdown, within the first third of the runway, I attempted to engage Beta Mode on both engines. Only the left engine engaged while the right engine remained at full power. My intention was to keep the aircraft directionally controllable and stop the aircraft in the shortest distance possible. After touch down I realized directional control was minimal. I made a decision to go around rather than to risk running off the runway. I advanced the power on the left engine to MAX power and rotated. The aircraft then spun out of control and off the runway (end)." During a telephone interview, he stated that he had problems controlling the airplane on the runway so he advanced power on the left engine and initiated a go-around 1/2 way down the runway. The airplane became airborne, but settled back to the ground after reaching 130 knots. According to the Federal Aviation Administration (FAA) approved Swearingen Metro SA226-TC Pilot's Operating Handbook, it states for a power plant control malfunction; "in the event there is an indication of improper operation of a fuel control or propeller control, it is recommended that the affected engine be shut down and a single engine landing accomplished." An Air Traffic Control Tower controller who was working Local and Ground Control observed the airplane touchdown at a high rate of speed in the vicinity of Taxiway M (approximately 1/3 down the runway). The controller reported that as the airplane passed Taxiway Q (2/3 down the runway), it appeared to be having directional control problems. The controller observed the airplane to exit the end of the runway and skid sideways through the localizer antenna onto the grass area. The pilot also did not advise nor declare an emergency. An FAA Inspector represented the NTSB during the on-scene investigation. The inspector observed tire marks which appeared to be skid marks from the end of the runway to where the airplane came to rest. During the investigation it was determined that the right engine power control cable housing was disconnected. This gives the cable no anchor point for the sheathing and it prevents the rod end from moving, but allows the sheathing to flop back and forth. This occurred due to a safety tab being broken off, allowing it to unscrew. The maintenance log books revealed maintenance was performed on the right engine on July 19, 1997. The discrepancy was on the right engine power lever being stiff. The mechanic re-rigged the engine power cable. All other flight and engine controls were inspected and were found to have continuity. Both engine propeller governors and fuel control units were removed and bench tested. The tests and inspections reveal no pre-accident anomalies with the units. During a landing approach, the pilot noted that the right engine remained at a high power setting, when he moved the power levers to reduce power. He executed a missed approach and had difficulty keeping the airplane straight and level. The pilot maneuvered for a second approach to land. After landing, he could not maintain directional control of the airplane and tried to go around, but the airplane went off the end of the runway and impacted the localizer antenna. The pilot did not advise ATC of the problem nor did he declare an emergency. The Pilot's Operating Handbook stated that for a power plant control malfunction, the affected engine should be shut down, and a single engine landing should be made. The power control cable was found disconnected from the anchoring point. A safety tab was broken off the housing, allowing it to unscrew. About one month before the accident, maintenance had been performed on the right engine to correct a discrepancy about the right engine power lever being stiff. The mechanic re-rigged the right engine power cable. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_CHI97LA266.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 (loss of control, go-around, 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.
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- 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…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- 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.
- 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.
- 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…
Browse the full corpus — academia portal ↗