In depth | Bilohorivka Crossing — when should the defender fire at a crossing it saw coming?

2026-08-13 · 2022-05-07 – 2022-05-13

Overview

Part 1: The Bilohorivka Crossing (May 2022) traced the big idea: prediction and timing. This piece asks what ground and information those judgements rested on. Early on 8 May the Russian 74th Motor Rifle Brigade bridged the bend west of Bilohorivka; Ukrainian forces confirmed the bridge, then massed fire on it and on the columns on both banks [1][2]. The Russians bridged again over the next days and were back on the north bank by the 13th [4][11]. Below we take the scenario's phases p1–p7 and what-if branches x1 and x2 in turn.

Strategic and operational context

By early May 2022 Russia was trying to encircle Lysychansk and Sievierodonetsk [2]. Bilohorivka was the northern jaw of the pincer, Popasna the southern [11]. A crossing here threatened the Lysychansk–Bakhmut highway; on 9 May the head of the Luhansk regional military administration warned that losing it could cut off both cities [8]. The attacker was the 74th Motor Rifle Brigade of the 41st Combined Arms Army [1][2]. The US Army's Infantry article argues that Russian commanders were under pressure to report gains [1], and the UK Ministry of Defence called the crossing "a highly risky manoeuvre" that showed that pressure (UK government assessment) [4][5]. Unable to cover the whole river, the Ukrainians first narrowed down where the enemy would cross: phase p1.

Terrain and weather in detail (OAKOC)

Figure 1. The Bilohorivka area and a north–south profile (approximate). Elevation sampled from the Copernicus DEM [18]; river follows the OpenStreetMap waterway [18]; unit positions estimated from open sources. May 2022 only — own work, after sources 1, 2, 7, 11, 14

Observation. Sampling the Copernicus elevation model at about 0.7 km spacing puts the water at 55–70 m above sea level, a step at 125–140 m within 1–2 km to the south, and heights of 180–215 m some 4–6 km south [18]. Opposite Bilohorivka the north bank is low ground at 60–75 m for several kilometres. The south looks down on the river; the north cannot see past the southern step. Hence the Ukrainians stayed on the heights and left the bank empty [1]. Yet it was drones, not height, that found the bridge through the fog [2][7].

Avenues of approach. Forest tracks led from the north-bank woods to the water; across it, a route climbs to the heights and the highway [8]. From OpenStreetMap coordinates, Hryhorivka lies about 4.5 km west of Bilohorivka, Serebrianka 8.7 km and Dronivka 15 km, with Lysychansk 13 km east [18]. Every reported crossing site falls in that stretch [11][14].

Key terrain. What mattered was the few stretches of bank that could take a pontoon bridge. The bend the Russians chose had gentle slopes on both banks and lay below the Ukrainian ground, a site straight out of the manual, which made the defender's sums easier [1].

Obstacles. With an average depth of about 2.4 m, tanks could not ford [1]. A Ukrainian engineer reckoned the bridge needed at least eight sections and two hours' work [7]. Later, wrecked pontoons choked the bank [11].

Cover and concealment. The woods hid the assembly areas, but the last stretch to the water was open, and spring foliage gave no continuous overhead cover [1]. The Russians used smoke grenades and set fields and forest alight; there was fog too [7]. ERA5 reanalysis agrees: no rain from 5 to 8 May, and at 0500 on the 8th 2.2°C, 75% humidity, wind about 2.6 m/s and no low cloud [17], good conditions for valley radiation fog. The roughly 25 km grid cannot show the river fog itself. Sunrise was at 0455 Kyiv time [17].

Order of battle and command relationships

Side	Echelon	Unit or element	Notes	Source
Ukraine	Brigade	80th Separate Air Assault Brigade	Companies of the 1st and 3rd Battalions; claimed nine attempts stopped	[6][11][14]
Ukraine	Artillery	17th Tank Brigade gunners; 26th Artillery Brigade elements	Credited with the bridge strikes	[10][14]
Ukraine	Armour, infantry	30th Mechanised Brigade tanks; 15th Bn, 128th Brigade	Bridgehead, adjacent sector	[14]
Ukraine	Engineers, air	Engineer/EOD officer and scouts; Air Force	Site analysis 7–8 May; bombing	[1][7]
Ukraine	Battalion	Defending battalion (scenario)	Drone team, engineer scouts	Scenario
Russia	Army, brigade	41st CAA; 74th Motor Rifle Brigade	At least one BTG (UK MoD), two (Ukrainian journalist)	[1][4][11]
Russia	Brigade	35th Motor Rifle Brigade (elements)	Losses claimed by an open-source group	[11]
Russia	Engineers	Pontoon units	PMP trucks, BMK boats, a PTS-3	[11]
Russia	Air defence	None	Nothing covered the crossing	[1][2]

