LoA Roma Tunis IVAO V0.1 .pdf



Nom original: LoA Roma-Tunis IVAO - V0.1.pdf
Titre: LoA Roma-Tunis IVAO - V0.1
Auteur: h.machghoul

Ce document au format PDF 1.4 a été généré par PDFCreator Version 0.9.3 / GPL Ghostscript 8.54, et a été envoyé sur fichier-pdf.fr le 20/12/2010 à 23:00, depuis l'adresse IP 41.230.x.x. La présente page de téléchargement du fichier a été vue 1511 fois.
Taille du document: 226 Ko (18 pages).
Confidentialité: fichier public


Aperçu du document


LETTER OF AGREEMENT
between

TN IVAO DIVISION

and

IT IVAO DIVISION

TUNIS ACC

ROMA ACC

Effective: 01.10.2010

1.

General.

1.1.

Purpose.
The purpose of this Letter of Agreement is to define the co-ordination procedures to be applied between
Tunis ACC/FIC and Roma ACC/FIC when providing ATS to (GAT) General Air Traffic (IFR/VFR) and/or
Operational Air Traffic (OAT).

1.2.

Operational Status.
The two (2) ATS Units concerned shall keep each other advised of any changes in the operational status of
the facilities and navigational aids which may affect the procedures specified in this Letter of Agreement.

1.3.

Definitions for General Air Traffic and Operational Air Traffic.

1.3.1

General Air Traffic (GAT):
“Flights conducted in accordance with the rules and provisions of IVAO.”

1.3.2

Operational Air Traffic (OAT):
“Flights which do not comply with the provisions stated for GAT and for which rules and procedures have been
specified by appropriate authorities.”

2.

Areas of Responsibility and Delegation of the Responsibility for the Provision of ATS.

2.1

Areas of Responsibility.
The lateral and vertical limits of the respective areas of responsibility are as follows:
Note: See para 2.2 for the description of the areas where delegation of the responsibility for the provision of
ATS is applicable.

2.1.1

Tunis ACC
Lateral limits: as published in AIP Tunisia ENR 2.1
Vertical limits: GND - MSL / UNL add chart on annexe

2.1.2

Roma ACC
Lateral limits: as published in AIP Italia ENR 2
Vertical limits: GND - MSL / UNL add chart on annexe

2.2.

Delegation of the Responsibility for the Provision of ATS.

2.2.1

The section of ATS Route UR723/UM739, during the availability periods, between DOPEL and TABOT is
managed by Tunis-Marseille ACC directly (no information on traffic to Roma ACC)

2.2.2.

The point DOPEL for ATS Routes UM858 and UM126 is managed by Roma ACC.

LoA between Tunis ACC and Roma ACC 04.06.2009

Page 1

3
3.1

Procedures.
In order to permit flexibility and efficiency in the processing of modification, the procedures to be applied
by Tunis ACC and Roma ACC are detailed in the Annexes to this Letter of Agreement:
Main Document:
Annex A:

Definitions and Abbreviations

Annex B:

Area of Common Interest

Annex C:

Exchange of Flight Data

Annex D:

Procedures for Co-ordination

Annex E:

Transfer of Control and Transfer of Communications

Annex F:

Radar Based Co-ordination Procedures

Annex G:

Supplementary Procedures

3.2

These procedures shall be promulgated to the operational staff of the ATS-units concerned.

4

Revisions and Deviations.

4.1

Revision of the Letter of Agreement.
The revision of the present Letter of Agreement, excluding Annexes, requires the mutual consent of the
signatory divisions’ HQ.

4.2

Revision of the Annexes to the Letter of Agreement.
The revision of Annexes to the present Letter of Agreement requires the mutual consent of the authorities
designated by the respective signatory approving authorities, normally the Heads of ATC Operations of the
respective Division departments.

4.3

Temporary Deviations.
When necessary, the connected controllers (ACC controllers) of the TN or IT divisions concerned may
introduce, by mutual agreement and for a specified time period, temporary modifications to the procedures laid
down in the Annexes to the present Letter of Agreement.

