Jump to content

2024 Korochansky Ilyushin Il-76 crash

From Alfawiki
Russian Air Force
Company typeMilitary
IndustryMilitary aviation
Headquarters
Russia
ProductsMilitary transport aircraft operations


Template:Pp Template:Infobox aircraft occurrence, {"type":"Feature", "geometry":{"type":"Point", "coordinates":[37.341319, 50.893626]}, "properties":{"marker-symbol":"airport", "marker-size":"small", "marker-color":"000000"}}, {"type":"Feature", "properties":{"stroke":"#1889e6", "stroke-width":5}, "geometry":{"type":"LineString", "coordinates":[[36.589676, 50.643945], [37.341319, 50.893626]]}}]}</maplink> (based on eyewitness accounts) | occupants = 74 | passengers = 68 | crew = 6 | fatalities = 74 | survivors = 0 }} Template:Campaignbox Russian invasion of Ukraine On 24 January 2024 at approximately 11:15 MSK,[1] a military transport aircraft of the Russian Air Force, an Ilyushin Il-76, crashed within Russia's Korochansky District of Belgorod Oblast, close to the border with Ukraine, resulting in no survivors among those onboard. According to Russian authorities, the plane was downed by Ukrainian forces while transporting 65 Ukrainian prisoners of war captured during the ongoing conflict, along with six crew members and three security personnel. The prisoners were reportedly intended for a prisoner exchange.[2] The Ukrainian General Staff refrained from confirming responsibility for shooting down the plane but characterized it as a legitimate military target and asserted that it was carrying S-300 surface-to-air missile systems intended for use in bombing operations over Kharkiv Oblast.[3]

Officials from France and the United States indicated that the aircraft’s destruction was caused by a Patriot missile launched by Ukrainian military forces.[4]

Background

Main article: Treatment of prisoners of war in the Russian invasion of Ukraine

According to Ukraine's Coordination Headquarters on the Treatment of POWs, since the onset of Russia's 2022 invasion, over 8,000 Ukrainian military personnel and civilians have been detained by Russian forces, with tens of thousands still missing. Just days before the incident, on 3 January, Ukraine conducted its largest prisoner swap of the conflict, exchanging 248 POWs to Russia in return for 230 Ukrainian nationals, facilitated through mediation by the United Arab Emirates.[5]

The crash took place in Belgorod Oblast, a region that has experienced spillover violence and cross-border clashes with Ukraine,[6] including an airstrike on Belgorod city on 30 December 2023 that resulted in 25 fatalities and over 100 injuries.[5]

Aircraft and crew

The Ilyushin Il-76 is a versatile aircraft commonly used in military operations to transport troops, equipment, and ammunition. Russian authorities reported that among those on board were 65 Ukrainian prisoners of war, alongside six Russian crew members and three security personnel.[7][8] The Russian Ministry of Defence described the crash as occurring during a "routine flight." The group of 65 Ukrainian soldiers was reportedly being moved to Belgorod Oblast for a prisoner exchange[9] near the Kolotilovka border checkpoint,[6] approximately 100 kilometers west of Belgorod city. The flight was said to have originated from Chkalovsky Air Base near Moscow.[10]

The Il-76 and its crew were part of the 117th Military Transport Aviation Regiment (military base No. 45097), tasked with operating military transport vehicles carrying special cargo to support Russian armed forces. This regiment's aircraft are stationed at Orenburg airfield.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

Russian media outlets confirmed a six-member crew,Cite error: The opening <ref> tag is malformed or has a bad name consisting of Captain Stanislav Alekseevich Bezzubkin (35),Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name co-pilot Vladislav Vadimovich Chmirev (24),Cite error: The opening <ref> tag is malformed or has a bad name navigator Alexey Anatolyevich Vysokin (31), flight engineer Andrey Leonidovich Piluev (38),Cite error: The opening <ref> tag is malformed or has a bad name technician Sergey Nikolaevich Zhitenev (34), and radio operator Igor Vyacheslavovich Sablinsky (54).

Crash

Template:External media]}</maplink>, camera oriented north-northwest)}} The incident took place in a field approximately 5–6 km (3.1–3.7 mi) from Yablonovo in Belgorod Oblast, as stated by the local parish priest. Former Commander of the Russian Aerospace Forces, Viktor Bondarev, indicated that the crew reported an external strike prior to the crash.[11] Analysis of social media videos by the Moscow Times suggests the military aircraft was moving away from the Ukrainian border at the time it went down.[12]

