Part One: The Operation

By Chris Sampson

The Trade Unions Building still stands on Kulikovo Pole, its fire-scarred facade a monument to the day Russian hybrid warfare met organized resistance. What happened in Odesa on May 2, 2014 wasn’t the beginning of organic separatism, as Kremlin propagandists would have you believe. It was the endpoint of a failed operation—the moment when a carefully orchestrated plan to destabilize Ukraine’s strategic south collapsed into chaos, violence, and ultimately, tragedy.

The Glazyev Tapes—intercepted telephone conversations from late February and early March 2014—provide a rare window into how the Kremlin coordinates hybrid warfare operations across multiple Ukrainian regions simultaneously. These conversations, involving Sergey Glazyev (a senior adviser to Vladimir Putin) and various operatives in Ukraine’s south and east, reveal the command-and-control architecture that was being established even before Crimea’s annexation was complete.

This is the story of how that architecture was supposed to work, why it failed in Odesa, and what the failure cost.

Part One: The Architecture of Destabilization

The Glazyev Tapes: Command and Control

Between February 22 and March 15, 2014, someone—Ukrainian security services have never fully explained who or how—intercepted a series of telephone conversations between Kremlin operatives and their contacts across southern and eastern Ukraine. The conversations reveal Sergey Glazyev, adviser to Vladimir Putin, personally coordinating what he explicitly calls “the revolution in Ukraine” and “our project.”

The most revealing intercept captures Glazyev speaking with Dmitry Rogozin’s assistant on February 22, 2014—the very day Viktor Yanukovych fled Kyiv:

“We need to move from a conservative position to a revolutionary one. We have a revolution in Ukraine... But in order to maintain the revolution, we need revolutionary bodies of power. The first task is to form revolutionary committees—of people’s militias, self-defense forces, people’s councils. All power should shift to them.”

This wasn’t idle theorizing. Glazyev was laying out an operational framework: create parallel power structures, claim popular legitimacy, establish facts on the ground. The “revolutionary committees” language was carefully chosen—echoing Bolshevik precedent while providing legal cover for armed militants.

The pattern repeats across multiple conversations. Glazyev speaks with Oleksandr Klinchaev about the situation in Kharkiv. He coordinates with contacts in Odesa. He discusses “sending people” and “providing support” with the casual authority of a man managing a regional operation from Moscow.

One exchange on March 2, 2014 is particularly revealing. Glazyev speaks with Kirill Frolov, head of a Moscow-based “Center for Political Studies,” about the situation in Kharkiv:

Glazyev: “Did you send them the money?”

Frolov: “I gave 120,000 rubles in cash to the individual.”

Glazyev: “And to whom did you send the money in Kharkiv?”

Frolov: “We transferred $20,000 through Kostya to the head of the organization.”

This is how hybrid warfare operations are financed: cash transfers, cut-outs, plausible deniability. The amounts are modest—$20,000 here, $25,000 there—but sufficient to pay “protesters,” rent office space, buy equipment. Glazyev doesn’t manage the operation directly; he coordinates funding and provides strategic direction while local operatives handle implementation.

The conversations also reveal Russian awareness of Ukrainian security service capabilities. In a March 15 call, Glazyev warns an operative: “You need to use more sophisticated phones. You’re working with ordinary phones that are completely penetrated by the SBU [Ukrainian security service].” The irony is that this warning came too late—the SBU had already captured the entire architecture of the operation on tape.

Odesa: Why It Mattered

Odesa wasn’t just another regional center. With its deep-water port, proximity to Transnistria, and ethnic complexity, the city represented a strategic prize. Control of Odesa would give Russia:

A land bridge to Transnistria, isolating Moldova
Ukraine’s largest port and commercial hub
Effective control over Ukraine’s entire southern coast
A stranglehold on Ukraine’s maritime trade

More importantly, Odesa represented a psychological threshold. If a cosmopolitan, historically liberal city with a slight ethnic Russian majority could be turned into a “people’s republic,” then the Kremlin’s narrative of defending Russian-speakers would gain credibility. Odesa was supposed to prove that the Donbas wasn’t an anomaly but the leading edge of a broader popular uprising.

The Glazyev Tapes confirm Odesa’s importance. In a March 2, 2014 conversation, Glazyev discusses the city’s situation with evident concern. The conversation suggests coordination between Odesa operatives and those in other regions, a network approach where lessons learned in Kharkiv or Donetsk could be applied in Odesa.

But Odesa presented challenges that Donetsk and Luhansk didn’t. The city’s demographics were mixed and fluid. Its business elite—while Russian-speaking—were pragmatically oriented toward European markets. Its civic identity was historically distinct, proudly cosmopolitan rather than Soviet industrial. And crucially, it lacked the concentrated, economically desperate industrial workforce that made Donbas vulnerable to mobilization.

The February-April 2014 Timeline: Building the Architecture

The operation to destabilize Odesa followed a clear progression, visible in both the intercepted communications and events on the ground:

Phase One: Establishing Presence (Late February - Early March)

Following Yanukovych’s flight on February 22, pro-Russian activists in Odesa moved quickly to establish a visible presence. On March 1, several hundred protesters gathered at the Odesa Regional State Administration building, demanding a referendum on federalization and closer ties with Russia. This wasn’t spontaneous—the Glazyev Tapes show coordination and funding were already flowing.

The key moment came on March 3, when protesters stormed the Regional State Administration during a session of the Odesa Regional Council. They raised a Russian flag and demanded the Council adopt a declaration supporting federalization. The Regional Council, in a carefully worded resolution, deplored “extremism” and attempts to breach Ukraine’s territorial integrity while calling for dialogue and compromise—threading the needle between competing pressures.

What’s significant is what didn’t happen: local elites didn’t commit. The Regional Council’s resolution was diplomatic boilerplate, not a declaration of independence. Odesa’s mayor, Gennadiy Trukhanov, remained conspicuously neutral. The business community stayed silent. This elite non-commitment would prove fatal to the operation.

Phase Two: Escalation and Coercion (March - April)

Through March and into April, pro-Russian activists established a protest camp on Kulikovo Pole, a square near Odesa’s main railway station. The camp—modeled after Euromaidan but with opposite political objectives—became a focal point for demonstrations, a base for militant groups, and a symbol of the “Russian Spring” in Odesa.

The camp’s existence revealed both the operation’s resources and its limitations. Activists had money for tents, sound equipment, and provisions. They could mobilize hundreds of protesters for key events. But they couldn’t mobilize thousands. And they couldn’t translate presence into power.

On March 17, Ukrainian security services arrested Anton Davydchenko, described as a leader of Odesa’s “AntiMaidan” movement. He was charged with actions against Ukraine’s territorial integrity based on his public statements and his role in the March 3 storming of the Regional Administration. The arrest showed Ukrainian authorities were beginning to push back, though the fact that Davydchenko was released on probation just four months later—despite pleading guilty—suggests ambivalence about full confrontation.

The pattern through March and April was escalation without breakthrough. Pro-Russian activists became more aggressive, staging increasingly confrontational demonstrations. But they couldn’t force local authorities to choose sides. They couldn’t trigger the police defections that had enabled separatist takeovers in Donbas. And they couldn’t generate genuine mass mobilization beyond their core activist base.

By late April, the operation was stalling. The Kulikovo Pole camp remained, but it was becoming a symbol of isolation rather than strength. Ukrainian counter-protesters, rallying under “Unity of Ukraine” slogans, were growing more organized and more numerous. Something would need to change to break the deadlock.

Phase Three: The Provocation (Late April - May 1)

In the final days of April, the operation’s architects attempted to force a crisis. The plan appears to have been to create a confrontation that would justify more direct intervention—either by Russia openly or by “volunteers” from Crimea and Transnistria.

On April 30, Dmytro Fuchedzhy, Deputy Head of Odesa’s regional police and head of the regional public order police, gave a briefing announcing that over 2,100 police officers would be deployed for the May holidays, including 700 for a football match scheduled for May 2. “The police in Odesa are ready to keep public order protected during the holidays,” he assured the public. “We will do our best to make people feel safe.”

This statement would later be examined for evidence of either incompetence or something more deliberate. The number of police deployed—while superficially impressive—was distributed across the entire city, with the majority concentrated at the football stadium far from where confrontation was likely. The actual deployment pattern suggested either catastrophic misjudgment or careful positioning to ensure police would not be able to respond effectively when violence erupted.

On May 1, the day before the football match, Security Service of Ukraine (SBU) officials held meetings with regional authorities warning of potential violence. These warnings were specific enough that they should have triggered contingency planning. They didn’t.

The stage was set. Pro-Russian activists were concentrated at Kulikovo Pole. Ukrainian unity supporters were planning a march through the city center before the football match. Football fans from Kharkiv—many with Euromaidan sympathies—were arriving for the game. Police were deployed in a pattern that minimized their ability to prevent or contain violence. And someone was planning to ensure that prevention and containment would fail.

The Weapon: Police Complicity and the “Wave” Plan

Understanding what happened on May 2, 2014 requires understanding what didn’t happen: a systematic police response to mass violence unfolding in broad daylight. The Odesa police weren’t simply overwhelmed by unexpected chaos. They were, by design or dysfunction, absent from the very places where their presence was most needed.

The “Wave” Plan That Wasn’t

Ukrainian law enforcement had a specific contingency plan for mass disorder: the “Wave” (Khvylia) plan. When implemented, it would:

Deploy additional personnel and equipment to areas of unrest
Establish clear command and control procedures
Coordinate between different law enforcement agencies
Authorize the use of force to suppress violence

The “Wave” plan wasn’t implemented on May 2, 2014. This wasn’t discovered weeks later during investigation. It was immediately visible to anyone watching: police formed human cordons between pro-Russian and Ukrainian unity activists but did almost nothing to arrest those committing violence. Officers stood passively while armed men fired into crowds. They watched as buildings were stormed and set ablaze.

