ATC-pie: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (Version update (v1.0.2))
m (Infobox software: Switch the 3 in Python3 from the 'writtenin' parameter to the 'writteninversion' parameter.)
(29 intermediate revisions by 3 users not shown)
Line 6: Line 6:
| title                  = ATC-pie
| title                  = ATC-pie
| logo                  = ATC-pie-logo.png
| logo                  = ATC-pie-logo.png
| image                  = ATC-pie-screenshot-KSFOmess.png
| image                  = ATC-pie-screenshot-towerViewing.png
| alt                    = ATC-pie at the KSFO mess
| alt                    = Tower viewing, following a departing aircraft
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = 1.0.2 (Dec. 22, 2016)
| latestrelease          = 1.7.1 (Sept. 1, 2020)
| writtenin              = Python3
| writtenin              = Python
| writteninversion      = 3
| os                    = Any
| os                    = Any
| platform              = Qt5
| platform              = Qt5
Line 17: Line 18:
| type                  = ATC client
| type                  = ATC client
| license                = GNU GPL v3
| license                = GNU GPL v3
| website                = https://sourceforge.net/projects/atc-pie
| website                = http://mickybadia.free.fr/atcpie
}}
}}


'''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It features en-route centre control (CTR) as well as airport-based service (TWR, APP, GND...) where 3d tower viewing is possible. It is essentially designed for realism and simulates many tasks of real-life ATC such as strip rack and sequence management, transponder identification, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict anticipation.
'''ATC-pie''' is an [[air traffic control]] simulation program featuring:
* solo sessions, incl. voice instruction recognition and pilot speech synthesis;
* network sessions through [[FGMS]] and FSD;
* tutorial sessions for teacher supervision of an ATC student.


The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install (except for tower viewing, which requires a running FlightGear install and the appropriate scenery).
It can simulate en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and allows 3D tower viewing through [[FlightGear]]. It is essentially designed for realism and simulates many tasks and situations of real-life ATC such as:
* strip rack and sequence management;
* radar monitoring and transponder identification;
* handovers to/from neighbouring controllers;
* routing and conflict anticipation;
* flight plan filing and editing...


== Program features ==
To download the program and learn more about how to use it, read the ATC-pie [[ATC-pie installation guide|installation]] and [[ATC-pie user guide|user]] guides. If you have a question, check the [[ATC-pie FAQ|FAQ]] first, or try the forum for help.


The features listed below have been tested on various Linux versions, Mac and Windows.
== Screenshots ==
 
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.
 
<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Playing solo with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-runwayIncursion.png|Runway incursion detected and highlighted in red
ATC-pie-screenshot-flightPlans.png|Flight plan editor
</gallery>
 
== Working principles ==
 
You are the air traffic controller, working with equipment depending on your position and local facility. This may include a tower view, radar scopes, data links, etc. Your traffic is the aircraft connected by human pilots (FlightGear, FSD), or simulated with AI (solo) or by a teacher (student). They all contact you with different types of aircraft, [[transponder]] equipment and intentions.
 
=== Strips ===
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]]
Your basic traffic flow and sequence working unit is the '''strip''', each representing a controlled (or soon expected) aircraft. Strips are created, filled with details and moved across ''racks'' and ''bays'' until handed over to a different controller or shelved. Strip details can all be manually edited, and include:
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* information like aircraft type, airspeed, route... that can be provided by the pilots themselves when filing ''flight plans'';
* transponder code and flight parameter assignments (heading, altitude/FL, air speed).


=== General features ===
=== Radar ===
As in real life, the main radar technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], which only shows what is picked up from on-board transponders in its range. This means that:
* if a transponder is off or out of range, you will not see the aircraft on your radar screen;
* if a transponder is on and in range, you will at least be able to see its position and read a transponder code, and possibly its altitude, type, callsign... depending on the transponder mode and your radar capabilities.


Available games:
=== Linking strips ===
* FlightGear multi-player server connection ([[FGMS]])
Every strip can be '''linked''' to a flight plan and to a transponder contact on radar. A linked strip will automatically:
* Solo games with AI IFR traffic
* display its missing elements when available from the linked flight plan or aircraft transponder;
* Teacher–student tutoring sessions
* populate the information in the radar tag of the linked aircraft with useful details, e.g. assigned altitude.
* For all game types: en-route centre or airport control mode
* For all airport games: tower view available (rendered by FlightGear)


Common data sources:
=== Radar identification ===
* Airport and navigation data retrieved from the latest [http://data.x-plane.com X-Plane] file set
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]]
* Nav/AD data customisation in separate files
When using radar, ATCs use different methods to ''identify'' an aircraft and link the right contact to its strip. They can read an aircraft's callsign straight away if its transponder is squawking mode S, tell from reported positions, or use a transponder code.
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
 
* Real world declination lookup and true/magnetic distinction
For instance, say a transponder-equipped VFR traffic makes radio contact giving their callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for '''radar identification''' of aircraft–strip pairs such that:
* Script to assist data import from .sct sector files (EuroScope/[http://www.vatsim.net VATSIM], IVAO)
* the strip is assigned a transponder code;
* Custom background images (integrated [[OpenStreetMap]] retrieval helper)
* no other strip is assigned the same code;
* the aircraft is the only unidentified traffic squawking that code in radar range.
 
ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified".


FlightGear multi-player games:
== Detailed feature list ==
* Weather: real world METAR retrieval
* ATC handovers: strip exchange with other ATC-pie and [[OpenRadar]] instances in range
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. in-game retrieval, filing and editing (work on local copies and manage sync with online status), opening and closing
* In-app announcement of ATC sessions on Lenny64's popular event page


Solo games:
=== General ===
* In airport mode, configurable combination of TWR, GND, APP and DEP positions
Available session types:
* Randomised weather
* Solo simulation (AI IFR traffic)
* Handovers to/from virtual ATCs
* FlightGear networks (FGMS protocol)
* Airline choice and custom aircraft appearence
* FSD connections (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
* Configurable runways in use, airspace and entry/exit/routing points
* Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)
* Adjustable difficulty (traffic density)
* Departure–arrival and ILS–visual balance options


Teaching/learning sessions:
Available modes for all session types:
* Teacher spawns and manipulates traffic visible to student (flight and transponder settings)
* Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
* Strip exchange, configurable ATC neighbours and handover supervision by teacher
* En-route centre (free positioning of radar, no base airport or runway-related options)
* Wind control
* Traffic snapshots and recall to repeat situations with the student


GUI:
Common data sources:
* Floatable, dockable and closable GUI panes: strips, radios, text chat, etc. (window layout saved)
* Airport and navigation data sourced in the [http://data.x-plane.com X-Plane] format (old world-wide default file set included)
* Notification system combining selectable sounds, status bar messages and time-tagged history
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* Notes, window state, general and location-specific settings saved on close and restored on restart
* Radar background images and hand drawings (integrated EuroScope/[http://www.vatsim.net VATSIM]/IVAO .sct sector file import)
* Customisable colours
* Ground elevation maps (can be generated automatically with a provided script)
* Instruct taxi, assign vectors and change routes with direct drag-and-drop mouse gestures
* Real world magnetic declination lookup
* Multiple weather stations


=== ATC surveillance ===
=== ATC surveillance ===
Radar and transponders:
Radar and transponders:
* Full transponder support and mode-dependant radar behaviour (off, A, C, S)
* SSR mode selection and primary radar activation
* Radar identification assistant (detects unique matches between strip info and radar signals)
* Full transponder support and mode-dependant radar behaviour
* Primary radar activation (see targets without XPDR signals)
* Traffic identification assistant
* Open multiple radar screens
* Runway occupation/incursion detection
* Configurable horizontal and vertical radar ranges and rotation speed
* Position/track vs. assignment mismatch warning system
* Individual and general cheat modes
* Ignore contacts


Tower viewing (not in CTR mode):
Tower viewing for airport mode (requires FlightGear):
* Real-time rendering of the airport scene from tower viewpoint
* Renders view of airport, aircraft, weather, time of day
* Internally started (requires FlightGear installed) or through connection to an external instance
* Internally started or through an externally running instance
* Controller pane to orient/zoom view or follow aircraft
* Control panel to orient/zoom view or follow aircraft
* Possible use of custom scenery and aircraft model addition/substitution
* Additional views can be connected (for multiple camera angles)
* Additional views can be connected (for multiple camera angles)


=== Traffic management ===
=== Traffic management ===
Strips, racks, flight plans:
Strips and racks:
* User-defined racks with configurable colours for linked radar contacts
* User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from
* Runway boxes with automatic WTC timers when freed
* Strip auto-print for expected departures or arrivals
* Runway boxes with automatic RWY separation timers
* Loose strip bays with customisable backgrounds
* Loose strip bays with customisable backgrounds
* Link strips, FPLs and radar contacts to merge details and inform radar display, tracking conflicts
* Mouse drag to move strips along and across racks, runway boxes and loose strip bays
* Handovers with neighbouring ATCs


Routes, vectors, conflicts:
Routes, vectors, conflicts:
* Route parsing, drawing and world map view
* World route suggestions, presets, analysis, radar drawing and world map view
* Route presets and quick retrieval between two end airports
* Convenient mouse input for vectors, taxi instructions and waypoint changes
* Current leg and next waypoint display with geodesic calculations of headings and distances
* Current leg and next waypoint display with geodesic calculations of headings and distances
* Anticipated path conflict warnings and separation incident alarm
* Route/vector conflict anticipation and separation incident alarm
* Visible mismatches between assigned vectors and picked up positions (see [[:File:ATC-pie-screenshot-courseAndAssignmentsGraphics.png|all-in-one graphics]])
* Approach spacing hints for inbound sequences
 
Misc. tools:
* Quick point-to-point heading and distance measuring tool and access to Earth coordinates
* Direct text annotation of radar screen
* Custom alarm clocks with quick two-key timer set-up
* AD/nav point browser and indicator


=== Communications ===
=== Communications ===
Radio:
With aircraft:
* [[FGCom]] integration, incl. echo test and possible use of externally running client
* [[FGCom]] radio integration for FlightGear sessions (stand-alone processes and Mumble plug-in)
* ATIS recording with pre-filled preparation notepad (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]])
* Multiple frequency transmissions and monitoring
* Multiple frequency transmissions and monitoring
* Frequency-specific sound level selection
* Radio direction finding (RDF) and integration to radar
* Controller-pilot data link communication (CPDLC)
* Text radio chat in network sessions, with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
* ATIS recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)


Text chat:
ATC coordination:
* Preset message list manager
* Strip exchange with known ATCs (handovers)
* Predefined and custom aliases for context-sensitive replacements (general, location- and ACFT-specific)
* CPDLC authority transfers
* Message history and single-click dest. or message recall
* Private messaging with other ATCs (text "landlines")
* Hardcore communication sim possible by disabling unknown senders' callsigns
* General ATC chat room
* Senders blacklist management (filter out trolls)
* "Who has?" requests


== Screenshots ==
=== Session environments ===
<gallery mode="packed">
Solo sessions (AI traffic):
ATC-pie-screenshot-soloMode.png|Playing solo mode with three coloured racks
* Strip exchange: handovers to/from virtual ATCs
ATC-pie-screenshot-towerViewing.png|Tower viewing, following a departing aircraft
* CPDLC: transfers with ATCs and instructions/requests with ACFT
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
* Weather: randomised and progressively changing
ATC-pie-screenshot-routeDetailsView.png|View route details and world path
* Voice instruction recognition (with Sphinx)
ATC-pie-screenshot-routeConflictDetection.png|Route conflict warning
* Pilot read-back speech synthesis (with pyttsx)
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
* Airline choice and custom aircraft appearence in tower view
</gallery>
* Configurable airspace rules
* Adjustable difficulty (traffic density)


== Working principles ==
FlightGear network sessions:
* Strip exchange: full handover support with ATC-pie, compatible with [[OpenRadar]]
* CPDLC: supported but no ACFT capable of connection yet
* Weather: real world METAR retrieval
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. filing, editing, opening and closing
* ATIS: voice recording through FGCom
* In-app announcement of ATC sessions on Lenny64's event page


=== General ===
FSD network sessions:
You are the air traffic controller, working with or without a tower window or radar scope, depending on your position and local facility. Players will connect to the network (multi-player), AI traffic be simulated (solo), or teacher traffic generated (tutorial session), with different types of aircraft and [[transponder]] equipment.
* Strip exchange: handovers with other clients (although lossy if not ATC-pie)
* CPDLC: not supported by FSD
* Weather: fetch from server or retrieve real world METAR
* Flight plans: available from the network (although only editable by the pilots, and open/close not supported by FSD)
* ATIS: recorded as text only (sent through chat system)


As in real life, your main radar technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence unless you cheat or activate the primary radar, will show you only what you pick up from on-board transponders in its range. This means:
Tutoring sessions (teacher with student):
* if a transponder is off, you will not see the aircraft on your radar screen;
* Strip exchange: configurable ATC neighbours and handover supervision by teacher
* if a transponder is on, you will at least be able to see its position and read the transponder code, possibly its altitude and even its type and callsign, depending on the mode set by the pilot.
* CPDLC: fully supported, incl. transfers to/from student and dialogues with teacher ACFT
* Weather: controlled by teacher
* Traffic snapshots and recall to repeat situations with the student


=== Strips ===
=== Misc. ===
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]]
GUI features:
Your basic traffic flow and sequence working unit is the '''strip''', each representing a controlled (or soon expected) aircraft. Strips are created, filled with details and moved along and across ''racks'' until handed over to a different controller or discarded. Strip details include:
* Multiple window workspace (radar screens, strip racks and bays) saved by location
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* Floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* information like aircraft type, airspeed, route... that can be specified by the pilots themselves when filing ''flight plans'';
* Customisable colours
* transponder code and flight parameter assignments (or vectors: heading, altitude/FL, speed).
* Notification system combining selectable sounds, status bar messages and time-tagged history
* General and location-specific notes and settings saved on close and restored on restart


=== Linking strips ===
Convenience tools:
Strip details can be manually edited, but every strip can also be '''linked''' to a flight plan and/or a visible radar contact on the scope screen. Linking to a strip will automatically:
* Quick point-to-point heading and distance measuring tool
* make the strip display the missing elements available from the linked aircraft transponder or flight plan;
* Multiple weather station monitor
* inform the radar contact label with useful details provided on the strip, e.g. assigned altitude.
* Direct text annotation of radar screen
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.
* World airport, map navpoint and AD parking position browsing/indicating
 
* Aeronautical unit conversion calculator
=== Radar identification ===
* Custom alarm clocks with quick keyboard timer start
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]]
To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, or use a transponder code.
 
For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for '''radar identification''' of aircraft–strip pairs such that:
* the strip is assigned a transponder code;
* no other strip is assigned the same code;
* the aircraft is the only unidentified traffic squawking that code in radar range.
 
ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified".
 
== Using ATC-pie ==
To download the program and learn more about how to use it, read the [[ATC-pie user guide]]. If you have a question, check the [[ATC-pie FAQ|FAQ]] for help or try the forum.


[[Category:ATC-pie]]
[[Category:ATC-pie]]
[[Category:ATC clients]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]

Revision as of 12:57, 11 September 2020

ATC-pie
ATC-pie logo
Tower viewing, following a departing aircraft
Tower viewing, following a departing aircraft
Developed by Michael Filhol
Initial release February 1, 2015
Latest release 1.7.1 (Sept. 1, 2020)
Written in Python (Version 3)
OS Any
Platform Qt5
Development status Active
Type ATC client
License GNU GPL v3
Website

ATC-pie is an air traffic control simulation program featuring:

  • solo sessions, incl. voice instruction recognition and pilot speech synthesis;
  • network sessions through FGMS and FSD;
  • tutorial sessions for teacher supervision of an ATC student.

It can simulate en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and allows 3D tower viewing through FlightGear. It is essentially designed for realism and simulates many tasks and situations of real-life ATC such as:

  • strip rack and sequence management;
  • radar monitoring and transponder identification;
  • handovers to/from neighbouring controllers;
  • routing and conflict anticipation;
  • flight plan filing and editing...

To download the program and learn more about how to use it, read the ATC-pie installation and user guides. If you have a question, check the FAQ first, or try the forum for help.

Screenshots

Visit the ATC-pie screenshot category for more.

Working principles

You are the air traffic controller, working with equipment depending on your position and local facility. This may include a tower view, radar scopes, data links, etc. Your traffic is the aircraft connected by human pilots (FlightGear, FSD), or simulated with AI (solo) or by a teacher (student). They all contact you with different types of aircraft, transponder equipment and intentions.

Strips

The ATC-pie strip detail sheet

Your basic traffic flow and sequence working unit is the strip, each representing a controlled (or soon expected) aircraft. Strips are created, filled with details and moved across racks and bays until handed over to a different controller or shelved. Strip details can all be manually edited, and include:

  • most importantly, the aircraft's callsign, to be used on the radio;
  • information like aircraft type, airspeed, route... that can be provided by the pilots themselves when filing flight plans;
  • transponder code and flight parameter assignments (heading, altitude/FL, air speed).

Radar

As in real life, the main radar technology is SSR, which only shows what is picked up from on-board transponders in its range. This means that:

  • if a transponder is off or out of range, you will not see the aircraft on your radar screen;
  • if a transponder is on and in range, you will at least be able to see its position and read a transponder code, and possibly its altitude, type, callsign... depending on the transponder mode and your radar capabilities.

Linking strips

Every strip can be linked to a flight plan and to a transponder contact on radar. A linked strip will automatically:

  • display its missing elements when available from the linked flight plan or aircraft transponder;
  • populate the information in the radar tag of the linked aircraft with useful details, e.g. assigned altitude.

Radar identification

Radar identification: both matched strip and radar contact marked in blue

When using radar, ATCs use different methods to identify an aircraft and link the right contact to its strip. They can read an aircraft's callsign straight away if its transponder is squawking mode S, tell from reported positions, or use a transponder code.

For instance, say a transponder-equipped VFR traffic makes radio contact giving their callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for radar identification of aircraft–strip pairs such that:

  • the strip is assigned a transponder code;
  • no other strip is assigned the same code;
  • the aircraft is the only unidentified traffic squawking that code in radar range.

ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified".

Detailed feature list

General

Available session types:

  • Solo simulation (AI IFR traffic)
  • FlightGear networks (FGMS protocol)
  • FSD connections (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in April 2020)
  • Teacher–student tutoring (teacher spawns and runs the traffic visible to the student)

Available modes for all session types:

  • Airport (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
  • En-route centre (free positioning of radar, no base airport or runway-related options)

Common data sources:

  • Airport and navigation data sourced in the X-Plane format (old world-wide default file set included)
  • Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
  • Radar background images and hand drawings (integrated EuroScope/VATSIM/IVAO .sct sector file import)
  • Ground elevation maps (can be generated automatically with a provided script)
  • Real world magnetic declination lookup

ATC surveillance

Radar and transponders:

  • SSR mode selection and primary radar activation
  • Full transponder support and mode-dependant radar behaviour
  • Traffic identification assistant
  • Runway occupation/incursion detection
  • Position/track vs. assignment mismatch warning system

Tower viewing for airport mode (requires FlightGear):

  • Renders view of airport, aircraft, weather, time of day
  • Internally started or through an externally running instance
  • Control panel to orient/zoom view or follow aircraft
  • Additional views can be connected (for multiple camera angles)

Traffic management

Strips and racks:

  • User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from
  • Strip auto-print for expected departures or arrivals
  • Runway boxes with automatic RWY separation timers
  • Loose strip bays with customisable backgrounds

Routes, vectors, conflicts:

  • World route suggestions, presets, analysis, radar drawing and world map view
  • Convenient mouse input for vectors, taxi instructions and waypoint changes
  • Current leg and next waypoint display with geodesic calculations of headings and distances
  • Route/vector conflict anticipation and separation incident alarm
  • Approach spacing hints for inbound sequences

Communications

With aircraft:

  • FGCom radio integration for FlightGear sessions (stand-alone processes and Mumble plug-in)
  • Multiple frequency transmissions and monitoring
  • Radio direction finding (RDF) and integration to radar
  • Controller-pilot data link communication (CPDLC)
  • Text radio chat in network sessions, with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
  • ATIS recording and reminder alarm (see dialog with pre-filled notepad)

ATC coordination:

  • Strip exchange with known ATCs (handovers)
  • CPDLC authority transfers
  • Private messaging with other ATCs (text "landlines")
  • General ATC chat room
  • "Who has?" requests

Session environments

Solo sessions (AI traffic):

  • Strip exchange: handovers to/from virtual ATCs
  • CPDLC: transfers with ATCs and instructions/requests with ACFT
  • Weather: randomised and progressively changing
  • Voice instruction recognition (with Sphinx)
  • Pilot read-back speech synthesis (with pyttsx)
  • Airline choice and custom aircraft appearence in tower view
  • Configurable airspace rules
  • Adjustable difficulty (traffic density)

FlightGear network sessions:

  • Strip exchange: full handover support with ATC-pie, compatible with OpenRadar
  • CPDLC: supported but no ACFT capable of connection yet
  • Weather: real world METAR retrieval
  • Flight plans: interface with Lenny64's data base (the de facto FG standard), incl. filing, editing, opening and closing
  • ATIS: voice recording through FGCom
  • In-app announcement of ATC sessions on Lenny64's event page

FSD network sessions:

  • Strip exchange: handovers with other clients (although lossy if not ATC-pie)
  • CPDLC: not supported by FSD
  • Weather: fetch from server or retrieve real world METAR
  • Flight plans: available from the network (although only editable by the pilots, and open/close not supported by FSD)
  • ATIS: recorded as text only (sent through chat system)

Tutoring sessions (teacher with student):

  • Strip exchange: configurable ATC neighbours and handover supervision by teacher
  • CPDLC: fully supported, incl. transfers to/from student and dialogues with teacher ACFT
  • Weather: controlled by teacher
  • Traffic snapshots and recall to repeat situations with the student

Misc.

GUI features:

  • Multiple window workspace (radar screens, strip racks and bays) saved by location
  • Floatable/dockable panels and toolbars (see screenshot) and layout save/restore
  • Customisable colours
  • Notification system combining selectable sounds, status bar messages and time-tagged history
  • General and location-specific notes and settings saved on close and restored on restart

Convenience tools:

  • Quick point-to-point heading and distance measuring tool
  • Multiple weather station monitor
  • Direct text annotation of radar screen
  • World airport, map navpoint and AD parking position browsing/indicating
  • Aeronautical unit conversion calculator
  • Custom alarm clocks with quick keyboard timer start