The gaps matter most: nothing on the Russian side covered air defence, counter-battery fire or the far bank [1][2]. The Protection Professional Bulletin (PPB) calls the Russian belief in an unopposed crossing a costly error [2].

Timeline

5–7 May: Dronivka and the reconnaissance

A Russian attempt near Dronivka on 5 May was reportedly stopped; it appears only in Ukrainian-side accounts [11][14]. On the 7th Ukrainian engineers began reconnaissance [2]. An engineer officer surveyed Bilohorivka and Hryhorivka, picked the likely sites, and told commanders to listen for the motor boats that push pontoon sections into place [7].

8 May: engines, fog, about twenty minutes

Early on the 8th, boat engines were heard where he had predicted [7]. Sunrise was at 0455 [17]. Through fog and smoke the drones saw the bridge going in, seven of eight sections in place [7]. Ukrainian artillery then waited about 20 minutes while vehicles bunched on the bridge and approaches before opening fire [1]; aviation followed, hitting the remains and a second bridge [7]. The Russians who had crossed halted in the low ground [1].

9–14 May: new bridges and withdrawal

On the 9th, 30–50 vehicles and infantry were stranded on the south bank, according to the engineer [7]. A BlackSky image of the 10th shows a Russian bridge just after a barrage, and CNN reported two bridges cut in 24 hours [16]. On the 11th the Ministry of Defence said the crossings had been destroyed "again" (Ukrainian government claim) [10]. On the 12th an open-source analyst counted 73 Russian vehicles destroyed or abandoned [9][12]. On the 13th the UK MoD assessed the loss of significant armoured elements of at least one BTG and its bridging equipment [4][5], and the 80th Brigade claimed nine attempts foiled [11]. By the 14th the Russians were back on the north bank [11].

The decision points in depth

Chart with 5–14 May along the bottom and four rows: Russian actions, decision points p1–p7 with what-if branches, source confidence, and weather with daily rain. 8 May is stretched out by the hour — Figure 2. Decision points and source confidence. Colour shows the strongest evidence behind each event. Times follow the training scenario; weather is a c. 25 km reanalysis grid [17] — own work

p1 Where will they cross? (7 May, 0900)

Knew: the Dronivka attempt had failed and the enemy was massing again; engineers rated the bend west of Bilohorivka best (B2); little enemy air defence was reported (C3). Options: troops forward on the bank; posts spread evenly; observers and drones on likely sites with the main body on the heights and fires pre-planned; shell the woods first. Decision: the third. The Ukrainians concentrated on the predicted sites and kept off the bank, avoiding direct fire and lulling the Russians [1]. Otherwise: troops on the bank would face fire from the woods and give the enemy a reason to move. Shelling the woods blind risked exposing the registered targets.

p2 Engines in the dark (8 May, 0300)

Knew: engines downstream, nothing visible, fog forming, drones only at first light. Options: fire now; wait and confirm by drone; send scouts or a company to the bank. Decision: wait. The drones confirmed the bridging [2][7], and if the bridge needed two hours or more [7], waiting cost little. Otherwise: firing blind might persuade the enemy his site was blown and send him elsewhere, throwing away the defender's best card: knowing where he would come.

p3 A bridge in the fog (8 May, 0600)

Knew: seven of eight sections in, vehicles queuing [7]; one massed strike meant a wait for the next. Options: fire at once; wait for vehicles to bunch, then mass artillery and air; counterattack; hold until the smoke lifts. Decision: wait, then mass. Fire began about 20 minutes after confirmation [1]. Otherwise: firing at once saves the enemy equipment for the next try; holding until the smoke clears risks the bridgehead growing. That is branch x1.

x1 The bridgehead holds (what-if)

The bridge stands and vehicles trickle across. The scenario's answer is to cut the bridge first, then turn on the bridgehead, as FM 3-90 has higher echelons isolate crossing sites while local units counterattack [3, para 9-57].

p4 Enemy on your bank (8 May, 1100)

Knew: the bridge was badly damaged; the enemy across was digging in low, not climbing; no counter-battery fire. Options: keep striking from the heights; counterattack with reserve and tanks; direct fire only; switch to the north-bank columns. Decision: the US Army reads it as fires alone, with no ground counterattack [1]. The 80th Brigade commander, though, later described infantry falling back and then counterattacking tanks that had crossed [14]. Otherwise: FM 3-90 says counterattack bridgeheads "immediately", yet allows waiting to mass overwhelming power, warning that waiting lets a bridgehead harden [3, paras 9-57–9-58].

