We use cookies to ensure you get the best experience on our website. Find out more here.

En-route Simulation

AirTOp supports all key en-route structures and controller tasks, as well as all static or dynamic restrictions related to them, thus providing realistic en-route simulation.

Key benefits

AirTOp provides easy to use high fidelity airspace and air traffic models ideal for capacity studies, resectorization projects, reorganisation of routes or free-route or RVSM implementation, and used by more than 20 ANSPs worldwide.

The airspace model can quickly be linked to airports and ATFCM modules and capacity, workload, delay, economic or environmental performance data is easily made available in the format you need it to have meaningful discussions with stakeholders.

Scenario definition and modeling

Waypoints, ATS routes with altitude and/or speed restriction per segment direction, ATC sectors and dynamic sectorization, FLAS areas, radar controller tasks and dynamic allocation of a radar controller to a sector, can all be easily defined by simply clicking on the map, or via the adjacent information display.

They can also be completely or partially imported from external data  sources.  The routing concept in AirTOp provides an easy way to quickly create en-route traffic simulation, avoiding duplication of traffic paths for aircraft flying to or from the same destination.

It supports the creation of flight routes mixing waypoints and airways/ATSRoutes. The ATSRoutes concept allows the creation of bi-directional airways, with opened flight levels specified by segment.

Modeling of sectors (elementary or combined, military), control centers (with their associated sector opening schemes, entry and occupancy capacities), as well as regional airspace (NAS, ECAC, …) is supported.

Letters of agreement (departure or arrival altitude/speed restrictions), context-based altitude changes, dynamic re-routing to avoid overloaded or closed sectors (military or weather), .., can be easily entered into the scenario using user-readable rules associated to controllers. They can then be realistically simulated.

Flow Management, AMAN, time constraints modeling: see Traffic Flow Management page.


Vertical view comparing actual flown trajectory (based on radar track record, demand and simulated). X-axis can be based on time, duration or distance. View can also show altitude or distance difference between all 4D trajectory types.



Conflict resolution rule base editor

Conflict detection and resolution can be modeled using a user editable conflict resolution rule base. The rule base includes resolution strategies (stop climb/descent, vector parallel/behind, cruise level change, earlier descent, follow at same speed/descent rate, shortcut etc) that can be customized by the user, taking into account the nature of the potential conflicts detected by the simulated radar controllers (conflict type, relative position of aircraft (highest, slowest), destination of aircraft, routing merging or not, distance to TOD, resolution manoeuvre feasible in sector, etc).


Aircraft movements and controller tasks, including conflicts detected and resolutions applied, conflict resolution demand, sector movements/entries/exit, flight events etc, generate exportable report events that can be used offline to realistically calculate the controller’s workload.

Controller workload can also be calculated dynamically in a user-customizable way. The workload model can take into account any event, and associate work duration to each one. It can also take into account monitoring activities of flights with any given attitude (climbing, cruising, in approach, holding etc). The work duration associated to event handling (e.g. sector entry in climbing, altitude change clearance etc) can be split into generic user-defined activities (radio com, monitoring, conflict resolution etc). Duration spent per event and per activity can then be logged per rolling hour.

Built-in statistics per sector, flight, airport, or runway can be easily queried and exported (Excel file, SQL databases). Result statistics can also be aggregated from multiple runs with random variations.


Airspace & sector report example: time distribution (rolling hour) of entry/exit count, average/max occupancy, average flown distance/duration/fuel burned in airspace, controller workload etc

Default and custom made statistics for sectors, flight, airport, runways, waypoint pair, routing slices etc