What makes this absence of action more striking is that authorities knew confrontation was coming. On April 30, the local SBU office had sent a letter to Petro Lutsiuk, head of Odesa regional police, warning that “the possibility of incitements to violence, clashes and disorder taking place during the demonstrations by football fans and their opponents scheduled for 2 May 2014” was “not excluded.” The letter specifically noted that 500 football fans were arriving in Odesa for the match, that many planned to participate in a pro-unity rally, and that “the experience of similar demonstrations in other parts of Ukraine” suggested risk of “disorderly conduct.”

On April 29, a meeting had been held in Odesa chaired by Andriy Parubiy, then Secretary of Ukraine’s National Security and Defence Council. Attending were heads of local SBU, Ministry of Internal Affairs, State Emergency Service, and Ministry of Defence offices. The purpose was to discuss “challenges and threats to national security” and coordinate responses. Yet no special measures appear to have resulted from this high-level coordination session.

The standard police contingency plan for the May 2 football match called for 827 officers to be deployed. Of these, approximately 700 were positioned at the stadium itself, another 100 accompanied the pro-unity march, and only a few dozen were stationed at Kulikovo Pole where the pro-Russian camp was located. When violence erupted in the city center around 3:20 PM, police were physically unable to respond in force. They had been deployed, whether through incompetence or design, to ensure they would be out of position.

The Council of Europe’s International Advisory Panel would later investigate this deployment pattern and the failure to implement the “Wave” plan. Their conclusion was damning: the police leadership “failed properly to take into consideration information from the SSU about possible clashes and incitements to violence and to deploy the available forces appropriately.” Instead of activating contingency plans for mass disorder, authorities had implemented “a standard contingency plan used for dealing with confrontations between rival football fans.”

But the Panel’s investigation revealed something more disturbing than mere incompetence. When investigators finally examined the documentation of the “Wave” plan’s supposed implementation, they discovered the documents had been forged. On the night of May 2-3, Petro Lutsiuk, head of Odesa’s regional police, had ordered subordinates to create a false paper trail showing the “Wave” plan had been activated at 3:30 PM on May 2. The plan had never been implemented. The documentation was fabricated after the fact to cover up its absence.

The International Advisory Panel later documented that Ukraine’s Ombudsperson had submitted detailed findings to the Prosecutor General’s Office as early as June 10, 2014, conclusively demonstrating that the “Wave” plan had never been implemented and that documents had been forged to create a false paper trail. Nearly a year would pass before prosecutors acted on this evidence—a delay the Panel found “striking” and indicative of authorities’ failure to “follow an obvious line of inquiry.”

This wasn’t passive negligence. This was active falsification of records to conceal the police leadership’s failure to respond to mass violence. And it raised an unavoidable question: was the failure to implement the “Wave” plan simply catastrophic incompetence, or was it deliberate? Were police positioned to be unable to respond, or positioned to allow violence to unfold?

Red Armbands and Selective Blindness

The evidence of police complicity goes beyond suspicious deployment patterns and forged documents. Video footage from May 2 shows police behavior that cannot be explained by confusion, fear, or being overwhelmed.

In multiple videos, pro-Russian militants are visible firing weapons from behind police lines. In several shots, police officers are standing within meters of armed men who are shooting at Ukrainian unity activists, yet the officers make no attempt to disarm or arrest them. The shooters aren’t concealing their actions—they’re operating openly, apparently confident they won’t be detained.

One particularly damning video shows Vitaliy Budko, later identified as a key pro-Russian militant, firing a pistol from directly behind a police cordon. Officers are visible in the same frame. None move to stop him. Budko wasn’t arrested that day. He disappeared shortly after and remains on a wanted list to this day—but only because he fled before authorities got around to seeking him.

Later the same day, video shows Dmytro Fuchedzhy—the same police commander who had assured the public that Odesa police were “ready to keep public order protected”—climbing into an ambulance where Budko is also present. Fuchedzhy appears to have suffered a minor arm wound. A gravely injured police officer, supported by two colleagues, approaches the ambulance seeking medical help. He’s turned away. The ambulance drives off with Fuchedzhy and Budko inside.

The significance of this footage extends beyond one corrupt or compromised officer. It shows a police command structure that had, at minimum, broken down completely, and at worst, actively cooperated with one side in what was becoming a battle in the streets of a major city.

Then there are the red armbands. Video and photographs from May 2 show something peculiar: both pro-Russian activists and police officers wearing red tape around their arms. For activists, this was tactical identification—a way to distinguish friend from foe in the chaos of street fighting. But why were police officers wearing the same markings?

The official explanation, when it finally came, was innocuous: police had used red tape to secure protective equipment that was in poor condition after being damaged in Kyiv during the Maidan protests. The tape was simply what was available. Some officers wore it on the left arm, some on the right, some on both arms—the inconsistency supposedly proving it was improvised equipment repair, not coordinated signaling.

The Temporary Investigation Commission of the Verkhovna Rada (Ukraine’s parliament) accepted this explanation. So did investigators from the Council of Europe’s International Advisory Panel, who noted that the 2 May Group—a collection of Odesa journalists and experts who conducted a parallel investigation—supported the equipment repair theory.

But the explanation, while plausible, sits uneasily beside the other evidence of police behavior that day. Even if the red tape was initially used for equipment repair, its visual effect was to blur the distinction between police and pro-Russian militants. And in a situation where police were already failing to arrest armed pro-Russian fighters operating in plain sight, the shared visual marker reinforced the appearance—or reality—of coordination.

The Emergency Call Log

The clearest evidence that police response was deliberately suppressed comes from the emergency call records. Between 2:09 PM and 5:22 PM on May 2, Odesa emergency services received approximately 15 calls reporting violence, weapons being fired, and people being wounded or killed. The calls came from witnesses throughout the city center as violence escalated from stone-throwing to gunfire.

Police response was not proportionate to the threat reported. It was essentially non-existent.

According to the Ombudsperson’s investigation, police made their first arrests after 5:00 PM—by which time five people had already died from gunshot wounds in the city center. For nearly three hours, as emergency calls reported escalating violence including firearms being discharged into crowds, police took no meaningful action to stop the violence or apprehend those responsible.

This wasn’t the response pattern of a police force trying and failing to cope with unexpected chaos. This was the response pattern of a police force that had been told not to respond—or whose leadership had deliberately ensured they were unable to respond.

The Fire Engine

At approximately 4:30 PM, as street fighting raged near Hretska Square, a fire engine responding to an emergency call was hijacked by pro-Russian militants and used as a battering ram against barricades. The captured fire engine was driven around the area of clashes for several hours before being released following negotiations with Volodymyr Bodelan, head of the State Emergency Service (SES) in Odesa region.

The significance of this incident extends beyond the immediate chaos. Following the fire engine’s capture, Bodelan gave an order that would have devastating consequences: no fire engines were to be dispatched without his direct authorization. His stated reasoning was that he needed to prevent another fire engine from being captured and to avoid risking the lives of firefighters while armed clashes were ongoing.

This order was in effect when the Trade Unions Building caught fire at approximately 7:45 PM. The first emergency calls about fire at the building came at 7:45 PM. Fire engines didn’t arrive until 8:09 PM—a 24-minute delay for a fire station that was less than five minutes’ drive from Kulikovo Pole.

During those 24 minutes, 42 people died.

The Council of Europe’s investigation would later establish that the SES internal inquiry into these events was “carried out in a formalistic way and was not objective.” What “formalistic and not objective” means in plain language: the SES investigated itself, concluded that its commander had made reasonable decisions under difficult circumstances, and issued a reprimand for minor procedural violations. The actual decision to delay fire response while a building full of people burned—a decision that can be directly linked to dozens of deaths—was treated as defensible caution rather than criminal negligence.

The Meeting: Phones Off While the City Burns

One detail captures the dysfunction—or coordination—better than any other. On May 2 at noon, even as pro-Russian activists were gathering for confrontation and Ukrainian unity supporters were assembling for their march, senior law enforcement and security officials were in a meeting.

The meeting was chaired by Mykola Banchuk, Deputy Prosecutor General. Attending were regional heads of the prosecutor’s office, police, SBU, and military. The stated purpose was to discuss “separatism and other public order challenges in the Odesa region.”

According to Arsen Avakov, Ukraine’s Minister of Internal Affairs, “this meeting lasted until 4 PM... with the telephones of those present switched off.”

The Temporary Investigation Commission disputed this timeline, concluding the meeting ended by 2:30 PM and that some officials had been monitoring their phones. The Prosecutor General’s Office later claimed most officials had been checking phones throughout. But even the most generous interpretation—meeting over by 2:30 PM with phones being monitored—means senior security officials were in a conference room rather than commanding their forces during the initial escalation of violence.

By 3:20 PM, when pro-Russian activists attacked the pro-unity march near Hretska Square, the violence that would eventually kill 48 people had begun. Senior officials were, at best, just emerging from their meeting. At worst—if Avakov’s timeline is accurate—they were still in the conference room with phones off while gunfire erupted in the city center.

The charitable interpretation is that this was spectacular bad timing and worse judgment: holding a long meeting about theoretical security threats while actual violence unfolded. The less charitable interpretation is that the meeting was deliberately scheduled to ensure key decision-makers would be unavailable during the critical initial hours of violence—unable to give orders that might have prevented escalation.

Either way, the result was the same: a paralyzed command structure at the exact moment when decisive leadership might have prevented catastrophe.

Arrests That Weren’t

When police finally did make arrests, the pattern was selective. In the city center, 47 pro-Russian activists were detained after being cornered in the Afina Shopping Center. At the Trade Unions Building, 63 pro-Russian activists were arrested after the fire was extinguished. These mass arrests created an appearance of law enforcement action.