4.4

Incidental Deviations.
Instances may arise where incidental deviations from the procedures specified in the Annexes to this Letter of
Agreement may become necessary. Under these circumstances air traffic controllers are expected to exercise
their best judgment, in agreeing to short term temporary derogation compatible with the requirements of this
agreement, to ensure the safety and efficiency of air traffic.

5.

Cancellation.

5.1.

Cancellation of the present Letter of Agreement by mutual agreement of the respective Approving Divisions
may take place at any time.

5.2.

Cancellation of this Letter of Agreement by either Approving division is possible at any time, provided that the
cancelling party declares its intention to cancel the Letter of Agreement with a minimum prenotification time of
ninety (90) days before the date the cancellation is to take effect.

6.

Interpretation and Settlement of Disputes.

6.1.

Should any doubt or diverging views arise regarding the interpretation of any provision of the present Letter of
Agreement, or in case of dispute regarding its application, the parties shall endeavour to reach a solution
acceptable to both of them.

LoA between Tunis ACC and Roma ACC 04.06.2009

Page 2

6.2.

Should no agreement be reached, each of the parties shall refer to a higher level of its Division-HQ, to which the
dispute shall be submitted for settlement.

7.

Validity.
This Letter of Agreement becomes effective on 01.01.2010 and supersedes to any anterior provisions.

Roma or Tunis , 01.01.2011

LoA between Tunis ACC and Roma ACC 04.06.2009

Page 3

TUNIS ACC

ROMA ACC
Letter of Agreement
RECORD OF AMENDMENTS

Effective: 01.01.2011
Revised: 01.01.2011

Nr.

Date

LoA between Tunis ACC and Roma ACC 04.06.2009

Annex

Page 4

TUNIS ACC

ROMA ACC
Annex A.
Definitions and Abbreviations.

Effective: 01.01.2011
Revised:

A. 1.

Definitions.

A. 1.1.

Area of Responsibility.
An airspace of defined dimensions where a sole ATS unit has responsibility for providing air traffic services.

A. 1.2.

Area of Common Interest.
A volume of airspace as agreed between 2 (two) ATS Units, extending into the adjacent/subjacent Areas of
Responsibility, within which airspace structure and related activities may have an impact on air traffic coordination procedures.

A. 1.3.

Approval Request.
Request from an ATS unit to the ATS unit concerned for an approval of:
• an aircraft not yet airborne, whenever the flying time to the transfer of control point is less than the agreed
minimum prenotification time, or
• an aircraft in flight intending to operate under conditions other than those described in mutually agreed
procedures.

A. 1.4.

Division Level (DL).
The flight level dividing two super-imposed areas of responsibility for the provision of ATS.

A. 1.5.

Release.

A. 1.5.1

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

A. 1.5.2

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

A. 1.5.3

The transferring unit remains responsible for separation within its Area of Responsibility unless
otherwise agreed.

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 o before the transfer of control.
Note:

The transferring unit remains responsible for separation within its Area of Responsibility unless
otherwise agreed.

LoA between Tunis ACC and Roma ACC 01.01.2011

Annex A

Page A 1

A. 2.

Abbreviations.
ACI*
AIP
AoR*
APP
ATC
ATS
CBA*
CDR*
CFL*
COP*
DL*
ETO
FIR
FL
FMP*
GAT*
IAS
ICAO
IFR
IT-ADIR
IT-AOC
IT-DIR
IT-DIV
IT-HQ
IVAO
LoA*
MEL
NM
OAT*
PEL*
RTF
RVSM
SSR
TAS
TSA*
UIR
VDF
VFR
Note:

Area of Common Interest
Aeronautical Information Publication
Area of Responsibility
Approach Control Office
Air Traffic Control
Air Traffic Services
Cross Border Area
Conditional Route
Cleared FL (for Transferring Unit)
Co-ordination Point
Division Level
Estimated Time Over Significant Point
Flight Information Region
Flight Level
Flow Management Position
General Air Traffic
Indicated Air Speed
International Civil Aviation Organization
Instrument Flight Rules

