Indian Digital Airspace
Digitised Indian airspace — and everything you can analyse with it.
Indian Digital Airspace is an internal platform for the Air Traffic Management department of the Airports Authority of India. It holds Indian airspace as a digitised model — every published ATS route, waypoint, navaid, FIR boundary, control sector, special-use airspace and aerodrome, as real geometry rather than as a chart or a document — and runs analysis modules on top of it.
The unit's own data is what it analyses. A daily movement log exported from DMS, a NOTAM, the day's Airspace Use Plan: each is read against the same airspace model, so questions that previously needed a controller, a chart and a spreadsheet get answered directly — with the working shown on the map.
NOTAM decoding was the first module and is now one of several. The design intent is that a new question about Indian airspace becomes a new module on the existing model, not a new application.
How it works
Four steps, one model.
01
Digitise the airspace
The AAI eAIP is converted into geometry — routes, fixes, navaids, boundaries, sectors, airspace volumes and aerodromes — so the airspace can be computed against, not just read.
02
Point unit data at it
A DMS movement log, a NOTAM, an AUP PDF. Each format needs a parser; everything downstream is shared.
03
Match and measure
Tracks are matched to routes, boundaries are crossed and interpolated, levels are captured at entry and exit, and anything off-corridor is flagged.
04
Show it and export it
Every result is visible on the same map and exportable as CSV, so a finding can be checked, defended and reported.
Capabilities
Exactly what exists today, and what is planned.
“Live” means usable in the application now. “Planned” means designed and specified but not yet built. Nothing on this page is claimed as live before it works.
Airspace model
| Capability | What it does | Status |
|---|---|---|
| ATS route network | All published airways with true geometry, waypoints in sequence, and route-segment lookup. | Live |
| Waypoints & navaids | Named fixes, navaid positions with magnetic variation, radial/DME token resolution. | Live |
| FIR, sector & airspace boundaries | FIR boundaries, control sectors, TSA/TRA, restricted/danger/prohibited areas as polygons. | Live |
| Chennai Oceanic boundary | Exact published boundary (Oceanic Chennai ∪ Upper Port Blair Oceanic), controller-verified. | Live |
| Aerodromes | Airport positions, runways, and rendered airport diagrams. | Live |
| Radial / DME position lookup | Radial + distance from any navaid, waypoint or airport → which danger, restricted, prohibited or TSA/TRA areas that position or block of activity falls in. | Live |
| Colombo FIR reference data | Colombo FIR and TMA limits, the KAT / MTL / CHB / RM navaids and 93 named waypoints from the Sri Lanka eAIP — so a radial/DME position given from KAT resolves like any Indian one. | Live |
| Colombo ATS route structure | The Colombo airway network, to extend route matching and conformance across the southern boundary. | Planned |
| Distance & bearing ruler | Snap-to-fix measuring between waypoints, navaids, airports or free coordinates, with running totals. | Live |
| Nationwide sector detail beyond Chennai | Same depth of sector and unit data for the remaining Indian FIRs. | Planned |
NOTAM
| Capability | What it does | Status |
|---|---|---|
| Paste-and-plot decoder | Raw ICAO NOTAM → Q-line, schedule, level band, geometry, on the map in under a second. | Live |
| Q-code intelligence | Q-code decoded to subject and condition, with sector tagging and status. | Live |
| NOTAM database | Stored, searchable NOTAMs with schedule expansion, status badges and per-airport views. | Live |
| AUP cross-reference | Any decoded NOTAM automatically checked against the day's TSA/TRA and CDR2 rows. | Live |
| Automated NOTAM ingestion | Direct feed instead of manual entry, with change detection and alerting. | Planned |
Movement analysis (DMS data)
| Capability | What it does | Status |
|---|---|---|
| Movement log import | CSV / XLSX daily movement log, one row per flight, up to 25 position reports each. | Live |
| Route detection & confidence | Each flight's track matched to candidate ATS routes with a confidence percentage. | Live |
| Deviation flagging | Resolved fixes lying outside every candidate route corridor are flagged as deviations. | Live |
| FIR entry / exit levels | Flight level at FIR entry and exit, interpolated at the boundary. | Live |
| Oceanic entry / exit analysis | Entry point, exit point, level at each, and level-change detection inside oceanic airspace. | Live |
| Track & filed-route map | Full flown path plus filed waypoints reconstructed, drawn on the digitised airspace. | Live |
| Filtering, sorting & CSV export | By callsign, route, traffic type, operator, confidence, level band, deviations, entry/exit point. | Live |
| Multi-day trend analysis | Persist uploads and compare across days, weeks and months rather than one file at a time. | Planned |
| Traffic flow & capacity analytics | Sector loading by hour, peak counts, entry-point demand, route utilisation. | Planned |
| Occurrence reporting pack | One-click evidence bundle for a reportable deviation, ready to attach to the report. | Planned |
| Radar / ADS-B track ingestion | Conformance measured against the actual flown path at surveillance resolution. | Planned |
Airspace planning & briefing
| Capability | What it does | Status |
|---|---|---|
| AUP day map | Daily Airspace Use Plan parsed from the published PDF and drawn with times and level blocks. | Live |
| Airport briefing pages | Per-aerodrome briefing built from eAIP data plus that airport's active NOTAMs. | Live |
| Airspace change what-if | Test a proposed route or boundary change against a recorded traffic day before proposing it. | Planned |
Ownership & intended use
Internal use — Airports Authority of India. Built for the Air Traffic Management department and Air Traffic Control Officers. Not for public distribution.
Developed by
Sai Venu Gopal Reddy
Manager (ATM) · Airports Authority of India, Chennai
Built in-house within the unit. For access, a walkthrough, or to have another data format supported, contact the developer directly.