p5 Stranded at a broken bridge (9 May, 0700)

Knew: the first bridge was cut, troops were stranded, new sections were coming. Options: keep the drones on and send the air sortie at the new work; clear the low ground; watch only; move drones upstream early. Decision: the first. Some 30–50 vehicles sat stranded [7]; the regional head said artillery dealt with those who reached the bank [9]. Otherwise: moving upstream would have anticipated the shift to Serebrianka, but on the 9th the enemy was still at the bend.

p6 The bridges come again (10–11 May)

Knew: same place, same method; two or three massed strikes left; a weak report of enemy air defence (F6). Options: strike each new bridge; seize the bridge end; fall back; hold fire until the enemy is firmly across. Decision: strike each bridge [10][16]. The Russians handed over the same target again. Otherwise: waiting saves rounds, but a foothold costs far more fire to remove than a bridge. The scenario links that failure to x2.

p7 The last bridge, toward Serebrianka (12 May)

Knew: the bend was choked; bridging gear was moving upstream (B2); smoke and vehicle noise at the old bend might be a feint (C3). Options: shift drones and guns upstream, leaving observers; leave the new site to the air force; send a company; treat the move as a feint. Decision: the brigade commander confirms attempts near Serebrianka [14], but the date and the cutting of a bridge there rest on the reporting used in Part 1. Otherwise: for once the Russians changed site and screened the old one. Treating it as a feint would have followed the smoke. B2 against C3 decided it.

x2 A foothold in the west (what-if)

A company digs in beside a standing bridge. The scenario prefers isolating it by fire on the bridge; containing it from the ridge to await the reserve is the "delay the counterattack" choice of para 9-58 [3].

Animated map of the seven phases from 5 to 13 May: the bridge going in, massed fire, re-bridging and new strikes, and a withdrawal north. The still frame shows 13 May — Figure 3. The phases in motion (16-second loop; with reduced motion only the final state shows). Positions approximate — own work, after sources 1, 2, 7–12, 14, 16

Reading it against doctrine

Gap crossing (FM 3-90, chapter 18). A crossing force must bunch at crossing points and re-form on the far side, vulnerable all the while, and needs "a force dedicated to the security of the bridgehead" [3, paras 18-40–18-41]. Gaps over about 20 m normally call for a deliberate crossing, with detailed reconnaissance, coordinated fire plans and rehearsals; a division is normally the smallest unit for a deliberate wet-gap crossing. Hasty crossings are for weak resistance, at several sites on a broad front [3, paras 18-44–18-49, 18-71]. The Russians crossed with a brigade, hastily, at one site. The PPB article adds that they misjudged this as an unopposed water-barrier assault in Russian doctrinal terms (citing ATP 7-100.1) [2].

SOSRA (para 18-23). Of suppress, obscure, secure, reduce and assault, the PPB finds no suppression, attempted obscuration and ignored security, and links the last directly to the BTG's loss [2]. The "advance from the far side" phase exists to remove "direct and observed indirect fires into the crossing area" [3, table 18-3]; without the southern heights, that is exactly what the Russians bridged under.

Russian principles and protection. Drawing on a 2019 Foreign Military Studies Office study, the Infantry article notes that Russian doctrine itself demands a broad front, fast tempo, air defence, heavy preparatory fire and counter-battery fire [1]. The failure was of means and time more than knowledge, though the reasons remain unconfirmed [1]. Through ADP 3-37's protection lens, no dispersion bunched the vehicles, no air defence let drones cue the guns, and no security on both banks doomed the bridgehead [2].

The defender (paras 9-50, 9-56–9-58, 8-52). FM 3-90 notes that a river cannot be held in strength along its whole length, so economy of force is needed [3, para 9-58]. The Ukrainians covered the river with observation and pre-planned fire, kept troops on the heights and isolated bridgeheads by cutting bridges. They also struck the crossing equipment, as para 9-50 suggests: the tally includes five PMP trucks and two BMK boats [11].

Source criticism

River width. The PPB gives 80 m [2]; the Infantry article gives 115–230 feet (35–70 m) in one place and over 260 feet (about 80 m) in another [1], as does Newsweek [7]. For the bridging site, the engineer's figure and the PPB's 80 m are the better guide.

Number of attempts. Reports of five were flagged by DFRLab as unverified [12]; the 80th Brigade claimed nine across its sector over a week [11][14]. The counts probably measure different things.

"About 20 minutes". Part 1 attributed this to Newsweek, but Newsweek gives no waiting time [7]. The figure is in the Infantry article [1], which cites Newsweek and The Times for the engineer's words; we could not check The Times. The wait is well supported; its length is one man's estimate.