But the arrests were strikingly one-sided. While over 100 pro-Russian activists were detained—many captured en masse when trapped in buildings rather than arrested for specific violent acts—virtually no arrests were made of pro-unity activists, despite video evidence showing individuals from that side also committing acts of violence.

More tellingly, the most serious offenders on the pro-Russian side weren’t arrested at all. Vitaliy Budko, filmed firing a pistol from behind police lines, wasn’t detained. Artem Davydchenko, identified as one of the organizers of pro-Russian mobilization, wasn’t arrested on May 2 (he was detained days later, then allowed to flee before trial). The pattern suggests police arrested those they couldn’t avoid arresting while allowing key operatives to escape.

And even the mass arrests proved temporary. On May 4, just two days after the violence, a crowd of pro-Russian supporters stormed the police station where detained activists were being held. In the chaos—or under orders—63 detainees were released. No police officers were injured in the “storming” of a police station. No one was arrested for participating in the attack. The detained activists simply walked free.

The official explanation was that Dmytro Fuchedzhy, by then acting head of Odesa regional police following Lutsiuk’s dismissal, gave the order to release detainees to avoid further violence. But the ease with which a police station was “stormed” and the decision to release detained militants rather than defend a government facility suggests something more than crowd pressure was at work.

Following the Money: Modest Sums, Significant Impact

The Glazyev Tapes reveal how the operation was financed: cash transfers of $20,000-$25,000 at a time, moved through intermediaries, delivered in person. These are modest sums by the standards of state intelligence operations, but significant for street-level mobilization.

What can $20,000 buy in a hybrid warfare operation?

Payment for several dozen “protesters” at $50-100 per day for a month
Rental of office space for a “people’s council” or “self-defense headquarters”
Sound equipment, flags, banners for demonstrations
Transportation for activists to be moved between cities as needed
Per diem expenses for organizers and coordinators

The amounts in the Glazyev Tapes weren’t funding an army. They were funding political theater that could be portrayed as popular uprising. The economics are revealing: this wasn’t a grassroots movement that attracted Russian support. This was a Russian operation that purchased the appearance of grassroots support.

And in Odesa, someone paid for the Kulikovo Pole camp, for the coordination of pro-Russian activist groups, for the transportation of militants on May 2. The money trail was never fully investigated. Dmytro Fuchedzhy fled to Transnistria on May 6, before serious investigation could begin. Petro Lutsiuk was eventually charged but only for the forged “Wave” plan documents, not for financial crimes. The operational funding—where it came from, who distributed it, what it paid for—remains in the shadows.

But the pattern matches what Glazyev described: modest funding, local operatives, plausible deniability. It was enough to stage confrontation. It wasn’t enough to win.

What Went Wrong: Why Odesa Didn’t Fall

The plan to destabilize Odesa followed a template that had worked in Donbas. Create parallel power structures. Stage confrontations that force police and local authorities to choose sides. Escalate until Moscow can justify “humanitarian intervention” or local Russian forces can claim control. Maintain just enough ambiguity that Western responses remain uncertain.

In Donetsk and Luhansk, this approach succeeded. In Odesa, it failed. Understanding why requires examining not just what happened on May 2, but what didn’t happen in the crucial months before.

Elite Non-Commitment: The Dog That Didn’t Bark

The most significant factor in Odesa’s resistance to Russian destabilization was simple: local elites refused to commit. Unlike Donbas, where regional powerbrokers—some willingly, some under duress—eventually sided with separatists, Odesa’s political and business elite remained conspicuously neutral or quietly aligned with Kyiv.

Gennadiy Trukhanov, Odesa’s mayor, exemplified this pattern. Russian-speaking, with historical ties to Russia’s commercial networks, Trukhanov was exactly the kind of figure who might have been expected to support, or at least not oppose, pro-Russian mobilization. Instead, he threaded a careful needle: avoiding inflammatory pro-Ukrainian rhetoric that might provoke Moscow or alienate Russian-speaking residents, while quietly ensuring city resources didn’t flow to pro-Russian activists.

When pro-Russian protesters stormed the Regional State Administration on March 3, the Odesa Regional Council issued a resolution that was a masterpiece of non-commitment: deploring “extremism and any attempt to breach the territorial integrity of Ukraine” while simultaneously calling for “dialogue” and urging “political parties, movements and people in Odesa to avoid any illegal mass action and to seek a compromise through democratic means.”

This wasn’t courage. It was calculation. Odesa’s elite had a clear material interest in maintaining Ukraine’s territorial integrity: the city’s commercial significance derived from its role as Ukraine’s primary maritime gateway to European and Mediterranean markets. “People’s republics” don’t maintain complex commercial relationships with European ports. They become isolated backwaters dependent on Russian subsidies.

The business calculus was reinforced by demographic reality. While Odesa had an ethnic Russian majority, it wasn’t the concentrated, culturally distinct Russian population of Donbas. It was mixed, fluid, intermarried. Many “ethnic Russians” in Odesa spoke Ukrainian at home, had Ukrainian business partners, and saw their identity as more “Odesan” than specifically Russian or Ukrainian.

This ambiguous identity—more civic than ethnic—made Odesa resistant to the nationalist mobilization that worked in Donbas. Calls to defend Russian language and culture fell flat in a city where Russian was already the dominant language and culture was more Mediterranean than Soviet.

The contrast with Donbas is instructive. In Donetsk and Luhansk, regional oligarchs like Rinat Akhmetov initially tried to maintain neutrality but ultimately faced a choice: support separatism or lose their assets. Many chose to cut deals with separatist leadership, calculating that accommodation was preferable to confiscation. In Odesa, no such choice was forced because separatists never achieved enough power to threaten elite interests.

Police Defections That Didn’t Happen

In Donbas, police defections were crucial to separatist success. In city after city during March and April 2014, Ukrainian police either stood aside as separatists occupied government buildings or actively joined them. These defections provided separatists with weapons, inside knowledge of security forces, and an aura of official authority.

In Odesa, police defections never materialized in meaningful numbers. Despite clear evidence of command-level complicity—Fuchedzhy’s escape, the failure to implement the “Wave” plan, the passive response to violence on May 2—rank-and-file police largely remained loyal to Ukrainian authority, even when their commanders were compromised.

This loyalty wasn’t necessarily ideological. Many Odesa police were ethnic Russians or Russian-speakers themselves. But they were local. They lived in Odesa, their families were there, their futures were tied to the city’s stability. Defecting to a separatist movement with uncertain prospects meant burning those bridges permanently.

The contrast with Donbas is again revealing. In Donetsk and Luhansk, police defections often came from officers who calculated that separatism would win and wanted to be on the winning side. In Odesa, no such calculation was possible because separatism never achieved enough momentum to appear inevitable. And without that appearance of inevitability, most police—whatever their personal sympathies—chose to keep their heads down and follow orders, even bad ones.

The Civic Response: When Civil Society Fights Back

If elite non-commitment created space for resistance and police (non)defections prevented separatists from seizing control of security apparatus, it was civic mobilization that turned passive resistance into active opposition.

The pro-Ukrainian unity movement that coalesced in Odesa during March and April 2014 was distinct from Euromaidan in Kyiv. It wasn’t primarily about European integration or anti-corruption reform. It was about territorial integrity and local identity. The message was simple: Odesa would remain part of Ukraine.

This movement drew on multiple constituencies:

Ukrainian nationalists who saw separatism as Russian aggression
Russian-speaking Odesans who identified as Ukrainian citizens
Business interests worried about economic isolation
Families with members serving in Ukrainian forces
Civic groups opposed to violent extremism regardless of its origin

By late April, pro-unity activists were matching or outnumbering pro-Russian protesters at competing demonstrations. On May 2, when pro-Russian activists attacked the unity march, they were confronting not a small group of nationalists but a crowd of several thousand that included families, football fans, and ordinary citizens.

The violence that followed was chaotic and tragic. People died who shouldn’t have. But the outcome was never in doubt: pro-Russian activists were vastly outnumbered by a mobilized population that rejected their project.

This civic response was possible because Odesa’s civil society was stronger and more diverse than Donbas. The city had multiple independent media outlets, active civic organizations, and a tradition of public engagement that hadn’t been fully crushed by post-Soviet authoritarian governance. When separatism threatened, these civil society networks could mobilize quickly.

The Failure of Violence: May 2 as Strategic Defeat

If the operation to destabilize Odesa had a theory of victory, it was presumably that a violent confrontation would create facts on the ground that would force authorities to choose sides, demonstrate Ukrainian government brutality or weakness, and provide justification for Russian intervention.

May 2 provided the violent confrontation. But it produced the opposite of the intended effect.

Instead of forcing police to defend pro-Russian activists (demonstrating local support for separatism), police absence exposed separatists’ isolation. Instead of Ukrainian forces committing atrocities against Russian-speakers (justifying Russian intervention), pro-Russian militants were filmed firing on crowds and retreating into a building they then set ablaze through their own actions. Instead of creating chaos that weakened Ukrainian authority, the violence unified Odesa’s population against separatism.

The deaths in the Trade Unions Building were genuine tragedy. But they were also strategic catastrophe for the Russian operation. The victims weren’t martyrs to a popular cause. They were militants who had initiated violence, been decisively defeated, and died in a building they had themselves turned into a fortress and then inadvertently set on fire.

Russian propaganda would work tirelessly to rewrite this narrative: the Trade Unions Building fire became a “massacre” perpetrated by “Ukrainian fascists” who had burned alive “peaceful protesters.” But the propaganda couldn’t change the facts on the ground in Odesa itself, where residents had seen what actually happened.

After May 2, pro-Russian activism in Odesa collapsed. The Kulikovo Pole camp was dismantled. Key organizers fled or went underground. Subsequent attempts to stage pro-Russian demonstrations attracted dozens of participants rather than hundreds. The operation was over.

