LoA_LRBB_LHCC_2.1_signed

BUDAPEST ACC VATSIM BUCUREȘTI ACC/ARAD APP
LETTER OF AGREEMENT
between
Virtual Area Control Centre Hungary Virtual Area Control Centre Romania
BUDAPEST ACC BUCUREȘTI ACC/ARAD APP
Effective: 01 DEC 2015

Revision: 18 MAY 2023
APPROVED BY
____________________ ____________________
Süle Balázs George Enciu

Director vACCHUN Director vACC Romania
____________________ ____________________
Bozi Bence Teodor G Petrică

ATC Training Director Public Relations
VERSION NR. 2
This LoA may only be used within the simulated VATSIM environment and is therefore not be used for real life ATC purposes.
Unauthorised use, distribution, duplication or modification of this document on any media, website or in any form is strictly
prohibited
without prior written approval by the authors.
_________________________________________________________________________
LoA between BUDAPEST ACC and BUCUREȘTI ACC/ARAD APP - VATSIM 1
1. General
1.1. Purpose
The purpose of this Letter of Agreement is to define the coordination procedures to

be applied between Hungary vACC and Romania vACC when providing ATS to
GAT/OAT, IFR/VFR.
All information and procedures described in this Letter of Agreements shall not be
used for real world purposes.
1.2. Operational Status
Both vACC units shall keep each other advised of any changes in the operational
status of their facilities and navigational aids which may affect the procedures
specified in this Letter of Agreement.
This LoA may only be used within the simulated VATSIM environment and is
therefore not to be used for real life ATC purposes.
1.3. Validity
This Letter of Agreement becomes effective 18 MAY 2023 (AIRAC 2305), and
supersedes the Letter of Agreement between Bucharest FIR and Budapest FIR
dated 01 DEC 2015.
_________________________________________________________________________
2. Definitions and Abbreviations
2.1. Definitions
2.1.1. General Air Traffic (GAT):

All movements of civil aircraft, as well as all movements of State aircraft
(including military, customs and police aircraft) when these movements are
carried out in conformity with the procedure of ICAO.
2.1.2. Operational Air Traffic (OAT):

All flights which do not comply with the provisions stated for GAT and for
which rules and procedures have been specified by appropriate national
authorities.
2.1.3. Release for Climb:

An authorization for the accepting unit to climb (a) specific aircraft before the
transfer of control.
Note:
An authorization for the accepting unit to climb (a) specific aircraft before the
transfer of control.
2.1.4. Release for Descent:

An authorization for the accepting unit to descend (a) specific aircraft before
the transfer of control.
Note:
The transferring unit remains responsible for separation within its Area of
Responsibility unless otherwise agreed.
2.1.5. Release for Turn:

An authorization for the accepting unit to turn (a) specific aircraft away from
the current flight path by not more than 45° before the transfer of control.
Note:
The transferring unit remains responsible for separation within its Area of
Responsibility unless otherwise agreed.
2.1.6. Area of Responsibility:

An airspace of defined dimensions where a sole ATS unit has responsibility
for providing air traffic services.
2.1.7. Free route airspace (FRA):

A specified airspace within pilots can freely plan a route between a defined
entry and exit point.
_________________________________________________________________________
2.1.8. Reduced vertical separation minimum:

Between FL290 - FL410 the vertical separation is 300 m / 1000 feet.
2.2. Abbreviations
ACC: Area Control Centre

AIP: Aeronautical Information Publication
AMSL: Altitude (above) Mean Sea Level
AoR: Area of Responsibility
APP: Approach
ARR: Arrival
ATC: Air Traffic Control
ATS: Air Traffic Service
CIZ: Controller Initiated Handoff Zone
COP: Changeover Point
CPDLC: Controller Pilot Data Link Communication
CTA: Control area
DEP: Departure
ENR: Enroute
ETO: Estimated Time Over
FIC: Flight Information Centre
FIR: Flight Information Region
FL: Flight Level
FLAS: Flight Level Allocation Scheme
FRA: Free Route Airspace
GAT: General Aviation Traffic
GND: ground
ICAO: International Civil Aviation Organisation
IFR: Instrument Flight Rules
NM: Nautical Mile
OAT: Operational Air Traffic
QNH: Pressure measured at the point of sea level
RFL: Requested Flight Level
RVSM: Reduced Vertical Separation Minima
STAR: Standard Arrival
TMA: Terminal Manoeuvring Area
TWR: Tower
vACC: virtual Area Control Centre
VCCS: Voice Communication Control System
VFR: Visual Flight Rules
_________________________________________________________________________
3. Areas of Responsibility, Airspace Structure & Sectorization
3.1. Area of Responsibility
3.1.1. BUDAPEST ACC
Lateral limits: as published in AIP HUNGARY, ENR 2.1
Vertical limits: 9500’ AMSL – FL660
ICAO airspace classification for the area of responsibility of BUDAPEST ACC

