Back at the end of 1998, IVAO was created as alternative to the SATCO network. Its main goals were, and still are, to provide a friendly and ’fun’ environment for Flight and Air Traffic Control simulation, while still maintaining it ”as real as it gets” as much as possible.
Starting with a few dozen friends, IVAO has now grown to one of the biggest flight simulation communities in the world, with nearly 60000 members. During these past 8 year, numerous people have helped build IVAO to what it is today. Great work has been done, providing many services to our members, both at the IVAO headquarters level, as well as in the various divisions that are part of IVAO.
Now we’ve come to a new milestone: the creation of a new software-suite: replacing the glorious, but somewhat outdated, ProController and Squawkbox, by a new generation of software. With great pride, I’m happy to announce the availability of the first component: IvAc - IVAO virtual ATC client. Also other components are now being developed and/or tested. This includes, voice support, server components and more.
Many thanks to all the people who made all this possible. Let’s make the best and oldest network, IVAO, even better!
Erwin Lion President of IVAO
A lot of people contributed to IvAc in various ways. We would especially like to thank all IvAc beta testers for the hours of work they spent in debugging and commenting IvAc and of course all the IVAO members who contributed ideas to the project.
In particular, we would like to thank:
Alain Debrower (Kortrijk Tower), Guy Viselé (Belgocontrol), Luca Bertagnolio (Milano Radar), René Foppes (Amsterdam Radar), Fernando Geronimo (Eurocontrol) and Filip Vanstraelen (Eurocontrol), for allowing us to visit and / or giving information about their ATC systems.
Allen W. Sindel and Alain Debrower for their help with the manual
Sebastien Boutry, Miguel Teixeira, Walter Peeters and Jan Cuypers, for the public presentations of IvAc.
Gustavo Hernandez, Alain Debrouwer, Keith Ryan, Erwin Lion and Fabio Ferragi, for trust in and support to our project
And finally we would like to thank our friends and families who respected our situation and gave us the time we needed for the project.
This version of the IVAO virtual ATC client, hereafter called “IvAc”, is distributed under a PUBLIC license. This means that the user of this software product shall comply in all respects to the following Terms and Conditions:
This end-user license and your right to use this software is effective upon installation of the software and will terminate if you fail to comply to the Terms and Conditions of this agreement. By using this software, you agree that upon such termination of this agreement, you will destroy all copies of the software and documentation you received.
You may use this program free of charge on ANY compatible computer as long as you are a member of the International Virtual Airline Organisation (www.ivao.aero), and use it on their network authorized servers. You are NOT ALLOWED to distribute, rent, lease or sublicense this program or its documentation to other users.
THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION), HOWEVER CAUSED, AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software is Copyrighted by the authors of the program: Bart Devriendt, Filip Jonckers and Kenny Moens.
This software is Copyrighted by the International Virtual Aviation Organisation (www.ivao.aero).
Flying online with IvAc on IVAO is quite simple. You just need to get a few programs, and set them up correctly. This manual will help you with these points.
First, you need a computer running Windows 2000 or XP (only partial support for Windows 98 and ME). IvAc impose a minimal load on your computer, like any other Multiplayer session does.
You also need a user account on the IVAO network. If you don’t have an account yet, you can create one at https://ivao.aero/members/person/register.htm . Write down your VID and your IVAO password, you will need them later.
Now you need to download some software.
Find more information about software used on the IVAO network at https://www.ivao.aero/softdev/software.asp
You can consult the activity of the IVAO network by opening the following web page https://webeye.ivao.aero/
Controlling online requires you to be connected to the Internet during your session (unsurprisingly so!). Please note that certain low-bandwidth connections such as GPRS might give less than optimal results, particularly for voice communication, with added delays and poor voice quality. Try to be online using at least a 56k modem connection if possible, to achieve good results in your online flying experience.
Remember that the official forum where to ask for support about IvAc is the IVAO Forum available at:
Installation of IvAc is very simple. Unzip the downloaded setup files and run the setup program.
Install IvAc to a directory of your choice. After setup, run IvAc by selecting it from the windows start menu or by double clicking the icon on the desktop.
When you start IvAc for the first time, it will ask you to load a sector file. Sector files are located in the SectorFiles subfolder and contain all the data needed to draw a radar screen. Go to the directory where you stored your previous sector files and load the sector file of your choice.
Before continuing, make sure you have loaded a sectorfile.
Open this dialog box by clicking on the PVD button on the toolbar and selecting “General Options...” (Figure 4.1).
In the general options dialog, you can change the look of the windows in IvAc.
You can set the background color and the fontcolor of the IO Window, COMMBox and ATCBox (Figure 4.2). If you are behind a proxy server you can also enter the necessary configuration parameters in this dialog. This is necessary because IvAc downloads an updated server list from the internet on startup.
In the PVD menu select “PVD Options...”. The PVD Options dialog pops up (Figure 4.3).
Select the wanted refresh rate of the PVD. The lower the value the faster the PVD redraws itself. This value can have an effect on general performance of IvAc. You can adjust this setting if you have an older computer or slow video card (Note: A 3D card with OpenGL support is strongly recommended)
Select from the PVD menu “COMMBox Options...” (Figure 4.1). The COMMBox Options window (Figure 4.4) will open and you will see 5 groups of options to customize:
You can also open this screen by selecting “Options…” from the context menu.
Note: Transparency is known to give a flickering effect on most video cards - this is a known problem caused by the redrawing of the PVD screen. If this occurs, leave transparency at 100%.
You can choose a different highlight color for every group of tabs in the COMMbox.
Note: As an example, if no color is set for the COM1 frequency, the COM button in the toolbar will loose the hightlight color when a message is received on this frequency. The order is from right to left.
When you select “ATC Options...” from the PVD Menu (Figure 4.1) you get the ATCBox Options Dialog (Figure 4.5).
Here you can change some preferences for the ATCBox:
Prefixes to show
In this input field you can enter prefixes that override the ATCBox filter buttons (see chapter 4). You can also enter the first two letters of ICAO codes. E.g. EB for all stations in the Brussels sector.
In the example above all ATC stations in EB* (Belgian FIR) and surrounding center controllers (EHAA, EDFF, EGTT,…) will always be shown in the ATCbox whatever filter button is enabled. However, the two letter ICAO code option will not work in the USA.
Remark: Transparency is known to give a flickering effect on most video cards - this is a known problem caused by the redrawing of the PVD screen. If this occurs, leave transparency at 100%.
When you select “IO Options…” from the PVD Menu (Figure 4.1) you get the IO Options Dialog (Figure 4.6).
Check the “Show Inbound flights” box to enable the listing of inbound flights in the IO Window. In this input field, you have to define a list for the destinations you want to show. Again, like in the ATCBox Options dialog, you can use the first two letters of an ICAO code.
Check the “Show Outbound flights” box to enable the listing of outbound flights in the IO Window. In this input field you have to define a list for the origins you want to show. Again, like in the ATCBox Options dialog, you can use the first two letters of an ICAO code.
Remark: Transparency is known to give a flickering effect on most video cards - this is a known problem caused by the redrawing of the PVD screen. If this occurs, leave transparency at 100%.
When you select “Label/Route Options...” from the PVD Menu, (Figure 4.1) you get the Label/Route Options Dialog (Figure 4.7).
Cleared Flight Level
When you select “Conflict Options...” from the PVD Menu, (Figure 4.1) you get the Conflict Options Dialog (Figure 4.8).
Aliases are used to reduce the typing of the controller. You can define your own commands. These pre-defined messages will be sent to your chat dialog box.
Alias File editing
Open the PVD menu and select “Aliases...” - the Aliases edit window (Figure 4.9) will open:
You can add additional entries in the empty line at the bottom of the list or delete the selected line by pressing the “delete” button.
An alias has 2 parts: name and content. The name is defined without the dot. You can use these variables and define an additional 9 arguments by using $1 up to $9.
|$1, $2, ..., $9||arguments|
|$aircraft||selected aircraft callsign|
|$callsign||controller callsign (your callsign)|
|$metar||current default metar|
|$winds||active winds detail (metar)|
|$cfl||cleared flightlevel of selected aircraft|
|$cwp||cleared waypoint of selected aircraft|
|$csp||cleared speed of selected aircraft|
|$utc||current time (Zulu)|
Table 4.1 – Alias variable fields
With the Color Schemes Editor you can change font type, colors for labels, VOR, FIXES, etc… It's easy to use, and you can save your favorite color profile. Open the PVD options on the toolbar and select “Color Scheme Editor” (Figure 4.10).
Under font for navdata and aircraft labels, you can change the font and size for the respective labels.
There is a whole list of items where you can selectively change the color. In the following example, we are changing the “Airway High Label” to “Bright Green”. Select the label under Objects, and in the Color of the Selected Object, scroll until you find “Bright Green”. Press the APPLY button, and you will see the Airway High Label has changed color.
Saving color Scheme
Now it's time to save your settings for your next controller session online. Press “Save As”, name your new color scheme, and press “Save”. Be sure that you save the scheme under the map Colorschemes subdirectory.
The “Apply” button will save your changes to the current color scheme - so before changing colors, use “save as” to create your own color scheme.
Hint: We have provided several real life color schemes. As you already noticed, the colors used in real life are very soft and monotone. Try to keep your color scheme as real as possible!
Loading color scheme
You can also load another color scheme for editing by using the “Load” button. The loaded color scheme will now become the active color scheme.
You can add sounds to different events using a Sound Scheme. Open the Sound Scheme Editor via the PVD menu (Figure 4.13):
If no sound scheme was previously loaded, a file open dialog will appear. You can select an existing Sound scheme or press the cancel button to create a new sound scheme. Next the Sound scheme editor will open (Figure 4.14):
For example, we would like to add a sound when we get disconnected from the network:
You can test the selected soundfile by pressing the [play] button
Don't forget to save the sound scheme file using the [Save As] button.
When you press the Connect button on the toolbar, you will get the Connection dialog screen (Figure 5.1).
Fill in your name, correct IVAO account/password information and if applicable, you may want to hide your SUP/ADM rating by checking the “Hide SUP/ADM rating” box. Although you are not visible as SUP/ADM when you hide your rating, you still will get WALLOP messages. At startup, IvAc downloads information about all IVAN network servers and starts pinging them. When opening the Connect screen, IvAc proposes a server to use. It is recommended to use this server to spread load on all servers. A default range is setup for the selected position.
When you check the “Remember VID/Password” box, your VID/Password is reminded the next time you start IvAc. Note that your password is always reminded in the current session of IvAc, thus it is only removed after a restart of IvAc.
If you are using voice, check the voice checkbox and select the IVAO voice server you are connected to. The voice information will be added automatically in your ATIS by the AUTO-ATIS system (See chapter 6). Do not add your callsign, IvAc will automatically add this for you.
WARNING! IvAc will NOT create the channel on TeamSpeak for you, it will only startup and connect to the correct server. The channel creation is planned, but not supported by TeamSpeak SDK yet.
IvAc contains an AUTO-ATIS generator. The only thing you need to do is fill in the ATIS settings (see Figure 6.1). When a new METAR is retrieved from the server or when you change the ATIS settings, IvAc automatically updates the ATIS to the next version letter, e.g. Bravo, Charlie, etc. This ATIS letter is shown in the upper right corner, next to the weather information and Clock (ZULU TIME). With the preview button, you can preview the ATIS as it will be shown to the pilot. When a pilot requests your ATIS, this is shown in the MSG tab in the COMMBox.
The toolbar (Figure 7.2) is found on the top of the IvAc Window
The function and the short key of which button is found in the Table 7.1 below:
|CONN||Connect/Disconnect to the IVAO Network|
|DISCON||Connect/Disconnect to the IVAO Network|
|PROF||Save/Load Controller Profile|
|PVD||PVD (Plan View Display) options menu|
|I/O||show/hide INbound/OUTbound flights||F3|
|ATC||show/hide ATC list||F2|
|L+||increase Leader line length|
|L--||decrease Leader Line Length|
|0 – 8||Speedvector line (timeline)|
|CC||show/hide ARTCC boundaries|
|HS||show/hide ARTCC High Sectors|
|LS||show/hide ARTCC Low Sectors|
show/hide selected Airports
hold [SHIFT] to select airports to show
|GEO||show/hide GEO data||SHIFT+F2|
|RR||show/hide range rings|
|RCL||show/hide runway center line||SHIFT+F3|
|T||show/hide vectoring T's|
show/hide selected VOR's
hold [SHIFT] to select VOR stations to show
show/hide selected NDB’s
hold [SHIFT] to select NDB stations to show
show/hide selected FIXES
hold [SHIFT] to select FIXES to show
|FRQ||show/hide Frequencies (VOR/NDB)||SHIFT+F8|
|N||show/hide Names for VOR, NDB, FIXES and Airports||SHIFT+F4|
show/hide Low Enroute Airways
hold [SHIFT] to select airways to show
show/hide High Enroute Airways
hold [SHIFT] to select airways to show
show/hide selected SIDs
hold [SHIFT] to select SIDs
show/hide selected STARs
hold [SHIFT] to select STARs
select Zoom Position \#1
hold [SHIFT] to define new favourite Zoom Position
select Zoom Position \#2
hold [SHIFT] to define new favourite Zoom Position
select Zoom Position \#3
hold [SHIFT] to define new favourite Zoom Position
select Zoom Position \#4
hold [SHIFT] to define new favourite Zoom Position
Table 7.1 – Buttons on the toolbar
There are several ways in which you can zoom in and out on the PVD:
You can move the map by left clicking on the map and keeping the left mouse button pressed (dragging) while moving the map around.
The same procedures are valid for dragging the “Clock”, “Weather Info” and the “Flightstrip” around on the map.
The clock shows the current UTC time calculated from the local time on your computer (Figure 7.3).
You can drag the clock to any position you want on the PVD, or show/hide the clock in the [PVD] menu (UTC Clock option). (Figure 7.4)
The Figure 7.5 shows the current METAR report for the default weather station defined in the sector file or selected in the ATIS Options. For center controllers, the default METAR can be set through the METAR request window or via the COMMBox.
This line shows several anchor data (Figure 7.6).
The following table (Table 7.2) gives an explanation of all the different fields with their labels.
|312nm||distance between mouse pointer and anchor|
|5' 03”||flighttime from cursor to anchored aircraft|
|198°||heading from anchor|
|18°||header to anchor|
Table 7.2 - Fields in the Anchor Data line
The anchor is the small cross in the middle of the screen and can be used to measure distance and indicate the “To/From” heading. To move the anchor, you first have to make sure the anchor is “not locked”. To lock/unlock the anchor, right-click on the radar and select “Lock Anchor” (see Figure 7.7).
When the anchor is unlocked, you can re-establish a temporary anchor point by moving it to a new position and then, double clicking at the desired radar-screen position.
You can attach the anchor to an airplane by rightclicking it and clicking [Anchor]. In addition, you can set the anchor to a specific object by using the .c command in the [COMMbox].
The Occupied Area Active (OCA) labels can be used to place short notes (cfr. post-it notes ;-) on the PVD. In real life controllers, these are used for: active sectors, used frequencies, atc/atc coordination notes, coordinated direct routes (which is not allowed unless coordinated).
Add a text label by right clicking at the required position for the OCA label and selecting OCA in the PVD menu. If you want to remove (or hide) the OCA, use the OCN (Occupied Area Not-active) option.
The PVD Centerpoint is the center point of your radar visual range. The radar visual range is a circle around this point with a diameter equal to the range in nautical miles as selected in the PVD Options. Always remember, up is North-360 Deg, down is South-180 Deg, and etc.
You can set or reset the centerpoint in the PVD popup menu by right clicking on the PVD map display (Figure 7.7) and selecting ‘set centerpoint’ or ‘reset centerpoint’.
“Reset Centerpoint” will set the centerpoint to the default setting in the loaded sectorfile.
Important data for the controller (Figure 7.8), is gathered from the current ATIS information and labeled as follows:
The ATIS information block is completely moveable and can be placed anywhere on the PVD.
VOR, NDB, FIXES
Using the toolbar buttons [VOR] [NDB] [FIX] you can hide or show the VOR, NDB or FIXES on the PVD. Clicking the [FRQ] button will show the frequencies of the applicable navigation aids. To hide individual frequencies, you can click on one of the buttons while pressing [ALT]+[SHIFT].
If you would like to hide some of these navaids, you can deselect it from the list by holding the SHIFT key and pressing the button on the toolbar. The next screenshot shows the VOR selection window, which is shown by pressing SHIFT + [VOR] (Figure 7.9).
You can also hide the labels of the navaids by clicking on the [VOR], [NDB] or [FIX] button while holding the ALT key.
Using the toolbar buttons [L] or [H] you can hide or show the High Enroute or Low Enroute airways on the PVD.
If you would like to hide some of these airways you can deselect it from the list by holding the SHIFT key and pressing the button on the toolbar. The next screenshot shows the Low Airways selection window which is shown by pressing SHIFT + [L] (Figure 7.10). You can also hide the labels of the airways by clicking on the buttons while pressing ALT on the keyboard.
You can hide the names of the navaids by clicking the [N] button on the toolbar.
Enable or disable the selected SID's and/or STAR's on the PVD by clicking on the [SID] or [STAR] toolbarbuttons. By default no SID's or STAR's are selected, so you need to define these first by holding the SHIFT key while clicking the [SID] or [STAR] button: (Figure 7.11) Make your selection in the list of SID's or STAR's and click "OK".
When you start IvAc for the first time, it will ask you to load a sector file. Go to the directory where you store your sector files and load the sector file of your choice. The selected sector file will be loaded and displayed on the screen. Loading another sector file can be done by:
In the window shown in Figure 7.13, select the folder containing your sector files, click "Open" and the sector that you have selected will become visible on your screen in IvAc. For more information about the sectorfile format: http://www.ivao.aero/softdev/ivac/sectorformat.htm
Colour Profiles are stored in the “ColorSchemes” subfolder of the IvAc program folder and contain font and colour settings for the PVD (Plan View Display).
You can load (or reload) a different Colour scheme by:
Loading a profile can be done by clicking on the PROF button on the toolbar (see Figure 7.15) and selecting “load Profile..”. Select the desired profile and click “ok”. Now the profile will be loaded. At startup, the last used profile is automatically used by IvAc.
After changing some settings like a color scheme, as an example, you can click on the PROF button and select “Save Profile” to save the changes to the Profile (see Figure 7.15). If you also changed your callsign, a new profile is created. When closing the program, the profile is automatically saved too.
IvAc contains a lot of different types of labels according to the status of a target. What follows is a description of each label type.
Now it is also possible to see under which ATC the Aircraft is assumed. You will see Characters like G, T, A, C and U. Each of those Characters has its own meaning:
|G||Ground||The aircraft is under control of the Ground Controller|
|T||Tower||The aircraft is under control of the Tower Controller|
|A||Approach||The aircraft is under control of the Apporach Controller|
|C||Center||The aircraft is under control of the Center|
|U||Uncontrolled||The aircraft is not under any Control|
Table 7.2a - Aircraft Labels
Tower / Approach
First we discuss the label format for Tower or Approach controllers.
a. Basic Label (Unconcerned)
On the first line:
On the second line:
If the squawk code disagrees with the type of flight a “*” is shown behind the callsign. E.g. a pilot files an IFR flight and his squawk code is 7000 (1200 USA) which is used by VFR flights (this can be set in the label/route options dialog) the * is shown.
The In/Out marker is shown when the aircraft is departing or arriving at an airport set in the IO Options dialog. Note: Out symbol has precedence on In symbol.
An Outbound flight has an arrow pointing up, an Inbound flight has an arrow pointing down.
If a target is climbing above/below the cleared flight level the climb/descend arrow changes to a plus (above and climbing) or minus (below and descending) sign.
b.Assumed Label (Concerned)
The assumed label adds a third line:
The extended label is shown when a target is selected and adds a fourth line:
The destination airport is replaced with the cleared speed (CSP) when a speed restriction has been applied, prefixed with “I” for Indicated Air Speed (IAS). When Final Approach Speed (FAS) has been assigned - you will see “IFAS”
Example (Figure 7.20): target has been speed restricted to 210 knots and cleared for descend to FL55 Transition Level. Also notice the squawk code disagree marker “*” behind the callsign.
Example (Figure 7.21): Target on final approach - cleared for ILS approach runway 25R (APP) - and speed restriction to Final Approach Speed (IFAS).
The label for use by center or UAC controllers.
a.Basic Label (Unconcerned)
On the first line:
On the second line:
b. Assumed Label (Concerned)
The assumed label adds a third line:
c. Extended Label
The extended label adds a fourth line:
d. Transponder on, without flightplan
This label contains one line, the squawk code of the aircraft.
Selecting an Aircraft The first step in working with a target aircraft is by selecting it:
This action selects the aircraft and changes the color to the selected aircraft color, shows the callsign in the COMMBox and shows the selected aircraft's flightplan in the “Flightstrip”. (Figure 7.26)
All actions concerning the selected aircraft are grouped in one menu, shown by right-clicking on the aircraft label (Figure 7.27) or by right-clicking on the flightstrip when the aircraft is selected.
The leaderlines connect the label to the RPS (radar position symbol). Use the [L+] toolbar button to increase the length of the leaderline of the selected aircraft.
Use the [L-] toolbar button to decrease the length of the leaderline of the selected aircraft.
When you hold SHIFT and click [L+] or [L-] leaderlines of all aircraft are in- or decreased.
Speed vectors are the lines in front of the target showing the last heading of the aircraft. The length can be changed by using the numeric buttons on the toolbar. By pressing a numeric button, the end of the speed-vector line shows the point were the target will be after n-minutes at current groundspeed. You can disable the speed-vectorline by selecting the 0 minutes button.
You can change the position of the aircraft label in a very quick and easy way: click on the dot: the label is moved clockwise! When you hold SHIFT and click on the dot the label is moved counter-clockwise. It's that simple !! (Thanks Belgocontrol for this wonderful idea!! :-)). Position of the label can also be changed freely according to the controllers wishes. You can do this in 2 ways:
To take over control of the aircraft, select ASSUME from the aircraft menu. The label changes to the assumed version as shown in Figure 7.28.
If no further ATC control is available online, you have to release the target aircraft (also known as “Radar Services terminated, switch to UNICOM”). Releasing an aircraft under your control can be done following these steps: Select aircraft label, right-click and select “RELEASE”
In the COMMBox you will see a text message send to the concerned pilot: “SLR24K, Switch to UNICOM 122.800 - Good day !!!” (In this example, the aircraft selected was SLR24K)
note: The Handoff/Release radio message is only sent to aircraft with the “NO VOICE" tag selected or when you select the option “Send handoff message when on voice” in the Commbox Options.
Transfer or handoff aircraft under your control to another controller online. Select the aircraft concerned and right-click. Select “TRANSFER” in the aircraft menu.
The select controller window will become visible. The list is populated with the controllers visible in the ATC Box. Select the controller you want to handoff the aircraft to, in this example LFRS\_TWR , and press “OK” (Figure 7.32) - or double click on the controller callsign.
On top of the aircraft label you will see a red color “REQ TRSF`”
Once the other controller accepted the handoff the label will switch to the basic label style. If you want to undo transfer you can right-click the label and select “CANCEL TRANSFER”.
When another controller wants to transfer an aircraft to you, the label of the aircraft announces “REQ HO” (Figure 7.33).
To accept the transfer select “ASSUME” from the aircraft context menu. If you want to reject transfer select the “REJECT TRANSFER” option from the aircraft context menu.
When an aircraft is in your airspace and it isn't tuned to your frequency and doesn't respond on guard messages you can send a force act to the aircraft. Right-click the label and select “FORCE ACT” from the menu. The pilot now gets a private message instructing him to contact you on your frequency.
NO VOICE tagging
If a pilot comes online, would not it be nice to know if he's on voice, yes or no? When he doesn't have voice (Teamspeak), you can now make a small note for your colleagues online, called the “NO VOICE” tag.
Select the aircraft and right click. From the menu select “NO VOICE” and in the aircraft label, just behind the callsign a minus sign appears. The minus sign is also shown on the screen of the next controllers online so they are aware of the voice capabilities of the pilot.
A new feature is the CFL or Cleared Flight Level. This means you can assign a Flight Level to an aircraft. This altitude is then shown in the label. Assigning an altitude is performed as follows: Press ALT on the keyboard (left or right) and click on the label or press F8 when the aircraft is selected. Now you get the CFL dialog (Figure 7.36). Select the appropriate level from the list or type the flight level on the numeric keypad.
Clicking on the West/East or North/South (option has to be set in the PVD Options dialog button switches between odd and even flight levels. When the dialog is first shown, the levels for the current aircraft heading are shown. By clicking on all, you can show all levels. Clicking on “CLEAR” removes the assigned flightlevel. Clicking “OK” or pressing return selects the flight level selected in the list. The label now shows the CFL on the second line (Figure 7.37).
There are several conditions for the CFL field:
When you select a CFL, the CFL is sent to all controllers in your neighbourhood/area. The basic label also shows CFL, so when an aircraft is being transferred between 2 controllers, the target controller already has CFL. To cancel the CFL dialog press the “escape” key on the keyboard. To clear an aircraft for the Approach you can also select “APP” from the list.
This field is primarily used to indicate an enroute waypoint clearance, but you can also use it to indicate the departure clearance. An airplane will receive a clearance from you or from another controller online. Lets take for example, you give a clearance to a pilot to proceed COA4C SID, as Published, at Brussels. How does this work ?
Select the aircraft label and right click, select “CLEARED WP” or press F5 when the aircraft is selected. A small popup window come's on your screen were you can enter the cleared waypoint.
Write in the text bar COA4C and click enter. The aircraft label will indicate the COA4C SID. Also your colleague controller will see your aircraft that you have cleared on a COA4C SID. It's also indicated in the flightstrip.
Next to flightlevel and heading/waypoint you can also assign a cleared speed to an aircraft. Right-click on the label and select “Cleared SP” from the menu or press F7 when the aircraft is selected. You get a similar dialog as the Cleared FL screen. Select a speed from the list or type a speed on the numeric keypad and click “OK” or press return. To cancel the CSP dialog press “escape” on the keyboard.
Restricting an aircraft to Final Approach Speed can be done by selecting “FAS” in the dropdownlist (press “F”) - the label will show “IFAS” (Indicated speed is Final Approach Speed).
When we want to know the frequency a PIC is on, we can select “Request COMM” and this will identify the frequency the PIC is monitoring. So, after selecting the “Request COMM” you will know if the PIC is already on your frequency or on the frequency of an adjacent controller.
Select the aircraft and then right click and choose “Req COMM” from the popup menu. The frequency will be shown on the MSG tab in the COMMBox: “DAT007 is tuned to 122.80”
When you want to re-request a flightplan of the selected aircraft, right-click on the aircraft and select “Req FPL”. The flightplan will now be updated.
When you select the “SELCAL” option, the SELCAL dialog pops up:
The dialog contains the callsign of the pilot and the squawk code of the target. The SELCAL code is parsed from the flightplan. When you press the “TX SELCAL” button, the SELCAL code is transmitted to the pilot which will hear a ding-dong sound if the SELCAL code entered by the ATC matches the code of the plane.
Note: you can only send a SELCAL to a pilot once a minute and the SELCAL feature is limited to CTR and FSS positions.
Apart from the “Flightstrip” you can also view a complete flightplan of an aircraft. Right-click the label and select “Show FPL” from the menu. This window can also be opend from the I/O window by double-clicking the corresponding line or right click the line and select “Show FPL”. Now you get the ICAO Flightplan window.
You can change some fields and click OK. The changes are sent to the pilot and then the pilot resends his flightplan with the changes.
Note: To be able to change a flightplan you have to be at least S3.
Remark: This feature is only available for pilots using IvAp and X-IvAp.
A new feature of IvAc is that you can show the route of an aircraft based on the flightplan (Figure 7.4). IvAc has a complex algorithm to draw the filed flightplan route on the PVD. It's very important that the airways in the sector file are defined correctly. For the rules check the definition on http://www.ivao.aero/softdev/IvAc/sectorformat.htm .
A validator for the sectorfiles can be found here:http://www.ivao.aero/softdev/IvAc/download.htm
Add aircraft to IO Window
Because the current sector file format limits our possibilities it's not possible to detect overflights at the moment. Therefore you can add an aircraft to the IO Window manually. Select “Add to IO” from the aircraft menu and a new entry will be made in the IO Window.
To activate the QDM (Distance and Heading Measurement), rightclick an aircraft and click QDM in the popup menu. The QDM measurement for the target Aircraft is now shown, attached to the cursor. To remove the QDM, select QDM again in the context menu of the same aircraft. If you would rightclick a second aircraft and click QDM+, the QDM between both targets will be shown. The QDM label contains two values: the heading and distance from the first selected target to the second target aircraft or cursor position.
To deactivate QDM rightclick one of the QDM selected targets and select QDM again.
The QDM Option is now also possible on the PVD map. You can now select the QDM between an Aircraft and a Position or between two Positions.
VERA (Verification of Separation/Range) is a system used at Eurocontrol Maastricht for Loss of Separation prediction and avoidance.
Loss of Separation: Lateral distance between two aircraft is less than 8nm
The system calculates the track between the two selected targets based on the current speed and heading. It draws two predicted ghost RPS were both targets will lose separation, a QDM between the 2 targets and popups a dialog box with details about a possible solution for the Loss of Separation:
The first line of the dialog contains:
The second line of the dialog contains resolutions to obtain 8nm separation (only if loss of separation predicted):
The third line of the dialog contains resolutions to obtain 8nm separation (only if loss of separation predicted):
To close VERA, just close the popup dialog or select VERA again in the aircraft context menu.
The following picture explains all fields in the flightstrip:
Using the COMMBox
Figure 7.48 shows the COMMBox.
On top of the window you will see the Channel tabs. IvAc's default is to have 8 Standard Comm channel frequencies open. The first is your primary frequency. Then you will find 2 secondary frequencies for monitoring purposes. Transmitting on these channels is still possible, though it’s primarily intended for monitoring communications as the user may deem necessary. Next to the frequencies you find the METAR tab (see further). Then you will find the GUARD tab. This is your “On Guard” frequency. Then you will find the ATC tab. This channel shows all ATC messages. The next tab is the BROADCAST tab which shows all broadcasted messages. The last tab is the MSG tab. Here all messages from the SERVER are shown. Other information is shown too, like requested METAR’s, requested COM frequencies and ATIS request notifications. When a new message is transmitted on a channel, the tab above highlights as shown in Figure 7.49.
Clicking on the tab removes the highlight from the tab as shown in Figure 7.49. Figure 7.50 shows a chat channel. This window differs from the normal message channels by the list of current ATC on the channel.
At the bottom of the window you see 2 input boxes. The one on the left shows the current selected aircraft and is not editable. The one on the right is the main command box. All commands and messages have to be typed here. We have already defined some commands shown in Table 7.3
|.chat <CALLSIGN>||Opens a new chat window with the callsign added to the list on the right|
|.a <CALLSIGN>||Adds a callsign to the list on the right|
|.r <CALLSIGN>||Removes a callsign from the list on the right|
|.d <\#>||Deletes a channel. # stands for the chat channel number shown in the tab. E.g. .d 5|
Changes the frequency of the current frequency tab (only possible on first 3 tabs)
Make sure the new frequency is not yet selected in one of the tabs.
|.atis <CALLSIGN>||Request the ATIS for station <CALLSIGN>|
Select a target with callsign <CALLSIGN> if in range.
You can enter a part of a callsign.
|.c <SECTORDATA>||Center on a specific VOR, NDB, FIX or AIRPORT|
|.ping <CALLSIGN>||Ping a client|
|.kill <CALLSIGN> <REASON>||Kill a client (only for supervisors)|
|.inf <CALLSIGN>||Request info of a specific client (only for supervisors)|
|.wallop <MESSAGE>||Sends the message to all online supervisors|
|.z <zoomlevel>||Sets the zoom level to the provided value (-80 up to approx 200 valid)|
|.selcal <CALLSIGN>||Opens the SELCAL dialog for this pilot|
|.alias<parameters>||Use of aliases defined in the alias file|
|<text>||Sends a message to the selected channel|
Table 7.3 - Commands available in COMMBox
You can clear the history of a channel by clicking with the right mouse button on the tab and select “Clear history” from the menu (Figure 7.5). When used on the METAR tab this clears the list of METARs. Chat channels can also be deleted by selecting “Delete tab” from the same menu. Finally clicking “Options...” from the menu opens the COMMBox Options dialog.
In the CHAT channels you can also remove a member by clicking on the callsign with the right mouse button and select “Remove” from the menu (Figure 7.5).
The metar tab contains a table with METARs defined by the user. On startup the primary METAR is added to the table. When controlling you can modify the table:
|+<ICAO>||Add METAR to the list|
|-<ICAO>||Remove METAR from the list|
|\#<ICAO>||Set default METAR (changes ATIS metar too)|
Table 7.4 - Commands for METAR tab
These commands have to be entered in the COMMBox inputline. You can combine these commands together in one line. E.g.:
+EBBR EBOS -EHAM \#EBFN +EBAW
This adds EBBR, EBOS and EBAW to the list, removes EHAM and sets EBFN as default METAR.
After connecting to the server the ATC View is populated with ATC within your neighbourhood (range). (Figure 7.5)
The list contains the callsigns of each ATC position, frequency, rating and full name. The list can be filtered using any combination of the buttons on top of the window. (Table 7.5)
|C||show/hide center positions|
|A||show/hide approach positions|
|D||show/hide departure positions|
|T||show/hide tower positions|
|G||show/hide ground positions|
|O||show/hide observers and other callsigns|
|*||show/hide all buttons|
Table 7.5 - Toggle buttons ATC View
Using the “Right click” on a position will bring up the ATC Menu (Figure 7.5). Here you can request the ATIS of a controller or open a chat channel in the COMMbox. The requested ATIS is also shown in a chatbox. Click “Options...” to set the options of the ATCBox.
Instead of using a flightstrip list as in ProController, IvAc uses only one flightstrip on the PVD and provides an IO Window with a list of all incoming and outgoing flights (Figure 7.5).
This list is split up in 3 sections (separated by an empty line):
1. Incoming flights
These lines start with an I. Next to the I are the following fields:
2. Outgoing flights
These lines start with an O. Next to the O are the following fields:
3. Manual added flights
These lines start with an -. Next to the - are the following fields:
When you right-click on the IOWindow entries a popup menu appears:
The ICAO flightplan of the selected aircraft can also be opened by double-clicking on the corresponding line.
To request the current METAR report for a particular station/airport, click on the METAR button in the toolbar. Enter the ICAO code in the dialogbox (Figure 7.5) and press “OK”. The requested METAR report will be added to the list in the METAR tab of the COMMbox. If you check “Make default” the entered ICAO will be used as default weather station for the ATIS and for the weather info on the PVD.
|F1||Show/Hide COMM box||Show/Hide Airports||-|
|F2||Show/Hide ATC box||Show/Hide GEO||-|
|F3||Show/Hide I/O box||Show/Hide Runway Center lines||-|
|F4||ASSUME/TRANSFER selected||Show/Hide NavAid Names||-|
|F5||Cleared Waypoint||Show/Hide VORs||-|
|F6||Show FPL of selected aircraft||Show/Hide NDBs||-|
|F7||Cleared Speed||Show/Hide FIXES||-|
|F8||Cleared FL||Show/Hide FRQ||-|
|F9||Low Airways||Low Select||Show/Hide|
|F10||High Airways||High Select||Show/Hide|
|TAB||Show route of selected aircraft||-||-|
|PGUP||Select next aircarft||-||-|
|PGDOWN||Select previous aircraft||-||-|
|num *||Cleared Flight level||-||-|
|num /||TRANSFER Selected||-||-|
|num -||toggle No Voice||-||-|
|num +||Cleared Waypoint||-||-|
|1||-||-||Zoom Level 1|
|2||-||-||Zoom Level 2|
|3||-||-||Zoom Level 3|
|4||-||-||Zoom Level 4|
|W||-||-||Remove all clearances|
Table 7.6 - Hotkeys
You can save your favorite controller position for future use. For storing information about the user, IvAc uses controller profile files (cpr), e.g. KZFW\_CTR.cpr. These are saved in the Profiles subfolder of IvAc. These profiles contain all your user settings that are specific for a controller position and enable the user to quickly switch or setup a favorite ATC position. The information saved in a controller profile contains:
You can create a Controller Profile for each ATC position you like controlling. Profiles are saved with the callsign, as the filename. E.g. EBBR\_APP.cpr is the profile for Brussels Approach EBBR\_APP.
Contents of the Controller Profile
The layout of the file is in the standard windows xxx.ini format. The controller profile files contains different sections. The purpose of these profiles is to be able to easily transfer your favorite profiles to another computer.
This section contains the files IvAc requires to load the profile. The following files are stored:
This section contains all information needed for the connection dialog. The password is of course encrypted for your protection.
This section contains all fields entered in ATIS dialog.
This section contains all settings concerning different items on top of the PVD (clock, flightstrip, weather info)
This section contains all toggle/selected values for the PVD buttons. It stores the last used settings for displaying radar data, like VOR, NDB, …
Options concerning other PVD data settings are stored as set on the PVD Options dialog window.
All settings for the COMMBox window
Contains saved zoompositions (Z1, Z2, Z3 and Z4 buttons)
Settings for the ATCBox
Contains settings for the IOWindow
Contains the label settings
Contains the general settings
Loading Controller Profiles
Loading a profile can be done by clicking on the PROF button on the toolbar (see Figure 8.1) and selecting “load Profile...”. Select the desired profile and click ok. Now the profile will be loaded. At startup, the last user profile is automatically read by IvAc.
Saving Controller Profiles
After changing some settings, like a color scheme or etc, you can click on the PROF button and select “Save Profile” to save the changes to the profile (see Figure 8.1). If you also changed your callsign, a new profile is created. When closing the program the profile is automatically saved too.
Color Profiles are stored in the “ColorSchemes” subfolder of the IvAc program folder and contain font and colorsettings for the PVD (Plan View Display). The files have the extension .clr. A colorscheme is automatically created when editing the assigned colors to each object in the Colorscheme editor or you can manually edit these color files using a text editor, like Notepad.
Contents of the Color Profiles files
The Colorscheme files contain a number of lines each tab separated. Every line contains a objectname of an item in IvAc and separated by a tab the corresponding RGB (red, green, blue) values. If you manually edit these files, make sure all object codes are in the file. Otherwise, the default color (green) will be used. You can create and use as many color schemes as you want by making a copy of the default files and editing them.
Sounds chemes are stored in the “SoundSchemes” subdirectory of the IvAc folder. They have the extension .ssf. The file contains a list of sound definitions for different events in IvAc.
The alias file (alias.txt) is stored in the “Data” subdirector of the IvAc folder. It contains all the user defined aliases (used by all Controller Profiles).
The network servers file (ipaddr.txt) contains the list of all IVAN Network Servers and is stored in the “Data” subdirectory of the IvAc folder.
The list of teamspeak servers is saved in (tsaddr.txt, stored in the “Data” subdirectory of the IvAc folder).
This file (ipstatic.txt) has also to be placed in the “Data” subdirectory. Here you can add your own static servers. This content of this file is loaded in the Servers dropdown list in the Connect dialog. These servers are not pinged by IvAc. When you click “Update Server” in the Connect dialog this file is not overwritten.
This file (aircraft.txt, stored in the “Data” subdirectory of the IvAc folder) contains a list of all aircraft types and their respective wake category.
This file (prefix.txt, stored in the “Data” subdirectory of the IvAc folder) contains a list of all airline prefixes (SN for Sabena, DLH for lufthansa, ...) and their full name. This list is used in the flightstrip to display the radio callsign.
For more information about the sector file format: http://www.ivao.aero/softdev/sectorfile.asp
As a side note, many Beta testers have successfully used the existing ProController Sector Files, either as-is or with little modifications.