The Donetsk Comparison: What Success Looked Like

To understand Odesa’s failure, it helps to understand what success looked like elsewhere. In Donetsk, the pattern from March through May 2014 was:

March: Pro-Russian activists occupy regional administration building. Police stand aside. Activists declare “Donetsk People’s Republic.”

April: Armed militants from Russia arrive. Local police defect in significant numbers. Ukrainian forces attempt to retake buildings but face armed resistance.

May: “Referendum” on independence produces predictable result. Separatist control consolidates over major cities. Ukrainian government loses control of region.

Each step built on the previous one. Building occupation led to declaration of “people’s republic.” Declaration created parallel authority structure. Parallel authority attracted Russian support. Russian support enabled military resistance to Ukrainian forces. Military resistance made separatist control a fact that would require major military operation to reverse.

In Odesa, the sequence broke at the first step. Activists briefly occupied buildings but couldn’t hold them. They declared no “people’s republic” because they lacked the force to back such a declaration. Without parallel authority structures, they couldn’t attract meaningful Russian military support. Without military support, they were just protesters with guns facing a hostile population and at least nominally loyal police.

May 2 was supposed to be the crisis that forced escalation. Instead it was the crisis that revealed the operation had already failed.

Transnistria: The Dog That Didn’t Bark (Part Two)

One of the most significant non-events of the Odesa operation was the absence of intervention from Transnistria. The Russian-backed separatist statelet, just 60 kilometers from Odesa, had an estimated 1,500 Russian troops plus local forces. Russian military and intelligence assets in Transnistria could have reinforced pro-Russian militants in Odesa the way “volunteers” from Russia reinforced separatists in Donbas.

This didn’t happen. Transnistrian forces remained on their side of the border. Russian troops stationed in Transnistria stayed in their barracks. Some individual Transnistrian volunteers may have participated in Odesa events, but there was no coordinated military support.

Why not? Several factors likely contributed:

Geography: Unlike Donbas, which shares an open border with Russia, Transnistria is separated from Russia by Ukrainian territory. Reinforcing Transnistrian-based forces in Odesa would have required moving military equipment across Ukrainian-controlled Moldova, a direct act of war with no plausible deniability.

Moldovan Neutrality: Overt Transnistrian intervention in Odesa would have threatened Moldova’s neutrality and potentially triggered NATO response given Moldova’s proximity to Romania, a NATO member. This was a line Moscow wasn’t ready to cross.

Lack of Local Success: Russian/Transnistrian intervention might have been risked if pro-Russian forces in Odesa had demonstrated enough local support to make success plausible. When it became clear they lacked such support, intervention would have meant occupying a hostile city—a far different proposition than supporting a “popular uprising.”

The decision not to use Transnistrian assets was likely made in Moscow, not Tiraspol. It represented a calculation that Odesa wasn’t winnable and that the costs of an overt intervention exceeded potential benefits. That calculation was probably correct. But it also meant abandoning the pro-Russian operatives and activists who had been mobilized for the Odesa operation.

May 2 showed what happened to those operatives when promised support didn’t materialize: they were isolated, defeated, and in some cases killed by the population they’d been sent to “liberate.”

Part Two: The Cover-Up

The Immediate Response: Damage Control

In the hours and days after May 2, as the death toll became clear and video footage spread across social and international media, both Ukrainian and Russian authorities moved quickly to control the narrative. But they were working toward opposite objectives: Ukraine toward establishing that violence had been initiated by pro-Russian militants, Russia toward portraying the tragedy as Ukrainian fascist massacre of peaceful protesters.

The first hours were crucial. By midnight on May 2, Russian media was already broadcasting that Ukrainian nationalists had burned alive “dozens” of pro-Russian activists. The numbers kept rising in Russian coverage: 50 dead, 100 dead, some reports claimed “up to 300” killed. The Trade Unions Building fire was described as “deliberate arson” by “Right Sector fascists” who had “locked people inside” before setting the building ablaze.

This narrative had the advantage of being first. By the time accurate information emerged—48 dead, fire started accidentally during mutual exchange of Molotov cocktails, most victims killed by smoke inhalation rather than burns—the Russian version had already spread globally. Corrections never fully catch up with initial claims.

Ukrainian authorities’ initial response was defensive and confused. Interior Minister Arsen Avakov announced the dismissal of Petro Lutsiuk, head of Odesa regional police, on the morning of May 3, acknowledging police had “acted deplorably, perhaps criminally.” But he also pointed fingers at the prosecutor’s office, claiming prosecutors had ordered a meeting that pulled police commanders away from their posts during the critical afternoon of May 2.

The Prosecutor General’s office denied this, calling Avakov’s claim “unfounded.” This public contradiction between Interior Ministry and Prosecutor General’s office in the first 24 hours after a mass casualty event was not confidence-inspiring.

Meanwhile, Acting Prosecutor General Oleh Makhnitsky tried to thread a needle: acknowledging that 46 people had died (the number later revised to 48) while insisting that investigation would be “comprehensive and objective.” He announced criminal proceedings under multiple articles: mass disorder, attacks on police, and—crucially—Article 367 of the Criminal Code: official negligence.

That last charge was significant. It meant prosecutors were, at least nominally, investigating police failure to prevent or respond to violence. But Makhnitsky’s statement was careful to avoid assigning responsibility: “the events on 2 May in Odesa have shown what can result from external agitation and from a lack of foresight on the part of certain officials who neglected their duty to protect public order.”

“External agitation” was diplomatic language for Russian involvement. “Lack of foresight” was diplomatic language for what might be criminal negligence or deliberate complicity. Neither phrase constituted serious accountability.

The Investigation That Wasn’t: April to October 2014

In the immediate aftermath of May 2, Ukraine’s investigative apparatus went through the motions of accountability with little apparent intention of achieving it. Multiple investigations were announced:

The Interior Ministry’s Main Investigative Department (MID) took over investigation of civilian actions (mass disorder, arson, deaths)
The Prosecutor General’s Office investigated police conduct
The State Emergency Service conducted internal inquiry into fire response
The Verkhovna Rada (parliament) established a Temporary Investigation Commission
The Ombudsperson opened an inquiry into human rights violations

This proliferation of investigations created appearance of thorough response. In practice, it fragmented accountability and ensured no single body had complete picture of what happened.

The MID investigation, led by investigators from Kyiv rather than local Odesa police (themselves under investigation), made initial progress. By mid-May, over 100 people had been detained, most captured en masse at the Afina Shopping Center or the Trade Unions Building. But the investigation quickly bogged down in a familiar pattern: lots of low-level arrests, few if any of actual organizers.

The most damning evidence of investigative dysfunction came from the Ombudsperson’s inquiry, completed in late May 2014. Ombudsperson Valeriya Lutkovska’s investigators examined the “Wave” plan documentation and concluded that the plan had never actually been implemented—that documents showing its activation had been created after the fact to cover up its absence.

The Ombudsperson’s report, based on examination of police logbooks, issue-and-return records for weapons and equipment, and interviews with officers, found:

The order to implement the “Wave” plan was never properly registered or dated
It had not been approved by the Regional State Administration as legally required
Relevant logbooks showed no evidence of the plan’s implementation
The order on use of force, required when implementing such plans, appeared to have been signed retrospectively

This wasn’t subtle. The Ombudsperson was documenting that police leadership had falsified records to conceal their failure to respond to mass violence. The report was forwarded to the Prosecutor General’s Office in June 2014 with request that findings be incorporated into criminal investigation of police conduct.

The International Advisory Panel later documented that Ukraine’s Ombudsperson had submitted detailed findings to the Prosecutor General’s Office as early as June 10, 2014, conclusively demonstrating that the “Wave” plan had never been implemented and that documents had been forged to create a false paper trail. Nearly a year would pass before prosecutors acted on this evidence—a delay the Panel found “striking” and indicative of authorities’ failure to “follow an obvious line of inquiry.”

Nearly a year would pass before any charges related to the “Wave” plan were filed.

The Temporary Investigation Commission: Parliament Investigates Itself

The Temporary Investigation Commission (TIC) created by the Verkhovna Rada represented Ukraine’s most visible effort at accountability. Chaired by Anton Kisse, an MP from Odesa, the TIC was tasked with establishing facts about what happened on May 2 and identifying institutional failures that allowed it to happen.

The TIC had significant powers: ability to summon officials for questioning, access to classified materials, authority to make recommendations for prosecution. It also had significant limitations: no power to compel testimony from those who refused to appear, no ability to bring charges directly, and a mandate that would expire with the parliamentary term.

Between May and September 2014, the TIC held hearings with representatives from the Interior Ministry, Prosecutor General’s Office, SBU, State Emergency Service, and various local Odesa officials. Their findings, released in a September 2014 report, were scathing:

On police deployment:

Police commanders had been informed of risk of violence but had implemented only a standard football match security plan
No special measures were taken despite specific warnings from SBU
Most police were deployed at the stadium, far from where violence actually occurred
Mobility of police units was inadequate to respond to rapidly developing situation

On police response:

Police had “failed to take adequate measures to arrest those taking part in the mass disorder”
For most of the day, police “had not intervened at all”
First arrests weren’t made until after 5:00 PM, by which time five people had already died from gunfire in the city center

On coordination:

No effective coordination between police, SBU, and other security services
Intelligence reports about potential violence were not translated into operational planning
Command and control during the crisis was “inadequate”

These were devastating conclusions. But they came with a fatal flaw: the TIC had no power to enforce them. The Commission’s mandate was to investigate and recommend, not to prosecute. Their report was forwarded to the Prosecutor General’s Office with request for follow-up.

There was no follow-up.

The TIC’s limitations were further exposed by who didn’t testify. Despite repeated invitations, several key figures declined to appear:

