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

TMA/TRACON

AirTOp also supports all key approach and departure structures for airports. AirTOp realistically simulates all related aircraft movements in the airport TMA/TRACON airspace and simulates all required departure/approach controller tasks.

Key benefits

Linking all airport processes and events with ATC on the surface and in the Terminal Area, such as advanced AMAN and DMAN and emulating ATFCM and CDM events, AirTOp will help the busy airport to understand capacity issues and underlying delay factors.

The integrated “what-if” capabilities will support quick decision making, from the strategic multi-million investment decision to day-to-day decisions supporting achievement of performance targets for delay, noise or cost and at the same time give users with diverging business objectives the choice between different scenarios.

Scenario definition

En-route domain objects, runways, SIDs, holding stacks, STARS and transition vectoring can be easily created/edited directly on the map, or using the adjacent information displays.

AirTOp supports all key static or dynamic (rule-based) restrictions associated to the above objects. These include speed/course/altitude restrictions along SIDs, STARs, manoeuvring areas on approach, rule-based departure/arrival separations, wake turbulence separations, etc.

AirTOp can import actual track trajectory records from various file formats (Stanly, FAA PDARS, …). Using the built-in styled and filtered trajectory display and playback, as well as vertical view and virtual walls, the AirTOp user can derive transition vectoring areas with their typical speed and altitude restrictions, whether or not they are published.

tma-image-1 tma-image-2

Rule-based departure and approach sequencing between dependent runways of single or multiple airports (New York metro and Frankfurt)
Approach sequencing combines speed control, vectoring, holding stacks and staggered operations

The rule-based runway dependencies concept of AirTOp lets users take into account all constraints imposed on the arrivals and departures of one runway by those on another. This includes synchronization of departures and arrivals on crossing or parallel runways and arrival staggered mode operations.  Separations (dep after dep, dep before or after arr) can be made for any pair of runways. They can be expressed as distance or duration, at runway lift off or start takeoff roll, for any combination of aircraft type, SID, SID group, departure fix, departure fix group, navigation equipment etc.

Simulated controllers tasks (tower, departure, pick-up, feeder) use all static or dynamic restrictions, and provide realistic departure and approach sequencing.

AirTOp also supports rule-based circuit/touch and go, as well as rule-based missed approach.

AirTOp also supports the modeling of flow management (En-Route queues/AMAN), time constrained 4D profile: see Traffic Flow Management page.

Reporting

Beside 2D/3D filtered and styled playback in top of maps and satellite data, AirTOp allows to report the following:3d

Controller workload can also be simulated dynamically, and can be customized for for both ATC and airport/tower controllers. The workload model can associate work duration to any event (e.g. TMA entries, vectoring/speed/holding control, landing/departure clearances, …). It can take also into account the monitoring of flight activities of all types (taxiing, stopped at crossing/stand-off, waiting for clearance etc).
The work duration associated to event handling can be split into generic user-defined activities (radio com, monitoring, conflict resolution etc), and the duration spent per event type and per activity can then be logged per rolling hour.

 

A customizable event log can be easily created by the user and exported to Excel files or an SQL database for external specific analysis. Events can be related to any action taken by a controller (see above) or an aircraft  (start takeoff roll, liftoff, runway touch down, runway exit, runway crossing reach, arrival at gate, start push back, start engine, start taxiing/runway crossing/lining-up etc). Each event  can be logged, together with information related to the current status of the aircraft (aircraft type, airline, landing/departing runway, speed/attitude, departure/arriving/long term allocated parking position, aircraft/airport delays, …).

Built-in event plotting and statistics query display are available and ready to use.

nymetro_trajectories

Filtered (altitude) and styled display of New York metropolitan area actual and simulated trajectories

screen-shot-2016-11-08-at-15-39-04

Built-in plotting of airport/TMA delays (rolling hour) comparing arrival gate/en-route/holding/sequencing delays with departure gate/taxi/runway delays after modeling new runway dep/arr separations and AMAN