Indian airspace,
digitised and analysable.
Every ATS route, waypoint, navaid, sector, FIR boundary and airport held as real geometry — with NOTAM decoding, movement and route-conformance analysis, oceanic entry/exit reporting and airspace planning built on top of it.
NOTAM decode — paste raw ICAO NOTAM text and see it on the digitised airspace.
Try a sample
NOTAM
A1375/26
Location
VOMF
Type
New
From
28 Apr 2026 03:00 UTC
Until
01 May 2026 11:30 UTC
Altitude
SFC – UNL
Affected routes
Modules
One digitised airspace. Many kinds of analysis on top of it.
NOTAM decoding is one module — not the product. Because the routes, sectors, boundaries and fixes exist as real geometry, any new question about Indian airspace becomes a module rather than a new application: route analysis, traffic analysis, sector loading, airspace and route restructuring, and more besides. 8 modules are live today; the rest are designed and marked as planned.
Digitised airspace base
LiveEvery published ATS route, waypoint, navaid, FIR boundary, control sector, TSA/TRA and airport in Indian airspace, held as real geometry from the eAIP — not a picture of a chart. Every other module is built on this layer.
NOTAM decode & plot
LivePaste raw ICAO NOTAM text. The Q-line, schedule, altitude band and affected geometry are extracted and rendered on the live map in under a second — closures in red, alternates in green, following true airway curvature.
Movement & route-conformance analysis
LiveUpload a daily movement log (DMS export). Each flight's actual track is reconstructed from its position reports, matched against the filed ATS route, and scored with a confidence figure — with off-route fixes flagged as deviations.
Oceanic entry/exit analysis
LiveChennai Oceanic modelled on its exact published boundary (OCH ∪ UPB). For every flight touching oceanic airspace: the entry point, the exit point, the flight level at each, and whether the level changed inside the sector.
Radial / DME position lookup
LiveGive a reference navaid or waypoint and a radial and distance — the way an aircraft working inside an exercise area reports its position — and see instantly which danger, restricted, prohibited or TSA/TRA areas that position falls in. Radial and distance ranges describe a whole block of activity, and Colombo FIR references such as KAT resolve too.
AUP / airspace use plan
LiveThe day's Airspace Use Plan parsed from the published PDF and drawn on the map — TSA/TRA activations, CDR2 availability, time bands and level blocks — and automatically cross-referenced against any NOTAM you decode.
Airport briefing & diagrams
LivePer-airport briefing pages built from eAIP data — runways, frequencies, navaids, procedures and the active NOTAMs for that aerodrome — alongside a rendered airport diagram.
NOTAM database & Q-code intelligence
LiveA searchable, sector-tagged NOTAM store with Q-code decoding, schedule expansion and status tracking, so a watch supervisor can answer 'what is live in my sector right now' without reading raw text.
Traffic flow & capacity analytics
PlannedSector loading by hour, peak-period counts, entry-point demand and route utilisation across the FIR — computed from the same movement data, to support capacity, sectorisation and staffing decisions.
Occurrence & deviation reporting pack
PlannedAuto-assemble the evidence for a reportable occurrence — track versus cleared route, level flown versus level cleared, timings and the flight's full log row — as a ready-to-attach pack for the WSO.
Radar / ADS-B track ingestion
PlannedIngest recorded surveillance tracks alongside the movement log so conformance is measured against the actual flown path at radar resolution, not just position reports.
And much more
The modules are a snapshot. The digitised airspace is the point.
Once every route, fix, sector and boundary exists as real geometry, almost any question about Indian airspace becomes answerable — and answering a new one means adding a module, not building another system. The list below is what people have already asked for; it is not the limit.
Custom analysis is part of the platform, not an exception to it. If your section needs something measured that isn't here, it can be built on the same model and the same data.
Route analysis
Utilisation, conformance, level occupancy and city-pair flows on any airway.
Traffic analysis
Volumes and mix by hour, day, entry point, operator and aircraft type.
Sector analysis
Loading, complexity, crossing counts and the case for splitting or merging.
Airspace & route restructuring
Test a proposed route, boundary or sector change against a recorded traffic day.
Boundary & LoA studies
Crossing points, levels and timings against adjacent FIRs.
Whatever you need next
A new question is a module on the same model — tell us what you need measured.
Data
Your unit already has the data. It just isn't analysable yet.
Every ATS unit holds movement data, flight plans and surveillance recordings — as spreadsheets, exports and PDFs that nobody can actually question. Point them at a digitised airspace and they stop being records and start being answers.
Unit data
- DMS logs
- Flight plans
- NOTAM / AUP
- Surveillance
Digitised airspace
- Routes & fixes
- Sectors & FIRs
- Boundaries
- Geometry engine
Answers
- Route conformance
- Entry / exit levels
- Deviations
- Flow & capacity
DMS daily movement log
ParsedCSV / XLSX export — one row per flight with filed route and up to 25 position reports (fix, time, level). Parsed today, validated on a full 2,195-flight day.
eAIP (AAI)
ParsedENR route tables, waypoints, navaids, FIR and sector boundaries, restricted/danger/prohibited areas, aerodrome data — the digitised base layer.
NOTAM text (ICAO format)
ParsedRaw Q/A/B/C/D/E field NOTAMs, pasted or stored — decoded into schedule, level band and map geometry.
AUP / UUP (published PDF)
ParsedThe daily Airspace Use Plan lifted straight out of the published PDF into TSA/TRA and CDR2 rows with times and levels.
Other DMS outputs & flight plans
PlannedOther DMS report formats held at the unit, FPL/RPL data and coordination records — the same engine reads them once the format is mapped.
Surveillance recordings
PlannedRadar / ADS-B / MLAT track replays, for conformance measured against the actual flown path at full resolution.
Adding a new source is a parser, not a new system — the airspace model, map, matching engine and reporting stay exactly the same.
Use cases
What the unit can actually do with it.
Grouped by who owns the question. Some of these are answered today; the rest become possible the moment the relevant data is pointed at the same airspace model.
Worked example
Reporting of significant deviation from parameters
DGCA requires mandatory reporting of unintentional significant deviation from intended track or altitude, and Chennai ATM Operational Note 169/2026 directs every controller and supervisor to report deviations from the cleared route, level or speed — whether or not an incident results.
Detecting those deviations by observation alone means the ones nobody happened to notice are never reported. This platform reads the day's movement data, compares every flight's actual track against its cleared route and every reported level against the level it should have held, and lists the exceptions — with the map, the levels, the timings and the original log row attached for the WSO.
Safety & compliance
Turning a day of traffic into evidence, not anecdote.
- Screen a full day of movements for aircraft that left the cleared ATS route centreline.
- Flag flights that maintained a level other than the one cleared, with the level at every reporting point.
- Detect level changes inside oceanic airspace where the level should have stayed constant.
- Check proximity of tracks to restricted, danger and prohibited areas and active TSA/TRA blocks.
- Resolve a radial-and-distance position report straight to the exercise area it falls in.
- Assemble the supporting data for a reportable occurrence — track, levels, timings and the original log row.
Watch supervision & live operations
One map instead of five sources.
- See what is actually live in a sector right now — NOTAMs, AUP activations and CDR2 availability together.
- Decode an incoming NOTAM to geometry immediately instead of reading coordinates off text.
- Cross-reference a NOTAM against the day's AUP to see which airspaces and conditional routes it hits.
- Work out contingency routing when a route or airspace block goes unavailable.
- Plot a block of activity given as radials and distances from a navaid, and see what it covers.
- Build a shift-briefing view for a sector or aerodrome before taking over the position.
Capacity, flow & airspace planning
Decisions backed by a real traffic day, not an estimate.
- Measure demand at each oceanic entry/exit point by hour of day.
- Quantify route utilisation — which airways actually carry the traffic, and at what levels.
- Study sector loading and peak periods to support sectorisation and manpower cases.
- Test an airspace or route change against a recorded traffic day before proposing it.
- Monitor whether a newly published route or procedure is actually being used after implementation.
Investigation & coordination
Answer a query about a specific flight in seconds.
- Reconstruct one flight's path, levels and timings across the FIR, with its complete original log row.
- Answer 'which flights crossed this point/boundary between these times' for a coordination query.
- Support Letter of Agreement and bilateral discussions with adjacent FIRs using actual crossing data.
- Verify entry and exit conditions agreed with a neighbouring unit against what was flown.
Quality management & reporting
Recurring returns produced from data, not by hand.
- Produce periodic route-conformance and deviation summaries for SQMS review.
- Track deviation trends by route, operator, entry point and time of day.
- Provide a repeatable, auditable method so two people analysing the same day get the same result.
- Export any result set to CSV for onward reporting.
Training & familiarisation
The geometry, visible.
- Familiarise trainees with FIR and sector geometry, route structure and boundary points.
- Teach NOTAM and Q-code reading against a live map rather than raw text.
- Walk through real traffic days in a classroom without needing operational systems.
Built for
The Air Traffic Management department — end to end.
Built inside the unit, for the people who run it: the officer on position, the supervisor on watch, the section that has to report it, and the people who plan what the airspace looks like next.
Air Traffic Control Officers
Sector-aware NOTAM and AUP picture, route geometry, boundary points.
Watch Supervisory Officers
What is live right now, and the data behind any occurrence to be reported.
SQMS / safety management
Deviation screening, conformance trends and repeatable, auditable analysis.
ATM / airspace planning
Route and sector utilisation, boundary studies, change proposals against real days.
Capacity & flow management
Entry-point demand, peak periods and sector loading from actual movements.
Regional & corporate ATM
One comparable method and picture across units instead of unit-by-unit spreadsheets.
ATC training
FIR geometry, route structure and NOTAM reading taught on a live map.
AIS & CNS coordination
NOTAM and AIP data checked visually against the airspace it describes.
Why one platform
Indian airspace is published, not digitised.
So nothing can be asked of it.
The routes, sectors, boundaries and fixes live in AIP documents and charts. The traffic lives in DMS exports and spreadsheets. Nothing joins the two, so every question gets answered by hand, slowly, and differently each time. Did this flight stay on route. Which entry point is loaded. What does this NOTAM actually close.
Indian Digital Airspace holds the airspace as real geometry and points the unit's own data at it. One model, one map, one method. A new question becomes a module instead of a new system.
Digitised
Geometry, not scanned charts.
One platform
Modules, not separate tools.
India-first
Built on the AAI eAIP.
Built inside ATM
By a controller, for the watch.