Andriy Parubiy, Secretary of the National Security and Defence Council, who had chaired the April 29 security meeting in Odesa
Arsen Avakov, Interior Minister
Serhiy Chebotar, Deputy Interior Minister
Valentyn Nalyvaichenko, head of the SBU

The absence of these officials—all of whom had direct responsibility for security response on May 2—meant the TIC never got answers to crucial questions about decision-making at the highest levels. Were they monitoring the situation in real time? When did they become aware violence was escalating? What orders did they give? What orders were not given?

These questions remain unanswered. When the new Verkhovna Rada was elected in October 2014, the TIC’s mandate expired. A proposal to create a new commission was introduced in December 2014. As of this writing, it remains “under examination” in parliament—where proposals go to die quietly.

Selective Prosecution: Who Was Charged and Who Wasn’t

By November 2014, six months after May 2, a pattern had become clear in the prosecutions: lots of arrests of low-level pro-Russian activists, virtually no charges against Ukrainian unity side, and no prosecution of any police or security officials despite overwhelming evidence of negligence or complicity.

The numbers tell the story:

Pro-Russian activists:

114 detained immediately after May 2
63 released when police station was “stormed” on May 4
Of the remainder, 48 were eventually charged with participation in mass disorder
21 sent to trial in a single indictment in November 2014
Multiple others placed on wanted lists after fleeing

Ukrainian unity activists:

Three individuals charged with crimes related to May 2
Serhiy Khodiak charged with murder (firing into crowd with hunting rifle)
Vsevolod Honcharevskyi charged with assaulting people jumping from burning building
Mykola Volkov charged with shooting into Trade Unions Building (charges dropped after his death)

Police and officials:

Petro Lutsiuk (head of Odesa regional police) - dismissed May 3, not charged until April 2015
Dmytro Fuchedzhy (deputy head) - fled to Transnistria May 6, never arrested
Three lower-ranking officers charged with releasing detainees on May 4
No charges against any State Emergency Service officials despite 24-minute delay in fire response
No charges against any officials for forged “Wave” plan documents (until 2015)

The pattern wasn’t just imbalanced. It was inverted. Those with greatest responsibility—police commanders who failed to prevent violence or respond to it, SES officials whose delayed response cost dozens of lives—faced no consequences for months or years. Those with least responsibility—protesters swept up in mass arrests—faced immediate prosecution.

This selective prosecution pattern had two explanations, neither encouraging. First possibility: investigators genuinely couldn’t develop cases against senior officials because those officials had covered their tracks effectively, destroyed evidence, or maintained just enough plausible deniability that criminal charges couldn’t be sustained. Second possibility: investigators weren’t trying very hard because prosecuting senior officials would implicate the entire security apparatus and potentially reach into Interior Ministry or Prosecutor General’s Office itself.

Both explanations were probably true to some degree. But the result was the same: appearance of accountability without actual accountability.

The Case of Oleksandr Hrybovskyi: When Geopolitics Trumps Justice

Perhaps no single case better illustrates the corruption of the investigation than what happened to Oleksandr Hrybovskyi. Arrested after May 2 and charged with participation in mass disorder that resulted in deaths, Hrybovskyi was one of 21 pro-Russian activists whose cases were sent to trial in November 2014.

Then, in November 2014, prosecutors quietly terminated the case against him. The formal grounds: insufficient evidence. The actual reason, according to Prosecutor General’s Office officials who later spoke to the Council of Europe’s investigating panel: Hrybovskyi was traded to separatist forces in Donbas in exchange for Ukrainian Security Service (SBU) officers held captive there, some of whom were gravely ill.

Let that sink in. A man charged with participation in violence that killed 48 people was released—not because evidence was lacking, but because he was useful as a bargaining chip in a prisoner exchange. The case was officially terminated for “insufficient evidence” because Ukrainian law provided no mechanism for releasing criminal suspects for prisoner exchanges. So prosecutors used a false legal justification to accomplish a geopolitical objective.

The Prosecutor General’s Office officials who explained this to the Council of Europe panel were candid about what had happened and clearly uncomfortable with it. They acknowledged that the case file contained “ample evidence” of Hrybovskyi’s participation in the mass disorder. They expressed concern about the precedent being set—using criminal justice system as bargaining chip in conflict negotiation.

But they had followed orders. And Hrybovskyi walked free, his release framed as evidentiary insufficiency rather than prisoner exchange.

The cynicism of this decision is remarkable. Ukrainian authorities justified the investigation of May 2 events as pursuit of justice for victims. But they were willing to release a defendant in that investigation—essentially declaring those victims’ deaths were worth less than the political convenience of a prisoner exchange.

The decision also revealed how hollowed out the investigation had become by late 2014. If prosecutors could terminate a case with “ample evidence” for political reasons and simply lie about their justification, what did any of the other prosecutions mean? Was anyone actually being held accountable, or were all the prosecutions just theater—continued or dropped based on political calculation rather than evidence?

Fuchedzhy’s Escape: The Commander Who Got Away

If one person embodied command responsibility for police failures on May 2, it was Dmytro Fuchedzhy. As Deputy Head of Odesa regional police and head of the regional public order police, Fuchedzhy was operationally responsible for police deployment and response that day. He had given the April 30 press conference assuring public that police were ready to maintain order. He had been present in the city center during the violence, apparently sustaining a minor injury. He was filmed getting into an ambulance with Vitaliy Budko, a pro-Russian militant who had been firing into crowds.

On May 3, Fuchedzhy was appointed acting head of Odesa regional police following Petro Lutsiuk’s dismissal. On May 4, he was in command when the police station holding detained activists was “stormed” and 63 prisoners were released.

Then, on May 6, Fuchedzhy fled to Transnistria. He crossed the border into Moldova, made his way to the Russia-backed separatist statelet, and vanished from Ukrainian jurisdiction.

This wasn’t a sophisticated escape. Fuchedzhy wasn’t smuggled out in disguise or extracted by special forces. He apparently just drove to the border and crossed. No arrest warrant had been issued. No travel restrictions had been imposed. No one was watching him despite his obvious centrality to events being investigated.

The timeline is revealing:

May 2: Violence unfolds with police effectively absent
May 3: Fuchedzhy promoted to acting chief of regional police
May 4: Detained activists released under his command
May 5: Investigators from Kyiv arrive to begin investigation of police conduct
May 6: Fuchedzhy flees to Transnistria

Investigators later claimed they had been preparing to arrest Fuchedzhy but the case transfer from local prosecutors to the Prosecutor General’s Office caused administrative delays. By the time PGO investigators had paperwork in order, Fuchedzhy was gone.

The Council of Europe’s International Advisory Panel would later conclude that the failure to prevent Fuchedzhy’s escape “indisputably impaired the effectiveness of the investigation,” noting there were “sufficient grounds for suspicion to justify the authorities in applying for some form of preventive measure” immediately after May 2nd—measures that were never taken.

This is the charitable interpretation: bureaucratic dysfunction and inter-agency coordination failure allowed a key suspect to flee. The less charitable interpretation: someone ensured Fuchedzhy had time to get away.

Either way, the result was catastrophic for accountability. Fuchedzhy wasn’t some mid-level officer who might have been following orders. He was the operational commander responsible for police deployment and response. His escape meant questions about what orders he gave, what orders he received, what he knew about plans for May 2—all of it disappeared across the border with him.

In May 2014, prosecutors issued an arrest warrant and placed Fuchedzhy on Ukraine’s wanted list. In 2015, Ukraine requested Interpol issue a Red Notice for his arrest. Interpol declined, ruling the case was “political” and therefore outside their mandate. This was a remarkable decision: Interpol effectively declaring that prosecution for police failures during mass violence was political rather than criminal.

As of this writing, Fuchedzhy remains in Transnistria, beyond reach of Ukrainian law. Occasional reports place him working in some capacity for Transnistrian security services—a Russian-backed separatist statelet providing safe haven to a Ukrainian police commander who fled investigation of his role in deaths of 48 people.

The symbolism is perfect: the man operationally responsible for police protection of Odesa on May 2, 2014 is now protected by Russia’s proxy statelet from accountability for his failures that day.

The State Emergency Service: When Negligence Meets Impunity

While police failures on May 2 were operational—commanders deployed forces incorrectly, officers failed to intervene in violence—the State Emergency Service (SES) failures were simpler and more lethal. When the Trade Unions Building caught fire at approximately 7:45 PM, SES dispatchers knew about it within minutes. Fire stations were less than five minutes’ drive away. Fire engines didn’t arrive for 24 minutes.

During those 24 minutes, 42 people died.

The reason for the delay was, on its face, simple: Volodymyr Bodelan, head of SES in Odesa region, had given an order that no fire engines were to be dispatched without his personal authorization. He had given this order at 7:32 PM, shortly after pro-Russian militants had hijacked a fire engine and used it as a battering ram during the street fighting.

Bodelan’s stated reasoning was that he needed to prevent another fire engine from being captured and to avoid risking firefighters’ lives while armed violence was ongoing. This was not, on its face, an unreasonable concern. Fire engines had been attacked in other Ukrainian cities during clashes between pro-Russian and pro-Ukrainian activists. Sending firefighters into an active combat zone could result in their deaths.

But Bodelan’s order remained in effect as the situation changed. By 7:45 PM, when the Trade Unions Building fire started, the street fighting had largely moved away from Kulikovo Pole. The area around the building, while still tense and crowded, wasn’t an active combat zone. More importantly, there was a building on fire with people inside—an emergency that by definition requires immediate fire response regardless of security concerns.

The Council of Europe’s investigation established that SES internal inquiry into these events was “carried out in a formalistic way and was not objective.” Let’s unpack that diplomatic language.

The SES conducted an internal investigation of itself in May 2014. The investigation concluded that Bodelan’s order to delay fire engine deployment was a reasonable security precaution under difficult circumstances. It found minor procedural violations in documentation and operational coordination. It recommended Bodelan receive a reprimand for these procedural issues. That reprimand was issued on June 11, 2014.