At 10:35 MSK, Vyacheslav Gladkov, governor of Belgorod Oblast, announced that the region’s air defense system had intercepted and destroyed a fixed-wing UAV over the village of Blizhne [ru], located 75 km (47 mi) southwest of Yablonovo.Cite error: The opening <ref> tag is malformed or has a bad name Later, at 11:12 MSK, he issued a "missile alert" for the area and advised citizens to seek shelter.Cite error: The opening <ref> tag is malformed or has a bad name[6] By 11:43 MSK, he confirmed that the alert had been lifted.Cite error: The opening <ref> tag is malformed or has a bad name Initial media coverage regarding the crash surfaced at 11:48.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

Russian perspective

The Russian foreign ministry held Ukraine responsible for the aircraft's downing, condemning the act as "barbaric"[13] and asserting that the plane was struck by one of three missiles—either a Patriot or an IRIS-T—fired by Ukrainian forces.[14] Foreign Minister Sergei Lavrov described the event as a "criminal" action by Ukraine and called for an immediate meeting of the United Nations Security Council to demand Ukraine provide an explanation;[15] the session was scheduled for the afternoon of 25 January, New York time,[16] where representatives from both Russia and Ukraine reiterated their stances, each accusing the other of responsibility.[17]

The Russian Defence Ministry reported that two missiles launched from the Lyptsi region, located approximately 100 km (62 mi) inside Ukrainian territory in Kharkiv Oblast, were responsible for shooting down the aircraft, based on data from its radar systems.[10][6] According to Andrei Kartapolov, chairman of Russia's State Duma defence committee, a second aircraft en route to transfer 80 Ukrainian prisoners of war aborted its mission after the incident,[12] adding that "any further prisoner exchanges are now impossible".[10] Kartapolov also claimed that Russia had issued a warning to Ukraine about this aircraft’s flight at least fifteen minutes prior to the event, a statement refuted by Ukrainian officials.[18] The State Duma speaker, Vyacheslav Volodin, announced plans to send formal communications to both the US Congress and Germany’s Bundestag, urging them to acknowledge their "responsibility" for the incident.[12]

Presidential press secretary Dmitry Peskov condemned the event as "a monstrous act" committed by the "Kyiv regime".[5] President Vladimir Putin stated it was "clear" that Ukraine was behind the attack on the plane and claimed Kyiv had prior knowledge regarding the prisoner transport arrangements aboard the aircraft.[19] He further promised to disclose findings from Russia’s investigation "so that Ukrainians understand what truly occurred."[20] Later, Putin identified a Patriot missile system as responsible for downing the plane.[21] On 25 January, Russia’s Investigative Committee of Russia launched a terrorism probe into the crash,[22] releasing footage from the site showing bloodstains and human remains,[23] including an image of a tattoo featuring a tryzub.[24] Subsequently, Russia released a low-quality video allegedly depicting prisoners being loaded onto the plane.[25]

On 30 January, TASS, citing an unnamed security service source, reported that analysis of black box data indicated the crash was caused by an "external impact".[26]

Ukraine's Position

The Ukrainian news outlet Ukrainska Pravda initially reported that sources within the Ukrainian General Staff claimed the downed aircraft was transporting S-300 missiles and that Ukraine had been responsible for shooting it down. However, this report was subsequently revised to clarify that these sources did not explicitly attribute the incident to Ukrainian forces. The Coordination Headquarters for the Treatment of Prisoners of War, Ukraine’s official body overseeing POW matters, accused Russia of conducting "active special information operations" aimed at destabilizing Ukrainian society. Additionally, the independent Russian media platform iStories, referencing Ukrainian open-source intelligence (OSINT) findings, noted that the plane's route included flights over Egypt, Saudi Arabia, the Red Sea, and Iran before it vanished from radar and later reappeared above Belgorod Oblast.

A representative from Ukraine’s Main Directorate of Intelligence (HUR) confirmed that a prisoner exchange with Russia had been planned for the day the crash occurred but ultimately did not take place. The agency further stated that, unlike prior arrangements, Russian counterparts had not informed Ukraine about securing airspace safety on that day and had already moved Russian POWs intended for exchange to the meeting point. HUR suggested this event might have been a "deliberate" act by Russia designed to endanger the lives and security of the prisoners.

