IvAc 2 Operational Data

IvAc2 implements the following automatic operational features:

• Selection of transition level based on aerodrome
• Allocation of Mode A SSR code
• Allocation of departure route (SID) based on aerodrome restrictions & runway in use
• Allocation of arrival route (STAR) based on arrival point & runway in use
• Allocation of arrival gate

Transition levels can be individually defined for every airport in the FIR. The rules governing the selection of the transition level are defined in the transitionlevel.xml file.

Mode A SSR codes are allocated and linked to the flight plan automatically when a clearance is generated. The range of codes are defined in the mode_a.xml file.

SIDs are allocated based on the following variables, set in the sid.xml file.

The query used to find the appropriate SID is based on:

1. FPL route first waypoint = exit
2. rwy active
3. FPL RFL ⇐ minrfl
4. FPL RFL ⇐ maxrfl
5. ETOD >= begin
6. ETOD ⇐ end
7. DOW is in dow
8. FPL WTC is in wtc

The first found SID is used. If necessary a controller can always override the selected SID when issuing the clearance.

<sid id="CIV6F"   short="CIV6F" exit="CIV"   rwy="02" cfl="60" minrfl="0" maxrfl="660" begin="0000" end="2359" dow="1234567" wtc="LMH"/>

STARs are allocated based on the following variables, set in the star.xml file.

The query used to find the appropriate SID is based on:

1. FPL route last waypoint = entry
2. rwy active
3. FPL RFL ⇐ minrfl
4. FPL RFL ⇐ maxrfl
5. ETA >= begin
6. ETA ⇐ end
7. DOW is in dow
8. FPL WTC is in wtc

The first found STAR is used. If necessary a controller can always override the selected STAR.

Arrival gates are allocated based on the following variables, set in the gates.xml file.

The query used to find the appropriate arrival gate is based on:

1. Airline
2. Type of aircraft
3. Type of flight
4. Departure aerodrome
5. gate occupancy (in future)

The first found gate is used. If necessary a controller can always override the selected gate when issuing the clearance.

Back