Letters of Agreement
Implemented coordination procedure symbols:
↓ ICAO – Arriving traffic at the specified airport
↑ ICAO – Departing traffic from the specified airport
↓ xxx – Descending to the specified level
↑ xxx – Climbing to the specified level
xxxA – At or above the specified level
xxxB – At or below the specified level
RLSD – Released (Radar control release)
T/TRN – Turn, D/DES – Descent, C/CLB – Climb
✆ – Direct transfer of communication to the specified controller
⇒ – Authorization to issue DCT (direct routing) for traffic operating to/from the specified airport
Agreements between APPs and ACC
Unless otherwise coordinated, ACC controllers initiate the preliminary descent of aircraft inbound to TMA according to the following guidelines. This ensures coordinated entry levels into TMA and facilitates the work of APP controllers in maintaining an appropriate descent profile (depending on the STAR procedure).
For each procedure, two altitude values are specified:
- first value (bold) – the coordinated level to which the aircraft should climb/descend (unless coordination dictates otherwise).
- second value (italic) – the maximum level at which the aircraft may pass a given point (unless coordination dictates otherwise). These restrictions are usually derived from SID/STAR constraints.
- TFR column – indicates the altitude at which communication transfer occurs.
TMA Warszawa (FL225/FL245)
APP Warszawa in TMA Warszawa provides radar control services for the airports: Warszawa Chopin [EPWA] and Warszawa Modlin [EPMO].
The APP Warszawa controller is responsible for the delegated airspaces CTA01 (FL95–FL245), CTA02 (FL225–FL245), and CTA03 (5500 ft–FL95).
TMA entry altitudes
| EPWA | 11 | 15 | 29 | 33 | TFR |
|---|---|---|---|---|---|
| AGAVA | 170 190 | 170 190 | 170 190 | 170 190 | 250 |
| BIMPA | 150 170 | 150 190 | 150 190 | 150 190 | 270 |
| LIMVI | 150 180 | 150 180 | 140 160 | 140 160 | 250 |
| LOGDA | 150 210 | 150 210 | 150 190 | 150 190 | 250 |
| NEPOX | 160 200 | 160 200 | 150 180 | 160 180 | 250 |
| SORIX | 130 150 | 130 170 | 130 210 | 130 210 | 250 |
| EPMO | 08 | 26 | TFR |
|---|---|---|---|
| DOSIX | 110 150 | 110 150 | 250 |
| GOGUS | 150 170 | 150 170 | 250 |
| LIMVI | 140 200 | 140 180 | 250 |
| LOGDA | 150 210 | 150 210 | 250 |
| NEPOX | 160 180 | 160 180 | 250 |
| NUBLI* | 120 160 | 120 160 | 250 |
| SORIX | 100 130 | 100 130 | 250 |
* NUBLI STAR not to be used for planning purposes, can be assigned by ATC
| EPRA | ALL RWY | TFR |
|---|---|---|
| DOSIX | 140 | 250 |
| HURTE | 100 | 250 |
| GERVI | 140 | 250 |
| GOGUS | 170 | 250 |
| PENEX | 140 | 250 |
| VADOL | 140 | 250 |
TMA exit altitudes
| EPWA/EPMO/EPRA | ALL RWY |
|---|---|
| BAMSO | 230 |
| EVINA | 240 |
| LOLSI | 240 |
| OLILA | 240 |
| POLON | 240 |
| RUXOM | 160 |
| SOXER | 240 |
| VENES | 230 (140A) |
| XIMBA | 230 |
Transfer on heading
In justified cases, ACC may – after prior coordination with APP – instruct an aircraft to enter TMA EPWA on a heading.
If an aircraft inbound to EPWA is not following a STAR procedure (e.g., due to suspension of the procedure, weather avoidance, or other reasons), ACC provides the aircraft with information regarding expected radar vectoring to final approach for the runway in use or other instructions agreed upon with APP.
Unless otherwise coordinated, the ACC controller vectors the aircraft to enter APP airspace (TMA) near the appropriate entry point (the first point of the STAR procedure) with the appropriate heading as specified in the table:
| EPWA | 11 | 15 | 29 | 33 |
|---|---|---|---|---|
| AGAVA | 060 | 105 | 100 | 100 |
| BIMPA | 090 | 090 | 090 | 090 |
| LIMVI | 020 | 020 | 020 | 020 |
| LOGDA | 310 | 310 | 350 | 350 |
| NEPOX | 240 | 240 | 300 | 270 |
| SORIX | 115 | 140 | 115 | 115 |
TMA Łódź (FL115)
TWR Łódź provides procedural control for Łódź/Lublinek Airport [EPLL].
The TMA EPLL Sector E, along with CTA03 (5500 ft – FL95), may be delegated to the APP Warszawa controller, where APP WAW provides radar control.
When traffic is transfered to TWR Łódź, radar service must be terminated.
TMA entry and exit altitudes
| EPLL | ARR ALL RWY | DEP ALL RWY |
|---|---|---|
| ABAKU | 100 110 | 100 |
| ADOXO | 100 110 | 100 |
| SOXER | 100 110 | 100 |
| UTOLU | 100 110 | 100 |
| VIDEV | 100 110 | 110 |
TMA Radom (FL115)
TWR Radom provides procedural control for Warszawa-Radom Airport [EPRA].
The TMA Radom airspace within CTA08 (FL95 – FL115) is delegated to the APP Warszawa controller, where APP WAW provides radar control.
When traffic is transfered to TWR Radom, radar service must be terminated.
TMA exit altitudes
| EPRA | 07 | 25 |
|---|---|---|
| NENFA | 090 | 090 |
| NUFKO | 100 | 090 |
| RUXOM | 090 | 090 |
| VENES | 140 | 140 |
Further climb of the aircraft is possible after coordination with APP Warszawa.
TWR Radom transfers aircraft to the area of responsibility of ACC Warszawa/APP Warszawa/TWR Lublin at FL80.
TMA entry altitudes
| EPRA | ALL RWY |
|---|---|
| ASKOX | 100 |
| HURTE | 100 |
| IFRAL | 100 |
| VADOL | 140 / 120* |
* applies when aircraft is transfered from TWR Lublin to TWR Radom
TMA Kraków (FL245/FL285)
APP Kraków provides radar control within LTMA/UTMA Kraków, extending up to FL245/FL285.
Within TMA Kraków, there are two controlled airports: EPKK Kraków/Balice and EPKT Katowice/Pyrzowice.
TMA exit altitudes
| EPKK/EPKT | Minimum flight level | Maximum flight level |
|---|---|---|
| KURON | 100 | 170 |
| POBOK | 100 | 170 |
| LUXAR | 150 | 270 |
| OMFOL | 200 | 280 |
| LUMVE | 200 | 280 |
| NAVUR | 100 | 170 |
TMA entry altitudes
| EPKK | EPKT | |
|---|---|---|
| GOVRI | 160 210 | 260 260 |
| MOFKE | 210 260 | 190 190 |
| UWLER | 210 280 | 190 190 |
| KUKAM | 180 230 | 180 200 |
For entry points BAVOK, LENOV, MEBAN, NETIR, PADKA descent is managed by ACC LKAA / ACC LZBB / APP EPKK* (if ACC control across the border is offline), according to LoA.
These arriving aircraft are handed over directly to APP Kraków for communication.
TMA Rzeszów (FL145)
TWR Rzeszów provides procedural control for Rzeszów/Jasionka Airport [EPRZ].
The CTA09 (up to FL145) airspace, is delegated to the APP Kraków controller, where APP KRK provides radar control.
If TWR Rzeszów is online and APP Kraków is offline, ACC Warszawa controller does not provide radar control in CTA09 (as top-down rule). TWR Rzeszów provides procedural control service in TMA Rzeszów.
When traffic is transfered to TWR Rzeszów, radar service must be terminated.
Traffic transferred to TWR Rzeszów must be procedurally separated.
TMA entry altitudes
| EPRZ | ALL RWY |
|---|---|
| ETITI | 130 140 |
| VELAX | 130 140 |
| DIBED | 130 140 |
| LUXAR | 130 140 |
| ARTOB | 130 140 |
TMA Gdańsk (FL285)
APP Gdańsk provides radar control within LTMA/UTMA Gdańsk, extending up to FL285.
Additionally, APP Gdańsk provides procedural control in TMA Bydgoszcz when TWR Bydgoszcz is offline.
TMA entry altitudes
| 11 | 29 | |
|---|---|---|
| KOSEX | 290 300 | 290 300 |
| NIKMI | 110 140 | 070 130 |
| RATOR | 290 300 | 290 300 |
| OSLOG | 240 280 | 240 280 |
| IRLUN | 290 300 | 290 300 |
For entry point OGDAV descent is managed by ACC ESMM / APP EPGD* (if ACC MALMO is offline), according to LoA.
IRLUN departures should be given instruction to cross waypoint at FL140 or higher, and arrivals to cross at FL120 or below, due to possible conflict.
TMA Bydgoszcz (FL135)
TWR Bydgoszcz provides procedural control for Bydgoszcz Airport [EPBY].
Bydgoszcz Airport has published STAR and RNAV STAR arrival procedures.
When traffic is transfered to TWR Bydgoszcz, radar service must be terminated.
Traffic transferred to TWR Bydgoszcz must be procedurally separated.
TMA entry altitudes
| EPBY | ALL RWY |
|---|---|
| KEVQI | 130 140 |
| GOBNI | 130 140 |
| NIQEF | 130 140 |
Arrivals to EPBY via KEVQI and GOBNI can be descended to FL200 (KEVQI) or FL290 (GOBNI) by ACC Warszawa, further descent via APP Poznań (KEVQI) or APP Gdańsk (GOBNI) or after coordination by ACC.
TMA Poznań (FL195)
The APP Poznań [North] controller provides radar control for Poznań/Ławica (EPPO) and Zielona Góra/Babimost (EPZG).
Additionally, this sector includes aircraft operating to/from the military airfield EPKS Poznań/Krzesiny.
The APP Poznań [South] controller provides radar control for Wrocław/Strachowice (EPWR).
TMA entry altitudes
| EPPO | 10 | 28 |
|---|---|---|
| DEKUT | 150 170 | 150 170 |
| MASIV | 150 170 | 130 150 |
| NILPU | 150 170 | 110 130 |
| AKAPI | 110 130 | 130 150 |
| KELOD | 110 130 | 150 170 |
| DENKO | 150 170 | 150 170 |
Arrivals via DEKUT can be descended to FL290 by ACC Warszawa, further descent via APP Gdańsk (or after coordination).
| EPWR | 11 | 29 |
|---|---|---|
| XIDNA | 110 130 | 160 180 |
| UVIVI | 140 160 | 170 190 |
| LUMVE | 170 190 | 170 190 |
| EPOPA | 170 190 | 160 180 |
| DINOV | 110 130 | 190 |
| VAGNI | 100 120 | 190 |
Arrivals via EPOPA and LUMVE can be descended to FL290 by ACC Warszawa, further descent via APP Kraków (or after coordination by ACC).
| EPZG | 06 | 24 |
|---|---|---|
| BAREP | 090 120 | 100 120 |
| OBOLA | 090 120 | 100 120 |
Arrivals to EPZG can be descended to FL200 by ACC Warszawa, further descent via APP Poznań (or after coordination by ACC).
TMA exit altitudes
| EPPO/EPWR | ALL RWY |
|---|---|
| ALL FIX | 190 |
TMA Lublin (FL135)
TWR Lublin provides procedural control for Lublin Airport [EPLB].
Lublin Airport has published STAR and RNAV STAR arrival procedures.
When traffic is transfered to TWR Lublin, radar service must be terminated.
Traffic transferred to TWR Lublin must be procedurally separated.
TMA entry altitudes
| EPLB | ALL RWY |
|---|---|
| VENES | 130 140 |
| GAVDU | 130 140 |
| OGVET | 130 140 |
TMA Szczecin (FL135)
TWR Szczecin provides procedural control for Szczecin/Goleniów Airport [EPSC].
When traffic is transfered to TWR Szczecin, radar service must be terminated.
Traffic transferred to TWR Szczecin must be procedurally separated.
TMA entry altitudes
| EPSC | ALL RWY |
|---|---|
| OBDEJ | 130 140 |
| ELTUB | 130 140 |
| ZAWIK | 130 140 |
| BODLA | 130 140 |
| FARCU | 130 140 |
TMA Olsztyn (FL115)
TWR Mazury provides procedural control for Olsztyn/Mazury Airport [EPSY].
When traffic is transfered to TWR Mazury, radar service must be terminated.
Traffic transferred to TWR Mazury must be procedurally separated.
TMA entry altitudes
| EPSY | ALL RWY |
|---|---|
| IBINO | 110 130 |
| UDROV | 110 130 |
| ARDUT | 110 130 |
Sweden FIR
General information
LoA signed between Polish VACC and VATSIM Scandinavia on 19 February 2026
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Sweden FIR [GND-UNL]
Sectorization
See: Original document available in CoreVACC
Transfer of control
Transfer of communications shall take place not later than 20 NM before the AoR boundary.
The transferring ATS unit shall make an approval request to the receiving ATS unit about which frequency to be used before the transfer of communications for aircraft that are not equipped with 8.33 kHz spacing capability.
Transfer of radar control may be effected after prior verbal coordination provided the minimum distance between the aircraft does not fall below 5 NM.”
Transfer of radar control may be effected without prior verbal coordination provided the minimum distance between successive aircraft about to be transferred is 10 NM and constant or increasing.
When using mach-number speed control, pilots concerned shall be instructed to report their assigned mach-number to the accepting ATS unit upon initial contact.
Bremen FIR
General information
LoA signed between Polish VACC and VATSIM Germany on 19 February 2026
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Bremen FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
For successive traffic on the same route and at the same flight level, the transferring controller shall establish lateral separation of 10 NM or more, remaining constant or increasing. Otherwise, vertical separation shall be established (successive descending traffic on higher levels, successive climbing traffic on lower levels).
EDDB traffic handoff from Warszawa Radar to Bremen Radar shall take place at least 20 nm before sector boundary. Bremen Radar is responsible for clearance of Transition. Warszawa Radar shall ask Bremen Radar which runway is active in EDDB. Bremen Radar shall inform Warszawa Radar in case of a runway change in EDDB.
Munchen FIR
General information
LoA signed between Polish VACC and VATSIM Germany on 19 February 2026
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Meunchen FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
For successive traffic on the same route and at the same flight level, the transferring controller shall establish lateral separation of 10 NM or more, remaining constant or increasing. Otherwise, vertical separation shall be established (successive descending traffic on higher levels, successive climbing traffic on lower levels).
Praha FIR
General information
LoA signed between on
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Praha FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
Transfer of Communications shall take place no later than Transfer of Control. Inability to accept hand-off of an aircraft, due to capacity issues, technical problems or because the receiving ATS unit is about to close, must be coordinated with the releasing ATS unit.
Transfer of Control takes place at the Area of Responsibility boundary. A minimum distance of 5 NM from Area of Responsibility boundary shall be observed for aircraft not intending to cross the Area of Responsibility boundary unless otherwise coordinated.
Transfer of Radar Identification shall take place without prior coordination provided that the minimum distance between two successive flights on the same route and flight level to be transferred is at least 10 NM and constant or increasing.
Hand-off without prior coordination shall be initiated by the releasing ATS unit no later than 2 minutes before the Area of responsibility boundary. Transfer of Radar Identification (Hand-off) shall be accepted by receiving unit only after a successful Transfer of Communications.
Any direct routing which deviates from the flight planned route of the flight to be transferred is indicated in the EuroScope and has been coordinated between the transferring and accepting ATS stations (either by chat or by COPN/COPX tools).
Any assigned speed or heading has been coordinated between the transferring and accepting ATS stations by chat.
In case the receiving ATS unit has set its state to “break”, transfer of communication shall only take place after prior coordination or after the track has been accepted.
Bratislava FIR
General information
LoA signed between Polish VACC and VACC Slovakia on 19 February 2026
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Bratislava FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
Any of non-standard arrivals such as NON-RNAVs etc. should be coordinated manually.
Transfer of radar control without the systematic use of bidirectional speech facilities may be affected provided the horizontal distance between the aircraft involved is not less than 10 NM within 5 minutes flying time after passing the transfer of control point unless vertical separation exists.
Transfer of Control shall take place at the AoR boundary.
If the downstream sector in Euro- Scope is set to. break, the procedure of hand-off procedure is suspended, and transfer of communication can ONLY take place after the downstream sector has assumed the flight via the appropriate function of the radar client.
Lviv FIR
General information
LoA signed between Polish VACC and VATSIM Ukraine on 24 February 2022
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Lviv FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
For successive traffic on the same route and at the same flight level, the transferring controller shall establish lateral separation of 10 NM or more, remaining constant or increasing. Otherwise, vertical separation shall be established (successive descending traffic on higher levels, successive climbing traffic on lower levels).
Minsk FIR
No LoA signed between Polish VACC and VATRUS.
It is recommended to use verbal coordination in all cases of conflicting traffic and inbound traffic at the boundary of the Area of Responsibility (AoR).
For traffic arriving to UMMG airport it is recommended to descend the aircraft to FL170 at all COPs, and for traffic to UMBB FL110.
Vilnius FIR
General information
LoA signed between Polish VACC and Lithuania VACC on 19 February 2026
Areas of responsibility:
- Warszawa FIR [GND-FL660]
- Vilnius FIR [GND-FL660]
Sectorization
See: Original document available in CoreVACC
Transfer of control
For successive traffic on the same route and at the same flight level, the transferring controller shall establish lateral separation of 10 NM or more, remaining constant or increasing. Otherwise, vertical separation shall be established (successive descending traffic on higher levels, successive climbing traffic on lower levels).
Kaliningrad FIR
No LoA signed between Polish VACC and VATRUS.
It is recommended to use verbal coordination in all cases of conflicting traffic and inbound traffic at the boundary of the Area of Responsibility (AoR).
For traffic arriving to UMKK airport it is recommended to descend the aircraft to FL110 at all COPs.