Ground counterattack. The Infantry article says there was none [1]. The 80th Brigade commander described about 20 tanks crossing once, infantry falling back, then counterattacking to destroy five or six, and a bridgehead up to 2.5 km deep [14]. The article leans on press reports; the commander spoke two months later from one unit's view. With nine attempts over a week, both may be right for different days.

Russian fire. "No counter-battery support" [1] sits beside the commander's "wall of fire" of rockets, howitzers, tanks and mortars [14]. Russian fire was plentiful but apparently not organised to find the Ukrainian guns at the moment of crossing.

Equipment losses. Counts grew: DFRLab's first estimate of at least six tanks and 14 BMPs [12], 73 vehicles on 12 May [9][12], 82 plus two boats on 13 May [11], and 50–70 per The Times via the Infantry article [1]. We use the geolocated 12 May count. Personnel estimates vary too widely to use.

Russian claims. Nothing geolocated supports the Russian MoD's 14 May claim [13], while DFRLab checked the Ukrainian images against Planet satellite imagery [12].

Lessons

Find the place the enemy has to use. A day of engineer reconnaissance made up for a shortage of troops [1][7].
Waiting only works while the watch holds. Lose the drones and waiting hands over a bridgehead.
Short of fire, hit the bridge first. Cut it and the bridgehead isolates itself [3, para 9-57].
As the attacker, take the far side first. Without it, the crossing sits under observed fire [2].
Watch for the enemy who stops repeating himself (p7).

Open questions

Exact dates and sites of each attempt, especially Dronivka and Serebrianka.
How long the Ukrainians actually waited, and whether and where they counterattacked on the ground.
Why the Russians crossed at one site without air defence [1]; Ukrainian losses.
The scenario's battalion decisions and times are a training reconstruction.

Further viewing

Drone footage released by Ukrainian forces of a wrecked pontoon bridge and Russian vehicles on both banks

Video: Ukraine — drone footage shows destroyed bridge and vehicles at Donbas river crossing · Guardian News, 2022

CNN report on two Russian pontoon bridges cut near Bilohorivka, with a 10 May satellite image

Video: Ukraine blows up two Russian pontoon bridges · CNN, 2022

Command the defending battalion in the training scenario "Bilohorivka Crossing". When you fire, and at what, decides it.

Sources

