Daily intelligence

UAF Strikes Belgorod Command Node as Russia Deploys FAB-3000 Glide Bombs

Published Intelligence Summary & Geospatial Analysis
Report number
630

At a glance

Counts of the stored claim records and follow-up, not a summary of the narrative. How to read these labels

Coverage window
Not stored for this report.
Follow-up investigation
None stored for this report.
Claim records by status
This report has no claim records.
Claim records by confidence
This report has no claim records.
SAR measurements
None supplied to this report. No SAR measurements for this period does not mean that monitored sites were unchanged.
Frontline map data
Age of the map data is not available.

Read with these limits in mind

  • This report is machine-generated from open sources and may contain errors.
  • A source’s publication time is not the time of the event it describes.
  • Frontline map data can lag the reporting period; map dates do not establish when territory changed.
  • No SAR measurements for this period does not mean that monitored sites were unchanged.

Intelligence Summary

Machine-generated narrative. Labels inside it are written by the model. How to read these labels

Strategic Overview

Reciprocal deep strikes defined the current reporting period. The Ukrainian Armed Forces (UAF) executed a direct UAV strike on the Belgorod regional administration building, continuing an interdiction campaign against Russian administrative and industrial nodes. In response, Russian forces sustained infrastructure strikes in Kryvyi Rih and escalated tactical aviation strikes by deploying a 3,000kg FAB-3000 glide bomb against a UAF position in Konstantinovka.

The operational environment across the line of contact is currently degraded by widespread rain and heavy overcast conditions. This weather front is actively suppressing tactical FPV and optical ISR drone operations, forcing a transition to ground-based sensors and infantry-led probes. Concurrently, Russian forces are increasingly deploying specialized Spetsnaz units for FPV-on-UAV interception to counter UAF reconnaissance advantages.

Operational Updates

  • Northern / North-Eastern Sector (Sumy, Kharkiv): The Russian Ministry of Defense claims elements of the 44th Army Corps captured Malaya Korchakovka in the Sumy region. In Kharkiv, authorities issued emergency warnings regarding Russian deployment of PTAB-2.5 "bell-shaped" cluster submunitions. Weather in Kharkiv / Vovchansk (15.7°C, light rain, 97% cloud cover) is severely restricting tactical air operations. UAF forces executed a cross-border MLRS strike on Suzemka in the Bryansk region.
  • Eastern Sector (Donetsk, Luhansk): Russian aviation utilized a FAB-3000 with a UMPK glide kit against a UAF point of temporary deployment in Konstantinovka, marking a significant escalation in ordnance weight. Russian psychological operations (PSYOP) are heavily promoting a narrative of a 60-day "ultimatum" for UAF withdrawal from the Donbas. Weather in Donetsk / Pokrovsk is 13.9°C with 90% overcast, hindering satellite and high-altitude ISR.
  • Central / Southern Sector (Dnipropetrovsk, Zaporizhzhia, Kherson): Russian forces launched coordinated kinetic strikes on infrastructure in Kryvyi Rih. The Russian 14th Guards Spetsnaz Brigade is actively utilizing FPV drones to intercept UAF reconnaissance UAVs in the Dnipropetrovsk sector. Russian guided aerial bombs (KAB) were launched toward Zaporizhzhia, while Shahed loitering munitions transited the Black Sea toward Tatarbunary (Odesa). Weather in Kherson (11.7°C, 98% cloud cover, light rain) is rapidly degrading unpaved supply routes.

SAR Intelligence (Satellite Data)

  • High Priority: CRITICAL deviations from baseline activity were detected across Long-Range Aviation and Northern Fleet assets. Anomalies were recorded at AB Severomorsk-1 (Score: 0.52), AB Monchegorsk (Score: 0.20), and within elements of the 45th Air and Air Defense Forces Army (including the 830th and 403rd Aviation Regiments). HIGH anomalies were noted at AB Olenya (Score: 0.15) and AB Kacha. A CRITICAL anomaly was also detected at the 153rd Separate Special Purpose Radio-Technical Brigade (GRU).
  • Analysis: The widespread anomalies across Northern Fleet aviation and strategic bomber bases (AB Olenya, AB Monchegorsk, AB Severomorsk-1) align with established Emission Control (EMCON) signatures that typically precede massed Long-Range Aviation missile sorties. The disruption at the 153rd GRU Brigade suggests heightened electronic warfare or SIGINT mobilization.

Equipment & Losses

  • Kinetic Strikes: UAF UAV successfully struck the main entrance of the regional administration building in Belgorod, Russia.
  • Industrial Attrition: Fatalities at the Nizhnekamskneftekhim facility in Tatarstan rose to three following secondary explosions from a previous UAF strike.
  • Heavy Ordnance: Visual evidence confirms Russian deployment of a FAB-3000 glide bomb in Konstantinovka.
  • UAF Drone Operations: The UAF 7th Air Assault Corps reported inflicting approximately 2,000 Russian casualties via coordinated drone operations throughout March.

Confidence Check

  • HIGH: UAF drone strike on Belgorod administration; Russian infrastructure strikes in Kryvyi Rih; weather conditions degrading optical ISR across all fronts.
  • MEDIUM: Russian deployment of FAB-3000 glide bombs; 14th Guards Spetsnaz counter-UAV operations in Dnipropetrovsk.
  • LOW: Russian territorial capture of Malaya Korchakovka; unconfirmed reports of a U.S. Patriot battery redeployment from Rzeszów, Poland.