On 25 January, HUR disclosed intelligence indicating that several high-ranking Russian military and political figures were expected to be on the flight but were instructed by the Federal Security Service (FSB) to use alternative transportation methods. It also reported that both the FSB and Russian military obstructed emergency personnel from accessing the crash site. Video evidence showed at least five bodies recovered and transported to a morgue in Belgorod, with no additional human remains found at the location. HUR speculated that friendly fire could have brought down the plane amid Russian air defense efforts targeting a drone. Addressing claims by Russia regarding Ukrainian POWs onboard, HUR posited that Russia might have been exploiting Ukrainian prisoners as human shields while transporting arms and ammunition.

In his evening address, President Volodymyr Zelenskyy remarked that it was clear Russia was "playing with the lives of Ukrainian prisoners, with their families’ emotions, and with public sentiment," though he did not confirm whether POWs were aboard the aircraft, stating that HUR was still investigating. Zelenskyy noted that the Security Service of Ukraine was also probing the incident and instructed Foreign Minister Dmytro Kuleba to brief international partners on Ukraine’s findings during the inquiry. He emphasized Ukraine’s demand for an international investigation to establish what transpired. Similarly, Ukrainian human rights ombudsman Dmytro Lubinets announced plans to appeal to the United Nations and International Committee of the Red Cross to advocate for an impartial investigation into the crash.

International Perspectives

On the evening of 24 January, the BBC reported that following an eight-hour period without official updates, two statements issued by the Ukrainian General Staff and the HUR effectively indicated that Ukraine might have been responsible for downing the aircraft. Western military experts speaking to BBC News Russian also analyzed crash footage, concluding that the plane appeared to have been shot down.[27] Cite error: The opening <ref> tag is malformed or has a bad name

According to a French military source cited by France Info (radio network), the aircraft was struck by a Patriot missile system of US origin, which was operated by Ukrainian forces.[28]

On 8 February, The New York Times conveyed information from anonymous US officials suggesting that the Il-76 was brought down by a Ukrainian-operated MIM-104 Patriot missile. These officials also described the reports of Ukrainian prisoners of war on board as "probable".[29]

Victim Identification

The initial remains were discovered approximately 1.5 to 2 kilometers from where the crash occurred.[11] Russia Today editor-in-chief Margarita Simonyan released a roster listing 65 individuals she asserted were Ukrainian POWs aboard the flight.[12] Ukraine's public broadcaster, Suspilne, verified that the names corresponded to Ukrainian prisoners held in Russia but stated it could not confirm their presence on the plane or involvement in any prisoner exchange.Cite error: The opening <ref> tag is malformed or has a bad name The Ukrainian authorities subsequently acknowledged that Simonyan’s list matched those slated for release in a prisoner swap on 24 January but emphasized uncertainty regarding whether these POWs were actually on the aircraft.Cite error: The opening <ref> tag is malformed or has a bad name

On 25 January, Ombudsman Lubinets noted that photographic and video evidence from the crash site showed no indication of such a large number of passengers aboard the Il-76.Cite error: The opening <ref> tag is malformed or has a bad name He further pointed out that some individuals named in Simonyan’s list had already been freed in earlier exchanges.Cite error: The opening <ref> tag is malformed or has a bad name After consultations between Ukrainian security representatives and families of POWs listed by Simonyan, the HUR reported that relatives could not identify any prisoners in Russian-released crash footage.Cite error: The opening <ref> tag is malformed or has a bad name Ukrainian officials stated they only received Russia’s list of supposed passengers on 26 January[30] and requested repatriation of deceased bodies but had yet to obtain a response from Russian authorities.Cite error: The opening <ref> tag is malformed or has a bad name On 9 February, Oleksii Danilov, Secretary of Ukraine's National Security and Defense Council, reiterated in an interview with Babel that no Ukrainian POWs were aboard, citing an absence of significant biological evidence at the site.Cite error: The opening <ref> tag is malformed or has a bad name

Among those named on Simonyan’s list was Maxim Anatolievich Konovalenko, who had been released back to Ukraine during a prisoner exchange on 3 January 2024.[31][32][33]

