ATMM Version 2.2 Issued at 2013-07-01 Effective from 2013-07-05 page 1/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
Content 0. Updates 4 0.1. New items 4 0.2. Updated items 4 0.3. Deleted items 4 1. LOWW_GND 5 1.1. Taxi flow 5 1.1.1. Dep Rwy 29/34 5 1.1.2. Dep Rwy 16 (Arr Rwy 16 / Dep Rwy 29) 5 1.1.3. Dep Rwy 16 (Arr Rwy 11) 5 1.1.4. Arr Rwy 11 5 1.1.5. Arr Rwy 16 (Dep Rwy 29) 6 1.1.6. Arr Rwy 16 (Arr Rwy 11) 6 1.1.7. Arr Rwy 34 6 1.2. Restrictions 6 1.2.1. Dep Rwy 11 / Arr Rwy 29 6 2. LOWW_TWR 7 2.1. Rwy usage 7 2.2. Traffic flow 7 2.2.1. Dep Rwy 29 (Arr Rwy 16) 7 2.2.2. Dep Rwy 29 (Arr Rwy 34) 7 2.3. Wake Turbulence Separation 8 2.3.1. Non Radar Separation 8 2.3.2. Radar Separation 8 2.4. Visual Approaches 8 2.5. Restrictions 9 2.6. Reduced Runway Separation 9 3. LOWW_APP 9 3.1. Radar separation 9 3.2. Simultaneous Approaches Rwy 11 and 16 10 3.3. Visual Approaches 10 3.4. Standard sector 10 3.4.1. Departures 10 3.4.2. Arrivals 11 3.5. Sector split 11 3.5.1. North/South Approach 11 3.5.2. Upper/Lower North/South Approach 11 4. LOVV_CTR 12 4.1. Radar separation 12 4.2. Arriving traffic separation 12 4.2.1. Destination LOWW 12 4.2.2. Destination LOWI 13 4.2.3. Destination LOWL/LOWG 13 4.2.4. Destination LOWS 13 4.2.5. Destination EDDM 13 page 2/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
4.3. Departing traffic 13 4.4. Sector split 13 5. LOWI_TWR/APP 14 5.1. Rwy usage 14 5.2. Dep Rwy 08 / Arr Rwy 26 14 5.3. Rwy 08 only 14 6. LOWS_TWR/APP 14 6.1. Rwy usage 14 6.2. Dep Rwy 34 / Arr Rwy 16 14 6.3. Rwy 16 only 14 6.4. Rwy 34 only 15 7. LOWG_TWR/APP 15 7.1. Rwy usage 15 7.2. Dep Rwy 17C / Arr Rwy 35C 15 page 3/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
0. Updates This chapter is only an overview at all changes since last issue. 0.1. New items 0.2. Updated items 2.2. Traffic flow 2.2.1. Dep Rwy 29 (Arr Rwy 16) 2.2.2. Dep Rwy 29 (Arr Rwy 34) 3.4.1. Departures 0.3. Deleted items page 4/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
1. LOWW_GND Wien Ground shall set up the initial departure sequence depending on Rwy configuration, SID and type of aircraft. Wien Ground shall guide arriving traffic to final parking position according to Rwy usage. 1.1. Taxi flow Departure sequence shall be set up as follows: No traffic behind the preceding with same SID Initial SID track shall be more than 30 off than the preceding Wake turbulence separation Faster traffic in front of slower traffic 1.1.1. Dep Rwy 29/34 Departing traffic from A, B, C, D, E and F01-F37 (only odd stand numbers south of Skylink) parking positions shall taxi on taxiway M to Rwy 29 or M and E to Rwy 34. F01-F37 (only odd stand numbers south of Skylink) shall pushback facing west on TL36 and taxi via TL35, EX7 and M (E) to assigned Rwy. Departing traffic from F04-F36 (only even stand numbers north of Skylink), F41-F59, H and K parking positions shall taxi via taxiway E, EX24 and EX1 to Rwy 29 or via E to Rwy 34. 1.1.2. Dep Rwy 16 (Arr Rwy 16 / Dep Rwy 29) Departing traffic from A, B, C, D, E and F01-F37 (only odd stand numbers south of Skylink) parking positions shall taxi on taxiway M, EX2, W, EX23 and E to Rwy 16. F01-F37 (only odd stand numbers south of Skylink) shall pushback facing west on TL36 and taxi via TL35, EX7, M, EX2, W, EX23 and E to Rwy 16. Departing traffic from F04-F36 (only even stand numbers north of Skylink), F41-F59, H and K parking positions shall taxi via taxiway W or E to Rwy 16. 1.1.3. Dep Rwy 16 (Arr Rwy 11) Departing traffic from A, B, C, D, E and F01-F37 (only odd stand numbers south of Skylink) parking positions shall taxi on taxiway L, W, EX23 and E to Rwy 16. F01-F37 (only odd stand numbers south of Skylink) shall pushback facing east on TL36 and taxi via TL36, W, EX23 and E to Rwy 16. Departing traffic from F04-F36 (only even stand numbers north of Skylink), F41-F59, H and K parking positions shall taxi via taxiway W or E to Rwy 16. 1.1.4. Arr Rwy 11 Arriving traffic via Rwy 11 shall taxi to parking positions A, B, C, D, E and F01-F59 (only odd stand numbers, south of Skylink) via taxiway L (eastbound) or M (westbound). Observe eastbound routing on TL36 in this configuration. page 5/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
Taxi to parking positions F04-F50 (only even stand numbers, north of Skylink) and H via taxiway L, W and TL40. TL40 maybe called blue line (TL39) for F stands and orange line (TL41) for H stands. Taxi to parking positions K via taxiway L, W, EX23 and E. 1.1.5. Arr Rwy 16 (Dep Rwy 29) Arriving traffic via Rwy 16 shall taxi to parking positions A, B, C and D via taxiway D or E and L. Taxi to parking positions E and F (only odd stand numbers, south of Skylink) via taxiway D or E, then via L, W and TL36 (westbound routing). Taxi to parking positions F (only even stand numbers, north of Skylink) and H via taxiway D, EX32, EX22 and TL40. TL40 maybe called blue line (TL39) for F stands and orange line (TL41) for H stands. Taxi to parking positions K via taxiway (D, EX32 and) E. 1.1.6. Arr Rwy 16 (Arr Rwy 11) Arriving traffic via Rwy 16 shall taxi to parking positions A, B, C and D via taxiway D or E, M and nearest EX (Exit) to cross taxiway L. Taxi to parking positions E and F (only odd stand numbers, south of Skylink) via taxiway D or E, then via M and nearest EX (Exit) to cross taxiway L to join TL36 (eastbound routing). Taxi to parking positions F (only even stand numbers, north of Skylink) and H via taxiway D, EX32, EX22 and TL40. TL40 maybe called blue line (TL39) for F stands and orange line (TL41) for H stands. Taxi to parking positions K via taxiway (D, EX32 and) E. 1.1.7. Arr Rwy 34 Arriving traffic via Rwy 34 shall taxi to parking positions A, B, C and D via taxiway D and L. Taxi to parking positions E and F (only odd stand numbers, south of Skylink) via taxiway D, L, W and TL36 (westbound routing). Taxi to parking positions F (only even stand numbers, north of Skylink) and H via taxiway D, EX32, EX22 and TL40. TL40 maybe called blue line (TL39) for F stands and orange line (TL41) for H stands. Taxi to parking positions K via taxiway D, EX32 and E. 1.2. Restrictions 1.2.1. Dep Rwy 11 / Arr Rwy 29 During Departure Rwy 11 or Arrival Rwy 29 no traffic allowed on taxiway E between E3 and E4 on taxiway D between D3 and D4 on Rwy 16 between B4 and B7 page 6/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
2. LOWW_TWR Wien Tower shall finalize departure sequence for expeditiously traffic flow with due regard to safety (wake turbulence, increased separation, aircraft performance, ). Arriving traffic has always priority over departing traffic or other traffic on ground. IFR traffic has always priority over VFR traffic. Further on emergency, ambulance, rescue or military traffic shall be given priority. 2.1. Rwy usage Rwy usage shall be optimized for current situation to optimize arrival and/or departure traffic flow. Wind below 3kt may be completely disregarded for optimal Rwy usage. Tailwind component limit is 10kt and crosswind component limit is 20kt for Rwy setup. 2.2. Traffic flow Departure sequence shall be set up as follows: No traffic behind the preceding with same SID Initial SID track shall be more than 30 off than the preceding Wake turbulence separation Faster traffic in front of slower traffic To increase departure flow initial visual turns maybe granted to Cat A, B and C aircraft only. 2.2.1. Dep Rwy 29 (Arr Rwy 16) Initial track shall be measured after the initial turn out of 1000ft. Therefore LEDVA, MIKOV, LANUX, KOVEL, MOTIX, LUGIM and SITNI4C are to be considered on the same track. SITNI2X, OSPEN, UMBIL and SNU are to be considered on the same track. SASAL, STEIN, KOXER and ADAMA are to be considered on the same track. During arriving traffic on Rwy 16 NO departures to WGM on Rwy 29 allowed! Use alternative Rwy 16 and WGM7B for departure. Anyway coordination with APP required due to SID crossing with arrival sector! During peak departure times it is recommended to use Rwy 16 for KOXER and ADAMA departures. Further on you may use Rwy 16 for SASAL, STEIN, LEDVA, MIKOV, LANUX or KOVEL departures to increase departure traffic flow. 2.2.2. Dep Rwy 29 (Arr Rwy 34) Initial track shall be measured after the initial turn out of 1000ft. Therefore LEDVA, MIKOV, LANUX, KOVEL, MOTIX, LUGIM and SITNI4C are to be considered on the same track. SITNI2X, OSPEN, UMBIL and SNU are to be considered on the same track. SASAL, STEIN, KOXER and ADAMA are to be considered on the same track. page 7/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
During arriving traffic on Rwy 34 NO departures to WGM on Rwy 29 allowed when arriving traffic is between 5 NM final and all wheel touch down! Departing traffic has to start T/O roll before inbound traffic is crossing 5 NM final on Rwy 34. Use alternative Rwy 34 and WGM5D for departure. During peak departure and arrival times it is recommended to use Rwy 34 for ADAMA and KOXER departures due to crossing of arrival sector Rwy 34 with SIDs ADAMA1C and KOXER1C. Further on you may use Rwy 34 for KOVEL, LANUX, LEDVA or MIKOV departures to increase departure traffic flow. 2.3. Wake Turbulence Separation 2.3.1. Non Radar Separation Departing aircraft medium behind heavy 2 min Departing aircraft light behind heavy or medium 2 min Increase both with 1 min if an intersection departure is used. Arriving aircraft medium behind heavy 2 min Arriving aircraft light behind heavy or medium 3 min 2.3.2. Radar Separation Leading aircraft heavy, following aircraft heavy 4 NM Leading aircraft heavy, following aircraft medium 5 NM Leading aircraft heavy, following aircraft light 6 NM Leading aircraft medium, following aircraft medium 3 NM Leading aircraft medium, following aircraft light 5 NM Under VMC reduced separation down to 2,5 NM for arriving traffic on the same Rwy may be applied. TWR/APP may always ask the pilot if he has the preceding traffic in sight AND if he is able to maintain own separation. Visual separation with less than 2,5 NM during simultaneous approaches to Rwy 11 and 16 has to be performed (only aloud during VMC). 2.4. Visual Approaches Visual approaches to Rwy 29 or 34 are allowed without further restriction. Visual approaches to Rwy 16 are only allowed via left hand downwind (from the east). Visual approaches to Rwy 11 are only allowed via right hand downwind (from the south). No visual approaches are allowed between extended center line Rwy 11 and extended center line Rwy 16. page 8/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
2.5. Restrictions If there are departures on the same SID at least 10nm separation has to be provided with T/O clearance (10nm when both are airborne). If there is slower traffic departing in front of faster traffic on the same SID or another SID with the initial track of less than 30 at least 15nm separation has to be provided with T/O clearance (15nm when both are airborne). No intersection T/O shall be granted when wake turbulence is a factor, otherwise increased wake turbulence separation has to be provided. 2.6. Reduced Runway Separation In line with ICAO Doc 4444 Reduced Runway Separation may be applied. An aeroplane may be cleared to land when: The previous A/C has left the RWY or The previous A/C has landed and past a point at least 2400m from the threshold of the runway, is in motion and will vacate the RWY without backtracking, or Is airborne and has passed a point at least 2400m from the threshold of the RWY. General operation instructions and limitations for the landing sequence: Under the above mentioned circumstances with an aeroplane still occupying the RWY, a landing shall only be considered safe under following conditions: During daylight; If braking action is not adversely affected by runway contaminants; If weather conditions do not prevent the Flight Crew Member from making an early assessment of traffic conditions on the RWY; If the preceding aeroplane is clearly in sight and at a distance of not less than approximately 2400m on passing the landing threshold; 3. LOWW_APP Wien Radar is responsible for sequencing departing and arriving traffic. 3.1. Radar separation Leading aircraft heavy, following aircraft heavy 4 NM Leading aircraft heavy, following aircraft medium 5 NM Leading aircraft heavy, following aircraft light 6 NM Leading aircraft medium, following aircraft medium 3 NM Leading aircraft medium, following aircraft light 5 NM TWR/APP may always ask the pilot if he has the preceding traffic in sight AND if he is able to maintain own separation. page 9/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
3.2. Simultaneous Approaches Rwy 11 and 16 Simultaneous Approaches are only aloud during VMC. Visual separation with less than 2,5 NM will be performed by TWR. Arriving traffic via BALAD shall be cleared for ILS Y approach Rwy 11. Arriving traffic via PESAT shall be cleared for ILS approach Rwy 16. Arriving traffic via NERDU or MABOD shall be cleared for Rwy 11 or 16 to optimize traffic flow. 3.3. Visual Approaches Visual approaches to Rwy 29 or 34 are allowed without further restriction. Visual approaches to Rwy 16 are only allowed via left hand downwind (from the east). Visual approaches to Rwy 11 are only allowed via right hand downwind (from the south). No visual approaches are allowed between extended center line Rwy 11 and extended center line Rwy 16. 3.4. Standard sector Only one vatco is online. 3.4.1. Departures Departures to LKAA via KOVEL or LANUX shall be cleared FL240 (or cruise FL if lower) and handoff to LKAA_CTR. Departures to LKAA via LEDVA or MIKOV shall be cleared FL230 (or cruise FL if lower) and handoff to LKAA_CTR. Departures with destination LKTB max FL120 and handoff to LKTB_APP. Departures with destination LKPR max FL180 and handoff to LKAA_CTR. Departures to LOVV airspace shall be cleared FL240 (or cruise FL if lower). Departures via LUGIM, MOTIX or SITNI and cruise FL160 at or below handoff traffic to LOWL_APP. Departures via OSPEN or UMBIL and cruise FL160 at or below handoff traffic to LOWG_APP. Departures with destination LOWL, LOWG, LOWK or LOWS max cruise FL160. Departures via ADAMA shall be cleared FL190, cross WW390 at FL100 or above, cross ADAMA at FL130 or above and handoff to LZBB_CTR. Departures via KOXER shall be cleared FL150, cross KOXER at FL100 or above and handoff to LZBB_CTR. Departures via SASAL or STEIN shall be cleared FL230 and handoff to LHCC_CTR. LOWW_APP has a general release for direct to the SID endfix. page 10/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
3.4.2. Arrivals Arrivals to LOWW shall be informed at the initial call about the expected type of approach and Rwy. Arriving traffic shall be cleared along transition to the FAF. If the traffic is unable for transition radar vectors shall be given along the transition. 3.5. Sector split When only Wien Director and Wien Radar are online, APP shall descend arriving traffic along the transition into a downwind. Altitudes shall be between 4000ft and FL60/6000ft depending on the Rwy and other traffic. Arrivals to Rwy 11 shall never be cleared below FL60/6000ft before handoff to Director. 3.5.1. North/South Approach Sector split between North and South Approach shall be the extended centerline Rwy 11/29. Sector Gols (between extended centerline Rwy 29 and Rwy 34) below FL115 delegated to North Approach. Arriving traffic via PESAT shall be sent to South Approach from LHCC_CTR. South Approach clears traffic on PESAT transition. In case of arrival Rwy 16 or 34, descend Traffic to FL120 and handoff to North Approach. In case of Rwy 29 only, Gols sector GND-FL245 belongs to South Approach. LANUX/KOVEL/LEDVA/MIKOV departures via Rwy 29 shall be cleared FL110 and handoff to North Approach. 3.5.2. Upper/Lower North/South Approach North sector will be split at FL105 and South sector (including Gols sector) at FL115. Upper North and Upper South may be controlled be either one or two stations. Arriving traffic shall be informed by Upper Approach about the expected type of approach and Rwy. It is the responsibility of Upper Approach to set up the initial arriving sequence (vectors into the sequence may be necessary). Basically arriving traffic shall be cleared according transition or shall be given radar vectors along the transition. Traffic shall be cleared for descend to FL110 by Nort Upper Approach, FL120 by South Upper Approach and as soon as there is no more possible conflict the handoff to Lower Approach shall be initiated. Shortcuts shall always be initiated by Lower Approach! Normally traffic is fully released with the handoff from Upper to Lower Approach. page 11/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
Departing traffic via Rwy 29 to LANUX/KOVEL/LEDVA/MIKOV shall be cleared FL110 on SID and handoff to North Upper Approach. Right turn departures via Rwy 16 shall be cleared FL110 on SID and handoff to Upper South Approach. Left turn departures via Rwy 16 and all departures via Rwy 34 shall be cleared FL100 on SID and handoff to Upper North Approach. As soon as there is no more possible conflict the handoff to Upper Approach shall be initiated. Upper Approach shall clear this departing traffic according to 3.4.1. During departure Rwy 29/34 and arrival Rwy 34 Lower Approach may keep departing traffic to SITNI, LUGIM, MOTIX,ADAMA, KOXER and clear this departing traffic according to 3.4.1 with handoff directly to LOVV_CTR, LZIB_APP or LZBB_CTR. During simultaneous approaches to Rwy 11 and 16 Lower Approach may keep departing traffic from Rwy 16 to ADAMA, KOXER, SASAL, STEIN and clear this departing traffic according to 3.4.1 with handoff directly to LZIB_APP or LHCC_CTR. 4. LOVV_CTR Wien Radar is responsible for sequencing flights which are crossing LOVV FIR, arriving traffic into TMA and departing traffic into enroute traffic. 4.1. Radar separation Leading aircraft heavy, following aircraft heavy 4 NM Leading aircraft heavy, following aircraft medium 5 NM Leading aircraft heavy, following aircraft light 6 NM Leading aircraft medium, following aircraft medium 3 NM Leading aircraft medium, following aircraft light 5 NM At least 10 NM for arriving traffic at same or converting waypoints! No visual separation allowed! 4.2. Arriving traffic separation 4.2.1. Destination LOWW Arriving traffic to LOWW via MASUR or BARUG shall cross MASUR or BARUG at (or below) FL170. Arriving traffic to LOWW via NIGSI shall cross NIGSI at FL180. All traffic shall have at least 10 NM separation! Initiate handoff latest 20 NM before MASUR/BARUG/NIGSI. page 12/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
4.2.2. Destination LOWI Arriving traffic to LOWI shall be cleared FL180. All direct routings to RTT need prior coordination and approval from LOWI_APP! All traffic shall have at least 10 NM separation! 4.2.3. Destination LOWL/LOWG Arriving traffic to LOWL/LOWG shall be cleared FL170. Coordination with LOWW_APP may be required (GND-FL245)! 4.2.4. Destination LOWS Arriving traffic to LOWS from the south shall be cleared FL130. Arriving traffic to LOWS from the east shall be cleared to cross MATIG at (or below) FL100. Coordination with LOWL_APP required (GND-FL165)! 4.2.5. Destination EDDM Arriving traffic to EDDM via AMADI shall cross AMADI at FL130. Arriving traffic to EDDM via REDBU shall cross REDBU at FL140. All traffic shall have at least 10 NM separation! 4.3. Departing traffic Traffic shall cross FIR boundary at cruising FL. If unable, coordination required! Traffic inbound LIMM/LIPP FIR handoff at ODD cruising FL! 4.4. Sector split Sector Split at CTR depends on the expected traffic flow. General recommendations: High outbound traffic from LOWW or high traffic within Austria, a High/Low CTR sector split (FL285 sector border). Traffic with departure and destination in Austria shall be cleared max. FL280 for cruise! High inbound traffic LOWW via MASUR/BARUG, a North/South CTR sector split. High inbound traffic LOWW via NIGSI, a High/Low CTR sector split (FL285 sector border). Advice LDZO CTR for traffic inbound LOWW to cross OBUTI at FL280. High inbound traffic to LOWI from the east, a High/Low CTR sector split (FL285 sector border). High crossing traffic in LOVV FIR and low in-/outbound traffic within Austria, a North/South CTR sector split. High crossing traffic in LOVV FIR and high in-/outbound traffic within Austria, a High/Low CTR sector split (FL285 sector border). page 13/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
5. LOWI_TWR/APP 5.1. Rwy usage General Rwy usage shall be departure 08 and arrival 26. For high traffic situations it is recommended to use Rwy 26 only. During typical Foehn situations Rwy 08 shall be used. Visual approaches shall be offered to arriving traffic and visual climb outs to RTT to departing traffic. 5.2. Dep Rwy 08 / Arr Rwy 26 Departing traffic via RTT has to pass AB before arriving traffic may be cleared for approach. Departing traffic via INN (special performance right turn SIDs) has to be airborne before arriving traffic may be cleared for approach. Once arriving traffic is cleared approach, no further departures allowed. 5.3. Rwy 08 only Departing traffic via RTT has to pass AB before arriving traffic may be cleared for approach. Departing traffic via INN (special performance right turn SIDs) has to be airborne before arriving traffic may be cleared for approach. Once arriving traffic is cleared approach, no further departures allowed until arriving traffic is joining right downwind Rwy 08 Departing traffic has to be ready for departure before lineup and backtrack. 6. LOWS_TWR/APP 6.1. Rwy usage General Rwy usage shall be departure 34 and arrival 16. For high traffic situations it is recommended to use Rwy 16 only. 6.2. Dep Rwy 34 / Arr Rwy 16 Departing traffic has to start takeoff roll before arriving traffic crosses 12 NM final. 6.3. Rwy 16 only If there is departing traffic, min separation 5 NM for arriving traffic. page 14/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH
Departing traffic has to be ready for departure before lineup (and backtrack). Takeoff clearance shall normally be given when next arriving traffic crosses 3 NM final. 6.4. Rwy 34 only Departing traffic has to start takeoff roll before second arriving traffic crosses 12 NM final and first arriving traffic is on a right hand downwind. Departing traffic has to be ready for departure before lineup. Minimum separation 10 NM for arriving traffic. 7. LOWG_TWR/APP 7.1. Rwy usage General Rwy usage shall be departure 17C and arrival 35C. 7.2. Dep Rwy 17C / Arr Rwy 35C Departing traffic has to be airborne before arriving traffic crosses 12 NM final. page 15/15 NOT FOR REAL NAVIGATION 2013-07-01 / PH