along the common boundary of the area of responsibility of BUDAPEST ACC
and BUCUREȘTI ACC is described in the Airspace Structure paragraph to
this Letter of Agreement.
3.1.2. BUCUREȘTI ACC
Lateral limits: as published in AIP ROMANIA, ENR 2.1
Vertical limits: lower limit of ATS routes up to FL660
ICAO airspace classification for the area of responsibility of BUCUREȘTI ACC

along the common boundary of the area of responsibility of BUDAPEST ACC
and BUCUREȘTI ACC is described in the Airspace Structure paragraph to
this Letter of Agreement.
3.1.3. ARAD APP
Lateral limits: as published in AIP ROMANIA, ENR 2.1
Vertical limits: 2500 ft AMSL - FL175
ICAO airspace classification for the area of responsibility of ARAD APP along
the common boundary of the area of responsibility of BUDAPEST ACC and
ARAD APP is described in the Airspace Structure paragraph to this Letter of
Agreement.
_________________________________________________________________________
3.2. Airspace Structure
3.2.1. BUDAPEST FIR
Area Vertical limits Airspace Classification
As published in AIP FL660 Class C - from 9500 ft AMSL to FL660

HUNGARY, ENR 2.1 GND Class G - GND - 9500 ft AMSL
FREE ROUTE AIRSPACE IN BUDAPEST CTA

Operating hours: H24
Encompasses the
horizontal boundaries
of Budapest FIR in FL660 Class C - from 9500 ft AMSL to FL660
their full extent, as GND Class G - GND - 9500 ft AMSL
published in AIP
HUNGARY, ENR 2.1
_________________________________________________________________________
BUDAPEST FIR
_________________________________________________________________________
3.2.2. BUCUREȘTI FIR
Area Vertical limits Airspace Classification
Class C - above FL105

- lower limit of ATS routes up
to FL105
- Arad TMA 2500 ft QNH up
As published in AIP FL660
to FL175
ROMANIA, ENR 2.1 GND
- Aerodrome Control Zones
Class G - outside the
above-mentioned Class C
airspace
FREE ROUTE AIRSPACE IN BUCUREȘTI CTA

Operating hours: H24
Encompasses the
horizontal boundaries FL660
of BUCUREȘTI CTA in FL105
Class C
their full extent, as except TMA
published in AIP areas
ROMANIA, ENR 2.1
Note: FRA is not applied within the airspace of TMAs. Below FL105 is non-FRA
airspace and fixed route network airspace exists. Detailed description of
BUCUREȘTI ACC AoR airspace, both FRA and non-FRA airspace is published in
national AIP.
_________________________________________________________________________
BUCUREȘTI FIR
_________________________________________________________________________
3.2.3. ARAD TMA
Airspace
Area Vertical limits
Classification
Above 2500 ft QNH up to

ARAD TMA 1
FL175
As published in
AIP ROMANIA, Above 3500 ft QNH up to
ARAD TMA 2
ENR 2.1, FL175
Class C
excluding Above 3500 ft QNH up to
ARAD TMA 3 TIMIȘOARA CTR FL175
and ARAD CTR
Above 6500 ft QNH up to
ARAD TMA 4
FL175
_________________________________________________________________________
TMA ARAD LATERAL AND VERTICAL SECTORS
_________________________________________________________________________
FREE ROUTE AIRSPACE (FRA)
_________________________________________________________________________
3.3. Sectorization
3.3.1 BUDAPEST ACC
BUDAPEST EAST ACC
Sector FL C1 C2 C3 C4
LHCC_2_CTR
FL660
Top Top
FL365 LHCC_U_CTR LHCC_K_CTR
135.200
Upper East Upper
LHCC_CTR 127.100 128.950
FL365
Upper Lower
FL345
120.375 LHCC_CTR
Lower
LHCC_CTR LHCC_CTR
120.375
Lower FL345 East Lower East Lower
120.375 120.375
LHCC_I_CTR
FIC 9500’ AMSL
119.350
BUDAPEST EAST ACC
Sector FL C5 C6
LHCC_1_CTR
FL660
Top East Top
FL365 LHCC_N_CTR
135.550
North
128.725
FL365
Upper
FL345
LHCC_CTR
East Lower
LHCC_CTR
120.375
Lower FL345 East Lower
120.375
LHCC_I_CTR
FIC 9500’ AMSL
119.350
_________________________________________________________________________
3.3.2. BUCUREȘTI ACC
BUCUREȘTI ACC
Sector FL C1 C2
LRBB_U_CTR
FL660
Upper Upper
FL345
132.875
LRBB_L_CTR
FL345 BUDMO
Mid
FL105 122.025 LRBB_L_CTR
BUDMO
FL105 122.025
Lower
MEL
MEL LRBB_I_CTR
FIC
SFC 129.400
3.3.3. ARAD APP
ARAD APP
Sector FL C1
As described in LRAR_APP
ARAD TMA
para 3.2.3. 127.250
_________________________________________________________________________
4. Procedures for Coordination
4.1. General Conditions for Acceptance of Flights
4.1.1. Reference Location
Coordination of flights shall normally take place by reference to the

