FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA275 · Meyers 200 B

19 Jul 2016 · Huron, SD, United States

Meyers 200 B · Accident: loss of engine power (partial) en route

From Huron Regional Airport (KHON) to Flying Cloud Airport (KFCM)

Report a problem

Event

NTSB case
CEN16LA275
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Meyers 200 B

Aircraft type
Meyers 200
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N229RS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Huron Regional Airport (KHON), Huron, SDTo Flying Cloud Airport (KFCM), Minneapolis, MN
Aircraft age
About 53 years (built 1963)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Fluids/miscellaneous hardware
  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

**This report was modified on August 9, 2024. Please see the public docket for this accident to view the original report.** The pilot and passenger were on a cross-country personal flight when the pilot noticed oil on the airplane's windscreen. The pilot subsequently landed and had maintenance personnel inspect the airplane. Maintenance personnel noted that the crankshaft seal was leaking and identified several other discrepancies. The pilot chose to have the repairs completed. During the repairs, maintenance personnel noticed that the bolt holding the throttle cable bracket was loose, worn, and not safety wired. The maintenance facility did not have an exact replacement bolt, so the mechanic found a similar bolt, drilled a hole in the bolt head for the safety wire, and installed the bolt. The mechanic reported that he installed the safety wire through the throttle bolt and then down to the mixture control bolt. Photographic stills from the maintenance shop security camera showed the pilot periodically inspected or observed the work as maintenance personnel finished the repairs on the airplane. The pilot also took a photograph of the fuel mixture cable and bolt during the repair process. After the repairs were completed, the pilot conducted a local test flight. No problems were noted, and the pilot and passenger continued their flight. After an en route fuel stop, the airplane departed and reached 2,300 ft, at which point the engine lost power Although the engine remained at idle, it would not respond to the pilot's throttle inputs. The pilot subsequently conducted a forced landing to a field. Following the forced landing, the pilot re-entered the airplane to ensure that the electrical power and fuel were off and that there was no fire. He then removed the engine cowling and found the throttle linkage "disconnected or broken." A postcrash examination of the airplane, revealed that the bolt holding the throttle cable bracket was missing, which had allowed the throttle cable to "float," meaning that manipulating the throttle control from the cabin would not govern the engine's throttle position. The examination also revealed that the mixture control bolt was in place. However, the throttle cable bolt and associated safety wire were not found; a bolt that was later found in the engine compartment after the airplane was transported to a salvage yard could not be positively identified as the missing bolt. Thus, based on the available information, it could not be determined how the throttle cable became unsecured.

Probable cause

The partial loss of engine power due an unsecured throttle cable. The reason for the unsecured throttle cable could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA275
Event ID
20160721X10019
Case number
CEN16LA275
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-07-20.
  • API snapshot SHA-256: 130dbe73ad0f7ec2187e186bfe2a7bc7e1c97f75819bd384a7be746634bef2ac; retrieved 2026-09-16T03:40:48.624Z.