International Virtual Aviation Organization
Letter of Agreement
Minimum En-route Level
Nautical Mile
Operational Air Traffic
Planned Entry Level (for Accepting Unit)
Radio Telephony Frequency
Reduced Vertical Separation Minima
Secondary Surveillance Radar
True Air Speed
Temporary Segregated Airspace
Upper Flight Information Region
Very High Directional Finder
Visual Flight Rules
abbreviations marked with an * are non-ICAO abbreviations.

LoA between Tunis ACC and Roma ACC 01.01.2011

Annex A

Page A 2

TUNIS ACC

ROMA ACC
Annex B.
Area of Common Interest.

Effective: 01.01.2011
Revised:

B. 1.

Airspace Structure and Classification within the Area of Common Interest.
The lines defining the area of responsibility, for providing ATS, is defined by the line of the common
FIR/UIR boundary as figured below, excluded that described in para 2.2.

SECTORISATION

LoA between Tunis ACC and Roma ACC 01.01.2011

Annex B

Page B 1

B. 1.1.

Airspace Structure within the Area of Common Interest

B. 1.2.

Tunis FIR/UIR
As described in AIP Tunisia

B. 1.3.

Roma FIR/UIR
As described in AIP Italia

B. 2.

Sectorisation.

B. 2.1.

The sectorisation within the ACI:

B. 2.1.1

TUNIS ACC
as described in AIP Tunisia (and in B.1 figures)

B.2.1.2

Roma ACC
as described in B.1 figures

B.2.1.2.1 Configurations interfacing sectors
In order to use correct way of communication from Tunis ACC to ACC ROMA; Roma controllers will
indicate Tunis controller the operational configuration by using 2 letters. The first letter will always
indicate EW sector configuration in use, second letter will always indicate SU sector configuration in use.

1^ letter: Configuration EW sectors and Tunis interfacing sectors:
PHASE

ROMA
SECTOR

A

EW1/2/3

B

FLs

Roma
FREQ.

Telephone
Line

FL460
MEL

135.700

EW1/2/3

FL460
MEL

127.125

EW2/3

↑ FL360

134.780

EW1

↑ FL355
MEL

135.700

EW2/3

↑ FL360

134.780

C

D
EW1

↑ FL355
MEL

127.125

EW2/3

↑ FL340

134.780

EW1

↑ FL335
MEL

135.700

EW2/3

↑ FL340

134.780

E

F
EW1

G

EW3
EW2
EW1

H

EW3
EW2
EW1

↑ FL335
MEL
↑ FL360
↑ FL355
↑ FL315
MEL
↑ FL360
↑ FL355
↑ FL315
MEL

COPs

TUNIS
SECTOR

FLs

INTERCOM
or
COMBOX chat

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

INTERCOM
or
COMBOX chat

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

OSMAR, NOLSI,
NIBEL, ABDAB,
DOPEL

NORTH

UNL
GND

132.550

INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat

127.125

INTERCOM
or
COMBOX chat

134.780
132.525

INTERCOM
or
COMBOX chat

135.700
134.780
132.525
127.125

LoA between Tunis ACC and Roma ACC 01.01.2011

INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat
INTERCOM
or
COMBOX chat

Annex B

Tunis
FREQ.

Page B 2

2^ letter: Configuration SU sectors and Tunis interfacing sectors:
PHASE

ROMA
SECTOR

A

SU1/2

Roma
FREQ.

Telephone
Line

FL460
MEL

128.800

SU2

↑ FL330

132.855

SU1

↑ FL325
MEL

128.800

B

B. 3.

FLs

COPs

TUNIS
SECTOR

FLs

Tunis
FREQ.

INTERCOM
or
COMBOX chat

TUNEX, TUPAL,
BABLO, SUSIP

NORTH

UNL
GND

132.550

INTERCOM
or
COMBOX chat

TUNEX, TUPAL,
BABLO, SUSIP

NORTH

UNL
GND

132.550