coordination point (COP) and in accordance with the appropriate levels
specified for the relevant route.
4.1.2. Level
Flights shall be considered to be maintaining the co-ordinated level at the

transfer of control point unless climb or descend conditions have been clearly
stated by verbal coordination, except if otherwise described in 4.2. and 4.3..
4.1.3. Accepting ATS unit conditions
If the accepting ATS Unit cannot accept a flight offered in accordance with the
conditions specified herein, it shall clearly indicate its inability and specify the
conditions under which the flight will be accepted.
4.1.4. Approval Request
For any proposed deviation from the conditions specified in this paragraph
(e.g. COP, route or level) the transferring unit shall initiate an Approval
Request.
4.1.5. Transfer of air-ground communication
The accepting ATS Unit shall not notify the transferring ATS Unit that it has
established ground-air communications with the transferred aircraft unless
specifically requested to do so. The Accepting Unit shall notify the transferring
Unit in the event that communication with the aircraft is not established as
expected.
_________________________________________________________________________
4.2. ATS Routes, Coordination Points and Level Allocation
Available ATS routes, COPs to be used and flight allocation to be applied, unless
otherwise described in paragraph 4.3., are described in the tables below.
4.2.1. Flights from BUDAPEST ACC to BUCUREȘTI ACC/ARAD APP using

COPs on common boundary
FRA relevance Flight Level Special

ATS-Routes COP
Budapest/București Allocation Conditions
KARIL
BADOR
NARKA
MEGIK
FRA
BUDOP INTERMEDIATE ODD
Budapest CTA
DEGET
TEGRI
MOPUG
INVED
4.2.2. FRA operation - Flights from BUDAPEST ACC to BUCUREȘTI

ACC/ARAD APP

ATS-Routes COP
FRA ALL
INTERMEDIATE ODD
Budapest CTA COPs
_________________________________________________________________________
4.2.3. Flights from BUCUREȘTI ACC/ARAD APP to BUDAPEST ACC using

COPs on common boundary

ATS-Routes COP
T33/Z948/Z949 KARIL
Z932 BADOR
Z941/Z942 NARKA
MEGIK
Y572 BUDOP INTERMEDIATE EVEN
DEGET
TEGRI
MOPUG
INVED
4.2.4. FRA operation - Flights from BUCUREȘTI ACC/ARAD APP

to BUDAPEST ACC

ATS-Routes COP
FRA ALL
INTERMEDIATE EVEN
București CTA COPs
_________________________________________________________________________
4.2.5. FLAS for ARR/DEP traffic
This scheme is a tool to standardise data exchange between the ATS Units
concerned and to give a general guide to avoid certain areas of airspace, but
does in no case release ATC personnel from the responsibility to separate
aircraft.
4.2.5.1. Departures shall be cleared as follows:

From CFL/max FL Entry conditions
LHBP
to LROP, LRBS 330 climbing
via all COPs
LRTR, LRAR climbing, cross MOPUG at

260
via MOPUG 10.000’ AMSL or above
LROD, LRSM, LRBM climbing, cross COPs at 10.000’

120
via KARIL LINE, NARKA LINE AMSL or above
LRCL
via KARIL LINE, NARKA LINE, 320 climbing
BUDOP LINE, DEGET LINE
From To via CFL/max FL Entry conditions
LROP
LHBP all COPs 330 climbing
LRBS
LRTR climbing, cross

