FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW03LA187 · Mikoyan MIG-15BIS

16 Jul 2003 · Little Rock, AR, United States

Mikoyan MIG-15BIS · Accident: loss of engine power during takeoff

From Bill & Hillary Clinton National Airport/Adams Field (LIT) to Monroe County Airport (BMG)

Report a problem

Event

NTSB case
FTW03LA187
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

Mikoyan MIG-15BIS

Aircraft type
Mikoyan MIG-15
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
N15PE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, ARTo Monroe County Airport (BMG), Bloomington, IN
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
Takeoff
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
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

  • Reason for occurrence undetermined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The vintage airplane overran the departure end of the runway during an aborted takeoff following a loss of engine power. The 12,450-hour pilot stated that right after rotation, while the airplane was about 10 feet off the runway, the airplane "shook" and the engine lost power. The aircraft subsequently settled back into the runway; however, the pilot was not able to stop the airplane in the 1,000 feet of runway remaining. A tower controller reported seeing a "puff of smoke" coming from the engine about the time the airplane became airborne. The airplane overran the departure end of the runway, impacted the perimeter fence, and came to rest in a field. The reason for the loss of engine power could not be determined.

Probable cause

The loss of engine power during takeoff for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW03LA187
Event ID
20030718X01142
Case number
FTW03LA187
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, coordinates. 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: fe61f12f49f999c6a93a9c7d5c531e6e7a9a9c9ab3e75fdd462f20125bcf4e75; retrieved 2026-09-22T09:00:17.695Z.