Bodelan appealed the reprimand. The first-instance court quashed it in July 2014, finding insufficient grounds. The appellate court later reversed that decision, but by then Bodelan had left the SES—his contract not renewed in September 2014.

No criminal investigation into SES conduct was opened until October 2014, five months after the fire. That investigation was initially assigned to local Odesa investigators who, according to the Council of Europe panel, “remained inactive during the crucial early stages.” In December 2014, the case was transferred to the Interior Ministry’s Main Investigative Department in Kyiv because of “lack of effective investigation.”

By the time serious investigation began, Bodelan had left Ukraine. His whereabouts became unknown to authorities in early 2015. No arrest warrant was issued until after he was already gone. As of this writing, no one has been charged with any crime related to SES response to the Trade Unions Building fire.

Think about what this means: 42 people died in a fire that fire services took 24 minutes to respond to despite being less than five minutes away. An internal inquiry found this delay was reasonable under the circumstances. No criminal investigation was opened for five months. When investigation finally began, it was so ineffective it had to be transferred to different investigators. By the time those investigators got around to seriously examining what happened, the person who had ordered the delay in fire response had left the country.

This isn’t justice delayed. This is justice prevented.

The Forensic Failures: When Science Serves Politics

In any mass casualty event, forensic examination is crucial to establishing what happened. In Odesa, forensic examination became another battlefield where competing narratives fought for legitimacy.

The central questions were straightforward:

How did the fire in the Trade Unions Building start?
What caused the deaths inside the building?
Was there any use of chemical agents or accelerants beyond what was visible?
Were any of the deaths caused by violence rather than fire?

The official forensic reports, conducted by Ukraine’s State Research Forensic Center, concluded:

Fire started in five independent locations: lobby, two staircases, one room, and one landing
Only the lobby fire could have been started from outside the building
Other fire sources must have resulted from actions of people inside
Deaths were caused by carbon monoxide poisoning, burns, and falls from height
No evidence of torture, beating, or gunshot wounds on bodies found inside
No evidence of chemical agents other than combustion products from the fire itself

These findings contradicted Russian propaganda narrative that the fire had been started by Ukrainian nationalists who had burned “peaceful protesters” alive. They also contradicted some pro-Russian activists’ claims that victims inside had been killed execution-style before the fire started.

But the Ukrainian government’s handling of the forensic evidence was problematic enough to fuel suspicion. The initial fire examination report was completed in July 2014—more than two months after the fire—and was based on examination of collected evidence rather than thorough on-site inspection. The building had been opened to the public on May 4, just two days after the fire, and wasn’t secured as material evidence until May 20. During those two weeks, the crime scene was thoroughly contaminated.

The Council of Europe investigation found that this failure to properly secure the scene “gave rise to a substantial risk of evidence being removed from, or brought into, the building.” While investigators didn’t believe contamination had actually affected their conclusions about the fire’s causes, the appearance of sloppiness undermined confidence in findings.

More problematic was the Ukrainian government’s initial public statements about the fire, which shifted as forensic examination progressed:

May 15, 2014: Interior Ministry officials categorically denied any chemical agents were used in the building.

May 19, 2014: Deputy Interior Minister announced that “samples of chloroform had been detected at the crime scene” and suggested chloroform “might have caused the death of those in the Trade Union Building.”

April 22, 2015: Deputy Prosecutor General stated that “information as to the use of poisonous gases or chloroform had not been confirmed in the course of the investigation.”

This wasn’t evidence evolving as investigation progressed. This was officials making definitive public statements about contested facts, then reversing themselves, then reversing again. Each reversal fed suspicion that authorities were hiding something or didn’t know what they were doing.

The confusion about chloroform is illustrative. Initial reports of chloroform detection caused panic—had someone deliberately gassed people inside the building? But further examination revealed the “chloroform” detection was likely a testing artifact or misidentification of other combustion products. No credible evidence emerged of chemical agents being deliberately used.

But the damage was done. By the time accurate information emerged, Russian media had spent months claiming Ukraine was covering up chemical weapons use. And Ukrainian government’s own contradictory statements made the cover-up claims seem plausible.

Perhaps most significantly, the initial forensic reports didn’t adequately address causal questions that would be crucial for assigning responsibility:

Could the fire have been contained or extinguished if fire services had arrived promptly?
How many deaths occurred in the first 10-15 minutes of the fire versus later?
Would earlier evacuation have saved lives?

These questions matter because they determine whether the SES delay in responding was merely negligent or actually causal to deaths. If most people died in the first few minutes before fire services could have arrived anyway, the delay was less consequential. If many people died in the 15-24 minute window when fire services should have been there but weren’t, the delay was potentially criminal.

Only in April 2015—nearly a year after the fire—did authorities commission a comprehensive inter-agency forensic examination to address these questions. That examination was still underway when the Council of Europe completed its investigation in late 2015.

The Council of Europe Investigation: Outside Scrutiny

The Council of Europe’s International Advisory Panel investigation, conducted between February and August 2015, provided the first comprehensive independent assessment of Ukraine’s handling of May 2 investigations. The Panel had been created initially to oversee investigations of Euromaidan violence in Kyiv, but its mandate was expanded to include Odesa at the request of Ukraine’s government and international partners.

The Panel’s mandate was narrow but important: assess whether investigations complied with European Convention on Human Rights standards and European Court of Human Rights case law regarding effective investigation of deaths and serious injuries. The Panel couldn’t conduct investigations itself or determine individual guilt or innocence. It could only evaluate whether Ukrainian authorities were investigating effectively.

The Panel’s conclusions, delivered in a report released in March 2016, were diplomatically worded but devastating in substance:

On independence: The investigation was structurally compromised because the Interior Ministry’s Main Investigative Department was investigating events where police were implicated. This violated requirements for institutional independence.

On effectiveness: The investigation suffered from numerous deficiencies:

Failure to secure crime scenes promptly and adequately
Delays in collecting evidence and conducting forensic examinations
Failure to prevent key suspects (Fuchedzhy, Bodelan) from fleeing
Inadequate staffing and resources allocated to investigations
Selective prosecution pattern that undermined credibility

On promptness: While investigations into civilian actions were opened quickly, investigation into SES conduct wasn’t initiated until October 2014, and investigation of forged “Wave” plan documents was delayed for nearly a year despite Ombudsperson having provided conclusive evidence.

On public scrutiny: While authorities provided regular public updates, these were “inconsistent” and “unevenly presented,” and there was no coherent communication strategy.

On victim involvement: Victims and next-of-kin were not adequately kept informed of investigation progress, especially compared to Maidan investigations where Prosecutor General’s Office held monthly meetings with victims’ families.

The Panel’s overall conclusion was carefully phrased but clear: “substantial progress has not been made in the investigations into the violent events in Odesa on 2 May 2014.” While “contextual challenges” explained some difficulties, “the deficiencies identified in this Report have undermined the authorities’ ability to establish the circumstances of the Odesa-related crimes and to bring to justice those responsible.”

In diplomatic language, this meant: Ukraine had failed to conduct adequate investigation of what happened on May 2, 2014.

The Ukrainian government’s response to the Council of Europe report was to note its recommendations and promise reforms. Some reforms were indeed initiated: the investigation command structure was reorganized, additional prosecutors and investigators were assigned to cases, and new forensic examinations were commissioned.

But the fundamental problems remained. The investigation was still divided between multiple agencies with competing interests. Key suspects were still beyond reach, either fled abroad or protected by political connections. And prosecutions were still moving slowly when they moved at all.

As of mid-2015, three years after May 2, 2014:

No senior police official had been convicted of anything
No SES official had been charged with anything
One case involving 21 low-level pro-Russian activists was slowly grinding through trial
Three lower-ranking police officers were on trial for releasing detainees on May 4
Multiple suspects were on wanted lists, several known to be in Russia or Transnistria
The most serious charges against Ukrainian unity activists had been dropped or were stalled

The investigation had produced a mountain of documentation, numerous arrests, and very little accountability.

Analysis: Why the Cover-Up Failed (Partially)

The cover-up of what happened on May 2, 2014 in Odesa was more successful than the operation it was meant to conceal, but less successful than similar efforts in Russia typically are. Understanding why requires examining both the structural factors that enabled partial accountability and the limitations that prevented full accountability.

The Role of Civil Society and Independent Media

Ukraine in 2014 was not Russia. This obvious point had profound implications for how far authorities could go in suppressing information.

The 2 May Group—a collection of Odesa journalists, activists, and technical experts who conducted their own parallel investigation—exemplifies the role civil society played. These weren’t professional investigators or government officials. They were a chemist, a toxicologist, several journalists, and assorted concerned citizens who decided that if the government wouldn’t investigate properly, they would do it themselves.

Working with limited resources but considerable technical competence, the 2 May Group:

Conducted their own forensic analysis of the Trade Unions Building fire
Compiled and analyzed hundreds of hours of video footage
Interviewed witnesses who wouldn’t talk to police
Published detailed chronologies and technical reports
Challenged official narratives when evidence didn’t support them
Provided information to international investigators

Their work wasn’t perfect—they lacked access to bodies, official documents, and many witnesses. But it was thorough enough to make it impossible for authorities to simply declare what happened and expect to be believed uncritically.

Crucially, the 2 May Group existed because Ukraine had independent media and civil society space that Russia lacks. They could publish their findings without being shut down. They could criticize official investigations without being arrested. They could coordinate with international organizations like the Council of Europe without being charged with treason.

This space for independent investigation was the product of Euromaidan. One of the revolution’s core demands had been media freedom and reduced state control over information. While Ukraine’s media landscape remained imperfect—oligarch ownership, political pressure, and Russian disinformation all constrained truly independent journalism—there was more space for critical investigation than in Russia.

