See small drones before they cross the border, and close the gaps they fly through.
Shyena is low-altitude airspace awareness for India's borders. It brings together cited drone figures, a sensor coverage planner for the Amritsar and Tarn Taran line, airspace and own-drone geofence tools that keep your own drones on your side of the line, and a seeded night replay. It is defensive: detect, track, classify, alert, plan lawful non-kinetic responses by authorised agencies, and keep evidence.
Drones now carry most cross-border drug deliveries into Punjab. BSF recovered 21 drones on the Punjab border in 2022, 107 in 2023 and 294 in 2024 (The Tribune, 14 Nov 2025). Of 305 drone-linked drug trafficking cases recorded in India in 2025, 298 were on the Punjab border (Ministry of Home Affairs reply in the Rajya Sabha, via Millennium Post, 22 Jul 2026).
Loading the figures…
The flights are hard to stop. They peak between 22:00 and 04:00, drop in fields 3.5 to 10 km inside, often follow pre-programmed GPS routes that RF detectors cannot hear, and fly home when jammed (Indian Express via SuperKalam, 12 Sep 2026). Own drones carry their own risk: on 5 May 2026 a BSF surveillance drone came down 10 to 20 yards inside Bangladesh at Patgram (Prothom Alo).
- Shows every official drone figure with who counted it, the period and the report, checks each report still says it, and adds a sample of individual incidents from the news, with no person named.
- Plans sensor coverage on the 238 km Amritsar and Tarn Taran line: radar, EO/IR, RF and acoustic, with line and drop-corridor coverage, gaps, warning time and the fewest sensors that close them.
- Maps advisory drone zones around 77 border-region aerodromes and the 25 km border belt, and sizes an own-drone geofence from speed, wind, reaction time and navigation error.
- Replays a simulated night with tracks, classification confidence, alerts and human-approved responses, compares layouts over 50 simulated nights, and exports the night as a trial log.
- Gives a sourced response playbook: detect, classify, alert, respond lawfully through authorised agencies, keep evidence, recover payloads safely, and test equipment before fielding it.
- DetectLayered radar, cameras, RF and acoustic sensors along the line and in depth.
- ClassifyEach cue changes the odds a track is a drone; a camera or RF match confirms it.
- AlertWatch, warning, danger and search levels, each with a recommended action and a police handoff.
- RespondOnly authorised agencies, only lawful non-kinetic means, and a person decides.
- EvidenceLogs, video and the drone itself kept under a chain of custody.
- InputsOfficial figures as reported by BSF, Punjab Police, the Ministry of Defence and the Ministry of Home Affairs; border lines and aerodromes from OpenStreetMap and OurAirports; sensor ranges from cited measurements; a seeded simulator.
- ViewsIncidents and tempo, airspace and own-drone geofence, the coverage planner, and the night replay with its 50-night comparison.
- Act and accountThe playbook: detect, classify, alert, respond lawfully and keep evidence, with every decision logged to Sakshi.
Every formula, threshold and assumption is in the methods note and on the console's Methods page, with its source.
| Source | What | Licence | Status |
|---|---|---|---|
| BSF, Punjab Police, Ministry of Defence, Ministry of Home Affairs, as reported | Drone recoveries, seizures, intrusions and drug cases; 43 figures from 18 reports | Cited reports; figures only | Checked |
| GDELT DOC 2.0 | News articles about drone incidents, 2024 to date; headlines not stored | Free with attribution | Partial |
| OpenStreetMap (Overpass API) | Approximate border lines and district outlines | ODbL 1.0 | Live |
| OurAirports | Aerodromes and runways near the land borders | Public domain | Live |
| Natural Earth 1:10m | Boundary lines for distance to the border | Public domain | Live |
| Peer-reviewed and government guidance | Sensor ranges (EuRAD 2018, IEEE HST 2018, CISA 2025), response and evidence practice (INTERPOL 2020, MHA 2023) | Cited | Cited |
| Shyena simulator | A night of crossings, birds and clutter; 50-night comparisons | Seeded, reproducible | Simulated |
- Border units and sector headquarters: where the line and the drop corridor lack coverage, and what closes the gap.
- State police anti-drone and checkpoint units: when and where drops happen, and the response sequence that preserves evidence.
- Own-drone operators: a geofence setback that holds in wind, after a link loss and under GNSS interference.
- Airport and airspace authorities: which aerodromes sit near the border, and where counter-drone measures need coordination.
- Defensive by design: detection, tracking, classification, alerting, lawful non-kinetic response planning and evidence. No weapon-targeting guidance.
- Responses only through authorised agencies: counter-drone jammers need Ministry of Home Affairs permission (Ministry of Defence for the defence forces) under the Cabinet Secretariat's jammer guidelines.
- Software recommends; trained people decide. Every response, including "no action", is logged.
- Events and places, never people: headlines are not stored, arrest stories are excluded, and no person, border outpost or troop position is mapped. Aerodromes come only from public aeronautical data (OurAirports), including air force stations, because own drones must keep clear of them.
- Simulated data is marked as simulated on every page and in its JSON. Airspace zones are advisory; the Digital Sky map is the authority.
- Sensor ranges are planning assumptions. Tree lines, crops, villages, fog and RF noise change them; plans need a site survey.
- The border line is approximate and must not be used for navigation or to program a geofence.
- Official figures come through press reports, some second-hand; agencies count differently.
- The news sample is incomplete by nature and is never presented as a count.
- The simulator's likelihood ratios and response effects are assumptions, not field measurements.
One sector for one season. We load your sensor list and ground survey, measure real detection ranges against these plans, replay your own logs through the classifier, and produce trial logs in the form a certifying committee can review. contact@trinetra.in