Special Areas within the Area of Common Interest.
LI-R46, LI-D40, LI-D40bis, LI-R54, LI-D122A/B, Air Corridors “ALPHA” and “BRAVO” sections, Firing
Areas LI-D112 A/B, LI-D114 A/B and heavy military air activity Areas Tirreno “EFA” LI-D115 A/B/C
(AIP Italia ENR 5).

B. 4.

Non-published Co-ordination Points.
COPs that are not related to significant points published in relevant AIPs :
COPs

NIL

CO-ORDINATES

NIL

LoA between Tunis ACC and Roma ACC 01.01.2011

Annex B

Page B 3

TUNIS ACC

ROMA ACC
Annex C.
Exchange of Flight Data.

Effective: 01.01.2010
Revised:

C. 1.

General.

C. 1.1.

COMBOX estimates.
A COMBOX estimate shall be passed to the appropriate sector at the accepting Centre at least 10 (ten) minutes
prior, but not earlier than 20 minutes before the aircraft is estimated to pass the transfer of control point, and
shall contain:
a.

Callsign (Flight Identification);
Note: To indicate that the flight plan is available, the accepting Centre should state aircraft
type and destination after having received the callsign.
b.
SSR code;
c.
ETO for the appropriate COP as laid down in Annex D to this LoA.;
d.
Cleared flight level, specifying climb or descent conditions if applicable, at the transfer of
control point;
e.
Requested flight level if different from cleared flight level;
f.
Other information, if applicable (as 8.33KHz spacing not provided, or RVSM not approved).
Example of a COMBOX estimate : AZA863 squawk 6145 SUSIP 1245 climbing FL280.

C. 1.2.

Verbal Estimates (INTERCOM).
For conditions that are not supported by the automatic data exchange, verbal estimates will be exchanged.
A verbal estimate shall be passed to the appropriate sector at the accepting Centre at least 10 (ten) minutes
prior, but not earlier than 20 minutes before the aircraft is estimated to pass the transfer of control point, and
shall contain:
a.
Callsign (Flight Identification);
Note: To indicate that the flight plan is available, the accepting Centre should state aircraft
type and destination after having received the callsign.
e.
SSR code;
f.
ETO for the appropriate COP as laid down in Annex D to this LoA.;
g.
Cleared flight level, specifying climb or descent conditions if applicable, at the transfer of
control point;
e.
Requested flight level if different from cleared flight level;
f.
Other information, if applicable (as 8.33KHz spacing not provided, or RVSM not approved).

C. 1.3.

Revisions.
Any significant revisions to the flight data are to be transmitted to the accepting Centre.
Time differences of 3 (three) minutes or more are to be exchanged.
Changes to the co-ordinated flight levels within 5 (five) minutes of the ETO for the transfer of control point are
subject to an Approval Request.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex C

Page C 1

C. 2.

Usable levels
a) Traffic departing Tunis FIR via OSMAR:
FLs 180-200-240-300;
b) Traffic dep. Tunis FIR via NIBEL, SUSIP,-TUPAL-BABLO: FLs 180-200-240-340;
c) Traffic departing DTKA via DOPEL:
FL 300 (FL 290+).
(FLs listed above consider the event the air refuelling “A” and “B” corridors are active)
Additional FLs could be used by Tunis ACC after receiving through one of the means set out in paragraphs
above, the information concerning the actual FLs used for the corridor.
Aircraft going to fly via TUPAL-TRP-PAL (L/UL869 at FL 240 or below) shall be instructed by Tunis ACC
to contact Trapani APP and ask for clearance through the CTR.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex C.

Page C 2

TUNIS ACC

ROMA ACC
Annex D.
Procedures for Co-ordination.

Effective: 01.01.2011
Revised:

D. 1.

General Conditions for Acceptance of Flights.

D. 1.2.

Procedures for co-ordination

D. 1.2.1

Co-ordination of flights and level allocation shall take place by reference the intersections listed in Annex C
for the relevant route according to the current Requirements for entry/exit Tunisia/Roma origin/overfly –
Southbound – or destination/overfly – Northbound – as shown below.

