Daily intelligence

UAF Confirms Su-24M Destruction at Saky Airbase; Zaporizhzhia Civilian Casualties Rise to Three

Published Intelligence Summary & Geospatial Analysis
Report number
742

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
Newest map data is 27.7 h older than this report.

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 most significant operational development of the last 24 hours is the Ukrainian Armed Forces’ (UAF) official confirmation of a successful strike on Saky airbase in occupied Crimea, resulting in the destruction of an RF Su-24M frontline bomber. This event underscores the continued degradation of RF aviation assets in the peninsula, complementing ongoing interdiction of Crimean energy and logistics nodes. Concurrently, Russian Federation (RF) forces intensified their aerospace campaign against civilian infrastructure, with guided aerial bomb (KAB) strikes on Zaporizhzhia city resulting in three confirmed fatalities and one missing person.

On the political front, the Verkhovna Rada concluded its session without appointing a new Minister of Defense or Foreign Affairs, entering a recess until 18 August. This leaves key security portfolios vacant amidst reported internal friction between the Presidential Office and parliamentary factions. Ground operations remain characterized by high-tempo RF assaults in the Pokrovsk and Sloviansk directions, though no operational breakthroughs were achieved. UAF maritime drones continued to interdict RF shadow fleet logistics in the Black Sea.

Operational Updates

  • Eastern Sector (Donetsk): RF maintained high-pressure assaults across multiple axes. The UAF General Staff reported repelling 54 attacks, with the highest concentrations in Pokrovsk (12 attacks), Sloviansk (13 attacks), and Kostiantynivka (9 attacks). RF milbloggers claimed tactical advances near Vasiutynske, alleging proximity to Kramatorsk, but these claims lack independent geospatial verification. UAF TSP "Omega" conducted clearing operations in the Pokrovsk sector.
  • Southern Sector (Zaporizhzhia/Kherson/Odesa): RF struck Zaporizhzhia city with three KABs, causing residential destruction and raising the death toll to three. In the maritime domain, UAF SBU "Mamai" naval drones reportedly struck two RF shadow fleet tankers, "Louise 1" and "Banda," in the Black Sea. Pro-RF sources claim the Black Sea Fleet is effectively confined to Novorossiysk due to sustained UAF asymmetric pressure.
  • Northern Sector (Kharkiv/Sumy): RF tracked reactive UAVs towards Kharkiv from the north and southwest, and towards Snovsk (Chernihiv Oblast). RF VKS conducted airstrikes using FAB-500s and Kh-39 LMURs on UAF positions in Sumy Oblast. No significant ground contact line changes were reported.
  • Kursk Direction: No significant change in ground contact lines. RF continues to face localized resistance and mining obstacles.

Deep Strikes & Air Defense

  • UAF Deep & Tactical Strikes: UAF National Guard Commander Pivenko officially confirmed that "Omega" Special Purpose Center operators destroyed an RF Su-24M bomber at Saky airbase (Crimea) using two UAV strikes. Additionally, UAF SBU Alpha and the 422nd Luftwaffe Regiment conducted joint strikes on RF command posts and ammunition/fuel depots in the Kostiantynivka direction.
  • RF Aerospace Campaign: RF launched a multi-vector UAV and missile campaign. Reactive UAVs were tracked towards Chernihiv, Poltava, Kharkiv, and Odesa/Chornomorsk. RF MoD claimed strikes on 147 areas, including energy and transport infrastructure, and alleged the interception of 802 UAVs, a figure assessed as highly exaggerated.
  • Air Defense: UAF Air Force actively tracked and engaged incoming threats across multiple oblasts. A reactive UAV was specifically tracked heading towards Poltava city from the east.

