¶
¶ Malta FIR/UIR
¶ 1 General Information
¶ 1.1 Geographical Information
| Country | Malta |
| Timezone | UTC+01:00 |
| Local AIP | https://www.transport.gov.mt/aviation/air-navigation-services-aerodromes/aeronautical-information-publication-3764 |
| Local NOTAM | https://www.icao.int/safety/istars/pages/notams.aspx |
¶ 1.2 Units of Measurement
The table of units of measurement shown below is used within Malta FIR/UIR for air and ground operations.
| For measurement of: | Units used: |
|---|---|
| Distance used in navigation, position reporting, etc - generally in excess of 2 NM | Nautical Miles (NM) and tenths |
| Relatively short distances such as those relating to aerodromes (e.g., runway lengths) | Metres (m) |
| Altitudes, elevations and heights | Feet (ft) |
| Horizontal speed including wind speed | Knots (kt) |
| Vertical speed | Feet per minute (ft/min) |
| Wind direction for landing and taking off | Degrees Magnetic (°) |
| Wind direction except for landing and taking off | Degrees True (°) |
| Visibility, incl. runway visual range | Kilometres or metres (km or m) |
| Altimeter setting | Hectopascal (hPa) |
| Temperature | Degrees Celsius (°) |
| Weight | Metric Tonnes or Kilogrammes (t or kg) |
| Time | Hours (HR) and minutes (min); beginning at midnight UTC |
¶ 2 General Rules and Procedures
¶ 2.1 Visual Flight Rules
General
Except when operating as a special VFR flight, VFR flights shall be conducted so that the aircraft is flown in conditions of visibility and distance from clouds equal or greater than those specified in the table below.
| VMC Table | |||
| Altitude band | Airspace class | Flight visibility | Distance from clouds |
| At and above 3050 m (10 000 feet) AMSL | C, G |
8 km |
1500 m horizontally, 300 m (1000 ft) vertically |
| Below 3050 m (10 000 ft) AMSL and above 900 m (1000 ft) AMSL or 300 m (1000 ft) above terrain, whichever is higher |
C, G | 5 km | 1500 m horizontally, 300 m (1000 ft) vertically |
|
At and below 900 m (3000 ft) AMSL, or 300 m (1000 ft) above terrain, whichever is higher |
C, D |
5 km |
1500 m horizontally, |
| G | 5 km* | Clear of cloud and with the surface in sight | |
*When operating over the high seas or territorial waters and when so prescribed by the appropriate (ATS) authority:
a) flight visibilities rediced to not less than 1500 m may be permitted for flights operating:
- at speeds that, in the prevailing visibility, will give adequate opportunity to observe other traffic or any obstacles in time to avoid collision; or
- in circumstances in which the probability of encounters with other traffic would normalls be low, e.g. in areas of low volume traffic and for aerial work at low levels.
b) Helicopters may be permitted to operate in less than 1500 m flight visibility, if manoeuvred at a speed that will give adequate opportunity to observe other traffic or any ostacles in time to avoid collision.
- VFR flights shall not be operated
a) at transonic and supersonic speeds unless authorised
b) above FL195. - VFR flights within the Malta UIR above FL195 are subject to prior approval. Special purpose general aviation, sporting and aerial work flights requesting to operate above FL195 in VFR may require exceptional arrangements to operate in reserved airspace.
- VFR flights operating as GAT shall not be authorised within the Malta UIR above FL285.
- Except when necessary for take-off and landing, a VFR flight shall not be flown:
a) over congested areas of cities, towns or settlements or over an open-air assembly of persons at a height less than 1000 ft above the highest obstacle within a radius of 600 m from the aricraft; and
b) elsewhere than as specified in 2.1.5a, at a height less than 500 ft above ground or water, or 150 m (500 ft) above the highest obstacle within a radius of 150 m (500 ft) from the aircraft. - Except where otherwise indicated in air traffic control clearances, VFR flights in level cruising flight, when operated above 3000 ft from the ground or water, shall be conducted at a flight level appropriate to the track as specified in the tables of cruising levels (see Annex A).
- VFR flights shall comply with the provisions of an air traffic control service:
a) when operated within Class C airspace;
b) when forming part of Luqa aerodrome traffic; or
c) en operated as special VFR flights. - The commander of an aircraft which is being operated in accordance with the visual flight rules who wishes to change to compliance with the instrument flight rules shall:
a) if a flight plan was submitted, communicate the necessary change to be effected to its current flightplan; or
b) submit a flight plan to the appropriate air traffic services unit and obtain a clearance prior toproceeding IFR, when in controlled airspace.
Authorisation for Special VFR flights in Control Zones
Special VFR flights may be authorised to operate within a control zone, subject to an ATC clearance. Except when permitted by the competent authority for helicopters in special cases such as, but not limited to, police, medical, search and rescue operations and fire-fighting flights, the following additional conditions shall be applied:
a) such special VFR flights may be conducted during day only, unless otherwise permitted by thecompetent authority;
b) by the pilot:
- clear of cloud and with the surface in sight;
- the flight visibility is not less than 1 500 m or, for helicopters, not less than 800 m;
- speed of 140 kts IAS or less to give adequate opportunity to observe other traffic and any obstacles in time to avoid a collision; and
c) air traffic control unit shall not issue a special VFR clearance to aircraft to take off or land at an aerodrome within a control zone, or enter the aerodrome traffic zone or aerodrome traffic circuit when the reported meteorological conditions at that aerodrome are below the following minima:
- the ground visibility is less than 1 500 m or, for helicopters, less than 800 m;
- the ceiling is less than 180 m (600 ft).
Malta ATC will provide standard separation between all special VFR flights and between special VFR flightsand all IFR flights.
Radio Communication Failure
The procedures to be adopted by pilots experiencing two-way communication failure are as follows:
a) operate the transponder on Mode A code 7600;
b) if it is believed that the transmitter is functioning, transmit blind giving position reports and intentions to ATC; and
c) if special VFR clearance has been obtained when the radio communication failure occurs, proceed in accordance with the special VFR clearance to Luqa aerodrome and land as soon as possible. When entering the aerodrome traffic circuit, watch for visual signals. If the aircraft is flying on a radar heading advised by ATC when the radio communication failure occurs, resume own navigation and proceed in the most direct manner to Luqa aerodrome.
¶ 2.2 Instrument Flight Rules
- Except when necessary for take-off or landing or when specifically authorised by the competent authority, anIFR flight shall be flown at a level that is not below the established minimum flight altitude.
- Change from IFR to VFR
a) An aircraft electing to change the conduct of its flight from compliance with the instrument flight rules to visual flight rules shall notify Malta ATC that the IFR flight is cancelled and communicate thereto the changes to be made to its current flight plan.
b) When an aircraft operating under the instrument flight rules is flown in or encounters visual meteorological conditions, it shall not cancel its IFR flight unless it is anticipated, and intended, that the flight will be continued for a reasonable period of time in uninterrupted visual meteorological conditions. - Rules applicable to IFR flights within controlled airspace
a) An IFR flight operating in cruising flight in controlled airspace shall be flown at a cruising level, or if authorised to employ cruise climb techniques, between two levels or above a level, selected from the tables of cruising levels (see Annex A), except that the correlation of levels to track prescribed therein shall not apply whenever otherwise indicated in ATC clearances
b) As specified in the ICAO EUR Regional Supplementary Procedures (Doc 7030/4 – EUR), flights shall be conducted in accordance with the Instrument Flight Rules when operated within or above EUR RVSM airspace. Therefore, flights operating as General Air Traffic (GAT) within the Malta UIR at or above FL290 shall be conducted in accordance with the Instrument Flight Rules. - Rules applicable to IFR flights outside controlled airspace
a) An IFR flight operating in cruising flight outside controlled airspace shall be flown at a cruising level appropriate to its track as specified in the tables of cruising levels (see Annex A).
b) An IFR flight operating outside controlled airspace shall maintain a listening watch on the appropriate radio frequency and establish two-way radio communication, as necessary, with Malta ATC.
¶ 2.3 ATS Surveillance Services and Procedures
¶ 2.3.1 Radar Services and Procedures
¶ 2.3.1.1 General
- Malta generally subscribes to the procedures for the use of radar in Air Traffic Services that are specified in ICAO Doc. 4444.
- The extent of flight information service and the use of radar in Class G airspace are limited by radar coverage and radio communications limitations over high seas airspace. Malta ACC will attempt to identify aircraft and provide a radar flight information service. Therefore, pilots operating in Class G airspace in radio and/or radar contact with Malta ACC should not always expect traffic information on other aircraft in Class G airspace. Pilots should also note that they are wholly responsible for maintaining separation from other aircraft whether or not the controller has passed traffic information.
- Pilots operating in Class G airspace should also be aware that military activity over high-seas airspace by foreign military forces is not always known or notified to Malta ACC.
¶ 2.3.1.2 Application of Radar Control Service
- Radar identification is achieved according to provision by ICAO.
- Radar control service is applicable within the whole of the Malta UIR from FL195 to FL660, along ATS routes within the Malta FIR from MEL to FL195, within the Luqa TMA from 2000ft AMSL to FL195 and in the Luqa CTR. This service may include:
a) radar separation of arriving, departing and en-route traffic;
b) radar monitoring of arriving, departing and en-route traffic to provide information on any significant deviation from the normal flight path;
c) radar vectoring when required;
d) assistance to aircraft in emergency;
e) assistance to aircraft crossing controlled airspace;
f) warnings and position information on other aircraft considered to constitute a hazard;
g) information to assist in the navigation of aircraft; and
h) information on observed weather
¶ 2.3.1.3 Identification Procedures
- Before providing a radar service to an aircraft radar identification shall be established and the pilot informed. Thereafter, radar identification shall be maintained until termination of radar service.
- When PSR is used, aircraft may be identified by the one of the following methods:
- Departure method: By observing and correlating the target of departure aircraft within 1NM (2KM) of the departure runway.
- Position correlation method: By pilot report over a prescribed position over or relation to prescribed point on the radar map.
- Identification turn method: By issuing instructions to a pilot to carry out a turn or by observing a turn or turns reported by a pilot.
- When SSR is used, aircraft may be identified by the one of the following methods:
- By transfer of radar identification;
- Observation of compliance with an instruction to set a specific code;
- Direct recognition of the aircraft identification of a mode S - equipped aircraft in radar label;
- Recognition of the aircraft identification in radar label;
- Recognition of an assigned discrete code, the setting of which has been verified in radar label;
- Observation of compliance with an instruction to squawk IDENT.
¶ 2.3.1.4 Navigation Information
- Whether or not radar control is being applied, navigation along the authorized flight routes is normally the responsibility of the pilot-in- command but, for a number of reasons, primarily the separation and expedition of traffic, the radar controller may require to establish positive control. Pilot will be advised when radar navigation of the aircraft is terminated where upon pilot will resume their own navigation.
- Position information will be given as follows:
- A well-known geographical position;
- Bearing and distance (using points of the compass) from a known position;
- Magnetic heading (QDM) and distance to appropriate reporting point or en-route navigational facility;
- A distance to the runway touchdown point (as track miles to run).
¶ 2.3.1.5 Radar Separation Minima
- 5NM inside the Malta TMA and the airspace immediately above it and 10NM elsewhere.
- Radar Controllers are only responsible for terrain clearance when vectoring IFR flights and when taking an aircraft off an ATS route by giving a direct routing. Levels or altitudes assigned by the radar controller will provide a minimum terrain clearance.
¶ 2.3.1.6 Conflict Traffic Information
- Information regarding traffic on a conflicting path will be given, whenever practicable, in the following form:
- relative bearing of conflicting traffic terms of the 12-hour clock;
- distance from the conflicting traffic in kilo meters (nautical miles);
- direction in which the conflicting traffic appears to be proceeding;
- level and type of aircraft or, if unknown, relative speed of conflicting traffic, e.g. slow or fast.
¶ 2.3.1.7 Termination of Radar Service
When the control of an aircraft is to be transferred from radar controller to non radar controller or radar service is terminated, the radar controller shall ensure that non-radar separation is established between such controlled flights.
¶ 2.3.1.8 Radar Failure
In the event of radar failure or loss of identification, instructions will be issued to restore non-radar standard separation. In such cases, vertical separation of 500 ft may be resorted to as a temporary measure.
¶ 2.4 Altimeter Setting Procedures
¶ 2.4.1 General
- The transition altitude for Luqa aerodrome is 5000 ft while the transition level is fixed at FL070.
- QNH and temperature reports are transmitted in automatic ATIS broadcasts. These reports are also available on request from Malta ATC. QNH values are given in hectopascals and are rounded down to the next whole hectopascal. For example, a QNH of 1015.3 HPA will be given as 1015 HPA.
- Vertical positioning of aircraft when at or below the transition altitude is expressed in terms of altitude, whereas such positioning at or above the transition level is expressed in terms of flight levels. While passing through the transition layer, vertical positioning is expressed in terms of altitude when descending and in terms of flight levels when ascending.
- Vertical separation exists, or is deemed to exist, between the transition altitude and the transition level.
¶ 2.4.2 Take-off and climb
- A QNH altimeter setting is made available in taxi clearance prior to take-off.
- At Luqa aerodrome, the designated location for pre-flight altimeter checks is on the apron.
¶ 2.4.3 En-route
- Vertical separation at and above the transition level and during en-route flight, shall be expressed in terms of flight levels.
- IFR flights, and VFR flights above 3000 ft AMSL, when in level cruising flight, shall be flown at such flight levels, corresponding to the magnetic tracks as indicated in table (see Annex A).
¶ 2.4.4 Approach and landing
- A QNH altimeter setting is made available in approach clearance and in clearance to enter the traffic circuit.
- A QFE altimeter setting is available, on request, in the final approach and landing clearances. At Luqa aerodrome, the QFE setting is given for the runway being used for landing.
- Malta ATC does not provide the transition altitude, unless this information is specifically requested by the pilot. The transition level is provided in ATIS broadcasts.
¶ 2.4.5 Missed approach
In the event of missed approach, pilots should continue to use the altimeter setting selected for finalapproach, unless otherwise authorised by Malta ATC.
¶ 2.5 Regional Procedures
¶ 2.5.1 VERTICAL SEPARATION MINIMUM WITHIN RVSM AIRSPACE
- The airspace within the Malta UIR between FL290 and FL410 inclusive, as described in ENR 2.1, is RVSM airspace.
- Within this airspace, the vertical separation minimum shall be:
a) 1000ft between RVSM approved aircraft;
b) 2000ft between:
- non-RVSM approved aircraft and any other aircraft operating within the RVSM airspace;
- formation flights of State aircraft and any other aircraft operating within the RVSM airspace; and
- aircraft experiencing a communications failure in flight and any other aircraft, when both aircraft are operating within the RVSM airspace.
¶ 3 Airspace Properties
¶ 3.1 Air Traffic Services Airspace
The following airspace exist in Malta FIR/UIR:
¶ 3.1.1 FIR, CTA and TMA
¶ FIR & CTA
| Name | Lateral Limits, Vertical Limits and Airspace Class |
Callsign and Language |
Frequency | Remarks |
|---|---|---|---|---|
| Malta FIR |
363000N 0113000E — 363000N 0190000E — 342000N 0233500E — 342000N 0113000E — 363000N 0113000E
|
Malta Control (LMMM_CTR) English |
127.525 MHz |
See Annex B
|
|
363000N 0113000E — 363000N 0190000E — 342000N 0233500E — 342000N 0113000E — 363000N 0113000E MSL - FL195 | Class G (outside the lateral limits of ATS routes) |
Malta Information (LMMM_FIS) English |
119.800 MHz | ||
| Malta UIR |
363000N 0113000E — 363000N 0190000E — 342000N 0233500E — 342000N 0113000E — 363000N 0113000E FL660 - UNL | G |
Malta Control (LMMM_CTR) English |
127.525 MHz | See Annex B |
| Malta ACC Sector East |
363000N 0190000E - 342000N 0233500E - 342000N 0170513E - 363000N 0160000E - 363000N 0190000E
|
Malta Control (LMMM_E_CTR) English |
122.775 MHz | See Annex B |
| Malta ACC Sector West |
342000N 0113000E - 363000N 0113000E - 363712N 0113000E - 364852N 0115757E - 371017N 0123259E - 372044N 0130131E - 372044N 0131127E - 370725N 0133912E -370032N 0135852E - 365146N 0142334E 364837N 0143219E - 363000N 0142802E - 363000N 0160000E - 342000N 0170513E - 342000N 0113000E (excluding TMA/CTR)
|
Malta Control (LMMM_W_CTR) English |
130.975 MHz | See Annex B |
¶ TMA
| Name | Lateral Limits, Vertical Limits and Airspace Class |
Callsign and Language |
Frequency | Remarks |
|---|---|---|---|---|
| Malta TMA |
363000N 0133223E — 363000N 0153700E — 352906N 0153700E — arc of circle, 60NM radius centred on 355127.15N 0142838.78E (LMML ARP) — 351247N 0133223E — 363000N 0133223E
|
Luqa Radar (LMML_APP) English |
128.150 MHz | See Annex B |
¶ CTR
| Name | Lateral Limits, Vertical Limits and Airspace Class |
Callsign and Language |
Frequency | Remarks |
|---|---|---|---|---|
| Luqa CTR |
arc of circle, 20NM radius centred on 355127.15N 0142838.78E (LMML ARP)
|
Luqa Tower (LMML_TWR) English |
135.100 MHz |
¶ 3.2 Special Use Airspace
¶ 3.2.1 Prohibited Areas
| Name | Lateral Limits | Vertical Limits | Remarks (activity, restrictions, nature of hazard) |
|---|---|---|---|
| LM-P1 “Delimara” | A circle, 600 M radius centred at 354949N 0143316E | SFC - 2000ft AMSL | Power Plant H24 |
¶ 3.2.2 Danger Areas
| Name | Lateral Limits | Vertical Limits | Remarks (activity, restrictions, nature of hazard) |
|---|---|---|---|
| LM-D1 “Pembroke High” | An arc, 8.5 NM radius centred at 355554N 0142832E joining the following points: 360337N 0142406E - 360009N 0143736E | SFC - 27000ft AMSL |
Gun firing First usable level above: FL290 |
| LM-D2 “Pembroke Low” | An arc, 4 NM radius centred at 355554N 0142832E joining thefollowing points: 355946N 0142715E - 355829N 0143219E | SFC - 8800ft AMSL |
Gun firing First usable level above: FL100 |
¶ 3.2.3 Military Air Refuelling Areas
| Name | Lateral Limits | Vertical Limits | Width of corridor | Remarks |
|---|---|---|---|---|
| Falcon Corridor | ARLOS - EVLIB - ABNAT - SUBOK | FL150 - FL280 | 5NM either side of centerline |
Bi-direcitonal Activated on a tactical basis |
| Osprey Corridor | ARLOS - ALIXA - TISAL | FL200 - FL280 | 5NM either side of centerline |
Bi-direcitonal Activated on a tactical basis |
¶ 3.2.4 Test Training Areas
| Name | Lateral Limits | Vertical Limits | Remarks |
|---|---|---|---|
| Area Gannet | ADIPO - BAGTU - DOMNA - FORUM | FL100 - FL660 | Activated on a tactical basis either as a volume of airspace or as a track on the significant points defining the area |
| Area Albatross | ADIPO - LACAN -GENLA - FORUM | FL100 - FL660 | Activated on a tactical basis either as a volume of airspace or as a track on the significant points defining the area |
| Area Pelican | ADIPO - EBAMI -TOTTI - FORUM | FL100 - FL660 | Activated on a tactical basis either as a volume of airspace or as a track on the significant points defining the area |
¶ 4 Area Control Procedures
¶ 4.1 General procedures
¶ 4.1.1 Speed control
- Above FL245, airspeeds shall be expressed in terms of Mach numbers (conversion levels might differ with each aircraft operator)
- Below FL245, airspeeds shall be expressed as indicated airspeed (IAS) using, as a rule, units of 10 kt, or mutiples thereof.
¶ 4.1.2 Silent transfer procedure
As a rule, transfer of radar control between laterally and vertically adjacent control sectors shall be carried out as silent transfer of radar control, provided that the following conditions are met:
- a minimum radar separation between crossing aircraft is never less than 10 NM
- the minimum radar separation for aircraft on converging or successive flight paths is at least 10 NM constant or increasing; or
- if the succeeding aircraft is faster
- at least 20 NM if the speed differs by not more than M0.05 or 20 kts IAS
- at least 30 NM if the speed differs by not more than M0.1 or 40 kts IAS
¶ 4.1.3 Direct routings
- Within Malta FIR (E and W sectors) directs may be issued to the first waypoint outside of the own sector without coordination, providing that the deviation from the original route is less tan 5NM.
- Any direct routing to waypoints outside of Malta FIR shall be coordinated individually
¶ 4.1.4 SSR code allocation
The following SSR code ranges are available in Malta FIR/UIR (for local VFR at LMML see section 5.1.1.2):
| Range | |
| VFR | 0060 - 0077 |
| IFR ARR/DEP | 1401 - 1477 |
| IFR transit | 3760 - 3777 6560 - 6577 |
¶
4.2 Procedures with adjoining ACCs
¶ 4.2.1 Athens ACC (LGGG)
Traffic from Athens ACC to Malta ACC:
| COP | ATS Route | Level allocation | Special conditions |
| ARLOS | (U)B1/(U)P868/UM1 | Even | |
| DEMAG | (U)M978 | Even | |
| NEVIK | (U)L144/(U)P32 | Even | |
| ROTAS | UN45 | Even |
Traffic from Malta ACC to Athens ACC:
| COP | ATS Route | Level allocation | Special conditions |
| ARLOS | M1/N4/P167/P868/T340 | Odd | to LGSA: ⇓FL230 |
| DEMAG | M978/P158/Q789 | Odd | |
| NEVIK | L144/P32/P33 | Odd | to LGSA: ⇓FL250 |
| ROTAS | N45 | Odd |
¶
4.2.2 Roma ACC (LIRR)
Traffic from Roma ACC to Malta ACC:
| COP | ATS Route | Level allocation | Special conditions |
| ADEXI | M742 | Odd | from LICJ to LICD: FL250- |
| DOBIX | M740 | from LICG: ⇑FL90 | |
| LEVDI | Y751 | Odd | |
| LONDI | M726 | Odd | from LICJ to LICD: FL250- |
| LORED | M600 | Even | to LMML: at FL210 |
| MARON | L12 | Odd | |
| NELDA | L137/N573/N982 | Odd | from LICJ to LMML: FL250- from LICC/LICZ: FL230 from LICC/LICZ to LMML: FL150- |
| ORTAP | Q789 | Odd | |
| PAN | N163/M740 | Odd | |
| SENTI | M727/M732 | Odd | |
| SUBOK | M871 | Odd | |
| TISAL | M620 | Odd | |
| VENIM | P3 | Odd | |
Traffic from Malta ACC to Roma ACC:
| COP | ATS Route | Level allocation | Special conditions |
| ADEXI | M215/M622/M742/P623 | Even | |
| ASKOT | M621 | Even | |
| DILIN | P126 | Even | from LMML: FL320- |
| DOBIX | M740/M978 | to LICG: at FL100 | |
| LONDI | M726/Q723 | Even | from LMML: FL320- from LICD/LMML to LICJ: FL240- |
| LORED | L20/L21/M600/P624 | Odd | from LMML: FL300+ |
| NELDA | N982 | Even | from LMML: FL320- | NELDA at FL220+ to LICC/LICZ: FL160- (transfer to LICC_APP) |
| ORTAP | P167/Q789 | Even | |
| PAN | M740 | Even | from LICD via M740: FL320- |
| SENTI | M732 | Even | from LMML: FL320- |
| SUBOK | M871/P8/P158 | Even | |
| TISAL | M620 | Even | |
¶
4.2.3 Tripoli ACC (HLLL)
Traffic from Tripoli ACC to Malta ACC:
| COP | ATS Route | Level allocation | Special conditions |
| EKLIS | UP32 | Odd | |
| INDOT | B21/M622/UM979 | Even | |
| LUMED | UM215/UP126/W863 | Even | |
| OLMAX | M621/N68/UZ270 | Even | |
| RASNO | M1/UY751/Z178/UZ350 | Odd | |
| SARKI | UM600/M726/M740/W857 | Even: M726/M740 Odd: N982 |
|
| VALKI | T565 | Even |
Traffic from Malta ACC to Tripoli ACC:
| COP | ATS Route | Level allocation | Special conditions |
| ABRAM | M395/M727/N163 | Odd | |
| BONAR | M9/M980 | Odd | |
| EKLIS | P32 | Even | |
| ELIMO | M732/Z333 | Odd | |
| LOTIN | L12/L31 | Even: L31/W852 Odd: UL12 |
|
| RASNO | M1/P33/Y751 | Even: M1/UZ350 Odd: T424/UY751/Z178 |
|
| VARIG | M739/T297/T299 | Even: T297/T299 Odd: M739 |
¶
4.2.4 Tunis ACC (DTTC)
Traffic from Tunis ACC to Malta ACC:
| COP | ATS Route | Level allocation | Special conditions |
| BASMO | (U)M980/(U)R783 | Odd | from DTMB: ⇑FL130 |
| BIRSA | (U)G361/(U)P624 | Odd | from DTTX: ⇑FL150 |
| NIGAT | (U)P868 | Odd | from DTMB: ⇑FL130 |
| OMENI | (U)L874 | Odd | from DTNH: FL170 |
| RALAK | (U)G362/(U)P623 | Odd | from DTTJ: ⇑FL170 |
| SONAK | (U)M739/(U)M978/(U)R723/(U)R781 | Odd | from DTTA: ⇑FL230 |
Traffic from Malta ACC to Tunis ACC:
| COP | ATS Route | Level allocation | Special conditions |
| BASMO | L20/M980/N573 | Even | to DTMB: at FL140 |
| BIRSA | N45/P624/Z351 | Even | to DTTX: at FL160 |
| NIGAT | P868 | Even | to DTMB: at FL140 |
| OMENI | L21/L30/L874/M9 | Even | to DTNH: at FL180 |
| RALAK | L144/M742/N47/P623 | Even | to DTTJ: at FL180 |
| SONAK | M395/M739/M978/M979 | Even | to DTTA: at FL240 |
¶
5 Aerodromes
¶ 5.1 International Aerodromes
¶ 5.1.1 Luqa International Airport (LMML)
¶ 5.1.1.1 ATS Units
| Position | Callsign | Frequency |
|---|---|---|
| LMML_GND | Luqa Ground | 121.600 MHz |
| LMML_TWR | Luqa Tower | 135.100 MHz |
| LMML_APP | Luqa Radar | 128.150 MHz |
¶ 5.1.1.2 Local Procedures
¶ Runway usage
IFR:
- The following runway usage scheme is applied for IFR traffic:
- 0600-1800 local time: Runway 31
- 1800-0600 local time: Runway 13 - Runway 05/23 may be used for IFR traffic anytime on request, in which case this traffic is having priority over any VFR traffic
- Maximum tailwind factor: 8 kts (dry conditions), 5 kts (wet conditions)
- If the crosswind component exceeds 25 kts, runway 05/23 is used for code A-D operations
VFR:
- Runway 05/23 is the main runway for VFR traffic
- If the crossind component exceeds 12 kts, runway 13/31 may be assigned on request
¶ SSR Code allocation
| Range | |
| VFR ARR/DEP | 0060 - 0077 |
| Local VFR | 3640 - 3677 |
| IFR ARR/DEP | 1401 - 1477 |
| IFR transit | 3760 - 3777 6560 - 6577 |
¶ VFR circuits
Circuit height:
- Light aircraft: 1300 ft AMSL (not above 1500 AMSL)
- Medium/Heavy aircraft: not above 2000 ft AMSL
- If Medium/Heavy aircraft are in the aerodrome traffic circuit, light aircraft are not permitted to join or remain in the pattern.
Standard patterns:
- Runway 05: right-hand
- Runway 13: right-hand
- Runway 23: left-hand
- Runway 31: left-hand
Variations in circuit directions are applicable to Light aircraft whenever required by ATC.
¶ VFR departures
Domestic:
- Standard VFR clearances for circuit training will be assigned by Luqa Ground as follows: EXPECT VFR CIRCUITS RWY [number]
- If planned to operate within the VFR sectors or to exit the Luqa CTR pilots should expect the following standard ATC clearances:
| Runway in use | |||||||
| VFR 23 IFR 31 |
VFR 23 IFR 13 |
VFR 05 IFR 31 |
VFR 05 IFR 13 |
VFR/IFR 13 | VFR/IFR 31 | ||
| Routing (sector) |
North | Dingli Radar, Not above 1500ft |
Madliena Fort via Grand Harbour, Not above 1500ft |
Madliena Fort, not above 1500ft |
|||
| East | Blue Grotto, Not above 1500ft |
Marsascala Bay, Not above 1500ft |
|||||
| West | Dingli Radar, Not above 1500ft |
Madliena Fort via Grand Harbour, Not above 1500ft |
Dingli Radar, Not above 1500ft |
||||
| South | Blue Grotto, Not above 1500ft |
Marsascala Bay, Not above 1500ft |
Blue Grotto, Not above 1500ft |
||||
International:
- The GOZO VFR DEP route will be the standard VFR departure route assigned by ATC for all international VFR departures
- If any VFR flight intends to exit the Luqa CTR via one of the North/South/West/East gates, depending on the traffic situation ATC will amend the standard GOZO VFR DEP clearance to enable the pilot to proceed to the requested exitgate in the most direct way.
- Luqa GND will clear departures to an altitude of 2000 FT or below on the assigned VFR departure route. Departing VFR flights should expect to be transferred to APP after exit from the INNER zone and ATC will subsequently clear the VFR departures to their Requested Flight Level depending on the traffic situation. For planning purposes pilots should expect to remain at an altitude of 2000 FT until exiting the Luqa CTR if the traffic situation does not permit clearance to higher levels after exit from the INNER zone.
¶ VFR arrivals
Domestic:
- ATC will clear the aircraft via the published VFR arrival routes or direct to one of the published VRPs.
- Domestic VFR flights planning to enter the Luqa CTR via controlled airspace (Class C from 2000 FT outside the CTR) and requesting to recover to LMML should normally expect to follow the same procedures as specified for international VFR arrivals below or expect clearance by ATC to proceed direct to specific VRPs.
- Clearance to operate via the published VFR arrival routes denotes that the clearance limit is the end of the VFR arrival route unless instructed to hold in the intermediate VRPs.
- ATC clearance is required for VFR flights operating in the INNER zone to transmit from one VFR sector to another unless otherwise advised by ATC or if cleared on a standard VFR arrival/departure route. Unless otherwise advised by ATC, clearance for VFR flights to transit from one VFR sector to another is not required when operating in the OUTER zone.
- To minimize taxiing time and reduce runway occupancy, VFR traffic landing on RWY 31 may request, or be asked to perform, a midfield landing to touch down at a point on the runway between (abeam) Taxiway C and Taxiway F.
International:
- Pilots should expect the following standard ATC clearances inbound to Luqa:
| Entry point/gate | Routing |
| GOZO (VRP) | Gozo VFR arrival |
| North Gate | Madliena Fort |
| East Gate | Marsascala Bay |
| South Gate | individual routing |
| West Gate | Dingli Radar |
| South West | SW1 - Temples |
- International VFR arrivals will be cleared by ATC to enter the Luqa CTR via the standard VFR arrival routes as flight planned by the pilot. If no arrival route is specified in the FPL, the GOZO VFR ARR route will be the standard VFR arrival route assigned by the ATC
- When LM-D1 is active, the NORTH GATE VFR ARR route is not available and ATC will instruct the pilot to proceed via the GOZO VFR ARR route.
- When LM-D6 is active, VFR arrivals planning the NORTH GATE VFR ARR route will be re-routed by ATC to COMINO TOWER - ST. PAUL'S ISLANDS - MADLIENA FORT..
- The GOZO VRP defining the VFR arrival route on RWY 05/13/31 is the GZO VOR/DME. If aircraft are not equipped with a VOR receiver or the navigational aid is not serviceable, the VRP SAN LAWRENZ CHURCH should be used instead.
¶ VFR holdings
- The main VFR holding areas have been established at the TEMPLES and the GRAND HARBOUR visual reporting points
- In case of high traffic, other VRPs (such as DINGLI RADAR or MADLIENA FORT) or orbits inside the traffic pattern can be used to delay VFR traffic as well
¶ IFR departures
- The departure clearance will be provided by Luqa GND following a clearance delivery request by the pilot:
"[Callsign] CLEARED TO [Destination] via the [SID] DEPARTURE, INITIALLY 5000 FEET, SQUAWK [xxxx]" - The initial climb for all SIDs is 5000ft.
- Whenever a SID cannot be issued, aircraft will be given a radar departure consisting of the initial track or heading to befollowed after take-off and the cleared level (to be coordinated with APP).
- Upon identification, APP clears departing traffic to FL140 (higher levels available upon individual coordination) and hands over the traffic to ACC (usually passing FL100/110 when clear of other traffic). Directs to the SID fixes may be given at any time above the Minimum Vectoring Altitude.
¶ IFR Arrivals
- Arriving IFR traffic is transferred from ACC to APP (usually on course to GZO VOR) descending FL150, fully released on contact.
a) Inbound traffic via LORED is transferred at FL 210 from LIRR_SU_CTR. These arrivals are released for descent by LMMM_CTR. - Since not STARs have been established at LMML, all arriving traffic is vectored towards the final approach
- Available approach procedures:
- RWY 05: RNP
- RWY 13: ILS/LOC, RNP
- RWY 23: RNP
- RWY 31; ILS/LOC, RNP, Visual RNAV
¶ 5.1.2 Lampedusa (LICD)
¶ 5.1.2.1 ATS Units and airspace
| Name | Lateral Limits, Vertical Limits and Airspace Class |
Callsign and Language |
Frequency | Remarks |
|---|---|---|---|---|
| Lampedusa ATZ |
Circle of radius 15.0 NM centered at: 352953'N 0123706E
|
Lampedusa Tower (LICD_TWR) English, Italian |
123.500 MHz |
¶ 5.1.2.2 Local procedures
- Transition altitude: 3000ft
- Transition level:
| QNH in HPA | TRL |
| <977 | 55 |
| 977 - 994.9 | 50 |
| 995 - 1013.1 | 45 |
| ≥1013.2 | 40 |
- Lampedusa is situated in a non-radar environment, requiring close coordination for all in- and outbound traffic.
¶ VFR arrivals/departures
- both VFR arrivals and departures shall be coordinated individually
- VFR arrivals shall be transferred to LICD_TWR no later than 20NM from the airport (5NM inbound the ATZ)
¶ IFR arrivals
- IFR arrivals shall be coordinated individually with LICD_TWR to obtain information on the STAR and the expected approach procedure.
- LMMM_CTR clears arriving traffic for the STAR given by TWR, descending FL70.
- Traffic shall be transferred to LICD_TWR at least 5NM before the arrival FIX
¶ IFR departures
- IFR departures shall be coordinated individually by obtaining an IFR clearance and departure release from LMMM_CTR
- The release conditions may vary depending on the traffic situation ("released", “released, clearance expires at [time]”, “hold, advise ready”)
¶ 5.1.3 Pantelleria (LICG)
¶ 5.1.3.1 ATS units and airspace
| Name | Lateral Limits, Vertical Limits and Airspace Class |
Callsign and Language |
Frequency | Remarks |
|---|---|---|---|---|
| Pantelleria CTR Zone 2 |
line joining following points: 364941N 0113108E - 365342N 0113153E - then arc ofcircle in clockwise direction radius 12.0 NM centred on 365212N 0114643E till point 370407N 0114827E - then line joining following points: 370341N 0115742E - then arc ofcircle in clockwise direction radius 12.0 NM centred on 365140N 0115743E - till point 370324N 0120054E - then line joining following points: 370236N 0120725E - then arc ofcircle in clockwise direction radius 12.0 NM centred on 365038N 0120618E - till point 364047N 0121450E - then line joining following points: 363617N 0120747E - then arc ofcircle in clockwise direction radius 12.0 NM centred on 364544N 0115834E - till point 363351N 0115621E - then line joining following points: 363459N 0114404E - then arc ofcircle in clockwise direction radius 12.0 NM centred on 364655N 0114539E - till point 364941N 0113108E
|
Pantelleria Approach (LICG_APP) English, Italian |
119.350 MHz | |
| Pantelleria CTR Zone 1 |
line joining following points: 365306N 0115234E - 365501N 0120240E - then arc of circle in clockwise direction radius 5.0 NM centred on 365010N 0120411E - till point 364514N 0120514E - then line joining following points: 364321N 0115525E - then arc of circle in clockwise direction radius 5.0 NM centred on 364811N 0115348E - till point 365306N 0115234E
SFC - 2500ft AMSL | D |
Pantelleria Tower (LICG_TWR) English, Italian |
122.100 MHz |
¶ 5.1.3.2 Local Procedures
¶ VFR arrivals/departures
VFR traffic shall be transferred to Roma Information (125.750 MHz) before crossing the FIR boundary.
¶ IFR arrivals
Inbound IFR traffic via DOBIX - RUBRI shall be transferred to LICG_APP at FL100, latest when passing DOBIX.
¶ IFR departures
IFR departures via (RUBRI - ) DOBIX shall be coordinated individually with an approval request to LMMM_CTR, climbing FL90.
¶ 5.2 Heliports
¶ 5.2.1 Gozo Heliport (LMMG)
¶ 5.2.1.2 Local procedures
- All traffic movements are handled by Luqa Tower (LMML_TWR).
- Meteorological information shall be given in reference to Luqa aerodrome.
- Landing and take-off at the Gozo Heliport shall be conducted at pilot’s discretion.
¶ ANNEX
¶ Annex A - Cruising Levels
¶ Annex B - Area of responsibility
¶ B1.1 LMMM_CTR
¶ B1.2 LMMM_E/W_CTR
¶ B1.3 LMMM_FSS
¶ B1.4 LMML_APP
¶ Annex C - VFR procedures
¶ C1.1 VFR sectors
| BG | CT | DR | EG | GH | GL | GZO | MB | MF |
| Blue Grotto | Comino Tower | Dingli Radar | East Gate | Grand Harbour | Gordan Lighthouse | Gozo VOR | Marsascala Bay | Madliena Fort |
| NG | SG | SL | SP | SW | SW1 | TP | WG | WP |
| North Gate | South Gate | San Lawrenz Church | St. Paul's Islands | South West | South West 1 | Temples | West Point | West Gate |