Daily intelligence

Ukrainian Deep Strikes Confirmed at Novorossiysk and Crimea as UAF Achieves Long-Range Drone Parity

Published Intelligence Summary & Geospatial Analysis
Report number
636

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

The Ukrainian Armed Forces (UAF) officially confirmed successful deep strikes against the Sheskharis oil terminal in Novorossiysk and the destruction of a Beriev Be-12 amphibious aircraft in occupied Crimea. These actions compound existing friction on Russian littoral Ground Lines of Communication (GLOCs) and degrade Black Sea Fleet anti-submarine warfare (ASW) capabilities. Concurrently, data indicates the UAF surpassed Russian forces in total long-range drone strike volume during March 2026, marking a strategic shift in strike parity.

Operationally, the immediate tactical environment will be dictated by an incoming rain front across the entire contact line. The forecast predicts an 80-98% probability of precipitation, which will temporarily ground low-altitude optical Unmanned Aerial Vehicles (UAVs) and force a transition back to traditional artillery and dismounted infantry maneuver.

Operational Updates

  • Northern Sector (Kyiv / Sumy / Belarus): Russian forces maintain strike pressure on civilian utility infrastructure. Russian sources claim the total destruction of the CHPP-4 power plant in Kyiv (UNCONFIRMED). Reports indicate Russia is constructing four new long-range drone launch bases in Belarus to bypass current UAF air defense arrays. Weather in Kharkiv/Vovchansk (17.6°C, wind 4.6 m/s, 100% cloud cover) with impending rain (80% probability, 7.5mm) will severely restrict tactical ISR.
  • Eastern Sector (Donetsk / Luhansk): The Pokrovsk and Oleksandrivske axes remain the primary focus of Russian ground assaults. Elements of the UAF 425th Separate Assault Regiment "Skelya" are conducting clearing operations in Hryshyne. Russian sources claim the use of a 3,000kg FAB-3000 glide bomb against a UAF Temporary Deployment Point (PVD) in Kostiantynivka. Incoming rain in Pokrovsk (16.8°C, wind 5.7 m/s, 95% rain probability, 2.2mm) will degrade cross-country mobility for mechanized units.
  • Southern Sector (Zaporizhzhia / Kherson / Crimea): UAF offensive pressure in the Stepnohirsk sector has reportedly forced localized Russian tactical retreats. UAF FPV operators successfully interdicted high-value Russian artillery and C2 assets in the Huliaipole sector, neutralizing multiple multiple-launch rocket systems (MLRS) and a counter-battery radar. Russian forces have begun deploying "Spirit-030" compact satellite communication terminals to frontline units to bypass terrestrial EW.

SAR Intelligence (Satellite Data)

  • High Priority: CRITICAL activity deviations were detected at AB Belbek (Z-Score: 5.96), the 38th Fighter Aviation Regiment HQ (Z-Score: 6.45), and across multiple elements of the 76th Guards Air-Assault Division, including the division HQ, the 237th Guards Air Assault Regiment, and the 124th Separate Tank Battalion.
  • Analysis: The synchronized, critical deviations across elite airborne forces (76th VDV) and Crimean aviation assets (AB Belbek) indicate a sudden shift in readiness posture or force redeployment. This activity likely correlates with Russian force repositioning in response to recent UAF deep strikes or preparation for localized maneuver operations before weather conditions deteriorate.

Equipment & Losses

  • Confirmed: Physical damage to the Sheskharis oil terminal infrastructure in Novorossiysk.
  • Confirmed: Destruction of a Russian Beriev Be-12 amphibious aircraft in Crimea.
  • Confirmed: Sinking of the Russian cargo vessel "Volgo-Balt 138" in the Sea of Azov (3 KIA).
  • Confirmed: Destruction of two BM-21 "Grad" MLRS, one BM-27 "Uragan" MLRS, and a 1L219 "Zoopark" counter-battery radar by UAF FPV drones near Huliaipole.
  • Confirmed: UAF 1st SBS Center successfully struck Russian "Gerber" loitering munition operators and mobile launchers (pickups) during launch operations.

Confidence Check

  • HIGH: UAF strikes on Novorossiysk terminal and Be-12 aircraft; sinking of the "Volgo-Balt 138"; destruction of the Zoopark radar in Zaporizhzhia; upcoming weather front impacts.
  • MEDIUM: UAF surpassing Russian long-range drone strike volume; Russian deployment of "Spirit-030" satellite terminals; construction of four new drone bases in Belarus.
  • LOW: Russian claims regarding the total destruction of Kyiv CHPP-4; the use of a FAB-3000 bomb in Kostiantynivka; claims of UAF deploying "graphite bombs" against the LNR/DNR energy grid.

The Bottom Line

The UAF's achievement of long-range strike parity, combined with successful, confirmed interdiction of critical maritime and energy nodes, demonstrates a highly effective, maturing multi-domain strike capability. Russian responses will likely focus on leveraging the impending rain front—which will blind UAF tactical FPV defenses—to advance mechanized reserves and dismounted infantry along the Pokrovsk axis. UAF commands must prepare for reduced ISR visibility and an increased reliance on pre-registered indirect fire over the next 24-48 hours.

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 06 Apr 2026, 15:01 UTC
Map revision comparison

Against the previous report from 05 Apr 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

4 visuals
Open full size
Nightwatch daily report #636: Hryshyne area

Geospatial Analysis

7 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 7 places with coordinates
Geocoded places in report 636
PlaceCountryLatitude, longitudeCopy
SheskharisRussia44.7178676, 37.8423371
BelbekUkraine (Occupied)48.379433, 31.16558
KyivUkraine50.0529506, 30.7667133
HuliaipoleUkraine47.6607145, 36.2732384
PokrovskUkraine48.282193, 37.1847804
HryshyneUkraine48.31771209999999, 37.0903532
BelarusBelarus52.1648754, 29.1333251

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.