Difference between revisions of "LOWW - High Traffic Procedures"
m (→Departures) |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
|134.670 || 118.770 || 129.050 || 125.170 || 119.800 || 132.470 | |134.670 || 118.770 || 129.050 || 125.170 || 119.800 || 132.470 | ||
|- | |- | ||
| − | |GND-FL245 || GND-FL245 || GND-FL245 || GND-FL245 || 1<sup>st</sup> | + | |GND-FL245 || GND-FL245 || GND-FL245 || GND-FL245 || 1<sup>st</sup> Arrival||2<sup>nd</sup> Arrival |
|- | |- | ||
|BALAD Area || NERDU Area || PESAT Area || MABOD Area || Rwy16/34 || Rwy11/29 | |BALAD Area || NERDU Area || PESAT Area || MABOD Area || Rwy16/34 || Rwy11/29 | ||
| Line 70: | Line 70: | ||
''This also indicates that the expected runway has been communicated to the pilot.'' | ''This also indicates that the expected runway has been communicated to the pilot.'' | ||
| − | ===LOWW_APP | + | ===LOWW_APP=== |
====Departures==== | ====Departures==== | ||
| − | Departures should be identified and climbed to | + | Departures should be identified and climbed to FL240 or RFL if lower. Directs to SID endpoints are possible without prior coordination. ''Flights are handed off to the next appropriate station according to their flight path. |
====Arrivals==== | ====Arrivals==== | ||
| − | LOWW_APP has to form a sequence, descend, and hand the aircraft off to | + | LOWW_APP has to form a sequence, descend, and hand the aircraft off to Arrival. At runways 11, 29 and 34 two downwinds can be established. At runway 16 this is only possible to limited extend due to LO(R)-15. |
Although forming downwind patterns is the best way to cope with big amounts of traffic, LOWW_APP has every liberty to modify the stream of traffic in order to build up a good sequence. | Although forming downwind patterns is the best way to cope with big amounts of traffic, LOWW_APP has every liberty to modify the stream of traffic in order to build up a good sequence. | ||
| − | Speed for Handoff to | + | Speed for Handoff to Arrival is 220 kn and altitude of 8.000ft |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
LOWW_APP and LOWW_F/D_APP are working closely together, so communication between them is very important. | LOWW_APP and LOWW_F/D_APP are working closely together, so communication between them is very important. | ||
| − | ===LOWW_F/D_APP ( | + | ===LOWW_F/D_APP (Arrival)=== |
| − | The | + | The Arrival forms the final sequence. He has to work closely together with LOWW_APP and in case of departure operations on the same runway, also with LOWW_X_TWR. |
LOWW_F/D_APP establishes the aircraft on final. Recommended speed up to 4 nm final is 160 kn, whereas 180 kn should not be exceeded. When the aircraft is established on Localizer and no more instructions have to be issued they should be handed off to TWR. | LOWW_F/D_APP establishes the aircraft on final. Recommended speed up to 4 nm final is 160 kn, whereas 180 kn should not be exceeded. When the aircraft is established on Localizer and no more instructions have to be issued they should be handed off to TWR. | ||
| Line 109: | Line 101: | ||
|} | |} | ||
| − | ''If the stack exceeds | + | ''If the stack exceeds FL150 LOVV_CTR has to be informed immediately.'' From this point on aircraft should be ''handed off to LOWW_N/S_APP at FL240 or RFL'' if lower and be informed of the holding taking place. Also LOWW_N/S_APP should be informed about aircraft with an RCL below FL240. This is to prevent aircraft from flying through the stack if APP can not contact them in time. If remote holdings in LOVV_CTR airspace have to be used, Approach should inform LOVV_CTR. |
Approach should take care that he is still able to pass departures and overflights through the arriving traffic. According to traffic situation leaving open some holding levels should be considered. | Approach should take care that he is still able to pass departures and overflights through the arriving traffic. According to traffic situation leaving open some holding levels should be considered. | ||
Latest revision as of 08:47, 26 January 2022
General
This document sets up general guidelines for working with large amounts of traffic at virtual LOWW Airport. They can always be modified by the controllers involved if deemed necessary. LOWW_APP can be divided into up to five Sectors:
| LOWW_APP | LOWW_N_APP | LOWW_P_APP | LOWW_M_APP | LOWW_F_APP | LOWW_D_APP |
| 134.670 | 118.770 | 129.050 | 125.170 | 119.800 | 132.470 |
| GND-FL245 | GND-FL245 | GND-FL245 | GND-FL245 | 1st Arrival | 2nd Arrival |
| BALAD Area | NERDU Area | PESAT Area | MABOD Area | Rwy16/34 | Rwy11/29 |
The decision which sectors are used shall be based on traffic Situation.
If LOWW_APP and LOWW_N_APP is online, Euroscope will detect a North/South Split.
Handoffs
In preparation to high traffic events every controller should have a close look onto the handoff procedures which are described in the Study Guide:Radar (page 13).
| Never hand off an aircraft that is in or can become into a conflicting situation while it is still in your own airspace.
You are responsible for everything that happens in your sector. |
Sector Procedures
LOVV_CTR
LOWW Arrivals are handed off to LOWW_APP from LOVV_ CTR according to these guidelines:
| BARUG | NIGSI |
| FL170 | FL180 |
- They should be placed at least ten miles in trail.
- Handoffs should be completed by the time the aircraft reaches the sector border (This includes Transfer of Communication!)
- Speed assignments are entered into the Euroscope tag.
- Non-standard routes and directs are subject to prior coordination.
- Controller has to be aware that directs to SID end points are possible without coordination if they do not interfere with STARs.
LOWW_N/S_APP (Upper)
The border between these two sectors is depicted in the Sectorfile.
Departures
Directs to SID endpoints are allowed without prior coordination, if the aircraft is always separated to all STARs outside LOWW Approach airspace. Departures to the south and to the west are handed off according to their Requested Cruise Level (RCL) if they can reach the associated sector within a reasonable distance (In some cases they might pass through LOVV_CTR or an APP airspace).
For Handoffs to Budapest, Bratislava or Praha Control check the respective LoA.
Arrivals
Aircraft are already cleared for a STAR inbound to one of these clearance limits:
Each of these points has got an associated holding pattern.
Upon initial contact with an aircraft Approach points out the expected Approach for each aircraft. From their clearance limit Aircraft are vectored or cleared onto a transition. This should be pointed out to the next controller by assigning the Transition or Vector in the TAG.
This also indicates that the expected runway has been communicated to the pilot.
LOWW_APP
Departures
Departures should be identified and climbed to FL240 or RFL if lower. Directs to SID endpoints are possible without prior coordination. Flights are handed off to the next appropriate station according to their flight path.
Arrivals
LOWW_APP has to form a sequence, descend, and hand the aircraft off to Arrival. At runways 11, 29 and 34 two downwinds can be established. At runway 16 this is only possible to limited extend due to LO(R)-15. Although forming downwind patterns is the best way to cope with big amounts of traffic, LOWW_APP has every liberty to modify the stream of traffic in order to build up a good sequence. Speed for Handoff to Arrival is 220 kn and altitude of 8.000ft
LOWW_APP and LOWW_F/D_APP are working closely together, so communication between them is very important.
LOWW_F/D_APP (Arrival)
The Arrival forms the final sequence. He has to work closely together with LOWW_APP and in case of departure operations on the same runway, also with LOWW_X_TWR. LOWW_F/D_APP establishes the aircraft on final. Recommended speed up to 4 nm final is 160 kn, whereas 180 kn should not be exceeded. When the aircraft is established on Localizer and no more instructions have to be issued they should be handed off to TWR.
Holding
Setting up holdings
If the stack exceeds FL150 LOVV_CTR has to be informed immediately. From this point on aircraft should be handed off to LOWW_N/S_APP at FL240 or RFL if lower and be informed of the holding taking place. Also LOWW_N/S_APP should be informed about aircraft with an RCL below FL240. This is to prevent aircraft from flying through the stack if APP can not contact them in time. If remote holdings in LOVV_CTR airspace have to be used, Approach should inform LOVV_CTR.
Approach should take care that he is still able to pass departures and overflights through the arriving traffic. According to traffic situation leaving open some holding levels should be considered.
Cancelling Holdings
In order to break up the holding patterns LOWW_APP starts to clear aircraft from the lowest levels out of the hold. Aircraft above have to be descended accordingly. LOWW_N/S_APP should handoff the lowest aircraft in his stack to LOWW_APP. LOWW_APP accepts this handoff as soon as he can take the aircraft and cancels the hold as necessary.
Transfer of communication should be carried out when LOWW_APP has accepted the handoff!
As soon as the level is vacated LOWW_N/S_APP can clear the next one to FL110 and initiate the handoff.
In a similar manner LOVV_CTR offers aircraft to LOWW_N/S_APP.