Deployment Assessment: Пціч Airport, Belarus

Site Overview

Пціч (Ptich) Airport is a Belarusian aviation facility classified under the CISA Transportation sector. Located in a country that has been a direct participant in the Russia-Ukraine conflict as a staging and logistics platform since February 2022, the site operates within a conflict-zone designation despite recording zero ACLED incidents within a 50 km radius. The absence of recorded kinetic incidents does not indicate low threat exposure — it reflects the current operational posture of Belarus as a rear-area support node rather than a frontline target. That status is not permanent.

The airport serves a sparse immediate population (1,576 within 5 km) but sits within a broader catchment of approximately 55,910 people within 25 km. Its strategic significance derives not from passenger throughput but from its potential dual-use role in a conflict environment where Belarusian airspace and airfields have been used for Russian military operations, including the initial 2022 assault on Kyiv.

The absence of recorded kinetic incidents does not indicate low threat exposure — it reflects the current operational posture of Belarus as a rear-area support node rather than a frontline target. That status is not permanent.

CARVER Analysis

Пціч scores 36/50 on the CARVER composite — a high-priority target profile by any standard operational threshold.

Component	Score	Interpretation
Criticality	7	Significant disruption potential to regional transport/logistics
Accessibility	5	Moderate physical access barriers
Recuperability	4	Moderate recovery timeline post-disruption
Vulnerability	6	Meaningful exposure to attack vectors
Effect	7	High downstream consequence if disrupted
Recognizability	7	Easily identified as a target by adversary ISR

A CARVER composite of 36 places this site in the upper tier of assessed infrastructure. A robotics applicability score of 7 (standalone, not a CARVER dimension) is operationally significant: it indicates that autonomous systems — including FPV drones, loitering munitions, and UAS-based ISR — are assessed as credible and relevant threat vectors for this site. A Recognizability score of 7 confirms the site is readily identifiable to adversary collection assets, reducing the friction for targeting.

DRES Assessment

The DRES composite of 6.6 (MEDIUM) masks significant internal variance across sub-dimensions:

• Subsurface: 11.2 — The highest sub-score in the profile. This is anomalous for an airport and warrants operator attention. It may reflect buried infrastructure (fuel lines, electrical conduit, communications cabling) that is both critical and difficult to harden against ground-penetrating or burrowing attack vectors.
• Hardening: 11.159 — Elevated hardening score indicates existing physical protection measures, but hardening alone does not address the air or cyber threat surface.
• Target Profile: 7.685 — Confirms the site presents a meaningful signature to adversary targeting systems.
• Ground: 7.7 — Above-threshold ground threat exposure, consistent with a conflict-zone airport that may face sabotage, ground infiltration, or UGV-based threats.
• Air: 4.1 — Moderate air threat score. In the context of a conflict zone with documented UAS use across the broader theater, a score of 4.1 should not be read as low-risk; it reflects current assessed probability, not theoretical ceiling.
• Surface: 2.5 / Accessibility: 2.5 — Lower scores suggest physical perimeter controls are partially effective.

The divergence between the elevated Hardening score (11.159) and the moderate Air score (4.1) suggests that existing hardening investments are concentrated on physical/ground protection rather than airspace denial. This is a structural gap.

Verified Deployments: A Critical Finding

No verified autonomous or robotic system deployments are recorded for this site.

This is a primary finding, not a data gap. For a site with a CARVER composite of 36, a conflict-zone designation, a robotics applicability score of 7, and a Ground DRES sub-score of 7.7, the absence of any publicly evidenced C-UAS, perimeter robotics, or autonomous surveillance deployment represents a material protection deficit.

Comparable transportation-sector sites in conflict-adjacent environments — including airports in Ukraine, Poland, and the Baltic states — have documented deployments of:

• RF-based drone detection systems (e.g., DroneShield DroneSentry, Dedrone DedroneTracker)
• Electro-optical/infrared perimeter surveillance
• Integrated C-UAS command nodes

None of these are confirmed at Пціч. The Robotics Gap is classified as UNKNOWN, which in this context means: no evidence of deployment, and no evidence of a structured assessment process that would precede procurement.

Threat Exposure: 12–24 Month Outlook

LOW CONFIDENCE on specific threat timelines; HIGH CONFIDENCE on structural exposure.

Several factors converge to elevate the 12–24 month risk window:

1. Conflict posture: Belarus remains a declared conflict-zone participant. Rear-area infrastructure — including airfields — has historically become higher-priority targets as conflicts evolve and frontlines stabilize. Ukrainian long-range strike capability (drones, ATACMS-class systems) has demonstrated reach into Belarusian-adjacent territory.

2. UAS proliferation in theater: The Russia-Ukraine conflict has normalized low-cost FPV drone strikes against airfield infrastructure. The technology transfer and operational doctrine for such attacks is now widely distributed across non-state and state-adjacent actors.

3. Zero confirmed C-UAS deployment: A site with CARVER 36 and no verified airspace denial capability presents an asymmetric opportunity for an adversary using commodity UAS. The cost-exchange ratio strongly favors the attacker.

4. Subsurface score of 11.2: If this reflects buried fuel or electrical infrastructure, it represents a high-consequence, low-visibility vulnerability that ground-based autonomous systems (UGVs, burrowing munitions) could exploit with minimal surface signature.

5. Regulatory coverage: No specific regulatory framework governing autonomous system deployment at Belarusian airports is publicly documented in the supplied data. This creates procurement ambiguity for any operator seeking to deploy C-UAS or perimeter robotics.

Procurement and Investment Implications

For defense program managers and C-UAS procurement officers:

• The site's CARVER 36 / robotics applicability score of 7 profile justifies immediate gap assessment. The first procurement priority should be a layered detection architecture (RF + EO/IR) before any kinetic defeat capability.
• Ground threat (DRES Ground: 7.7) warrants evaluation of autonomous perimeter patrol or fixed sensor networks.

For FEMA C-UAS grant applicants (where applicable to allied/partner programs):

• The absence of any baseline deployment means grant applications can be structured around foundational capability rather than upgrade cycles — a simpler justification pathway.

For dual-use investors:

• Belarusian procurement is constrained by sanctions regimes. Western C-UAS vendors face significant export control barriers. This site is not a near-term commercial opportunity for Western suppliers; it is a leading indicator of the broader Eastern European airfield protection deficit that is addressable in NATO-adjacent markets.

Summary

Пціч Airport presents a high CARVER score (36), conflict-zone status, and a robotics applicability score of 7 (standalone, not a CARVER dimension) against a verified deployment count of zero. The structural gap between assessed threat exposure and documented protection capability is the defining finding of this assessment. The elevated Subsurface DRES score (11.2) and Ground score (7.7) indicate that buried and perimeter infrastructure are the highest-priority hardening targets. In the absence of confirmed C-UAS or autonomous perimeter systems, the site's air and ground threat surfaces remain unaddressed by any publicly evidenced autonomous capability.

Confidence: MODERATE | Assessment Valid Until: 2027-05-01

---

Assessment based on CARVER/DRES scoring data, ACLED conflict incident records, and open-source deployment evidence as of 2026-05-01. Verified deployment data reflects public evidence only; classified or undisclosed systems are not captured.