In February 2025, a representative from Ukraine's Coordination Headquarters for the Treatment of Prisoners of War revealed in an interview that most recovered remains matched DNA samples from relatives of POWs. However, it remained unconfirmed whether these remains originated from individuals aboard the crashed aircraft.Cite error: The opening <ref> tag is malformed or has a bad name By April 2025, Leonid Tymchenko, Deputy Minister of Internal Affairs of Ukraine, stated in an interview that DNA experts were examining approximately 500 remains provided by Russia to establish profiles aimed at identifying around 60 deceased Ukrainian POWs from the shootdown incident.Cite error: The opening <ref> tag is malformed or has a bad name

Aftermath

Vyacheslav Gladkov, the governor of Belgorod Oblast, announced via Telegram that "an investigation team and emergency responders" had been dispatched to the site of the crash, mentioning that he had personally "traveled to the district." He confirmed that there were no survivors from the incident. Additionally, the Russian Aerospace Forces sent their own investigative unit to examine the crash. On 25 January, the flight data recorders were retrieved from the wreckage, with TASS reporting that these devices would be forwarded to a Russian defense ministry laboratory for detailed examination.

Following the crash, Ukraine briefly issued a nationwide air raid alert lasting from 11:41 to 13:58 EET. President Zelenskyy postponed a planned trip on 25 January in response to the event. The Ukrainian military declared its intention to persist in targeting Russian aircraft within Belgorod Oblast.

On 26 January, a prearranged exchange of deceased soldiers took place between Russia and Ukraine as planned. This operation resulted in 55 Russian bodies being returned home in exchange for 77 Ukrainian fatalities. United Nations undersecretary-general Rosemary DiCarlo called on all parties involved to avoid actions, inflammatory language, or accusations that might exacerbate the already volatile conflict. Meanwhile, a representative from the International Committee of the Red Cross in Ukraine urged Russia to return the remains of any POWs who may have perished in the crash.

On 28 January, Russian hackers launched a cyberattack targeting the Coordination Headquarters for the Treatment of Prisoners of War, disrupting its information systems. The agency attributed this cyberattack to repercussions related to the plane crash.

A prisoner swap between Russia and Ukraine occurred on 31 January, facilitated by the United Arab Emirates. This exchange saw 195 Russian and 207 Ukrainian detainees repatriated. Notably, none of those listed by Russia as passengers on the downed aircraft were included in this swap.

On 29 February, Tatyana Moskalkova, Russia's presidential commissioner for human rights, stated that Russia was prepared to return the remains of POWs who died in the crash. In response, Ukraine’s human rights ombudsman Dmytro Lubinets accused Moskalkova of speculation regarding the incident and highlighted that Russia had neither released an official passenger manifest nor granted international organizations access to inspect the crash site.

On 8 November, Russia returned the bodies of 563 Ukrainian servicemen in exchange for 37 Russian remains. According to Russian news outlet Mash and the Zaporizhzhia-based collaborationist group We Are Together with Russia, among those repatriated were 62 POWs who had died in the crash.

Subsequently, on 9 December, Tatyana Moskalkova announced that the remains of POWs killed in the crash had been handed over to Ukraine following an exchange but did not provide additional details.

See also

References

  1. ↑ ...
  2. ↑ ...
  3. ↑ ...
  4. ↑ ...
  5. ↑ 5.0 5.1 5.2 Cite error: Invalid <ref> tag; no text was provided for refs named bbc25
  6. ↑ 6.0 6.1 6.2 6.3 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  7. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ru1
  8. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named aj1
  9. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named cna1
  10. ↑ 10.0 10.1 10.2 Cite error: Invalid <ref> tag; no text was provided for refs named BBC2
  11. ↑ 11.0 11.1 Cite error: Invalid <ref> tag; no text was provided for refs named meduza
  12. ↑ 12.0 12.1 12.2 12.3 Cite error: Invalid <ref> tag; no text was provided for refs named moscow
  13. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named BBC_2024-01-24
  14. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  15. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  16. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  17. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  18. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  19. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  20. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  21. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  22. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  23. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  24. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  25. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  26. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  27. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named bbc-20240124
  28. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named french
  29. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named nyt
  30. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named noevidence
  31. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ukrainskapravda
  32. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named wartears
  33. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named novynarnia

Template:Aviation accidents and incidents in 2024 Template:Aviation accidents and incidents in Russia in the 2020s Template:Russian invasion of Ukraine

Retrieved from "https://www.alfawiki.org/index.php?title=2024_Korochansky_Ilyushin_Il-76_crash&oldid=75009"