MIA89IA118 · Cessna P206B
Cessna P206B · Incident: airframe, component or system failure en route
From an unrecorded airport to Lynden Pindling International Airport (MYNN)
Event
- NTSB case
- MIA89IA118
- 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
- Incident
- 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
- 0
- 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
Cessna P206B
- Aircraft type
- Cessna 206
- 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
- N4740F
- Operator
- Williams, Lindy C. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Lynden Pindling International Airport (MYNN), Nassau
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Fuel injection control, linkage › Failure, total
- Fuel injection control, linkage › Worn
- Other maintenance personnel › Maintenance, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TAKEOFF WHILE CLIMBING TO CRUISE, THE PLT PULLED THE THROTTLE TO REDUCE POWER, BUT WAS UNABLE. HE THEN ADVISED ATC & REQUESTED LANDING ON THE LONGEST RWY. ATC VECTORED THE ACFT TO THE WEST & WHEN IT WAS 3 MILES FROM THE RWY, THE ENG RPM DROPPED TO IDLE. THE PLT LANDED THE ACFT IN A FIELD. AN INVESTIGATION REVEALED THE THROTTLE CONTROL ARM AT THE FUEL CONTROLLER FAILED. VIBRATION THEN CAUSED THE THROTTLE TO VIBRATE TO IDLE. REPORTEDLY, IT WAS WORN & HAD FAILED DUE TO POOR MAINTENANCE.
Probable cause
FAILURE OF THE THROTTLE CONTROL ARM RESULTING IN THE LOSS OF ENGINE POWER. THE FAILURE WAS CAUSED BY POOR MAINTENANCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA89IA118
- Event ID
- 20001213X27941
- Case number
- MIA89IA118
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: bf3c011422dd4cbba5b7a87df30443cab6869d2bfc6d52fb3d96bb51bcdb7cde; retrieved 2026-09-23T07:46:01.178Z.