TRAFFIC ORIENTATION
a) Traffic inbound to:
► DTTA A/D will normally be routed via: NOLSI or ABDAB or SUSIP or TUPAL;
► DTNZ A/D will normally be routed via: TUPAL or TUNEX or DOPEL or OSMAR
► DTMB/TJ/TX/TZ/KA AA/DD will normally be routed via: DOPEL or OSMAR or TUNEX or
TUPAL
b) Traffic departing from:
► DTTA A/D will normally be routed via: OSMAR or NIBEL (M/UM734) or TUPAL or SUSIP
► DTNZ A/D will normally be routed via: NIBEL, or DOPEL or OSMAR or SUSIP
► DTMB, DTTJ, DTTX A/D will normally be routed via: OSMAR or BABLO or DOPEL
D. 1.2.2

Flights (when radar monitored), shall be considered to be maintaining the co-ordinated FL at least ten (10)
NM before the COP, unless climb or descent conditions have been clearly co-ordinated in advance.

D. 1.2.3

If the accepting ATS Unit cannot accept a flight in accordance with the conditions specified by the
transferring ATS Unit, it shall clearly indicate the conditions under which the flight will be accepted.

D. 1.2.4

The accepting ATS Unit shall not notify the transferring Centre that is established G/A/G communication
with the transferred aircraft unless specifically requested to do so.

D. 2.

ATS Routes, Co-ordination points and Flight Level Allocation
Available ATS Routes, COPs to be used and flight level allocation to be applied, unless otherwise described
in paragraph D.3, are described in the tables below.

D. 2.1.

Flights from Roma to Tunis

ATS ROUTE

COP

FLIGHT LEVEL
ALLOCATION

UM126

DOPEL

FL310

UM858

DOPEL

ODD LEVELS

OSMAR

ODD LEVELS

NOLSI

ODD LEVELS

M*/UM731
M/UM733
P/UP161
UT543

SPECIAL CONDITIONS
Other FLs co-ordinated by phone
NO FL290

Only DTTA AD ↓ FL250 normally
Only DTTA A/D ↓ FL230 normally

L/UL44
UN157

ABDAB

ODD LEVELS

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex D.

► Not available for all TFC when firing areas LI-D112A/B,
LI-D114A/B or LI-D115A/B are activated;
Page D 1

► Not available for TFC with RFL240 or below when firing areas LID112A, LI-D114A or LI-D115A are activated;
► Not available for TFC with RFL240 or above when firing areas
LI-D112B, LI-D114B or LI-D115B are activated.
UM738

TUNEX

ODD LEVELS

For TFC dest DTNZ A/D ↓ FL310 normally
For TFC dest DTTA/ A/D FL290

M/UM725

SUSIP

ODD LEVELS

L/UL869

TUPAL

ODD LEVELS

► Available for TFC with RFL240 or below when firing areas LID112A,
LI-D114A or LI-D115A are activated;
►Available for all TFC when firing areas LI-D112A/B,LI-D114A/B or LID115A/B are activated;
► Available for TFC with RFL240 or above when firing areas LI-D112B,
LI-D114B or LI-D115B are activated
For TFC dest DTTA A/D ↓ FL210
For TFC dest DTNZ A/D ↓ FL290 normally

* Route only available within Tunis FIR

D. 2.2. Flights from Tunis to Roma
ATS ROUTE

COP

FLIGHT LEVEL
ALLOCATION

UM126
UM858

DOPEL
DOPEL

EVEN LEVELS FL 300+
EVEN LEVELS FL300+

M/UM733

OSMAR

EVEN LEVELS

DEP from DTTA AD ↑ max FL280

SPECIAL CONDITIONS

M/UM734

NIBEL

EVEN LEVELS

DEP from DTTA/NZ AA/DD ↑ max FL280 for TFC from DTTA
► Not available for all TFC when firing areas LI-D112A/B,
LI-D114A/B or LI-D115A/B are activated;
► Not available for TFC with RFL240 or above when firing areas LID112B, LI-D114B or LI-D115B are activated;
► Not available all TFC when firing areas LI-D112A/B, LI-D114A/B or
LI-D115A/B are activated.