ANY MOPUG 260 MOPUG at 10.000’
LRAR AMSL or above
LROD
climbing, cross
KARIL LINE,
LRSM ANY 120 COPs at 10.000’
NARKA LINE
AMSL or above
LRBM
KARIL LINE,
LRCL NARKA LINE,
ANY 320 climbing
BUDOP LINE
DEGET LINE
_________________________________________________________________________
4.2.5.2. Arrivals shall be cleared as follows:

Destination CFL/max FL Entry conditions
LRTR, LRAR descending, cross TEGRI at

130
via TEGRI FL170 or below
LROD
130 descending
via BADOR, BUDOP
LRSM, LRBM
130 descending
via KARIL LINE, NARKA LINE
LRCL
via KARIL LINE, NARKA LINE, 270 descending
BUDOP LINE
LRTM
via KARIL LINE, NARKA LINE, 330 at level (or below, if RFL is less)
BUDOP LINE
LRSB
via NARKA LINE,
350 at level (or below, if RFL is less)
BUDOP LINE, DEGET LINE,
TEGRI LINE
LHBP, LHKE, LHTL, LHKK

via all COPs
LHDC
via NARKA LINE
LZKZ, LZTT
via NARKA LINE
LZKZ, LZTT
via KARIL LINE
LZIB, LZPP, LZSL, LHSM,

LHPP, LHPR 340 at level (or below, if RFL is less)
via all COPs
LOWW
via all COPs
LDZA
Via TEGRI LINE, MOPUG 360 at level (or below, if RFL is less)
LINE
EPKK/EPKT
via KARIL LINE, NARKA LINE
_________________________________________________________________________
4.2.6. APPENDIX 1 - LINE definitions
KARIL LINE
_________________________________________________________________________
NARKA LINE
_________________________________________________________________________
BUDOP LINE
_________________________________________________________________________
DEGET LINE
_________________________________________________________________________
TEGRI LINE
_________________________________________________________________________
MOPUG LINE
_________________________________________________________________________
4.2.7. APPENDIX 2 - CIZ LINES
CIZ LINE BUCURESTI
LH1 N482024 E0221911
LH2 N475936 E0214720
LH3 N464037 E0204421
LH4 N462651 E0194751
LH5 N460820 E0194751
CIZ LINE BUDAPEST
LR1 N475755 E0240042
LR2 N472343 E0224600
LR3 N455556 E0213454
LR4 N454714 E0204703
_________________________________________________________________________
4.3. Special Procedures
4.3.1. Flights from BUDAPEST ACC to BUCUREȘTI ACC/ARAD APP
(1) Flights departing from LHDC via NARKA are subject of Approval Request
procedures.
(2) According to AIP Romania, filing “DCT” in flight plan Item 15(c) Route
(including changes of speed, level and/or flight rules) by the aircraft operators
is allowed inside Arad TMA above FL105, in accordance with the airspace
utilisation rules and availability.
(3) Coordination for flights from 2500 ft QNH to FL175 via TEGRI and INVED
shall be addressed to ARAD APP. Coordination for flights below 2500 ft QNH
shall be addressed to BUCUREȘTI FIC.
(4) VFR flights with destination LRSM, LROD and LRAR shall be transferred to
respective TWR’s frequency 5 minutes prior to crossing COP in order to
obtain ATC Clearance in due time before entering CTR’s.
(5) All VFR flights below 2500 ft QNH via TEGRI shall be transferred to LRAR
TWR frequency.
4.3.2. Flights from BUCUREȘTI ACC/ARAD APP to BUDAPEST ACC
(1) Flights departing from LRTR, LRAR, LROD, LRSM and LRBM entering
BUDAPEST FIR are not subject to Approval Request procedure.
(2) Limited information, consisting of ETA and SSR Code shall be verbally
forwarded to BUDAPEST FIC for traffic performing VOR or ILS instrument
approach RWY 19 at LRSM.
(3) Verbal estimates and revisions for traffic entering BUDAPEST FIR below 9500
ft AMSL shall be forwarded to BUDAPEST FIC.
(4) Transfer of Communication of flights crossing MOPUG LINE shall be

performed 20 nautical miles before the common AoR boundary.
(5) The flights mentioned in paragraph 4.3.2.(4) above have to be at the

