Project Akashteer and India's automated air-defence backbone
What Akashteer integrates, what it means for counter-UAS doctrine, and why the operator-decision layer is now the bottleneck.
Project Akashteer is the most consequential Indian air-defence integration programme of the decade. Developed by Bharat Electronics Limited for the Indian Army's Corps of Army Air Defence and progressively inducted across formations, Akashteer is not a new sensor or a new weapon — it is the command-and-control layer that integrates the existing sensors, the existing weapons, and the existing decision authorities into a single automated air-defence picture. What it actually changes, and what new training requirements it introduces, deserves more careful examination than the headlines have provided.
What Akashteer integrates
Akashteer connects a heterogeneous mix of Indian Army Air Defence assets into a unified C2 fabric:
- Radar systems — including 3D Tactical Control Radars, Low-Level Light Weight Radars (LLLWR), and Battle Field Surveillance Radars, each with different ranges and altitude envelopes.
- Weapons — Schilka self-propelled anti-aircraft, OSA-AK and Strela short-range missile systems, Akash medium-range systems, shoulder-fired Igla missiles, and progressively, indigenous counter-UAS solutions.
- Adjacent forces — the IAF's Integrated Air Command and Control System (IACCS) is the interoperability partner, allowing Indian Army Air Defence to operate within the broader airspace picture.
- Counter-UAS systems — DRDO's Anti-Drone System and iDEX-funded counter-UAS solutions are progressively integrating with Akashteer's C2 backbone.
The result is that an air-defence unit operating under Akashteer sees a unified tactical picture rather than a sensor-specific one. The radar, the optical tracker, the RF detector and the adjacent unit's report all converge in a single command screen with engagement-quality data on every track.
Why this is operationally significant
Pre-Akashteer, Indian Army Air Defence engagements were structurally vulnerable to the same problem that has plagued every air-defence force since the Yom Kippur War: the operator at the seat had a partial picture, made a partial decision, and engaged a partial target. Sensor fusion was manual; engagement authority was distributed; the decision loop was slow enough that low-and-slow threats — exactly the threats the Punjab and J&K drone-drop pattern presents — could complete their mission inside it.
Akashteer collapses the decision loop by automating the fusion step. The operator no longer has to assemble the tactical picture; the picture is assembled by the system and presented to the operator for the decision step. Decision quality, in this regime, becomes the primary determinant of engagement outcome.
Sensor fusion was the bottleneck. Decision quality is the new bottleneck. Decision quality is a training variable.
The training-side implication
Decision-quality bottlenecks are training bottlenecks. The Akashteer operator population — across multiple Corps of Army Air Defence units, across heterogeneous equipment mixes, across the active rotation cycle — needs to compound reps on the specific decision regime Akashteer enables. The reps required are:
- Classify-to-engage timing under procedurally varied threat conditions. The operator has seconds. The training pipeline must reflect that.
- Effector selection under cost-exchange constraints. A counter-UAS engagement may have multiple valid effectors. Which is selected is a judgment call that depends on engagement-rules training.
- Sustained-engagement performance under fatigue. A real air-defence engagement may run hours. Operator-fatigue performance degradation is a known variable.
- Multi-track prioritisation in a saturated tactical picture. The next generation of threats will not arrive one at a time — swarm attacks will arrive in groups. Prioritisation is itself a skill.
None of these reps are cheaply produced in live exercise. The radar emissions, the RF environment, the airspace clearances and the targets-of-engagement required all impose constraints that make live training the wrong tool for the job. Synthetic environments are the right tool. KAVACH-SIM is structured against precisely this operator-decision-loop requirement, with procedurally varied threat injection and engagement-rules-driven scoring.
Where Akashteer training fits in DefenceVR's stack
The DefenceVR counter-UAS training stack — KAVACH-SIM at the operator-decision layer, NETRA-SIM at the ISR layer, VAYU-SIM at the EW layer — composes against the Akashteer operational environment. A Corps of Army Air Defence operator trained on the integrated stack rehearses the decisions that Akashteer requires in the configuration Akashteer presents. The training-side investment compounds the procurement-side investment.
The 2026–2030 priority
Akashteer's induction is on a multi-year curve. The operator population that will sit at the seat of an Akashteer-equipped air-defence battery in 2030 is, in many cases, currently in pre-deployment training. The decision-quality reps that operator will bring to the first engagement are being banked now. The training stack the Indian Army standardises on this year is the stack that will produce those reps. The case for synthetic-first training in the counter-UAS layer is not an aspirational case. It is the operational case Akashteer's induction has already made.