MIA94LA075 · Beech G18S
Beech G18S · Accident: loss of engine power en route
From an unrecorded airport to MYQF · Freeport
Event
- NTSB case
- MIA94LA075
- 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
Beech G18S
- Aircraft type
- Beechcraft 18
- 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
- N49K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo MYQF · Freeport
- 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
- Loss of engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Gear extension, premature
- Pilot in command › Planned approach, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated the left engine backfired and began to run rough shortly after takeoff. The engine was shut down and the propeller was feathered. He decided to return and land on the departure runway. Witnesses observed the aircraft on the downwind leg at 800 to 1,000 feet with the landing gear extended. As the aircraft turned to base leg it yawed sharply to the left and the left wing dropped. The aircraft descended rapidly. The pilot stated that as he turned from base to final leg at 75 to 100 feet the aircraft was buffeting and beginning to stall. He realized he would not make the runway and crash landed in a vacant lot. Examination of the left engine after the accident revealed no evidence to indicate precrash failure or malfunction of the engine.
Probable cause
THE PILOT-IN-COMMAND'S IMPROPER APPROACH PLANNING AND PREMATURE EXTENSION OF THE LANDING GEAR, RESULTING IN THE FLIGHT BEING UNABLE TO MAINTAIN SUFFICIENT ALTITUDE AND AIRSPEED TO REACH THE RUNWAY. THE LOSS OF ENGINE POWER ON ONE ENGINE WAS A FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94LA075
- Event ID
- 20001206X00804
- Case number
- MIA94LA075
- 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: 7206867fcc6a93b83f3424d65a7ab6a3eefe12684e5b19675b2ca822747f7591; retrieved 2026-09-21T22:42:54.100Z.