UAF Neutralizes Yastreb-AV Radar Amid Expanding VKS Aerial Campaign
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
Analyst briefMachine-generated narrative. Labels inside it are written by the model. How to read these labels
Strategic Overview
The Ukrainian Armed Forces (UAF) are effectively maturing their counter-UAS and precision interdiction capabilities, highlighted by the destruction of a high-value Russian counter-battery radar and the mass interception of Russian loitering munitions via FPV drones. Concurrently, the Russian Aerospace Forces (VKS) have expanded their Guided Aerial Bomb (KAB) strike corridors into Dnipropetrovsk Oblast, exploiting clear weather in the southern theater.
Institutionally, the UAF is formalizing technological and personnel adaptations. The National Guard (NGU) is restructuring to implement specialized drone and assault detachments, while command continuity is reinforced by the promotion of the 1st Azov Brigade commander to Brigadier General.
Operational Updates
- Northeastern Sector (Kharkiv/Sumy/Kursk): Ukrainian GUR specialists achieved a high interception rate, neutralizing 19 Russian "Molniya" drones and one "Lancet" munition using interceptor FPVs. The 15th NGU "Kara-Dag" maintains sustained FPV interdiction against Russian logistics on the Kupiansk axis. Russian sources allege UAF kinetic activity in Bryansk (RF); this remains unconfirmed. Frontline weather in Kharkiv (10.2°C) is transitioning to overnight fog (Code 45) with temperatures dropping to -3.8°C, which will severely degrade optical ISR and FPV operations.
- Eastern Sector (Donetsk/Luhansk): In a significant deep-strike success, the NGU "Lasar's Group" destroyed a Russian 1K148 "Yastreb-AV" counter-battery radar ($50M value), temporarily degrading Russian counter-fire capabilities. In the Pokrovsk sector, the 3rd "Spartan" Brigade successfully utilized FPV drones to guide 25 surrendering Russian personnel to UAF lines over the past month. Russian infantry units are increasingly deploying electric bikes and scooters to minimize acoustic and thermal signatures while traversing FPV-saturated zones.
- Southern Sector (Zaporizhzhia/Dnipropetrovsk): The VKS has intensified KAB saturation, notably extending target vectors deeper into Dnipropetrovsk Oblast. In Zaporizhzhia, Russian drones have demonstrated a shift in targeting by engaging local law enforcement vehicles. Weather remains clear (12.2°C, winds 4.2 m/s), providing optimal conditions for continued standoff aviation sorties.
Equipment & Losses
- Confirmed Russian Loss: One 1K148 "Yastreb-AV" counter-battery radar system.
- Confirmed Russian Loss: 19 "Molniya" fixed-wing drones and 1 "Lancet" loitering munition intercepted by UAF FPVs.
- Tactical Shift (Russian): Integration of electric bikes/scooters for low-signature frontline mobility.
- Unconfirmed Ukrainian Loss: 95th Air Assault Brigade BTR near Novoaleksandrovka; one 103rd TDF officer casualty in Sumy.
- Field Integration (UAF): Operationalization of the "Khyzhyak" police unit's dedicated Unmanned Ground Vehicle (UGV) maintenance and modernization workshop.
Confidence Check
- HIGH: UAF destruction of Yastreb-AV radar; mass interception of Russian Molniya UAVs; VKS KAB expansion into Dnipropetrovsk; Northern Fleet SAR anomalies.
- MEDIUM: Scale of Russian e-bike proliferation across frontline motorized rifle units.
- LOW: Russian assertions of UAF strikes in Bryansk; Russian claims of 95th Air Assault BTR destruction.
The Bottom Line
The UAF has successfully operationalized FPV interceptors to degrade Russian long-range ISR and strike networks. Tactically, expect a temporary lull in optical drone efficacy in the Northeastern sector as heavy overnight fog develops, potentially masking localized ground movements.
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.
Against the previous report from 12 Mar 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.
Report Visuals
3 visualsGeospatial 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
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Kupiansk | Ukraine | 49.7055574, 37.6027997 | |
| Pokrovsk | Ukraine | 48.282193, 37.1847804 | |
| AB Severomorsk-3 | Russia | 68.88283539999999, 33.731971 | |
| AB Olenya | Russia | 69.214167, 33.37 | |
| Dnipropetrovsk Oblast | Ukraine | 48.464717, 35.046183 | |
| Bryansk | Russia | 53.2635306, 34.41611 |
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.