coordinated level related to MOPUG LINE and the separation is done by
BUCUREȘTI ACC before transfer of communication. Final coordination shall
be made not later than 5 minutes before common AoR boundary time.
_________________________________________________________________________
4.3.3. Flights not following the prescribed route but affecting the adjacent FIR
shall be coordinated.
4.3.4. Normally, the clearance limit for inter-area flights shall be the aerodrome
of intended landing.
4.3.5. RVSM Procedures
(1) ATS Units shall coordinate the provision of VSM of 2000 ft between RVSM
approved civil aircraft and non-RVSM approved state aircraft operating as
GAT at the transfer of control point.
(2) In case RVSM will be suspended, the ATS Unit suspending RVSM shall
coordinate with adjacent ATS Units with regard to the flight levels appropriate
for the transfer of traffic. The ATS Unit suspending RVSM shall also
coordinate applicable sector capacities with adjacent ATS Units, as
appropriate.
_________________________________________________________________________
4.4. VFR Flights
4.4.1. Procedures for Inter-Area VFR traffic
(1) All VFR flights shall normally enter BUDAPEST/BUCUREȘTI FIR over the
published COPs.
(2) The following limited information shall be exchanged between ATS units
regard to VFR flights:
a) VFR;
b) identification, type of aircraft and SSR code (if available);
c) routing and flight level (altitude)
d) estimated time over COP;
e) other information if necessary
(3) If no flight plan available for the receiving unit, the information above, shall be
supplemented with the following:
a) departure and destination aerodrome;
b) further route of flights;
c) ETO for the next two points or estimated time of arrival (if the aircraft is
going to land at airports in BUDAPEST FIR or BUCUREȘTI FIR);
d) any additional information, if necessary
(4) For a group of VFR flights, the precise number of aircraft shall be emphasised
as well as the call sign of the group leader.
(5) Exchange of available data for VFR flights shall be transferred at least 10
minutes prior, but not earlier than 30 minutes before the aircraft is estimated to
pass the common FIR boundary.
(6) A revision, if available, shall be forwarded whenever flight data have changed
and/or the estimate varies by 5 minutes or more.
_________________________________________________________________________
4.5. Direct Routings
4.5.1. Without individual coordination, flights shall, as far as traffic permits, be

cleared across the common line of responsibility to the exit points of the areas
of responsibility of BUCUREȘTI ACC / BUDAPEST ACC.
4.5.2. The additional exceptions/provisions shall apply:
(1) Arrivals shall be cleared to the respective TMA entry or ARR

(STAR/Connecting Route) starting points, except as stated in 4.5.2.(2) and
4.5.2.(3).
(2) Arrivals to LOWW and LZIB shall be cleared to BALUX.
(3) Arrivals to LROP via TOSVI shall be cleared to LAMIT / IRLOX, according to
FPL.
(4) Conflicts shifted from the common line of responsibility shall be notified to the
accepting sector.
(5) Re-entries affecting the accepting unit shall be avoided (e.g. DCTs affecting
Beograd ACC or Lviv ACC).
_________________________________________________________________________
5. Transfer of Control and Transfer of Communications
5.1. Transfer of Control
(1) Transfer of Control shall take place at the AoR boundary. If the downstream
sector in EuroScope is set to .break, the procedure 5.4 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. If it
becomes necessary to reduce or suspend transfers, a 5-minute prior
notification is required. When transfers are suspended, the hand-off
procedure (5.4) is suspended.
(2) Traffic shall be handed off at the levels defined in the regulations below. If a
specified level restriction cannot be met due to a lower RFL, traffic shall be
handed off AT RFL, if this does not cause a conflict with other traffic,
otherwise traffic shall be coordinated.
(3) If a traffic situation is not covered herein, individual coordination between the
concerned sectors shall be made.
(4) To avoid additional workload in relation to the transfer of radar identification

and separation on radar track, the downstream unit shall not perform the
operation of “LABEL ASSUME” until it has made two-way contact with the
traffic and relevant ATC.
5.2. Silent Transfer of Control
Transfer of radar control from one elementary sector to another 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.
_________________________________________________________________________
5.3. Transfer of Communication
(1) Transfer of Communication shall be made when aircraft are crossing the CIZ
Line. After handoff, traffic is NOT released for climb, descend or turns, unless
otherwise specified in the regulations below.
(2) Spacing between two aircraft on same level and same routing shall be at least
10 NM, if the speed of the succeeding traffic is equal or less than the speed of
the preceding traffic, otherwise at least 15 NM. Spacing deviating from this
regulation shall be coordinated.
(3) Transfer of communications can be performed either by voice or via