M/UM725

SUSIP

EVEN LEVELS

DEP from DTTA/NZ AA/DD ↑ max FL280 for TFC from DTTA
DEP from DTTA/NZ AA/DD

↑ max FL280 for TFC from DTTA

► Available for TFC with RFL240 or below when firing areas LI-D112A,
LI-D114A or LI-D115A are activated;
► Available for all TFC when firing areas LI-D112A/B, LI-D114A/B or
LI-D115A/B are activated;
► Available for TFC with RFL240 or above when firing areas LID112B, LI-D114B or LI-D115B are activated.

M/UM738

SUSIP

EVEN LEVELS

L/UL869

TUPAL

EVEN LEVELS

DEP from DTTA A/D ↑ max FL280
NO FL320

M*/UM735

BABLO

EVEN LEVELS

DEP from DTMB AD ↑ max FL300
NO FL320

* Route only available within Tunis FIR

D. 3.

Special Procedures

D. 3.1.

Flights from Roma to Tunis

D. 3.1.1

Traffic destination DTTA


D. 3.1.2

Roma ACC (EW1) will compatibilize traffic inbound to DTTA A/D via NOLSI (↓FL250 normally) and
traffic inbound to DTTA via ABDAB (↓FL230 normally).

Air Corridors


In case of corridors “Alpha” and/or “Bravo” section activities (information by appropriate Roma ACC
sectors) over NOLSI and/or ABDAB points, flights will be managed by Roma ACC ↓ FL290 (if FLs
engaged are 260 / 270 / 280), or ↓ FL250 (if FLs engaged are 210 / 220 / 230), and so co-ordinated via
OLDI.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex D.

Page D 2

D. 3.1.3

Traffic destination DTNZ


Roma ACC will compatibilize traffic inbound to DTNZ A/D via TUNEX (↓FL310 normally) and
traffic inbound to DTNZ via TUPAL (↓FL290 normally).

D. 3.2.

Flights from Tunis to Roma

3.2.1

Air Corridors
In case that corridor “Alpha” or “Bravo” are engaged (information by appropriate Roma ACC sectors),
flights departing from DTTA A/D will be transferred over COPs OSMAR, NIBEL, SUSIP, TUPAL as
follows:
a)

FLs engaged into corridors “Alpha” or “Bravo” sections 210 / 220 / 230: flights have to cross OSMAR,
NIBEL, SUSIP, TUPAL FL240+ ↑ FL280 maximum; otherwise only FL 200;

b) FLs engaged into corridors “Alpha” or/and “Bravo” sections 260 / 270 / 280: flights have to cross same
points, FL 240 maximum.
D. 3.2.2

Usable levels in case of ground/ground voice communications failure when refuelling “A” and “B”
corridors are active.
a)

Traffic departing Tunis FIR via OSMAR:

FLs 180-200-240-300;

b) Traffic dep. Tunis FIR via NIBEL, SUSIP,-TUPAL-BABLO:

FLs 180-200-240-340;

c)

FL 300 ( FL 290+).

Traffic departing DTKA via DOPEL:

Additional FLs could be used by Tunis ACC after receiving through one of the means set out in Annex C,
the information concerning the actual FLs used for the refuelling corridor.
Aircraft going to fly via TUPAL-TRP-PAL (L/UL869 at FL 240 or below) shall be instructed by Tunis ACC
to contact Trapani APP and ask for clearance through the CTR.

D. 4.

VFR Flights
Information on VFR flights shall be exchanged between the two ACCs / FICs including the following:
a) VFR;
b) Identification and type of aircraft;
c) Departure and Destination point;
d) Flight level or altitude (if available);
e) Estimated time of crossing the common FIR boundary;
f) SSR code (if available);
g) Other information, if applicable.
When possible, VFR flights shall be instructed to contact entering FIC, 10 minutes before the FIR boundary.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex D.

Page D 3