The Bottom Line

The operational integration of 3,000kg glide bombs by Russian aviation introduces a critical threat to hardened UAF defensive structures in the Eastern sector, necessitating immediate tactical dispersal and enhanced counter-air prioritization. Concurrently, the impending rain front will neutralize UAF optical drone advantages, forcing a reliance on ground-based sensors to counter localized Russian infantry infiltrations. UAF air defense networks must maintain high readiness, as SAR anomalies at Russian strategic airbases indicate a high probability of an impending mass missile wave.

Legacy provenance

This archived report predates claim-level evidence records. Treat its confidence labels as editorial assessments rather than independently verifiable citations.

Frontline context

Territorial control and recent changes shown by DeepState.

Report 31 Mar 2026, 15:02 UTC
Map revision comparison

Against the previous report from 30 Mar 2026, 15:02 UTC, bright red is newly marked Russian-occupied and green is no longer marked occupied. For the infiltration area, yellow is this report and cyan is the previous report.

Compare on map
Frontline change measurements are unavailable for this briefing.

Report Visuals

5 visuals
Open full size
Nightwatch daily report #630: Malaya Korchakovka area

Geospatial Analysis

6 locations identified

Historical reconstruction from source editions available by report time.

Places and data export

Coordinates come from geocoding place names found in the report. They locate the named place, not the event described there. Latitude and longitude are WGS 84 decimal degrees.

Show 6 places with coordinates
Geocoded places in report 630
PlaceCountryLatitude, longitudeCopy
BelgorodRussia50.5997134, 36.5982621
Kryvyi RihUkraine47.910483, 33.391783
KonstantinovkaUkraine48.52394289999999, 37.7075811
AB OlenyaRussia69.214167, 33.37
Malaya KorchakovkaUkraine50.9077, 34.7981
NizhnekamskneftekhimRussia55.1802364, 50.7263945

How to read the labels

Labels on this page come from three separate mechanisms. A label from one does not mean the same as a similar word from another.

1. In the narrative

Machine-generated narrative. Labels inside it are written by the model.

Unconfirmed:
Written by the model. Its instruction is to mark claims that rest on a single source.
Confidence: HIGH / MEDIUM / LOW
Written by the model. The report stores no definition of these levels, and they are not computed from the claim records. Do not read them as the record confidence above.

2. On claim records: confidence

Record confidence is a threshold on a number stored with the source observation. It is not a probability that the event happened. The follow-up investigation may lower it and never raises it.

HIGH confidence
The status is Independently corroborated, Geolocated or Imagery corroborated, and the stored confidence of the supporting observation is at least 0.75.
MEDIUM confidence
The stored confidence of the supporting observation is at least 0.5 and the rule for HIGH is not met.
LOW confidence
The stored confidence of the supporting observation is below 0.5.

2. On claim records: status

Machine-selected records from the source ledger, labelled by fixed rules. They are a separate selection and are not a list of the sources behind the narrative above.

Single-source claim
One retained source observation supports the record, from a sender that is not on the list of official bodies.
Official claim
One retained source observation, from a sender whose name matches a keyword list of official bodies. It says who made the claim, not that the claim is verified.
Multiple reports, same origin
Several retained observations that do not meet the rule for independent corroboration. They are treated as one origin.
Independently corroborated
At least two distinct source documents from at least two differently named senders. The rule compares sender names and document fingerprints. It does not establish that the senders had separate access to the event, and a repost under another name can satisfy it.
Geolocated
One retained observation carrying coordinates with a geolocation confidence of at least 0.5. It concerns the location only, not the cause or the outcome.
Imagery corroborated
Imagery supports the observation. It does not by itself establish cause or intent.
Analyst assessment
A Nightwatch assessment rather than a directly observed fact.
Contested
Set by the follow-up investigation: material source accounts remain in conflict.
Corrected
Set by the follow-up investigation: the record was changed after the investigation reached a definitive answer.
Insufficient evidence
Set by the follow-up investigation: the available evidence does not support the record as first labelled.

3. In the follow-up investigation

Machine-run follow-up on one selected claim record. Sources listed include material that was retrieved and not used.

Confirmed
The investigation reached a definitive answer supporting the selected claim. The report was rewritten after it.
Refuted
The investigation reached a definitive answer against the selected claim. The report was rewritten after it.
Materially refined
The investigation reached a definitive answer that changes the selected claim in a material way. The report was rewritten after it.
Inconclusive
The investigation did not reach a definitive answer. The report text was kept; the investigation could only attribute, hedge or lower confidence. Individual findings inside it can still carry their own outcome.

Each finding has its own outcome and a confidence written by the model. That confidence is in the finding as worded, which may itself be a statement that something is unknown.

Kinds of investigation source

External web page
A web page retrieved during the follow-up investigation. Its address is stored and linked.
Source observation behind a claim record
A source observation the claim records were built from. No address is stored for it.
Nightwatch archive item
An item found by searching the Nightwatch archive during the investigation. It may be unrelated to the question. No address is stored for it.