Archived operational intelligence briefing
DTG: 2025-12-14T23:10Z PRIORITY: CRITICAL (Sustained Multi-Vector Air Attrition)
| Sector | Assessment | Details |
|---|---|---|
| Southern Axis (Odesa) | Threat Reactivated | UAV swarm confirmed approaching Odesa from the Black Sea. UAF AD assets are engaged. This requires rapid prioritization of coastal/port defense resources, potentially drawing assets away from the Dnipro region. |
| Central Axis (Kharkiv/Poltava/Dnipropetrovsk) | Launch Location Claimed | RF claims launches originated near Krasnohrad Raion (Kharkiv). If confirmed, this shortens the flight path to Kremenchuk/Pyatykhatky, reducing warning time and complicating long-range radar detection. The central axis remains the primary target of RF air attrition. |
| Northern Axis (Sumy) | Status Quo (Fixation) | Previous threat assessment toward Sumy remains valid, continuing to act as a diversionary vector tying down UAF assets on the border. |
| Deep Rear (RF Territory) | IO Escalation | RF propaganda amplifying deep strike threats ("Moscow breach") alongside normalization efforts (TASS subsidized flights) to manage domestic public opinion. |
Current Threat Level: CRITICAL (Multi-Directional Air Saturation and IO Escalation)
MLCOA (Most Likely Course of Action): UAV Attrition and Central Penetration RF will continue to sustain the current UAV strike pattern until approximately 04:00Z. The central axis (Dnipropetrovsk/Poltava) remains the highest kinematic priority, likely supported by further waves originating from the claimed Krasnohrad area to maximize deep penetration and infrastructure damage (utilizing the newly identified 100kg Shahed variant, per Daily Report). Odesa remains a secondary target intended to fix coastal AD.
MDCOA (Most Dangerous Course of Action): Retaliatory High-Speed Strike RF leverages the IO narrative ("Moscow breach") and the strategic AD dispersion to launch high-speed ballistic or cruise missiles (Kalibr, Kinzhal, Iskander) targeting crucial logistical nodes or strategic C2 facilities in Dnipro, Zaporizhzhia, or Kryvyi Rih, while UAF AD resources are fixed by the UAV swarms on the periphery (Odesa, Sumy). This MDCOA is assessed as rising in likelihood due to the aggressive IO framing.
Recommendation: UAF J3 should immediately prioritize Mobile Fire Groups (MFGs) to cover critical logistical choke points in Dnipro and Zaporizhzhia through the 01:00Z - 04:00Z window. Tactical commanders must confirm the launch origin claim in Krasnohrad Raion and, if validated, immediately adjust AD interception zones and pre-target RF mobile launch teams near the claimed location.
| Priority | Gap / Request | Justification / Need |
|---|---|---|
| P1 (CRITICAL) | UAV Launch Origin Validation (Krasnohrad Raion) | Immediate IMINT/SIGINT/HUMINT required to verify the RF claim regarding UAV launches near Krasnohrad. Confirmation dictates an immediate shift in UAF AD and counter-launch tactics. |
| P1 (CRITICAL) | 260th GRAU Outflow Vector (UNCHANGED) | Immediate verification of rail material destination (Volnovakha vs. Ilovaisk) is required to predict the axis of the RF artillery main effort (expected 24-48 hours). (Prev. SitRep P1) |
| P1 (CRITICAL) | Belgorod BDA Confirmation (HIMARS Claim) | Immediate IMINT/HUMINT required to determine the exact impact location and munition type used in the recent Belgorod strike to definitively rebut escalating RF IO narratives. |
| P2 (URGENT) | Odesa UAV Target Assessment | AD reporting required to confirm the specific target type near Odesa (e.g., port infrastructure, grain terminal, energy transformer) to confirm RF prioritization. |
| P3 (URGENT) | Huliaipole Ground Status (UNCHANGED) | IMINT/HUMINT required immediately to verify if RF forces are transitioning from air shaping to a full-scale ground assault by the Vostok Grouping. (Persistent Gap) |
We only use optional analytics cookies if you allow them. Necessary cookies stay on for sign-in and site security.
Learn more in our Privacy Policy.