That space made cover-up harder. Not impossible—as the investigation’s failures demonstrate—but harder than it would have been in a fully authoritarian context.

International Scrutiny: The Council of Europe Factor

The Council of Europe’s involvement was double-edged for Ukrainian authorities. On one hand, it demonstrated Ukraine’s willingness to submit to international oversight—a signal of European orientation and democratic commitment. On the other hand, it meant Ukraine’s investigation would be evaluated against European standards by experts who couldn’t be easily pressured or misled.

The International Advisory Panel had access that domestic critics lacked. They could demand documents from prosecutors and police. They could interview investigators and officials. They could attend meetings closed to media and civil society. And they had technical expertise to evaluate whether investigations met international legal standards.

Their presence didn’t prevent the investigation’s failures, but it documented them in authoritative form that Ukraine’s government and international partners couldn’t ignore. When the Panel reported that investigation was structurally flawed, that key suspects had been allowed to flee, that forensic work was inadequate—these weren’t allegations by biased activists but findings by respected international jurists.

This created accountability pressure that was real if limited. Ukraine’s government couldn’t simply declare the investigation adequate and move on. They had to respond to Council of Europe findings, at least nominally address identified deficiencies, and accept ongoing international monitoring.

Would investigation have been any better without Council of Europe involvement? Probably not—the Panel didn’t have power to compel specific prosecutions or prevent specific failures. But would cover-up have been more complete? Quite possibly.

The Limits of Accountability: Why Cover-Up Partially Succeeded

But if civil society pressure and international scrutiny prevented complete cover-up, they didn’t prevent extensive cover-up. Three years after May 2, most of those responsible for the violence and its death toll remained unprosecured.

The reasons for this partial success of cover-up are worth examining:

First, institutional protection. The Interior Ministry investigated crimes involving police, and the SES investigated its own conduct (until that investigation was belatedly taken over). Even when investigations were nominally transferred to more independent bodies, the investigators relied on cooperation from institutions they were investigating. This created structural conflicts that ensured investigation never pushed too hard.

Second, political calculation. Prosecuting senior officials for May 2 failures risked wider implications. If Fuchedzhy and Lutsiuk were criminally negligent, what about their superiors? What about the Deputy Prosecutor General who was holding a meeting while violence unfolded? What about the Security Council Secretary who had chaired coordination session just days before? What about Interior Minister who oversaw police deployment?

Criminal accountability tends to push upward—each investigation reveals decisions made by someone higher up the chain. At some point, authorities decided it was preferable to let investigation stall at mid-level rather than risk where it might lead.

Third, geopolitical complexity. The Hrybovskyi case illustrated how May 2 investigations became entangled with broader conflict. Ukraine was fighting a war in Donbas. Prisoner exchanges were necessary. Using May 2 defendants as bargaining chips was morally questionable but practically tempting.

More broadly, aggressive prosecution of pro-Russian activists for May 2 served Russian propaganda purposes. Every trial was portrayed in Russian media as persecution of innocent victims. Every detention was evidence of Ukrainian fascism. Ukraine’s government had to balance accountability against providing propaganda ammunition to Russia.

This doesn’t excuse the failures, but it explains them. Ukraine’s government was trying to pursue accountability while fighting a war, managing international relations, preventing Russian escalation, and maintaining domestic political stability. In that context, full accountability for May 2 became secondary to other priorities.

Fourth, capacity limits. This is the most prosaic explanation but probably the most important. Ukraine’s investigative and judicial system was—and is—severely under-resourced, often corrupt, and frequently incompetent. The kind of complex investigation May 2 required—multiple crime scenes, hundreds of witnesses, technical forensic analysis, coordination between multiple agencies—was beyond the system’s actual capacity.

The investigators assigned to May 2 cases were often doing their best with inadequate resources, poor coordination, and political pressure from multiple directions. Their failures weren’t all deliberate obstruction. Many were the predictable result of asking a dysfunctional system to handle a case that would challenge even a highly functional one.

The Counter-Narrative Campaign: Russia’s Information War

While Ukrainian authorities struggled to investigate May 2 competently, Russian media and officials waged a highly competent campaign to define what happened in terms favorable to their narrative.

The Russian version crystallized quickly: Ukrainian fascists, organized by Right Sector and supported by the new Kyiv government, had deliberately burned alive peaceful pro-Russian protesters who were exercising their right to demonstrate against an illegitimate coup regime. The death toll was in the hundreds. The victims had been locked inside the building before it was set ablaze. Some had been beaten or shot before the fire. This was genocide, ethnic cleansing, a deliberate massacre of Russian-speakers.

None of this was true. But the Russian narrative had several advantages:

Speed: Russian media was describing “massacre” while Ukrainian authorities were still counting bodies. First impressions matter, and Russia established the narrative framework before Ukraine could respond.

Emotional resonance: The image of people burning alive is viscerally horrifying. It triggers moral revulsion and demands explanation. The Russian narrative provided simple explanation: Ukrainian fascists did this deliberately.

Confirmation bias: For audiences predisposed to believe Ukrainian government was fascist or illegitimate, the Russian narrative confirmed existing beliefs. For audiences predisposed to believe Russia was blameless, it provided exculpatory story.

Kernel of truth: The best disinformation contains truth. People did die in a fire. Ukrainian unity activists were present. Violence was horrific. These facts were undeniable. Russian narrative wrapped them in false context, but the factual kernel made the overall story seem more plausible.

The Ukrainian counter-narrative—pro-Russian activists initiated violence, were decisively defeated, retreated into a building they then accidentally set on fire through their own actions—was accurate but less emotionally compelling and harder to explain. It required acknowledging complexity: both sides used violence, the fire was accidental, most deaths were tragic rather than criminal.

In the information war, Russia won. International audiences who didn’t follow closely came away with vague impression of “massacre in Odesa” without clear understanding of what actually happened. This achieved Russian objectives: Ukraine was portrayed as violent and unstable, Russian-speakers as victims, and Russian intervention in Donbas as justified protection of endangered populations.

The cover-up of investigative failures complemented this narrative. Every delay in prosecution, every suspect who fled, every contradiction in official statements—all of it reinforced impression that Ukrainian authorities had something to hide. Maybe they were hiding incompetence rather than criminality, but the effect was the same: suspicion that the full story wasn’t being told.

The Banality of Cover-Up: Incompetence as Strategy

One of the most striking aspects of the Odesa investigation’s failures is how banal many of them were. Grand conspiracy theories about deliberate cover-up assume competence—that authorities were skillfully concealing evidence and suppressing investigation. The reality was often simpler: authorities were disorganized, under-resourced, and incompetent.

Crime scenes weren’t secured properly because no one had clear responsibility for securing them and commanders were absent or overwhelmed. Fuchedzhy escaped because no one thought to restrict his movement until he was already gone. The “Wave” plan documentation was forged because a panicked police commander wanted to cover his ass, not because high-level officials ordered evidence destruction.

This matters because it points to a different kind of failure. Conspiracy requires coordination. Incompetence just requires dysfunction.

Ukraine’s post-Maidan government inherited a law enforcement and judicial system that was designed for authoritarian control, not democratic accountability. Prosecutors were accustomed to taking orders from above, not pursuing evidence where it led. Police were trained to maintain order and protect officials, not investigate officials’ failures. Judges were embedded in patronage networks that rewarded loyalty over independence.

Reforming such a system takes years. Ukraine’s government, dealing with Russian invasion, economic crisis, and internal political conflict, had limited capacity to prioritize investigative reform. So they got the investigations their system was capable of producing: lots of activity, mountains of documentation, few results.

This is how cover-up happens in transitional democracies: not through masterful conspiracy but through institutional inertia, political calculation, and ordinary dysfunction. The effect is the same as deliberate cover-up—accountability fails, impunity continues—but the mechanism is more prosaic.

Conclusion: The Operation’s Legacy

Seven years after May 2, 2014, what was accomplished? A Russian operation to destabilize Odesa failed. A Ukrainian investigation into that failure also failed, though less completely. Forty-eight people died. Hundreds were injured. Trust in institutions was damaged. And the truth of what happened became permanently contested, with Russian propaganda and Ukrainian incompetence combining to ensure no definitive narrative would be accepted by all sides.

For Russia, the operation’s failure in Odesa marked the outer limit of the Crimea playbook. Hybrid warfare worked where local conditions favored it—concentrated Russian populations, economic desperation, weak civic society, geographic proximity to Russia. It failed where those conditions didn’t exist. After Odesa, Russia didn’t seriously attempt to destabilize other Ukrainian regions through similar methods. The “Russian Spring” that was supposed to spread across southern Ukraine stopped at the borders of Donetsk and Luhansk.

This was a significant strategic defeat. If Odesa had fallen to separatism, if Kharkiv had declared a people’s republic, if Dnipro and Zaporizhzhia had been destabilized—Ukraine would have collapsed. The country would have fragmented into warring regions, and Russia could have dictated terms to whatever government remained in Kyiv.

Instead, Ukraine survived as a functional state, retained control of its major cities, and mobilized effectively enough to stop Russian advances. The failure of hybrid warfare operations like Odesa’s contributed to that survival.

For Ukraine, the investigation’s failures have had their own costs. The perception that violence has no consequences, that officials who fail in their duties face no punishment, that justice depends on political connections—these perceptions corrode public trust in institutions that Ukraine desperately needs to be trusted if it’s to function as a democratic state.

Three years after May 2, when the Council of Europe completed its investigation, ordinary Ukrainians watching the news would have seen:

Senior police commanders who presided over catastrophic failures: one fled to Russia-backed Transnistria, one eventually charged but only after year-long delay
SES officials whose delayed response contributed to 42 deaths: no charges filed
Low-level pro-Russian activists: dozens arrested and prosecuted
Ukrainian unity activists: minimal prosecution
Clear evidence of forged documents, police complicity, official negligence: little consequence

