Ukrainian Operative Sets Russian Su-30 Jets on Fire in Daring Lipetsk Air Base Sabotage

Ukrainian military intelligence said a resistance operative set fire to two Russian fighter aircraft inside a hangar at Lipetsk Air Base in western Russia, roughly 340 kilometers, or about 210 miles, from the Ukrainian border. Defense officials confirm the public case rests on a short video released by Ukraine and on Ukrainian statements issued the same day. Russian authorities had not publicly confirmed aircraft losses in the reporting reviewed by publication time.

Lipetsk Air Base sabotage video shows fire started on parked fighters inside a hangar

Ukraine’s Defense Intelligence Directorate said the strike took place on the night of Dec. 20-21 and was carried out by “a representative of the resistance movement” inside Russia. The service said planning took two weeks and that the operative studied patrol patterns and guard changes before entering the base, reaching the aircraft, and leaving without detection. Ukrainian reporting first described the targets as one Su-30 and one Su-27, then later corrected the claim to two Su-30s.

The released footage shows a person moving close to parked Flanker-series aircraft inside a shelter, sitting in at least one cockpit, and placing or applying an ignition source near a main landing gear area. Flames then spread upward into the side of the fuselage and the intake area. The video does not show the full burn sequence for both aircraft, and it does not provide a timestamp, a wide establishing view of the hangar, or any post-fire inspection shots.

Ukraine’s intelligence service said the aircraft were “put out of action” and valued the damage at up to $100 million. The wording stopped short of an unambiguous destruction claim in the technical sense. Contemporary reporting outside the official statement described the damage as serious, but no imagery released on Dec. 22 established whether either airframe was beyond repair.

Ukraine’s official account stressed how the breach happened. One translated version of the agency statement said the operative succeeded after “Studying the patrol route and guard change schedule.” Another cited line from the same account said the saboteur was able to enter the facility, strike the aircraft in a protective hangar, and leave the airfield unhindered. Those details, if accurate, point less to stand-off strike tactics and more to a close-access security failure at a guarded military base deep behind the front.

Red 12 and Red 82 point to Su-30SM fighters after Ukraine first named a Su-27

The visual debate turned on two details in the released video. Close shots showed red tail numbers “12” and “82.” Other frames showed a canard foreplane on the aircraft that caught fire. According to industry sources and open-source airframe analysis published the same day, those features line up with Su-30SM fighters rather than a mixed Su-27 and Su-30 pair.

One reason the identification shifted quickly is simple. A Su-30SM carries canards, while a standard Su-27UB does not. Reporting that reviewed the video frame by frame said the “12 red” aircraft matches Su-30SM RF-95838 and the “82 red” aircraft matches Su-30SM RF-81740. Ukraine’s intelligence service eventually moved in the same direction and said the two damaged aircraft were both Su-30s.

At least one of the jets seen in the footage was not stripped down or obviously derelict. The video showed underwing air-to-air missiles on one aircraft, and the cockpit and surrounding surfaces did not look like long-term storage. That does not prove the aircraft were mission-ready at the exact moment of the sabotage, but it does support the judgment that the targets were current operational airframes rather than museum pieces or range hulks.

A fire that begins at the landing gear and then reaches the intake section can leave outcomes that range from localized burn damage to a near-total write-off, depending on how far heat, smoke, and suppressant agents travel through wiring, hydraulics, engine components, and avionics bays. None of that can be confirmed from the available clip. Public reporting on Dec. 22 offered no repair assessment, no satellite imagery, and no Russian-side maintenance or recovery photos.

Lipetsk 4th State Center role gives the damaged aircraft unusual weight inside Russian tactical aviation

Lipetsk is not just another parking base. Reporting on the Dec. 22 incident described the airfield as home to the 4th State Air Personnel Preparation and Military Evaluation Center, one of the Russian Aerospace Forces’ main hubs for testing, evaluation, and combat training on tactical aircraft. The same reporting said the resident 968th Research Instructor Composite Aviation Regiment has historically handled first batches of several newer combat types, including the Su-34, Yak-130, Su-30SM, and Su-35S.

That role changes how aircraft losses there are read. Lipetsk supports pilot instruction, tactics work, and evaluation activity in addition to routine flying. Damage to aircraft at such a base does not carry the same meaning as damage at a storage annex or a rear-area transit stop. A sabotage breach there touches aircraft security, base protection, and the credibility of a site tied to training and doctrinal development.

Contemporaneous reporting also said the “12 red” and “82 red” aircraft were not regular residents of Lipetsk. One analysis linked them to the 14th and 31st Fighter Aviation Regiments rather than to the base’s standing training unit. That finding has not been confirmed by a Russian official source, but if correct it would suggest the airfield was hosting active fleet aircraft beyond its own resident instructional mix.

Earlier in the war, Lipetsk had already drawn Ukrainian attention as a valuable rear-area aviation site. Reuters reported in August 2024 that Ukraine struck the Lipetsk region airfield and said aircraft including Su-34s, Su-35s, and MiG-31s were stationed there. Ukrainian forces also said they targeted storage and support areas at Lipetsk in October 2024. The Dec. 22 sabotage claim therefore fits an established Ukrainian view of the base as a useful target set, even before this latest breach inside a hangar.

Belbek drone raids and the Lipetsk arson case show aircraft on the ground remain vulnerable

Lipetsk came under scrutiny only days after two separate Ukrainian attacks on Belbek Air Base in occupied Crimea. On Dec. 18, Ukraine’s Security Service said long-range drones hit air defense assets and a MiG-31 at Belbek. On Dec. 20, the same service said drones struck two Su-27 fighters there. Those claims remain Ukrainian claims, but they show how the pressure on Russian aircraft has continued through both stand-off drone attacks and close-access sabotage.

The two Belbek episodes and the Lipetsk sabotage were not copies of each other. Belbek was presented as a remote drone effort against aircraft and radars on an occupied peninsula. Lipetsk was presented as a covert penetration by a resistance operative inside Russia proper. Ukraine used different tools, different access methods, and different target environments within a span of days.

Recent Ukrainian operations have kept pushing at the same weak point in Russian airpower, which is the period when aircraft sit on the ground between sorties, inspections, and shelter movements. Hangars, dispersal pads, and taxi areas reduce exposure, but they do not remove it. Once a saboteur or a drone gets close enough, the cost exchange turns sharply against the defender, since a small fire source or a light warhead can threaten an aircraft worth tens of millions of dollars.

Russia’s silence on the Lipetsk case, at least in the public reporting available on Dec. 22, leaves the full outcome unresolved. Ukraine’s side supplied the video, the timeline, and the account of how the operative entered and left. Independent confirmation of final aircraft condition had not appeared by the time of publication. The Defense-Aerospace editorial team reviewed the released footage and the day’s reporting. Our analysis shows the clearest established point is not the final repair bill. It is that a saboteur appears to have reached two Russian Flankers inside a protected shelter at one of the VKS’s most important tactical aviation bases.

Ukrainian Operative Sets Russian Su-30 Jets on Fire in Daring Lipetsk Air Base Sabotage

Lipetsk Air Base sabotage video shows fire started on parked fighters inside a hangar

Red 12 and Red 82 point to Su-30SM fighters after Ukraine first named a Su-27

Lipetsk 4th State Center role gives the damaged aircraft unusual weight inside Russian tactical aviation

Belbek drone raids and the Lipetsk arson case show aircraft on the ground remain vulnerable

REFERENCE SOURCES

Don't Miss

Italy Gains In‑Country Multi‑Sensor Calibration Center from L3Harris, ELT Group

The Netherlands Buy Additional F-35 Fighter Aircraft