SAR Intelligence (Satellite Data)

  • High Priority: SAR anomaly detection identified critical activity deviations at several locations:
    • 96th Operational Purpose Regiment (46th Separate Operational Purpose Brigade): Score 6.59 (Critical Anomaly). Indicates significant logistical reshuffling or unit movement.
    • 16th Separate EW Regiment (Air Force and Air Defence Forces of the Republic of Belarus): Score 5.68 (Critical Anomaly). Suggests reactive logistical adjustments or dispersal.
    • Separate Police Battalion (4th Separate Special Police Brigade): Score 4.06 (Critical Anomaly). Warrants monitoring for aviation asset movements or dispersal.
  • Analysis: The elevated scores at the 96th Operational Purpose Regiment and 16th Separate EW Regiment suggest reactive logistical adjustments in response to UAF deep strikes and ongoing rear-area security concerns. The confirmed destruction of the Su-24M at Saky aligns with operational reporting of aviation interdiction in Crimea.

Equipment & Losses

  • RF Losses: UAF confirmed destruction of one Su-24M bomber at Saky airbase. UAF SBU "Mamai" claimed damage/destruction of two RF shadow fleet tankers ("Louise 1" and "Banda") in the Black Sea.
  • UAF Losses: Confirmed civilian casualties in Zaporizhzhia (3 killed, 1 missing). Infrastructure damage reported in Zaporizhzhia city following KAB strikes.

Confidence Check

  • Saky Airbase Strike: HIGH (Confirmed by UAF NGU Commander Pivenko).
  • Zaporizhzhia Casualties: HIGH (Confirmed by Zaporizhzhia OVA).
  • Black Sea Maritime Strikes: MEDIUM (Claimed by UAF SBS; independent AIS/satellite verification required).
  • RF Advances near Kramatorsk: LOW (RF claim only; no independent geospatial confirmation).
  • MoD/MFA Appointments: HIGH (Verkhovna Rada adjourned without voting; vacancies confirmed).

The Bottom Line

The conflict trajectory is defined by UAF’s successful expansion of asymmetric strikes to critical Crimean aviation assets (Saky) and continued maritime interdiction, exacerbating RF logistical constraints. RF continues to rely on KABs to target Ukrainian urban centers, particularly Zaporizhzhia, while facing systemic domestic fuel shortages and political friction. In the next 24 hours, monitor:

  1. Political Vacuum: Developments regarding the appointment of the Minister of Defense and Foreign Affairs during the Rada's recess.
  2. Crimean Aviation: Further RF aircraft dispersal or defensive measures following the confirmed Su-24M loss at Saky.
  3. RF Ballistic/UAV Aftermath: Damage assessment in Poltava and Chernihiv following the latest reactive UAV waves.

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 16 Jul 2026, 15:06 UTCLagged by 27.7 h
Map revision comparison

Against the previous report from 15 Jul 2026, 15:06 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

The latest control-map interval ended 27.7 hours before this report. The daily change covers 22.5 h. These map dates may differ from the reporting period and do not establish when territorial changes occurred.

Latest interval
+0.8 km²
22 h ending 15 Jul 2026, 11:27 UTC
Daily net
+0.8 km²
22.5 h comparison
Seven-day net
-26 km²
158.7 h comparison
Largest changes in the latest measured interval
Near Pokrovsk
0.8 km² changed · RF-held gained 0.8 / lost 0.0 km²

Positive values indicate an increase in Russian-occupied area; negative values indicate a decrease. Yellow marks DeepState's infiltration area (gray zone), which is not included in occupied-area totals.

Report Visuals

4 visuals
Open full size
Nightwatch daily report #742: Pokrovsk area

Geospatial Analysis

12 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 12 places with coordinates
Geocoded places in report 742
PlaceCountryLatitude, longitudeCopy
SakyUA45.1310529, 33.5941066
ZaporizhzhiaUA47.83928419999999, 35.13870970000001
PokrovskUA48.282193, 37.1847804
SlovianskUA48.8532, 37.6053
KostiantynivkaUA48.52394289999999, 37.7075811
KharkivUA50.00201269999999, 36.3073994
ChernihivUA51.4982, 31.28935
PoltavaUA49.58826699999999, 34.551417
OdesaUA46.4845702, 30.7326047
Black SeaUA0, 0
SnovskUA51.8178825, 31.9467381
Sumy OblastUA0, 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.