FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA361 · Mikoyan Gurevich MIG-23UB

13 Aug 2023 · Belleville, MI, United States

Mikoyan Gurevich MIG-23UB · Accident while maneuvering

From Willow Run Airport (YIP) to an unrecorded destination

Report a problem

Event

NTSB case
CEN23FA361
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
Event fatalities
Unknown
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 Gurevich MIG-23UB

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
N23UB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willow Run Airport (YIP), Belleville, MITo not recorded
Aircraft age
About 42 years (built 1981)
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
Maneuvering · low-altitude flying
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
Unknown or undetermined
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

  • Aircraft › Aircraft power plant

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

NTSB narrative

Both the front-seat pilot-in-command (PIC) and the rear-seat pilot-rated observer (PRO) of the Russian-manufactured fighter jet reported that the airplane’s engine did not respond to application of afterburner power during a display pass at an air show. According to the PIC, the engine was operating in a degraded power condition that was insufficient to sustain altitude and airspeed. The PIC maneuvered the airplane back toward the airport while he attempted to restore engine power. The PIC believed that his corrective measures would have restored engine power; however, the PRO activated the crew ejection system before engine power was restored. The PRO reported that he inquired about ejection with the PIC but did not hear a response before he activated the ejection system; however, the PIC reported that he replied “no” in response to the PRO’s ejection inquiry and that he was ejected from the airplane while he was troubleshooting the loss of engine power and still flying the airplane. Although the PIC was completing corrective actions, engine power was not restored by the time of the crew ejection and, therefore, the investigation was unable to determine if his corrective efforts would have been successful. According to the PRO, the ejection system was activated about 350 ft above ground level (agl) and below 200 kts. Both pilots were ejected from the airplane, with the PRO ejected first, followed by the PIC. The airplane continued in a left bank and descended into the ground about 1.7 miles from the runway. The airplane impacted the ground adjacent an apartment building and was destroyed by impact forces and a post impact fire. Other than the PIC’s mechanic, the NTSB was unaware of any independent engine shop or manufacturer within the United States with the appropriate tooling and expertise to perform a teardown examination of the Tumansky R27F2M-300 engine. The PIC’s written statement addressed potential sources for degraded engine performance; however, the NTSB could not validate the PIC’s opinion of the reason for the loss of engine power. Based on photographic evidence, the engine was producing some power at impact; however, the level of power output could not be determined. Due to investigative support limitations and the extend of damage, the investigators were unable to determine the reason for the loss of engine power. The airplane flight manual indicated that during a descent, the minimum safe altitude for crew ejection is calculated based on the airplane’s rate of descent and is equal to the rate of descent multiplied by 5. Based on the 350 ft agl altitude at ejection provided by the PRO, this altitude would be appropriate for ejection at a maximum rate of descent of 70 feet per minute (fpm). Although the airplane’s actual rate of descent was not known, it was likely significantly higher than the 70 fpm limitation at the time of crew ejection. Additionally, video evidence showed that the ejection seat parachutes did not fully deploy until the occupants had descended to just above treetop level. Therefore, the timing of the crew ejection was not premature. Given the serious injuries received by both occupants, crew ejection at a higher altitude may have reduced the severity of their injuries. Likewise, had the crew ejection been further delayed, the occupant injuries may have been more severe.

Probable cause

A reported partial loss of engine power while maneuvering for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA361
Event ID
20230814192855
Case number
CEN23FA361
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: investigation status, coordinates, cause areas. 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: 6986a61f198a34704d40de6e779536e9ad03325c78d9fb0c2e59db34d0a4bb80; retrieved 2026-09-16T17:59:31.789Z.