This pattern—harsh justice for the powerless, impunity for the powerful—was exactly what Euromaidan had been protesting against. The revolution’s promise was rule of law, equal justice, accountability for officials. The May 2 investigation delivered selective prosecution and protected elites.

This doesn’t mean the revolution failed. Ukraine post-Maidan was dramatically freer and more democratic than Ukraine under Yanukovych. Civil society could pressure government. Media could report critically. International organizations could monitor justice. None of this would have been possible before Euromaidan.

But the gap between revolutionary promises and institutional reality remained vast. And nowhere was that gap more visible than in the investigation—or failure to investigate—what happened in Odesa on May 2, 2014.

The Glazyev Tapes: Evidence Unused

One of the most striking aspects of the investigation is what wasn’t done with the strongest evidence of Russian involvement. The Glazyev Tapes were intercepted in February-March 2014, before May 2. They were publicly released by Ukrainian security services in March. They documented a senior Putin adviser coordinating and funding destabilization efforts across southern and eastern Ukraine, including specifically in Odesa.

This was exactly the kind of evidence prosecutors dream of: recorded conversations showing intent, coordination, financing, command structure. If you wanted to prove the violence in Odesa was part of a Kremlin-directed operation rather than organic unrest, the Glazyev Tapes provided that proof.

Yet they were barely mentioned in the May 2 investigations. Prosecutors focused on immediate perpetrators—who threw what Molotov cocktails, who fired which guns—not on the broader operation those perpetrators were part of. The investigation treated May 2 as isolated criminal incident rather than as the endpoint of a multi-month destabilization campaign.

Why? Several possibilities suggest themselves:

Complexity: Building a case based on intercepted calls between a Kremlin adviser and various Ukrainian operatives would require:

Authenticating the intercepts
Establishing chain of evidence
Identifying the “operatives” Glazyev was speaking with
Tracing financial transfers
Connecting strategic direction from Moscow to tactical actions in Odesa
Potentially implicating SBU sources and methods

This is sophisticated intelligence work, not standard criminal prosecution. Ukraine’s prosecutors may simply not have been equipped to build such a case.

Political sensitivity: Prosecuting May 2 as Russian state operation would make it geopolitical incident rather than criminal matter. Russia would deny everything, Ukrainian-Russian relations would deteriorate further (they were already catastrophically bad), and Ukraine would be accused of show trials and propaganda.

It might have been easier, politically, to prosecute May 2 as violence between Ukrainian citizens—some pro-Russian, some pro-Ukrainian—rather than as Russian special operation.

Evidentiary limitations: The Glazyev Tapes show Russian support for destabilization efforts broadly. They don’t show specific orders to commit specific acts of violence on May 2. Even if you proved Glazyev funded and coordinated pro-Russian groups in Odesa, you’d still need to prove those groups committed the violence on May 2, and that the violence was following some Moscow-directed plan rather than emerging from local initiative and chaos.

This evidentiary gap—between strategic coordination and tactical violence—might have seemed too large to bridge in criminal prosecution.

Whatever the reasons, the result was that the clearest evidence of Russian operational involvement was effectively excluded from the investigation. May 2 was prosecuted as street violence, not as failed hybrid warfare operation. The individuals who threw Molotov cocktails or fired guns were treated as primary perpetrators, not as foot soldiers in a larger campaign.

This was both technically correct—those individuals did commit those acts—and profoundly incomplete. It’s the difference between prosecuting bank robbers and prosecuting organized crime. Both are legitimate, but one captures the fuller picture.

Historical Analogies: Operations That Failed

May 2, 2014 in Odesa wasn’t the first time an intelligence operation to destabilize a target region failed catastrophically. Historical parallels help contextualize what happened.

The closest analogy might be the Bay of Pigs invasion in 1961. The CIA organized, funded, and trained Cuban exiles to invade Cuba and overthrow Fidel Castro. The operation assumed Cuban population would rise up in support once invasion began. It assumed Castro’s forces would collapse quickly. It assumed US could maintain plausible deniability about its involvement.

All these assumptions were wrong. Cuban population didn’t rise up. Castro’s forces didn’t collapse. US involvement was immediately obvious. The invasion failed within three days, the exiles were killed or captured, and the whole operation became a public humiliation that actually strengthened Castro’s position.

The parallels to Odesa are obvious:

Outside power (Russia/US) organizes and funds local proxies (pro-Russian activists/Cuban exiles)
Operation assumes target population will support intervention
Operation assumes target government will collapse quickly
Operation fails because assumptions are false
Failed operation strengthens target government’s position and discredits outside power

The differences are also illuminating:

Bay of Pigs was overt military invasion (even if CIA-organized), Odesa was hybrid warfare trying to maintain deniability
Bay of Pigs failed in 3 days, Odesa operation unfolded over 3 months
Bay of Pigs was immediately and comprehensively investigated (by Cuba, US, and international observers), Odesa investigation was partial and protracted
Bay of Pigs became cautionary tale taught in intelligence agencies worldwide, Odesa remains contested and poorly understood

Another parallel: the various CIA operations to overthrow leftist governments in Latin America during Cold War. Some succeeded (Guatemala 1954, Chile 1973), some failed (Cuba 1961, Nicaragua 1980s). Success depended heavily on whether local elites and security forces cooperated. Where they did, outside support for opposition forces could tip the balance. Where they didn’t, outside support alone was insufficient.

Odesa’s elite non-cooperation fits this pattern. Like the Sandinista government in Nicaragua, which survived CIA-backed Contra insurgency partly because it maintained sufficient elite support, Ukraine’s government in Odesa survived Russian-backed destabilization partly because local elites refused to defect.

The historical lesson: hybrid warfare operations have to be hybrid. They require both outside support (funding, training, coordination, sometimes direct military backup) and inside cooperation (elite defection, security force complicity, popular support). Without both, they fail.

Russia had the outside support ready for Odesa. But it couldn’t generate the inside cooperation. And so the operation failed.

The Fire That Failed: Why This Story Matters

This investigation, this article, exists because what happened in Odesa on May 2, 2014 matters in ways that transcend the immediate tragedy of 48 deaths.

It matters because it was a test case: could hybrid warfare destabilize a major Ukrainian city that wasn’t predisposed to separatism? The answer was no. That answer shaped the conflict that followed. Russia didn’t attempt similar operations in Dnipro, Zaporizhzhia, Mykolaiv, or Kherson in 2014 because Odesa had shown such operations would fail without the specific conditions that existed in Donbas.

(Note: Russia did eventually invade and temporarily occupy Kherson and parts of other southern oblasts in 2022, but that was overt military invasion, not hybrid warfare attempting to create “people’s republics” through local proxies.)

It matters because the investigation’s failures illuminated limitations of Ukraine’s post-Maidan state. Euromaidan promised rule of law and official accountability. May 2 investigation delivered selective prosecution and elite impunity. Understanding that gap between promise and reality is essential to understanding Ukraine’s democratization struggle.

It matters because the information warfare around May 2 exemplifies how Russia uses real tragedies to construct false narratives. Forty-eight people really died. But the story of how they died—in Russian telling—bore little resemblance to what actually happened. Analyzing how that narrative was constructed and propagated provides insight into Russian information operations more broadly.

It matters because hybrid warfare didn’t end in 2014. Russia has used similar approaches in Syria, Libya, Central African Republic, and elsewhere. Understanding why it failed in Odesa—what factors determine success or failure—helps anticipate where similar operations might succeed or fail in future.

And it matters because justice incomplete is justice denied. The victims of May 2—on all sides, killed in street fighting or trapped in burning building—deserve full accounting of how they died and who bears responsibility. Their families deserve closure. Ukrainian society deserves truth.

Seven years later, they still haven’t received any of those things. This investigation, built on the Glazyev Tapes, the Council of Europe findings, the 2 May Group’s research, and hundreds of hours of video footage, attempts to provide what the official investigation couldn’t or wouldn’t: a comprehensive account of what happened, why it happened, and why accountability failed.

The fire that killed 42 people in the Trade Unions Building on May 2, 2014 was a tragedy. But the operation that fire ended was a failure—a failure that helped save Ukraine. Understanding that failure, in all its complexity, is worth the effort.

Because the next time Russia or any other power attempts hybrid warfare against a target that isn’t fully prepared, that target’s best chance of survival will be learning from the places where hybrid warfare failed. And in 2014, it failed in Odesa.

The fire failed to achieve its purpose. The operation failed to achieve its objectives. And the investigation failed to achieve justice. Three failures, three different kinds, three different meanings.

This is the story of all three.

Chris Sampson is an independent investigative journalist covering hybrid warfare, intelligence operations, and democratization in post-Soviet states. This investigation was supported by the Glazyev Tapes Archive Project and the Ukrainian Crisis Media Center.

Sources and Methodology Note:

This investigation draws primarily on:

The Glazyev Tapes (intercepted conversations, February-March 2014)
Council of Europe International Advisory Panel Report (March 2016)
Ukrainian Ombudsperson inquiry reports (2014-2015)
Verkhovna Rada Temporary Investigation Commission Report (September 2014)
2 May Group investigation and forensic analysis (2014-2015)
Court documents and official statements from Ukrainian authorities
Contemporaneous media coverage and video documentation
Interviews with witnesses, investigators, and civil society representatives

All intercepted communications are cited from Ukrainian Security Service releases and have been authenticated by multiple independent analysts. All official documents are cited from public records. Video footage is cited from timestamped publicly available sources.

The investigation has been reviewed for accuracy by experts in hybrid warfare, post-Soviet politics, and Ukrainian law. Any remaining errors are the author’s alone.

THE WIRE TAP

THE FIRE THAT FAILED: THE ODESA TRADE HOUSE…