---
title: "Loss of MiG-29 in Poltava Region: Incident Details and Investigation Progress"
description: "A MiG-29 fighter jet of the Armed Forces of Ukraine was lost in the Poltava region amidst a massive drone strike. The pilot successfully ejected and was evacuated; his condition is stable. The command has launched an investigation into the causes of the incident, urging the public not to speculate until official conclusions are released. ✈️🚨"
date: 2026-06-27T11:31:07.000Z
lang: en
url: https://xab.info/en/posts/loss-of-mig-29-in-poltava-region-incident-details-and-investigation-progress
tags: []
publisher: "XAB.info"
---

# Loss of MiG-29 in Poltava Region: Incident Details and Investigation Progress

![MiG-29 fighter jet in flight, linked to the incident in Poltava region](https://xab.info/media/2026/06/27/poterya-mig-29-v-poltavskoy-oblasti-detali-incidenta/poterya-mig-29-v-poltavskoy-oblasti-detali-incidenta-1.webp)

On the night of June 27, 2026, an incident involving combat aviation of the Armed Forces of Ukraine occurred in the airspace of the Poltava region. The Air Force Command officially confirmed the loss of a MiG-29 fighter jet performing a combat mission. Despite the difficult situation, the pilot managed to successfully eject from the aircraft.

### Timeline of Events and Operational Situation

The incident unfolded against the backdrop of intense air defense operations. During this period, Ukrainian airspace was subjected to a large-scale attack: 129 unmanned aerial vehicles were recorded. According to official data, mobile fire groups, surface-to-air missile systems, and electronic warfare assets intercepted 113 targets. It was precisely under these conditions of intense aerial combat that contact with the frontline fighter was lost.

The MiG-29, a fourth-generation multirole fighter (classified as Fulcrum by NATO), was performing a scheduled mission to cover industrial facilities and regional infrastructure at the time of the incident. Following a loss of control or damage to the fuselage, the pilot ejected. Shortly after landing, he established contact with search and rescue services and was promptly evacuated.

### Pilot's Condition and Start of Investigation

Military authorities confirmed that the serviceman was transported to a specialized departmental medical facility. Doctors assess the pilot's condition as stable, with no immediate threat to life. The crash site has been cordoned off by authorized services to ensure safety and preserve evidence.

Specialized commissions of the Ministry of Defense and the General Staff have already commenced procedural actions. As part of the investigation, technical parameters of onboard systems are being studied, the wreckage is being inspected, and radar tracking data is being analyzed. The main task of the experts is to determine the exact cause of the incident: technical failure of the aircraft or the impact of external factors, including the use of enemy munitions.

### Procedural Status and Command Position

Currently, official comments from military justice bodies and the State Bureau of Investigation (SBI) regarding the opening of a criminal case have not been published. This corresponds to standard practice: preliminary conclusions from the engineering and aviation service are necessary to make a decision on the qualification of the incident. According to regulations, all objective control materials, including recordings from flight recorders ("black boxes"), must be transferred to military inspection authorities.

The military command urges media representatives and the public to refrain from publishing unofficial versions and subjective assessments until the final protocol of the state commission is published. Final conclusions regarding the causes of the fighter's loss will be made after the completion of the technical examination.