Controller-Pilot Data Link Communications (CPDLC), when used.
5.4. Handoff procedures
Unless otherwise agreed between stations online, the following hand-off procedure
shall apply:
(1) The upstream sector sends the aircraft to the frequency of the downstream
sector by voice or text.
(2) The upstream sector initiates a transfer via the appropriate function of the
radar client.
(3) Upon initial call the downstream sector assumes the flight via the appropriate
function of the radar client.
_________________________________________________________________________
6. Flight Plans
(1) All traffic, including VFR traffic, intending to cross the international borders
shall mandatorily submit a complete and valid flight plan for the entire journey.
Traffic not complying with the present rule shall not obtain by the Air Traffic
Services any en route clearance beyond the airspace of the originating nation.
(2) All traffic, IFR and VFR, submitting a complete and valid flight plan shall be
considered as authorised to enter the foreign airspace, unless explicit denial is
notified as part of the individual controller to controller coordination. Border
crossing may be denied only in case of grave and proven operational
limitations.
7. Verbal Communication
7.1. VCCS
For any coordination use Euroscope VCCS setup by voice.
7.2. Alternate for verbal Communication
In case of VCCS failure, for coordination use private messages.
_________________________________________________________________________
ANNEX 1
Version Control
Version Date Changes Paragraphs
1 01 DEC 2015 New document all
New format
2 18 MAY 2023 All document all
changed
_________________________________________________________________________

LoA_LRBB_LHCC_2.1_signed

Uploaded by

Copyright:

Available Formats

LoA_LRBB_LHCC_2.1_signed

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LoA_LRBB_LHCC_2.1_signed

Uploaded by

Copyright:

Available Formats

BUDAPEST ACC VATSIM BUCUREȘTI ACC/ARAD APP

Effective: 01 DEC 2015

Süle Balázs George Enciu

Bozi Bence Teodor G Petrică

without prior written approval by the authors.

The purpose of this Letter of Agreement is to define the coordination procedures to

1.2. Operational Status

2. Definitions and Abbreviations

2.1.1. General Air Traffic (GAT):

2.1.2. Operational Air Traffic (OAT):

2.1.3. Release for Climb:

2.1.4. Release for Descent:

2.1.5. Release for Turn:

2.1.6. Area of Responsibility:

2.1.7. Free route airspace (FRA):

2.1.8. Reduced vertical separation minimum:

ACC: Area Control Centre

3. Areas of Responsibility, Airspace Structure & Sectorization

3.1. Area of Responsibility

3.1.1. BUDAPEST ACC

Lateral limits: as published in AIP HUNGARY, ENR 2.1

Vertical limits: 9500’ AMSL – FL660

ICAO airspace classification for the area of responsibility of BUDAPEST ACC

3.1.2. BUCUREȘTI ACC

Lateral limits: as published in AIP ROMANIA, ENR 2.1

Vertical limits: lower limit of ATS routes up to FL660

ICAO airspace classification for the area of responsibility of BUCUREȘTI ACC

3.1.3. ARAD APP

Lateral limits: as published in AIP ROMANIA, ENR 2.1

Vertical limits: 2500 ft AMSL - FL175

3.2. Airspace Structure

3.2.1. BUDAPEST FIR

Area Vertical limits Airspace Classification

As published in AIP FL660 Class C - from 9500 ft AMSL to FL660

FREE ROUTE AIRSPACE IN BUDAPEST CTA

3.2.2. BUCUREȘTI FIR

Area Vertical limits Airspace Classification

Class C - above FL105

FREE ROUTE AIRSPACE IN BUCUREȘTI CTA

3.2.3. ARAD TMA

Above 2500 ft QNH up to

TMA ARAD LATERAL AND VERTICAL SECTORS

FREE ROUTE AIRSPACE (FRA)

3.3.1 BUDAPEST ACC

BUDAPEST EAST ACC

BUDAPEST EAST ACC

3.3.2. BUCUREȘTI ACC

3.3.3. ARAD APP

4. Procedures for Coordination

4.1. General Conditions for Acceptance of Flights

4.1.1. Reference Location

Coordination of flights shall normally take place by reference to the

Flights shall be considered to be maintaining the co-ordinated level at the

4.1.3. Accepting ATS unit conditions

4.1.4. Approval Request

4.1.5. Transfer of air-ground communication

4.2. ATS Routes, Coordination Points and Level Allocation

4.2.1. Flights from BUDAPEST ACC to BUCUREȘTI ACC/ARAD APP using

FRA relevance Flight Level Special

4.2.2. FRA operation - Flights from BUDAPEST ACC to BUCUREȘTI