Kyle D. Kindy, "Russian River Crossing Failure During the Battle of the Siverskyi Donets", Infantry, Spring 2025, US Army (army.mil, 31 Mar 2025). https://www.army.mil/article/284080/russian_river_crossing_failure_during_the_battle_of_the_siverskyi_donets (accessed 14 Oct 2026)
Peter J. Witcomb, "Failure to Consider Protection in Large-Scale Combat Operations: The Siverskyi Donets River Crossing", Protection Professional Bulletin, US Army Maneuver Support Center of Excellence, 16 Sep 2025. https://home.army.mil/wood/contact/publications/ppb/Failure-to-Consider-Protection-in-Large-Scale-Combat-Operations-The-Siverskyi-Donets-River-Crossing (accessed 14 Oct 2026)
Headquarters, Department of the Army, FM 3-90 Tactics, 1 May 2023 (paras 9-50, 9-56–9-58, 18-23, 18-40–18-49, 18-71, table 18-3). https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN38160-FM_3-90-000-WEB-1.pdf (accessed 14 Oct 2026)
Radio Free Europe/Radio Liberty, "Ukrainian Forces Appear To Destroy Russian Armored Battalion; Scholz Urges Cease-Fire In Call With Putin", 13 May 2022 (reporting the UK MoD intelligence update of 13 May; UK government assessment). https://www.rferl.org/a/ukraine-russian-advances-halted-war-crimes/31847676.html (accessed 14 Oct 2026)
Oleksandr Stashevskyi and David Keyton, "Russia takes losses in failed river crossing, officials say", Associated Press (via WHYY), 13 May 2022. https://whyy.org/articles/russia-losses-failed-river-crossing-ukraine-war/ (accessed 14 Oct 2026)
Patrick Galey and Sara Mhaidli, "Ukraine says it blew up Russian pontoon bridges over a key river — and units trying to cross it", NBC News, 12 May 2022. https://www.nbcnews.com/news/world/ukrainian-military-says-destroyed-russian-pontoon-bridges-strategic-wi-rcna28466 (accessed 14 Oct 2026)
Giulia Carbonaro, "Ukrainian Soldier Reveals How He Secretly Blew Up Russian Bridge", Newsweek, 12 May 2022 (account of a Ukrainian engineer officer). https://www.newsweek.com/ukrainian-soldier-reveals-how-he-secretly-blew-russian-bridge-1706083 (accessed 14 Oct 2026)
Olivia Sapwood, "The Russian troops crossed the Siverskyi Donets river, but the pontoon crossing is already destroyed", Militarnyi, 9 May 2022 (statement by the head of the Luhansk regional military administration). https://militarnyi.com/en/news/the-russian-troops-crossed-the-siverskyi-donets-river-but-the-pontoon-crossing-is-already-destroyed-haidai (accessed 14 Oct 2026)
Vadim Kushnikov, "In Bilohorivka, the invaders lost more than 70 units of equipment after forcing the river", Militarnyi, 12 May 2022. https://militarnyi.com/en/news/in-bilohorivka-the-invaders-lost-more-than-70-units-of-equipment-after-forcing-the-river/ (accessed 14 Oct 2026)
Kateryna Tyshchenko, "Luhansk region: Armed Forces of Ukraine destroy the occupiers' crossings across the Siverskyi Donets river", Ukrainska Pravda, 11 May 2022 (Ukrainian MoD claim). https://www.pravda.com.ua/eng/news/2022/05/11/7345599/ (accessed 14 Oct 2026)
Yuri Zoria, "Russian troops suffer epic fail while attempting to cross river at Bilohorivka", Euromaidan Press, 15 May 2022. https://euromaidanpress.com/?p=167058 (accessed 14 Oct 2026)
Digital Forensic Research Lab (Atlantic Council), "Russian War Report: Drone footage confirms failed Russian military pontoon crossing", 13 May 2022. https://dfrlab.org/2022/05/13/russian-war-report-drone-footage-confirms-failed-russian-military-pontoon-crossing/ (accessed 14 Oct 2026)
Novaya Gazeta Europe, "Russian forces destroy pontoon bridge over Siversky Donets River, Russian Defence Ministry claims. Experts earlier reported huge losses among Russian troops in this area", 14 May 2022 (Russian MoD claim). https://novayagazeta.eu/articles/2022/05/14/russian-forces-destroy-pontoon-bridge-over-siversky-donets-river-russian-defence-ministry-claims-experts-earlier-reported-huge-losses-among-russian-troops-in-this-area-news (accessed 14 Oct 2026)
Alina Lohvynenko and Serhii Lysenko, interview with the commander of the 80th Separate Air Assault Brigade, Ukrinform, 22 Jul 2022 (commander's account). https://www.ukrinform.net/rubric-ato/3534862-commander-of-the-80th-separate-air-assault-brigade.html (accessed 14 Oct 2026)
Guardian News, "Ukraine: drone footage shows destroyed bridge and vehicles at Donbas river crossing", YouTube, 13 May 2022. https://www.youtube.com/watch?v=j0O6zZtx-Bo (accessed 14 Oct 2026)
CNN, "Ukraine blows up two Russian pontoon bridges", YouTube, 11 May 2022 (includes BlackSky satellite image of 10 May). https://www.youtube.com/watch?v=gZ7l2VqGoyM (accessed 14 Oct 2026)
Open-Meteo, Historical Weather API (ERA5 reanalysis), 48.93°N 38.22°E, hourly and daily data for 5–13 May 2022. https://archive-api.open-meteo.com/v1/archive?latitude=48.93&longitude=38.22&start_date=2022-05-05&end_date=2022-05-13&daily=sunrise,sunset,precipitation_sum&hourly=relative_humidity_2m,temperature_2m,cloud_cover_low,wind_speed_10m&timezone=Europe%2FKyiv (accessed 14 Oct 2026)
Open-Meteo, Elevation API (Copernicus DEM 90 m), grid sample over 38.02–38.46°E and 48.86–49.00°N, and OpenStreetMap Nominatim place coordinates and the Siverskyi Donets waterway line. https://api.open-meteo.com/v1/elevation?latitude=48.93&longitude=38.22 · https://nominatim.openstreetmap.org/search?format=json&q=Bilohorivka (accessed 14 Oct 2026)
Wikimedia Commons, "Siverskyi Donets (Sep 2021) 1.jpg" (QAtlantic.mn, CC BY-SA 4.0). https://commons.wikimedia.org/wiki/File:Siverskyi_Donets_(Sep_2021)_1.jpg (accessed 14 Oct 2026)
Wikimedia Commons, "KrAZ-255 PMP Pontoon Bridge.jpg" (Zinnsoldat, CC BY-SA 4.0). https://commons.wikimedia.org/wiki/File:KrAZ-255_PMP_Pontoon_Bridge.jpg (accessed 14 Oct 2026)