FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90LA030 · Cessna 177RG

21 Nov 1989 · Mims, FL, United States

Grady Francis Cessna 177RG · Accident: partial loss of engine power (mechanical failure) on approach

From Orlando Sanford International Airport (SFB) to an unrecorded destination

Report a problem

Event

NTSB case
MIA90LA030
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
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 177RG

Aircraft type
Cessna 177
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
N7628V
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (SFB), Sanford, FLTo not recorded
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
Approach · VFR go-around
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
Partial loss of engine power (mechanical failure)
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

  • Throttle/power lever › Failure, total
  • Throttle/power lever › Worn

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

NTSB narrative

WHILE ON A COMMERCIAL PLT CHECK FLT, THE APPLICANT WAS GIVEN A SIMULATED ENG FAILURE. HE SELECTED A DIRT ROAD FOR A SIMULATED FORCED LANDING. AT AN ALT OF ABOUT 500 FT, AFTER THE EXAMINER WAS ASSURED THE APPLICANT COULD HAVE LANDED, THE APPLICANT WAS TOLD TO GO AROUND. THE APPLICANT APPLIED THROTTLE, BUT THE ENG DID NOT RESPOND. WHILE ATTEMPTING TO CORRECT THE PROBLEM, THE ACFT OVERFLEW MOST OF THE ROAD. UNABLE TO LAND ON THE ROAD, THE PLTS SELECTED A FIELD OF SAPLINGS & THE ACFT WAS DAMAGED DURING AN EMERGENCY LANDING. AN EXAM OF THE ENG REVEALED THE THROTTLE CONTROL ASSEMBLY WAS WORN & HAD FAILED, WHICH ALLOWED THE INNER CABLE TO EXIT ITS HOUSING.

Probable cause

A WORN THROTTLE CONTROL ASSEMBLY THAT HAD FAILED.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90LA030
Event ID
20001213X29843
Case number
MIA90LA030
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. 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: 31edb605600a07ee1972746676989c95bdcc2ebec2175c7f10987e246f9e6a9f; retrieved 2026-09-23T06:58:09.106Z.