TUNIS ACC

ROMA ACC
Annex E.
Transfer of Control and Transfer of Communications.

Effective: 01.01.2011
Revised:

E. 1.

Transfer of Control.
The transfer of control takes place at the AoR-boundary, unless otherwise specified in para E.3.

E. 2.

Transfer of Communications
The transfer of communications shall take place not later than the transfer of control and as specified in
paragraph E.3 unless otherwise co-ordinated.

E. 3.

Specific points for transfer of control and transfer of communications
ATS ROUTES

TRANSFER OF
CONTROL POINT

TRANSFER OF COMMUNICATIONS
ROMA TO TUNIS

TUNIS TO ROMA

UM126

DOPEL

CAR VOR + 3’

DOPEL

UM858

DOPEL

DOPEL –3’

DOPEL

M/UM733

OSMAR

OSMAR

OSMAR

M*/UM731

OSMAR

OSMAR

---

P/UP161

NOLSI

NOLSI

---

L/UL44

ABDAB

BULAR

M/UM734

NIBEL

---

SIRVI

M/UM725

SUSIP

PININ

SIRVI

M/UM725-M/UM738 after

SUSIP

---

SIRVI

M/UM738

TUNEX

PININ

---

L/UL869

TUPAL

MEGAN

TUPAL

UM735

BABLO

---

BABLO

* Route only available within Tunis FIR

Note 1:

The transfer point may be moved to suit traffic requirements for a particular flight by stating the place or
level at which such traffic will be released to the accepting ACC.

Note 2:

In case of telephone failure between Tunis and Alger, and when so requested by Tunis ACC controller,
Roma ACC will release traffic on UM126 as soon as possible (CAR VOR + 3’).

Note 3:

For aircraft flying outside controlled airspace and to which FIS is provided, transfer of communication will
be effected at the common FIR boundary.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex E.

Page E 1

TUNIS ACC

ROMA ACC
Annex F.
Radar Based Co-ordination Procedures.

Effective: 01.01.2011
Revised:

F. 1.

SSR Code Assignment.

F. 1.1.

The ATS Units concerned shall transfer aircraft on verified discrete SSR codes.

F. 1.2.

Any change of SSR code by the accepting ATS Unit may only take place after the transfer of control point.

F. 1.3.

The accepting ATS Unit shall be notified of any observed irregularity in the operation of SSR transponders.

F. 2.

Radar Co-ordination Procedures.

F. 2.1.

General

F. 2.1.1

Transfer of radar identification and transfer of radar control between Tunis ACC and Roma ACC will be
subject to the serviceability of the respective radar systems and two-way direct speech facilities between the
radar positions.

F. 2.1.2

If it becomes necessary to reduce or suspend radar transfers, a 15 (fifteen) minutes prior notification will be
observed, except in emergency situations.

F. 2.1.3

Aircraft shall not be vectored closed than 10 (ten) NM from common AoR boundary.

F. 2.2.

Transfer of Radar Control.
Transfer of radar control may be effected after prior verbal co-ordination provided the minimum distance
between the aircraft does not fall below 10 NM.

F. 2.2.1

Flights from Tunis ACC to Roma ACC and vice-versa along same routes
a)

if the succeeding aircraft is faster:
30 (thirty) NM and Mach numbers differing by not more than M .01 at FL 270 or above.

b) if the succeeding aircraft is not faster:
20 (twenty) NM
Following converging routes are considered as unique route:
Tunis ACC → Roma ACC L/UL869- M/UM725; M/UM735-L/UL869/UP784; UM733-UM126;
Roma ACC → Tunis ACC M/UM731- M/UM733- P/UP161- UL44-UP161, M/UM738- L/UL869.

F. 2.3.

Silent Transfer of Radar Control.
Silent transfer of radar control may be conducted between Roma ACC and Tunis ACC subject to the
following conditions:


The minimum longitudinal separation between aircraft on the same route at the same level, about to be
transferred, is in accordance with § F. 2.2.1.
When applying speed control (mach-number or indicated airspeed), pilots concerned shall be instructed to
report their assigned speed to the accepting ATS unit upon initial contact.



