Massive Reciprocal Deep Strikes: Russia Targets Energy Grid as UAF UAVs Paralyze Moscow Airspace
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 operational environment over the past 24 hours has been dominated by a high-intensity, reciprocal deep-strike campaign. Russian forces launched a synchronized 347-asset attack (297 strike UAVs and 50 missiles) prioritizing the Ukrainian energy grid, specifically targeting the Trypilska Thermal Power Plant (TPP) near Kyiv. Despite high interception rates, localized grid disruptions persist.
Simultaneously, Ukrainian forces executed a massive UAV incursion into the Russian Federation, with over 71 drones penetrating airspace and forcing the total shutdown of major Moscow air hubs (Vnukovo, Domodedovo, Zhukovsky, Sheremetyevo). This sustained pressure successfully fixed Russian Integrated Air Defense Systems (IADS) and disrupted civil-military logistics in the capital.
Operational Updates
- Northern Sector (Kharkiv/Sumy): Extreme cold persists, with Kharkiv facing temperatures dropping to -14.7°C. The Russian "Sever" (North) group is expanding a designated "security zone" along the border, integrating drone, artillery, and EW assets while enforcing strict operational security (banning Telegram). UAF FPV drones conducted a high-value strike on a Russian logistics facility, reportedly destroying 10 vehicles and a significant cache of FPV drones.
- Eastern Sector (Donetsk/Luhansk): Russian command posts in the Konstantinovskoye sector are adapting to the loss of Starlink access by transitioning to backup communication systems. Concurrently, Russian forces are field-testing "Kuryer" NRTK (automated ground drones) equipped with AGS-17 grenade launchers and RPO-A Shmel thermobaric weapons at local training ranges, indicating a shift toward utilizing unmanned systems for urban and trench clearing.
- Central/Western Sector (Kyiv/Lviv): A coordinated "time-on-target" strike involving Kh-101 cruise missiles and Shahed UAVs struck the Trypilska TPP and a residential high-rise in the Sviatoshynskyi district of Kyiv. In Lviv, authorities detained a suspect following an IED detonation on Danylyshyna Street, ruling the event a localized terrorist act rather than a Russian long-range kinetic strike.
- Southern Sector (Zaporizhzhia/Odesa): High-speed maritime threats (likely ballistic/cruise missiles) were launched from the Black Sea toward Odesa/Chornomorsk. Power disruptions continue in the Odesa and Zaporizhzhia regions following the overnight mass strike.
SAR Intelligence (Satellite Data) Recent synthetic-aperture radar (SAR) collections indicate stable, baseline activity across monitored rear-area logistics and aviation nodes.
- Air Bases & Border Outposts: AB Monchegorsk (Score: 0.00) and the FSB Border Outpost (Score: 0.35) show no significant deviations from established baselines. A score near 0 indicates no major physical changes or large-scale movement, not that the facilities are empty.
- Analysis: Logistics outloading associated with the recent 347-asset strike has concluded. Current radar signatures do not yet show the localized massing of replacement munitions at these specific monitored sites.
Equipment & Losses
- Confirmed: Damage to the Trypilska TPP (Kyiv region) and a rail locomotive following the overnight Russian strike.
- Confirmed: Satellite imagery verified a UAF deep strike on an oil depot in Velikiye Luki, Pskov Oblast.
- Confirmed: Interception of multiple Ukrainian UAVs over Moscow, resulting in extensive civilian flight groundings.
- Unconfirmed: Destruction of 10,000 Russian FPV drones in a single UAF warehouse strike.
- Unconfirmed: Explosions reported in the suburbs of Tehran, Iran, potentially impacting Shahed-type drone supply chains.
Confidence Check
- HIGH: Russian 347-asset combined strike; closure of Moscow airspace due to UAF UAVs; Lviv IED investigation.
- MEDIUM: Extent of thermal generation degradation at Trypilska TPP; field testing of Russian "Kuryer" ground drones.
- LOW: Total destruction of 10,000 Russian FPVs in one strike; FSB allegations of British involvement in the assassination attempt on GRU Lt. Gen. Alekseev.
The Bottom Line Russia's strategy has fully pivoted to energy grid attrition during the severe temperature drop, seeking cumulative "minor hits" to outpace Ukrainian repair capabilities. Concurrently, Ukraine has proven capable of routinely penetrating the Moscow air defense ring, forcing Russia to expend heavy surface-to-air interceptors defensively. In the next 24-48 hours, monitor the Pokrovsk and Donetsk sectors for the initial frontline deployment of the newly tested Russian "Kuryer" automated ground combat systems.
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 21 Feb 2026, 21:17 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
5 visualsGeospatial 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
| Place | Country | Latitude, longitude | Copy |
|---|---|---|---|
| Trypilska TPP | Ukraine | 50.1353073, 30.7504291 | |
| Kyiv (Sviatoshynskyi District) | Ukraine | 50.4503596, 30.5245025 | |
| Moscow Air Hubs (Vnukovo, Domodedovo, Zhukovsky, Sheremetyevo) | Russia | 55.41030689999999, 37.9024513 | |
| Kharkiv | Ukraine | 50.00201269999999, 36.3073994 | |
| Sever Security Zone Expansion Area | Ukraine | 50.00201269999999, 36.3073994 | |
| Konstantinovskoye Sector | Ukraine | 48.015883, 37.80285 | |
| Odesa/Chornomorsk Ports | Ukraine | 46.3093943, 30.6531831 | |
| Zaporizhzhia Region | Ukraine | 47.8388, 35.139567 | |
| AB Monchegorsk | Russia | 67.943134, 32.8919562 | |
| FSB Border Outpost | Russia | 61.52401, 105.318756 | |
| Velikiye Luki Oil Depot | Russia | 56.33960880000001, 30.5314751 | |
| Pokrovsk/Donetsk Deployment Zone | Ukraine | 48.282193, 37.1847804 |
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.
