Daily intelligence

Ukrainian Strikes Target Novorossiysk and Azov Sea Logistics as Russian Forces Introduce Jet-Powered Loitering Munitions

Published Intelligence Summary & Geospatial Analysis
Report number
635

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) have expanded their deep-strike campaign, successfully penetrating the air defense envelope of Novorossiysk and interdicting maritime logistics in the Sea of Azov. Concurrently, President Zelenskyy initiated a strategic diplomatic pivot, holding direct negotiations with Syrian leadership in Damascus to isolate Russian regional influence. In response to UAF defensive adaptations, Russian forces have escalated their suppression campaign by deploying a jet-powered variant of the "Geran" loitering munition ("Geran-5"), designed to compress Ukrainian air defense reaction times against critical energy and urban targets.

Operational Updates

  • Northern Sector (Kharkiv / Sumy): Russian forces utilized "Geran-5" jet-powered munitions against the "Neftegazdobycha" facility in Moshenka (Sumy Oblast) and the Shevchenkivskyi and Slobidskyi districts in Kharkiv. Strikes severely damaged civilian utility infrastructure. Elements of the Russian 106th VDV Division are withdrawing from Sumy for southern redeployment. Weather in Kharkiv (11.8°C, wind 5.6 m/s, 73% cloud cover) continues to support low-altitude UAV approaches.
  • Eastern Sector (Donetsk / Luhansk): The UAF recorded 41 combat engagements, with intense defensive operations focused on the Pokrovsk and Kostyantynivka axes. Clear conditions in Pokrovsk (13.9°C, 5% cloud cover) facilitated UAF FPV strikes, which inflicted heavy attrition on Russian motorcycle-borne assault groups in open terrain. The Russian Zapad Group officially reported persistent communication failures, contradicting Ministry of Defense claims regarding jam-resistant network capabilities.
  • Southern Sector & Rear (Zaporizhzhia / Kherson / Crimea): UAF UAVs triggered air raid sirens in Novorossiysk, fixing Russian air defense assets in the rear. In the Sea of Azov (north of Kerch), the Russian cargo vessel "Volgo-Balt" was confirmed sunk following a drone strike, resulting in 3 fatalities. In Nikopol, Russian forces executed a coordinated leaflet psychological operation followed by a lethal artillery and drone strike on a marketplace (5 KIA, 28 WIA). The Russian 14th Spetsnaz Brigade maintains high UAV pressure near Lyubitskoye.

SAR Intelligence (Satellite Data)

  • High Priority: CRITICAL activity deviations were detected at the 40th Mixed Aviation Regiment (Score: 0.47), a Long-Range Aviation unit formerly of the 6950th Air Base (Score: 0.35), and the 566th Support Vessel Group (Score: 0.57). A HIGH anomaly was observed at AB Olenya (Score: 0.35).
  • Analysis: The synchronized, critical deviations across Northern Fleet and Long-Range Aviation installations (AB Olenya, 40th Regiment) indicate a heightened state of readiness, correlating with historical precursors for strategic aviation sorties. Anomalous activity at the 566th Support Vessel Group suggests localized maritime logistics adjustments.

Equipment & Losses

  • Confirmed sinking of the Russian dry cargo ship "Volgo-Balt" in the Sea of Azov.
  • Visual confirmation of the destruction of a Russian TOS-1A thermobaric system by the UAF 129th Separate Territorial Defense Brigade.
  • Confirmed destruction of a UAF 152-mm "Giatsint-B" artillery piece by a Russian FPV drone in the Zapad area of operations.
  • Unconfirmed: Death of Russian "Zircon" hypersonic missile lead developer Alexander Leonov.

Confidence Check

  • HIGH: Sinking of the "Volgo-Balt"; strikes on civilian infrastructure in Kharkiv and Nikopol; Zelenskyy's diplomatic presence in Damascus.
  • MEDIUM: Widespread integration of jet-powered "Geran-5" munitions; internal Russian C2 friction within the Zapad Group.
  • LOW: Russian claims targeting a military recruitment center in Kharkiv; reports of US aircraft losses in Iran (assessed as Russian information warfare to project Western instability).

The Bottom Line

The introduction of jet-powered loitering munitions represents a tactical escalation intended to defeat UAF Mobile Fire Groups (MOG) through sheer velocity. UAF air defense networks must adjust interception parameters to account for reduced engagement windows. Furthermore, UAF maritime reach into the Sea of Azov and Novorossiysk demonstrates persistent vulnerabilities in Russian littoral Ground Lines of Communication (GLOCs), compounding their existing logistical friction.

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

Against the previous report from 04 Apr 2026, 15:01 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 #635: Moshenka 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 635
PlaceCountryLatitude, longitudeCopy
NovorossiyskRussia44.7180464, 37.7770118
MoshenkaUkraine50.2454877, 34.9110131
KharkivUkraine50.00201269999999, 36.3073994
PokrovskUkraine48.282193, 37.1847804
NikopolUkraine47.56746, 34.394815
AB OlenyaRussia69.214167, 33.37
Sea of AzovInternational/Contested0, 0

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.