F. 2.4

The co-ordination procedures based on radar reported in F.2.2 and F.2.3 will not applicable for:
o
o
o
o

Head of State flight;
Aircraft on high jacking;
Aircraft on radio failure;
Aircraft not SSR equipped.

LoA between Tunis ACC and Roma ACC 01.01.2011 Annex F.

Page F 1

TUNIS ACC

ROMA ACC
Annex G.
Supplementary Procedures

Effective: 01.01.2011
Revised:

G. 1.

Departing Traffic from DTKA Airport.
For aircraft departing from Tabarka airport (DTKA), co-ordination shall be effected by Tunis ACC in form
of approval request. This approval request expires 10 minutes by its issuance and may contain a crossing
level on point DOPEL provided by Roma ACC, according to the estimate on the transfer of control point.

G.2

Traffic on ATS Route UM739 (UR723):
Segment TABOT – DOPEL to be considered.
► ATS Permanent route
- Saturday 00.01 to 12.00 (11.00) with MNM ENRT FL 260;
-

from Saturday 12.01 (11.01) to Sunday 24.00 (23.00) and all Italian National holidays as reported in
Italian AIC;
► CDR3

G. 3.

-

From Monday to Friday (H24) first usable level 290 subject to specific request originated by Tunis ACC
and specific approval of Cagliari APP (by Roma ACC).

-

Exchange of information for aircraft flying along UM739 (UR723), shall be referred to point TABOT.

Traffic on ATS Routes UM978/UM979.
Traffic on ATS Route UM978/M979 shall be directed by Tunis/Malta ACC, no details for Roma ACC.

G.4

RVSM Procedures

G.4.1. Definitions.
- RVSM: Reduced Vertical Separation Minimum.
A vertical separation minimum of 1000 FT is applicable between FL290 and FL410 included on the basis of
a regional agreement and in accordance with the present document.
- RVSM approved aircraft.
Aircraft having been certified for RVSM operation by the competent authorities of their countries for
operation in continental RVSM airspace.
- State aircraft.
For the purpose of continental RVSM solely aircraft used by the armed forces, customs and police services
are considered as state aircraft.

G.4.2. Application
RVSM procedures are applicable between ACC Tunis and Roma.
The flight level allocation used within the area of responsibility of the ACCs concerned is in accordance with
ICAO, annex 2, appendix 3, paragraph a.

G.4.3 General procedures
Except state aircraft, only RVSM approved IFR flights shall be cleared to enter the RVSM airspace of the
ACCs concerned.
In case of state aircraft (aircraft used by armed forces, custom and police services as defined above) not
approved for RVSM operation, the conditions relevant to the acceptance in RVSM airspace shall be coordinated with a minimum 30 minutes notification.
LoA between Tunis ACC and Roma ACC 01.01.2011

Annex G

Page G 2

G.4.4 Verbal co-ordination
In addition to the co-ordination procedures described in Annex D, the ACCs concerned shall complete,
whenever applicable, their verbal co-ordination with the following message:
concerning aircraft status:
- NEGATIVE RVSM
- NEGATIVE RVSM STATE AIRCRAFT
concerning loss of RVSM capability:
- UNABLE RVSM DUE EQUIPMENT
- UNABLE RVSM DUE TURBULENCE

G.4.5 Replacement procedures
In case of meteorological conditions resulting in severe turbulence that requires reversion to 2000 ft vertical
separation, the controller in charge of the centers concerned shall co-ordinate the flight level(s) not available
for transfer.
In case of equipment failure during the period of transfer of communication of the aircraft, the controllers
concerned shall co-ordinate the appropriate flight level of transfer.

LoA between Tunis ACC and Roma ACC 01.01.2011

Annex G

Page G 2



Télécharger le fichier (PDF)










Documents similaires


loa roma tunis ivao v0 1
u2s manual guide
flight manual f 18e f super hornet
air law
perguntas
gtb v111   january 2019   without signature block

Sur le même sujet..