Edinburgh vMATS Part 2 2020 13

Edinburgh vMATS Part 2 – Revision 2020/13
Effective 03 December 2020
Operations DEPARTMENT
Edinburgh vMATS Part 2

EGPH
REVISION 2020/13 - Effective 03 December 2020

Edinburgh vMATS Part 2 – Revision 2020/13 PRE
Distribution and Scope

This manual is for controllers of Edinburgh Aerodrome and Approach positions, containing specific and local
procedures relevant to these positions. Controllers must be familiar with controlling procedures in the UK;
this manual should be read in conjunction with CAP 493 (MATS Part 1) and guidance on standard UK
Radiotelephony phraseology, detailed in CAP 413.
Exclusion of Liability
This manual is for use on the VATSIM Network only and should never be adopted for real world use.
The information published by VATSIM UK within this document is made available without warranty of any
kind; the Organisation accepts no responsibility or liability whether direct or indirect, as to the currency,
accuracy or quality of the information, nor for any consequence of its use.
Several procedures have been adapted or created using content published in the AIS (published and
maintained by NATS). Any information in this document does not constitute as a real-world replacement for
any official procedure / documentation set out on the AIS website, and any similar procedures set out here
or influenced by NATS’ content is written under the Limited License provided by the AIS.
Acknowledgements
This document has been written and proofread by a huge wealth of people, without which the development
of this document would not have been possible. On behalf of all VATSIM UK’s members, this acts as an
acknowledgement and thanks for their work.
Definitions
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC
2119.
2
Marked Changes
Changes made since the last release are marked with a black bar, as indicated, in the left-hand margin. They
are also described briefly in the table below.
Amendment History
Revision Effective Date Notes
(New template, and other minor changes to formatting, grammar and
content)
New speed separation table (SEP 1.2); Added table of flight level capping
(ADC 1.2.2); Corrected SID availability/restrictions information (ADC 1.6);
2020/13 03 Dec 2020 Clarified VFR clearance procedures (ADC 2.3 & 3.7); Added guidance for
stopping departures (ADC 3.5); Added key for departure handoff priority and
note about APC working departures (ADC 3.8.2); Significant reworking of APC
section – added STARs (3.3), updated inbound release procedures (3.6),
introduced ‘Local Area’ and 3NM Buffer (4.1) and other updates.
Updated format; Remove references to Runway 12/30; SIDs and restrictions
2020/08 updated; STARS updated; VRPs/VFR Lanes Updated; Helicopter Procedures
03 Jul 2020
Updated; EGPH_DEL Added; Frequencies Updated; Major Rewrite of entire
document.
Rev 6 05 Feb 2016 Sixth publication
…
Rev 1 14 Dec 2014 First publication
3
Introduction and Structure

The Edinburgh virtual Manual of Air Traffic Services (vMATS) Part 2 is complementary to the MATS Part 1
(CAP493). Together, these two documents provide comprehensive instructions and information for ATS
controllers within VATSIM UK.
This vMATS has been divided into separate sections for ease of reference, each with its own three letter
identification code.
This document is divided into sections as follows:
Page Abbreviation Section
PRE Preface
GEN Unit General Operating Procedures
SEP Local Separation Standards
ADC Aerodrome Control
APC Approach Control
ELL Edinburgh Low Level Procedures
EMG Emergency Procedures
Time References
All time references within this document are Coordinated Universal Time (UTC), or Zulu time, unless
otherwise specified.
The UK observes daylight saving time in the summer months (British Summer Time, or BST), so the clocks
shift forwards by one (1) hour. In summer therefore, UK local time is one hour ahead of UTC/Zulu time.
List of Figures
Figure 1 – Scottish TMA Airfield Local Areas and 3NM Buffer Zone ................................................................. 35
4
Contents
GEN | General Operating Instructions....................................................................................................... 9
Chapter 1 Altimeter Setting Procedures ...................................................................................................... 9
1.1 Departing Aircraft ............................................................................................................................ 9
1.2 Arriving/Transit Aircraft................................................................................................................... 9
1.3 QFE Threshold.................................................................................................................................. 9
1.4 Transition Altitude ........................................................................................................................... 9
1.5 Transition Levels and Minimum Stack Levels .................................................................................. 9
1.6 Altimeter Setting Regions ................................................................................................................ 9
Chapter 2 All Weather Operations ............................................................................................................. 10
2.1 Low Visibility Procedures (LVP) ..................................................................................................... 10
2.2 Meteorological Information .......................................................................................................... 11
Chapter 3 Description of Airfield ................................................................................................................ 12
3.1 Aerodrome Geographical Data ...................................................................................................... 12
3.2 ATC Communication Facilities ....................................................................................................... 12
3.3 Radio Navigation and Landing Aids ............................................................................................... 12
Chapter 4 Use of Runways ......................................................................................................................... 13
4.1 Preferential Runway ...................................................................................................................... 13
4.2 Selection of Runway in Use ........................................................................................................... 13
4.3 Minimum Runway Occupancy Time .............................................................................................. 13
4.4 Runway Vacation ........................................................................................................................... 13
4.5 Land After Procedures ................................................................................................................... 14
Chapter 5 Use of ATM ................................................................................................................................ 14
SEP | Local Separation Standards ........................................................................................................... 15

Chapter 1 Departure Separation ................................................................................................................ 15
1.1 General .......................................................................................................................................... 15
1.2 Speed Separation........................................................................................................................... 15
1.3 Wake Turbulence Separation ........................................................................................................ 16
1.4 Route Separation ........................................................................................................................... 16
Chapter 2 Arrival Separation ...................................................................................................................... 16
2.1 Wake Turbulence Separation ........................................................................................................ 16
2.2 Deemed Separations ..................................................................................................................... 16
5
ADC | Aerodrome Control ...................................................................................................................... 17

Chapter 1 Ground Movement Planner (GMP) ........................................................................................... 17
1.1 Area of Responsibility .................................................................................................................... 17
1.2 Issuing Clearances ......................................................................................................................... 17
1.3 Pre-Departure Clearance (PDC) ..................................................................................................... 19
1.4 Runway Change Procedures .......................................................................................................... 19
1.5 Stand Allocation............................................................................................................................. 19
1.6 Departure Restrictions .................................................................................................................. 20
Chapter 2 Ground Movement Controller (GMC) ....................................................................................... 21
2.2 Pushback Clearance ....................................................................................................................... 21
2.3 VFR Clearances .............................................................................................................................. 21
2.4 Taxiway Restrictions ...................................................................................................................... 21
2.5 Non-Direct Taxi Instructions to Stand ........................................................................................... 22
Chapter 3 Edinburgh AIR ............................................................................................................................ 23
3.2 Runway Change Procedures .......................................................................................................... 23
3.3 Line Up Procedures........................................................................................................................ 23
3.4 Conditional Clearances .................................................................................................................. 24
3.5 Stopping a Departure .................................................................................................................... 24
3.6 Wake Separation ........................................................................................................................... 24
3.7 VFR Departures .............................................................................................................................. 24
3.8 Transfer of Control ........................................................................................................................ 25
3.9 Aircraft on Approach ..................................................................................................................... 25
3.10 Training Flights .............................................................................................................................. 26
3.11 Landing Clearance ......................................................................................................................... 26
3.12 Arrival Spacing ............................................................................................................................... 26
3.13 Missed Approaches ....................................................................................................................... 26
6
APC | Approach Control ......................................................................................................................... 28

Chapter 1 General ...................................................................................................................................... 28
1.2 Function ......................................................................................................................................... 28
Chapter 2 Procedures for Radar Directors ................................................................................................. 29
2.1 Introduction ................................................................................................................................... 29
2.2 Terrain Clearance........................................................................................................................... 29
2.3 Radar Separation Minima .............................................................................................................. 29
2.4 SSR Code Allocations ..................................................................................................................... 29
2.5 Liaison with Aerodrome Control ................................................................................................... 30
Chapter 3 Inbound Procedures .................................................................................................................. 31
3.1 Information to Arriving Aircraft ..................................................................................................... 31
3.2 Non-public transport minima ........................................................................................................ 31
3.3 Inbound Routes ............................................................................................................................. 32
3.4 Holding Procedures ....................................................................................................................... 32
3.5 Expected Approach Times ............................................................................................................. 33
3.6 Inbound Release Procedures ......................................................................................................... 33
3.7 Transfer of Communication Procedures ....................................................................................... 34
3.8 Descent before Release Point ....................................................................................................... 34
Chapter 4 Intermediate and Final Approach Procedures .......................................................................... 35
4.1 Local Area ...................................................................................................................................... 35
4.2 Continuous Descent Approaches .................................................................................................. 36
4.3 Speed Control ................................................................................................................................ 36
4.4 Procedures for Aircraft on Intermediate Approach ...................................................................... 36
4.5 Procedures for Aircraft on Final Approach .................................................................................... 37
4.6 Missed Approach Procedures ........................................................................................................ 39
Chapter 5 Outbound Procedures ............................................................................................................... 40
5.1 General .......................................................................................................................................... 40
5.2 Departures Subject to Radar Approval .......................................................................................... 40
5.3 APC Responsibilities....................................................................................................................... 40
5.4 Verification of Mode C................................................................................................................... 40
5.5 Non-Airways Departures ............................................................................................................... 41
5.6 Standard Instrument Departures (SIDs) ........................................................................................ 41
5.7 Transfer of Departures .................................................................................................................. 41
5.8 Vectoring of Departures ................................................................................................................ 42
7
5.9 Climb above SID Levels .................................................................................................................. 42
ELL | Edinburgh Low Level Procedures .................................................................................................... 43

Chapter 1 Airspace ..................................................................................................................................... 43
1.1 Classification .................................................................................................................................. 43
1.2 Provision of Air Traffic Services ..................................................................................................... 43
1.3 Visual Reference Points (VRPs) ...................................................................................................... 43
Chapter 2 VFR Operations .......................................................................................................................... 45
2.1 Penetration of ATZ......................................................................................................................... 45
2.2 Entry/Exit Lanes ............................................................................................................................. 45
2.3 Helicopter Operations ................................................................................................................... 46
2.4 SVFR Procedures ............................................................................................................................ 47
EMG | Emergencies................................................................................................................................ 48
1.1 Initial Actions ................................................................................................................................. 48
1.2 GMC Specific .................................................................................................................................. 48
1.3 AIR Specific .................................................................................................................................... 48
1.4 APC Specific ................................................................................................................................... 48
8
Edinburgh vMATS Part 2 – Revision 2020/13 GEN
GEN | General Operating Instructions

Chapter 1 Altimeter Setting Procedures
1.1 Departing Aircraft
Departing aircraft should state the QNH on first contact with GMC, otherwise it should be
issued by the GMC controller. Aircraft should be informed of any changes to the QNH as
soon as the information is available. Aircraft operating in the visual circuit can be given the
QFE if requested.
1.2 Arriving/Transit Aircraft

When aircraft are at or below the Transition Altitude, pilots are to fly on the Edinburgh QNH
until established on the final approach, at which point they may operate on the QFE. Pilots
will be issued the Edinburgh QNH by the approach controller when issued a descent to an
altitude.
1.3 QFE Threshold

The QFE for all runway thresholds is 4hPa less than the Edinburgh QNH.
1.4 Transition Altitude

The Transition Altitude in the Scottish TMA is 6000ft above Mean Sea Level (AMSL). This is
based on the Glasgow QNH.
1.5 Transition Levels and Minimum Stack Levels

The transition level and minimum stack level for Edinburgh are based on the Glasgow QNH.
Glasgow QNH Transition Level Minimum Stack Level (MSL)
1049-1032 FL65 FL70
1031 - 1014 FL70 FL70
1013-995 FL75 FL80
994-977 FL80 FL80
976-959 FL85 FL90
958-940 FL90 FL90
Note: The classification of 1013 hPa as ‘low pressure’ in the above table aligns with
MATS Part 1.
1.6 Altimeter Setting Regions

The airport is located within the Belfast Altimeter Setting Region. All VFR aircraft operating
under the Edinburgh CTA should be given the QNH by the radar controller irrespective of
which service is being provided.
9
Chapter 2 All Weather Operations

2.1 Low Visibility Procedures (LVP)
2.1.1 Enforcement
Pilots will be informed when these procedures are in operation by the ATIS or by RTF. Low
Visibility Procedures will be applied when one or more of the following weather conditions
are present:
▪ The IRVR or Metrological Visibility is 600m or less.
▪ The cloud ceiling is 200ft or lower (BKN or more).
2.1.2 Safeguarding Procedures

Safeguarding procedures are to be initiated at 1000m or lower IRVR if forecast to go into
LVPs, likewise if the cloud ceiling is 200ft or lower and forecast to drop.
Safeguarding procedures are to be initiated when the following conditions are met:
▪ The Runway Visual Range (RVR) is 1000m or less and forecast to drop into LVP.
▪ The cloud ceiling is 200ft or below and forecast to drop into LVP.
2.1.3 Instrumented Runway Visual Range (IRVR)

The IRVR is measured at three points along the runway; at the Touchdown Zone (TDZ), the
mid-point and the stop-end. The minimum IRVR that can be measured is 50m and the
maximum is 1500m.
Only the TDZ IRVR value is published in METARs, thus the remaining two IRVR values are
‘unknown’ to the VATSIM controller. When LVPs are in force, pilots should be informed of
the reported IRVR and any subsequent updates.
2.1.4 CAT II/III Holding Points

When the ILS signal is to be protected to safely permit CAT II/III approaches (in LVPs), the use
of Category II/III holding points is required.
▪ All departing aircraft must enter the runway through either A1 or D1, as appropriate.
▪ Arriving aircraft may vacate the runway through B1 or C1.
2.1.5 Arrival Separation

During LVPs, the minimum spacing used must be 10NM (6NM can be used if a gap is not
required for a departure). This is to ensure that aircraft have received a landing clearance by
2NM from touchdown, exceptionally 1NM from touchdown. During LVPs, aircraft require to
establish on the localiser at an early stage, therefore, aircraft must be vectored to intercept
the localiser at a range of not less than 10NM from touchdown.
2.1.6 Arriving Aircraft

Arriving aircraft should vacate at the first available exit from the runway in use, except Code
E/F aircraft which must vacate at the end of the runway in use (A1 or D1).
10
2.2 Meteorological Information

An ATIS will be available on frequency 131.350 MHz. The ATIS shall be maintained by the AIR
controller, though in busy periods this can be delegated to another controller. Aircraft are
required to confirm the current ATIS information on first contact. When LVPs are in force
then this should be included in the ATIS broadcast.
11
Chapter 3 Description of Airfield

3.1 Aerodrome Geographical Data
ICAO Code EGPH
Aerodrome Reference Point (ARP) Lat: 555700N Long: 0032221W
Elevation 136ft AMSL
Magnetic Variation / Annual Change 1.21°W (2022) / 0.22° E
Transition Altitude 6000ft AMSL
Safety Altitude 2700ft (N)
3.2 ATC Communication Facilities

Callsign Logon Callsign Abbreviation Frequency (MHz)
Edinburgh EGPH_ATIS ATIS 131.350
Information
Edinburgh Delivery EGPH_DEL GMP 121.975*
Edinburgh Ground EGPH_GND GMC 121.750*
Edinburgh Tower EGPH_TWR AIR 118.700*
Edinburgh Radar EGPH_APP INT 121.200*
Edinburgh Director EGPH_F_APP FIN 128.975*
3.2.1 8.33 KHz Frequencies

Due to the limitations of simulators used on VATSIM, the 8.33 KHz frequencies for Edinburgh
as found in the eAIP are unable to be used.
3.3 Radio Navigation and Landing Aids

Type Identifier Frequency Remarks
ILS 06 I-VG 108.900 MHz 3° GP
ILS 24 I-TH 108.900 MHz 3° GP
12
Chapter 4 Use of Runways

4.1 Preferential Runway
In calm conditions, Runway 24 is the preferred runway if the tailwind component is less than
5kts and the runway surface is dry. When there is a strong crosswind, then the tail wind
component should be calculated and the general trend should be assessed.
4.2 Selection of Runway in Use

AIR will select the runway in use according to the prevailing weather conditions with
reference to the current and forecast winds. In calm wind, changing and crosswind
circumstances then, in addition to the current VATSIM METAR, the TAF and winds at 2000ft
should be used to identify the most appropriate runway to use.
When a change in runway is predicted, AIR will agree with APC a suitable point to effect the
change based on the current traffic situation. GMC should be given at least 15 minutes
notice so that traffic may be re-routed to the new runway. Terminal Control shall also be
notified of the agreed action. AIR in consultation with APC, will tactically decide the last
landing and departing aircraft prior to the runway change.
Note: AIR should request release from INT for the first departure after a runway
change on the runway.
4.3 Minimum Runway Occupancy Time

Pilots should be encouraged to exit from the runway as soon as practicable as this enables
ATC to apply the minimum spacing on final approach that will achieve maximum runway
utilisation, which is important to keep the airfield operations running smoothly. It also keeps
the frequency of missed approaches to a minimum.
AIR should give arriving aircraft taxi instructions to the intermediate hold points noted in the
table below as they vacate the runway, and before handing them to GMC.
4.4 Runway Vacation

In the event an aircraft lands but cannot contact the Ground Movement Controller due to
RTF congestion, the pilot should completely vacate the landing runway and follow the
Standard Taxi Route to the clearance limit specified below:
Runway Exit Used Clearance Limit Via
A1 A8 Taxiway A
B1* A12 Taxiways B & A
C1* As instructed by ATC (Normally A15 or A16) Taxiways C & A
D1 A18 Taxiways D & A
* Code E/F aircraft must vacate the runway at the end (via A1 or D1)
13
4.5 Land After Procedures

Normally, only one aircraft is permitted to land or take-off on the runway in use at any one
time. However, when the traffic sequence is two successive landing aircraft, the second one
may be allowed to land before the first one has cleared the runway in use, providing that:
▪ it is during daylight hours;
▪ there is no evidence that braking action may be adversely affected;
▪ the second aircraft will be able to see the first aircraft clearly and continuously until
it is clear of the runway;
▪ the second aircraft has been warned.
The AIR controller will provide said warning by issuing the second aircraft with the following
instruction.
Example: “ABC123, runway 24, land after the B788 surface wind 270 degrees 12
knots”
The above procedures may only be used under the following conditions:
▪ Reported meteorological conditions are equal to or better than 6km visibility and
ceiling of 1000ft and the AIR controller is satisfied that the pilot of the second
arriving aircraft will be able to continuously observe the proceeding aircraft.
▪ When both aircraft are being operated in a normal manner.
▪ When the AIR controller can assess the separation either visually or by means of an
Aerodrome Traffic Monitor (ATM)
Chapter 5 Use of ATM

An Aerodrome Traffic Monitor is available for Advanced Use and the information derived
from the ATM may be used by suitably trained controllers to:
▪ Determine the landing order, spacing and distance from touchdown of arriving
aircraft.
▪ Assist in applying longitudinal separation for departing aircraft.
▪ Enable controllers to confirm that the initial track of departing aircraft conforms
with the clearance issued.
▪ Provide information to aircraft on the position of other aircraft in the circuit or
carrying out an instrument approach.
▪ Following identification, validate SSR codes of departing aircraft and verify
associated Mode C readouts.
▪ Monitor the progress of overflying aircraft identified by Approach Radar Control to
ensure that they do not conflict with the tracks of arriving or departing aircraft.
▪ Establish separation between departing aircraft.
▪ Pass traffic information.
▪ Establish separation in the event of a missed approach.
▪ Assist in taking initial corrective action when the separation between arriving
aircraft becomes less than the prescribed minima.
14
Edinburgh vMATS Part 2 – Revision 2020/13 SEP
SEP | Local Separation Standards

Chapter 1 Departure Separation
1.1 General
Standard separation is to be provided between all IFR and SVFR flights as specified in MATS
Part 1, Section 1, Chapter 3.
1.2 Speed Separation

If a faster aircraft follows a slower aircraft, then the minimum route separation is increased
by 1 minute for each successive group. If a slower aircraft follows an aircraft of at least 2
groups higher, the minimum route separation may be reduced by 1 minute.
▪ Group 1 followed by Group 2: add 1 minute to route separation
▪ Group 1 followed by Group 4: add 3 minutes to route separation
▪ Group 5 followed by Group 3: subtract 1 minute from route separation (but note
that the required wake separation may now exceed the route separation)
For aircraft marked with an asterisk*, which follow an aircraft in the same or lower group
with a different aircraft type, an additional minute should be added to the separation.
Example: D328 followed by DH8D*: assuming 2-minute route separation, an
additional 1 minute is required since the faster DH8D* follows the slower D328 in
the same group = total 3 minutes
Group 6 Group 5 Group 4 Group 3 Group 2 Group 1
← Faster – Slower →
CONC All Jet aircraft A400M ATR All F27 DHC6
except those in variants *
Group 4 and BA46 and RJ * F406 L410
military fast jets. (all variants) ATP
JS31/32
C56X/680/750 DH8D * BE9L/9T/10/
20/30 BE99
D328
A340 Series – TBM7
departures B350
EA50
following require C130 TBM8
coordination due E50P
DH8A/B/C E120
to slow/variable SB20
speeds. F50
All Citations
except JS41 *
C56X/680/
750 PC12
SF34
SW3/4
15
Edinburgh vMATS Part 2 – Revision 2020/13 SEP
1.3 Wake Turbulence Separation

There are no local variations to the procedures set out in MATS Part 1, Section 1, Chapter 3,
Section 9F.
1.4 Route Separation

There are no reduced route separation criteria for Edinburgh departures. Departure tracks
at Edinburgh are all deemed to be the same route. The table below demonstrates how these
apply for departures from Edinburgh (subject to aircraft speed groups in section 1.2 above).
1st Departure 2nd Departure Time
GOSAM GRICE/TLA 2 minutes
GOSAM
TLA GOSAM/GRICE
TLA
GRICE GOSAM/TLA
GRICE
Chapter 2 Arrival Separation

2.1 Wake Turbulence Separation
There are no local variations to the procedures set out in MATS Part 1, Section 1, Chapter 3,
Section 9F.
2.2 Deemed Separations

The TARTN hold is deemed separated from GOW, TRN, LANAK, SUMIN, STIRA and FYNER at
FL140 and below.
The STIRA hold is deemed separated from FOYLE (FL120 and below) and GOW, SUMIN,
TARTN, and FYNER at FL140 and below.
16
Edinburgh vMATS Part 2 – Revision 2020/13 ADC
ADC | Aerodrome Control

Chapter 1 Ground Movement Planner (GMP)
1.1 Area of Responsibility
Delivery (GMP) (“Edinburgh Delivery”) provides full departure clearance to standard IFR
departures. GMP will also ensure that an appropriate SSR code is set, initial altitude entered,
and the flight plan is consistent with the standard route document. They will also
provide/confirm ATIS information and provide any start-up delays/slots during events.
GMP will also update the scratchpad of incoming flights to note the stand number for GMC.
1.2 Issuing Clearances

It is the responsibility of GMP to issue clearances. Pilots should report the following
information when requesting clearance:
1. their stand number
2. their aircraft type
3. the ATIS information letter they are in receipt of
4. the current QNH.
GMP should ensure that both the stand number and aircraft type are confirmed by the pilot
before issuing a clearance.
An IFR clearance should follow the format:
1. Callsign
2. Destination
3. Standard Instrument Departure
4. Squawk Code
Example: “ABC123, cleared to Ibiza, GOSAM 1 Charlie departure, squawk 0356”

GMP must obtain a full read back of the given clearance. If the QNH and/or ATIS Letter were
not correctly reported by the pilot, the GMP controller will pass this to the pilot.
Example: “ABC123, correct. Information Alpha, QNH 1020”
On transfer to GMC, it is assumed that the aircraft has been informed of any changes to their
clearance and has been issued the latest QNH.
17
1.2.1 Standard Instrument Departures

Standard Instrument Departures are different to many airfields as there are restrictions on
which type of aircraft can take a certain type of SID.
SID Designator Initial Altitude Remarks
24 06
GOSAM 1C 1D 6000 feet Jet aircraft only. Minimum climb

3.3% for obstacle clearance.
TLA 6C 6D 6000 feet Non-jet aircraft. (See ADC 1.6.2

for exceptions). Minimum climb
3.3% for obstacle clearance.
GRICE 3C 4D 6000 feet Minimum climb 3.3% for

obstacle clearance.
1.2.2 Flight Level Capping

Flights to certain destinations are capped, generally due to operational reasons. Controllers
shall ensure adherence with this table, informing the pilot of necessary changes whilst being
careful to prevent the pilot from misinterpreting the change as an initial climb. Controllers
may inform pilots that, in some cases, it will be possible to obtain a higher climb from area
controllers – but this shall not be coordinated on the ground.
Destination Maximum FL
EGAA/AC FL245
EGBB/BE/NX FL275
EGCC FL255
EGGP/NR/CN/NH/NJ/NM/NO FL245
EGNT FL245
EGPD FL245
EIDW/ME/WT/CM FL245
18
1.3 Pre-Departure Clearance (PDC)

When both the controller and pilot are suitably equipped, a PDC may be offered in order to
clear pilots electronically. This can be offered up to EOBT-25 mins. A request within EOBT-15
mins can be given or given via voice at GMP discretion.
Successful clearances MUST be accepted within 5 minutes of receipt or a ‘REVERT TO VOICE’
message must be sent to the pilot.
Instructions for operation of both the vSMR and Hoppie’s clients – the two options for
facilitating clearances via datalink – are detailed on their respective websites.
1.3.1 Availability of PDC

PDC clearances will not be available in the following circumstances:
▪ Up to half an hour before a runway change, to prevent the incorrect issuing of a SID.
The actual availability of PDC will be at the GMP controller’s discretion.
▪ When the route of an aircraft’s flight plan needs to be changed.
1.4 Runway Change Procedures

When GMP is informed of a planned runway change by AIR, AIR and GMP should coordinate
to agree on the last departure from the current runway and therefore the aircraft that shall
be cleared from the new duty runway. AIR will need to inform APC of the last 3 departures
(or fewer when there are less than 3 active departures). GMC should be informed of the
decision.
In the case that aircraft which have already been cleared will be departing from the new
duty runway, these aircraft will need to be re-cleared. If the aircraft is still on the GMP
controller’s frequency, then they may issue the new clearance. If the aircraft has already
moved to a GMC / AIR frequency, GMP must arrange the re-clearing of the aircraft. The
aircraft will need to either:
▪ re-contact GMP for an amended clearance; or
▪ get a clearance relayed by GMC or AIR which has been issued by GMP.
1.5 Stand Allocation

It is the responsibility of the GMP controller to assign stands to inbound aircraft. It is
imperative that aircraft are assigned stands in a timely manner to allow appropriate
coordination between AIR and GMC to occur where there are several options for taxi
instructions before transfer to GMC.
19
1.6 Departure Restrictions

GMP is required to be aware of departure restrictions on all Standard Instrument Departure
(SIDs) with regards to SID availability. These are as included in the section below.
1.6.1 Allocation of GOSAM SID

The GOSAM SID is for jet aircraft only.
1.6.2 Allocation of Talla (TLA) SID

The TLA SID is available to non-jet aircraft at all times.
It is only available to jet aircraft if:
▪ They are routing via the Y96 or leaving controlled airspace via TLA
▪ They are routing via the N57/L612/N864 between 2300-0600 local (See Note)
Note: Given the fact that traffic levels on VATSIM differ from real life, Scottish may
elect to make the TLA SID unavailable for jet departures between 2300-0600. This
shall be coordinated with Edinburgh AIR.
20
Chapter 2 Ground Movement Controller (GMC)

Ground Movement Controller (GMC) (“Edinburgh Ground”) is responsible for the safe and
expeditious movement of aircraft on the aprons and taxiways. When aircraft are
approaching the runway, they would normally be transferred to the AIR controller.
In the absence of GMP, GMC provides full departure clearance to standard IFR departures.
GMC will also ensure that an appropriate SSR code is set, initial altitude entered, and the
flight plan is consistent with the standard route document.
2.1.1 Departure Handoffs

Aircraft should be handed to AIR with reasonable timing to prevent excessive delays and to
allow AIR to sequence aircraft effectively.
2.2 Pushback Clearance

Clearance to push must include the stand number of the aircraft being given clearance. This
is to aid bring attention to nearby aircraft of the movement.
Example: “ABC123 stand 24, push and start approved face east”
Start clearance will be provided once the aircraft is ready for pushback. Turbine aircraft will
be passed the outside air temperature if they have not acknowledged receipt of the ATIS.
Pushback directions are at the discretion of the controller for all stands.
Simultaneous pushbacks are only to be given where there is a whole stand gap between two
aircraft and 2 stand gaps when the aircraft is B752 or bigger.
2.3 VFR Clearances

VFR aircraft should contact GMC to request start and taxi. GMC shall pre-note AIR for all VFR
departures. If a VFR departure is requesting a standard routing via a prescribed exit lane (see
ELL 2.2), GMC should request clearance from AIR. Else, the aircraft should expect clearance
at the holding point.
2.4 Taxiway Restrictions

2.4.1 Taxiway Limits
Code E/F aircraft must only depart from Holding Points A1 and D1.
Code E aircraft are limited to:
▪ Taxiway E from E1 as far as Stand 2A
▪ Taxiway M from M1 to M3
▪ Taxiway G between G1 and Stand 25
21
2.4.2 Simultaneous Use of Lima and Mike Taxiways

Aircraft up to and including Code D are permitted to pass abeam each other on taxiway Lima
and taxiway Mike.
When a Code E aircraft is on taxiway Lima or taxiway Mike, the other taxiway (Mike or Lima)
is available for up to and including code C aircraft.
2.4.3 Simultaneous Use of Lima and Golf Taxiways

When a maximum Code C aircraft is stationary at L2, any aircraft up to maximum Code E is
permitted to pass behind on taxiway Golf. Aircraft pushing back from Stands 15A and 15B
facing north may be instructed to pull forward to L2, if necessary.
2.4.4 Taxiway Alpha Loops

At either end of Taxiway A, passing places (V and W loops) have been provided to allow
aircraft to hold and/or pass aircraft holding on the Taxiway Alpha. Aircraft may pass other
aircraft at these locations only when both aircraft concerned have a wingspan of less than
36m.
2.5 Non-Direct Taxi Instructions to Stand

Where a clear route and taxi instruction cannot be issued to take an aircraft to its stand, the
phrase “expect stand” should be used to inform the aircraft of their parking position.
Example: “ABC123 taxi to holding point A12, expect stand 8”
22
Chapter 3 Edinburgh AIR

Air Control (AIR) (“Edinburgh Tower”) is responsible for the safe and expeditious use of the
active runway and exit taxiways. AIR is also responsible for giving information to aircraft on
an instrument approach and VFR remaining in the visual circuit and operating within the
vicinity of the ATZ with visual reference to the surface. AIR is also responsible for transferring
departures to the relevant radar unit and obtaining releases for non-standard operations or
when otherwise required.
3.1.1 Delegated Responsibilities

AIR is responsible for traffic operating under VFR within and in the vicinity of the ATZ. Traffic
in the vicinity of the ATZ should be coordinated with FINFIN should also be informed of the
presence of aircraft within the visual circuit.
3.2 Runway Change Procedures

In case of a change to the active runway, AIR shall initiate coordination with INT to agree a
last arrival and time for the runway change. INT will coordinate with FIN.
Based on this time, AIR should then coordinate with GMC and GMP as to the last departure.
GMP will reclear any previously cleared aircraft that will now depart on the new runway.
AIR must then inform FIN of the intended last 3 (if appropriate) departures before, and the
first departure after, the runway change (callsign and routing).
AIR must obtain a release from FIN before the first aircraft departs off the new runway.
3.3 Line Up Procedures

3.3.1 RTF Phraseology
All instructions to enter a runway shall include:
1. The relevant runway designator
2. The holding point designator at which the aircraft is to enter the runway, including
from full length.
Example: “ABC123, via A1 line up runway 23”
3.3.2 Multiple Aircraft on the Runway

The AIR controller needs to be aware of the potential effects of jet blast when lining up
multiple aircraft on the runway. It is generally acceptable to line up two aircraft provided
there is a gap of at least one holding point between them. For example:
▪ Runway 06 – A1 and B1
▪ Runway 24 – C1 and D1
23
3.4 Conditional Clearances

3.4.1 Runway Safeguarding Phraseology
The word “follow” must not be used in conditionals in the runway holding area. Aircraft
should not be instructed to “follow” another one to prevent two aircraft lining up with only
one of them having clearance to do so.
Aircraft should not be told their number in the intended departure sequence. Instead, AIR
may issue approximate airborne times as either a time past the hour, or an approximate wait
in minutes.
3.4.2 Intersection Conditionals

Aircraft at an intersection may only be issued a conditional line up or crossing instruction
behind the next departing aircraft. i.e. The aircraft should be able to perform the intended
action behind the next aircraft that passes them.
3.5 Stopping a Departure

Where possible, departures who are rolling at or over 80 knots ground speed should not be
instructed to cancel their take-off roll, in accordance with CAP 493 MATS Part 1. At
Edinburgh, 300m is approximately abeam holding point A16 for Runway 24, and A8 for
Runway 06.
3.6 Wake Separation

3.6.1 Wake Turbulence Separation
Wake turbulence separation should be provided in accordance with MATS Part 1.
3.6.2 Holding Points

All holding points are considered to be different points for the purpose of providing wake
turbulence separation.
3.7 VFR Departures

VFR aircraft will contact GMC to request start and taxi. GMC will pre-note AIR for all VFR
departures. If a VFR departure is requesting a standard routing via a prescribed exit lane (see
ELL 2.2), GMC will request clearance from AIR which shall be relayed to the pilot. Else, AIR
shall coordinate with APC and issue clearance at the holding point.
24
3.8 Transfer of Control

3.8.1 Departures
Departures may only be transferred to the appropriate frequency once all aerodrome
conflictions have been resolved. Ideally transfer shall occur no later than 2000ft or 2.5NM
from the end of the runway, though if required to retain traffic to resolve a confliction, the
AIR controller shall look out for pilots climbing above their initial (cleared) level and take
action.
If the departure time separation applied does not achieve the expected airborne separation,
then the AIR controller should co-ordinate with the INT controller to provide headings to
establish separation. This action is to be retrospectively co-ordinated with the appropriate
TC controller.
3.8.2 Handoff Priority

Departure 1 2 3 4 5 6 7
GOSAM STW ST SD SWD SS S INT
TLA STE ST SD SWD SS S INT
GRICE SS SE S INT - - -
▪ INT – Edinburgh Intermediate Director

▪ STW – (TMA) Galloway
▪ STE – (TMA) Talla
▪ ST – Scottish TMA
▪ SD – Deancross
▪ SWD – West-Deancross
▪ SS – Scottish South
▪ SE – Scottish East
▪ S – Scottish Bandbox
INT Top-Down Order: STE – ST – SD – SWD – SS – SCO
Edinburgh APC may elect to work certain departures. If this is the case, they will coordinate
with AIR which departures should be transferred to APC, the frequency, and when this
arrangement shall cease.
3.9 Aircraft on Approach

The transfer of communications of an aircraft from Edinburgh INT/FIN to AIR should occur no
later than 4NM from touchdown which is prior to the transfer of control.
APC will retain control of all aircraft on approach until 4NM from touchdown. It remains the
responsibility of FIN to monitor the wake turbulence separation and radar separation up to
this point. Any instruction which AIR wishes to issue outside of 4NM must be co-ordinated
with FIN before it is given.
25
3.10 Training Flights

Requests for IFR training must only be accepted if the training flight may be handled without
affecting or causing delays to normal flights and at the discretion of the Edinburgh radar
controllers.
▪ When an IFR training flight is requested by the pilot, their clearance should be
obtained by the GMP/GMC controller from PH INT.
▪ Clearance will include initial altitude, departure instructions and SSR.
▪ All training flights are subject to the radar release from the INT controller, radar
release should be obtained by AIR controller before departure.
3.11 Landing Clearance

3.11.1 Runway Designator
The runway designator should be included in all landing clearances.
Example: “ABC123, runway 24, cleared to land, surface wind 040 degrees 10 knots”
3.11.2 Cancelling Approach Clearance

It is the responsibility of the AIR controller to issue landing clearances to all aircraft. If they
are not satisfied that an approach can continue safely, they may issue instructions to re-
position a particular aircraft or instruct the aircraft to “go around”.
3.12 Arrival Spacing

All arrival wake turbulence separation is as per MATS Part 1.
In routine operations FIN should ideally seek to achieve spacing of at least 6NM to allow 1
departure or at least 8NM to allow 2 departures. However, this is subject to coordination
between FIN and AIR, dependent on the traffic situation.
3.13 Missed Approaches

The standard missed approach procedures are as published on approach charts, and the
table below.
Runway Missed Approach Procedure
06 Continuous climb straight ahead to 3000ft then as directed.
24 Continuous climb straight ahead to 3000ft then as directed.
26
3.13.1 Go Around Procedure

On becoming aware of, or after initiating a ‘go around’, the AIR controller is to:
1. Establish separation between the ‘go-around’ and all departing traffic, issuing
tactical headings ONLY if necessary;
2. Ensure separation is maintained and monitor aircraft visually. Co-ordination must
be effected with FIN in order to establish separation through use of headings if you
are not visual. After separation is assured, co-ordinate with FIN and the appropriate
TC Outbound Sector.
3. Pass details of the callsign, heading and all action taken above to FIN. FIN will issue a
frequency for the aircraft to contact and any revised heading and/or altitude.
4. After coordinating with FIN, resume departures once the departure track is clear. A
departure release should be obtained from FIN for the first departure after a missed
approach.
27
Edinburgh vMATS Part 2 – Revision 2020/13 APC
APC | Approach Control

Chapter 1 General
Edinburgh Radar is responsible for the Edinburgh CTR and the airspace contained within the
Edinburgh Local Area, as defined in APC 4.1.
Edinburgh Radar shall provide approach control services to aircraft from the time and place
at which:
▪ Arriving aircraft are released by Scottish TMA until control is transferred to ADC;
▪ Aircraft approaching from outside controlled airspace place themselves under the
control of Approach Control until control is transferred to ADC;
▪ Overflying aircraft within the relevant controlled airspace.
1.2 Function
Edinburgh APC shall provide services appropriate for the Approach and Approach Radar
control functions, as specified in CAP493 (MATS Part 1).
1.2.1 Intermediate Director (INT)

▪ Provide an approach radar service to aircraft within 40NM of the ATZ below FL195
▪ The acceptance of releases and control of aircraft released by TC until control is
released to PH FIN or ADC.
▪ The control of overflying aircraft within the Edinburgh CTR including transits within
Edinburgh CAS.
▪ Coordination with ADC (AIR) for all except range checks, final approach spacing, low
approach/landing clearances and missed approaches.
▪ Coordination with other relevant ATSUs.
▪ Provision of UK FIS (subject to workload) to aircraft operating within the AOR.
▪ Issuing clearances to VFR/SVFR traffic entering the CTR and VFR entering the CTA.
1.2.2 Final Director (FIN)

FIN shall only be opened with the prior approval of the INT controller.
▪ Radar vectoring and sequencing of traffic received from PH INT for ILS and visual
approaches.
▪ Provision of a Radar Service to non-airways departures.
▪ Coordination of missed approaches and control such traffic unless specified by PH
INT.
▪ Coordination with ADC with respect to range checks, final approach spacing and low
approach/landing clearances.
28
Chapter 2 Procedures for Radar Directors

2.1 Introduction
INT will control inbound traffic from the two holding stacks – TARTN and STIRA – and
coordinate with adjacent units for inbound releases.
FIN will control inbound traffic from after transfer of control from INT.
All Directors will coordinate with adjacent sectors or other agencies as required and manage
their own flight progress strip display.
2.2 Terrain Clearance

The Minimum Sector Altitude (MSA) within 25NM of the airfield is:
Cardinal Direction MSA Cardinal Direction MSA
North East 3000 feet South West 3900 feet
South East 3900 feet North West 3400 feet
2.3 Radar Separation Minima

Standard radar separation may be reduced to 3NM between identified / coordinated aircraft
with both PSR & SSR functioning; otherwise 5NM must be used.
2.4 SSR Code Allocations

2.4.1 Edinburgh
When identifying an aircraft for the purpose of providing a radar service or for the benefit of
adjacent units, aircraft shall be given a local squawk code between the ranges of 0430-0437.
Listening Squawk
Aircraft within 10NM of the Edinburgh CTR or operating underneath the Edinburgh CTA may
select the code 0440. This indicates that the aircraft is maintaining a listening watch on
Edinburgh Radar’s frequency (121.200 MHz), however the Mode A and C readout displayed
must be considered unvalidated and unverified, respectively.
2.4.2 Glasgow
Aircraft operating in the vicinity of Glasgow being worked by Glasgow Radar may display a
Glasgow local squawk code between the ranges of 2601-2617. Squawk 2620 is used to show
that an aircraft displaying this code is maintaining a listening watch on Glasgow Radar
(119.100 MHz).
2.4.3 Leuchars
Aircraft operating in the vicinity of Leuchars being worked by Leuchars ATC may display a
Leuchars squawk code between the ranges of 7403-7427. The conspicuity squawk for
Leuchars is 7402, which is to be considered unvalidated.
29
2.4.4 Dundee
The conspicuity squawk for Dundee is 7374 (IFR Procedural Approach) or 7376 (VFR
Conspicuity). The Mode A and C readout displayed must be considered unvalidated and
unverified, respectively.
2.4.5 Scottish Information

Aircraft in receipt of a Basic Service from Scottish Information (119.875 MHz) shall be
assigned the squawk 7401. the Mode A and C readout displayed must be considered
unvalidated and unverified, respectively.
2.5 Liaison with Aerodrome Control

APC shall supply the following information to Aerodrome Control:
▪ The type of approach for IFR aircraft if anything other than ILS, with a range check
provided by 10NM;
▪ The anticipated delay to departing IFR flights together with the reason for the delay;
▪ Information on VFR or SVFR aircraft intending to land or transit the Edinburgh ATZ;
▪ Missed approach instructions when required;
▪ Departure releases together with after departure instructions when required.
2.5.1 Transfer of Arriving Aircraft

▪ IFR aircraft shall be transferred to ADC in the intended landing order;
▪ VFR aircraft shall be transferred to ADC when visual with the airfield or at the CTR
boundary as coordinated. Transfer of control/communications may only occur once
co-ordinated with ADC;
▪ SVFR aircraft shall be transferred when visual with the airfield and any preceding
aircraft and only once co-ordinated with ADC.
2.5.2 Tower Check

Aerodrome Control is equipped with an ATM displaying both primary and secondary radar
and therefore it is only necessary to give a 10NM check to the ADC controller in respect of an
inbound aircraft for the following:
▪ Non-transponding aircraft;
▪ Aircraft whose Squawk is not Code/Callsign converted;
▪ Training traffic which does not intend to land;
▪ Aircraft carrying out anything other than an ILS approach (type of approach must be
given).
30
Chapter 3 Inbound Procedures

3.1 Information to Arriving Aircraft
After an arriving aircraft has made its initial call to Approach Control, the following
information shall be passed as soon as practicable:
▪ Runway in Use and the type of approach, if not already received from the ATIS;
▪ Current ATIS weather code, if not reported correctly;
▪ Any changes in the operational status of visual or non-visual aids essential for
approach and landing;
▪ LVP in operation, if not already received from the ATIS;
▪ Any delay to be expected.
APC shall also confirm the aircraft type, including type variants, plus cleared level of all
aircraft placed under its control.
Subsequent Changes
Aircraft that have received the information above must be kept informed of the following
until they have landed:
▪ Significant changes in the meteorological and runway conditions;
▪ Further reports from other pilots;
▪ Further changes in the operational status of approach and landing aids;
▪ Implementation or cancellation of LVPs.
3.2 Non-public transport minima

The minimum value of 800 metres RVR will be used at all airports as the absolute minimum
for visual approaches. If a pilot requests a visual approach when the visibility is less than 800
metres, controllers should inform the pilot that this type of approach is unavailable and
request the pilot’s intentions.
31
3.3 Inbound Routes

Aircraft leaving the airways system will be instructed to follow the appropriate STAR by
Scottish Control. All STARs terminate at either the TARTN or STIRA stack and aircraft must
not pass the stacks without ATC clearance.
STAR Designator Via Route Descent Planning
AGPED 1E Y96, N110 AGPED – HAVEN – TARTN FL260 by AGPED
FL70 by TARTN
GIRVA 1E P600 GIRVA – TLA – TARTN FL120 by GIRVA
FL70 by TARTN
INPIP 1E (U)N601 INPIP – INREV – ESKDO – FL260 by INPIP
TARTN FL200 by INREV
FL70 by TARTN
PTH 1G P600 PTH – GRICE – STIRA FL70 by STIRA
TUNSO 1E P600 TUNSO – TLA – TARTN FL170 by TUNSO
FL70 by TARTN
3.4 Holding Procedures

Stack Inbound Radial / Minimum Maximum Holding Speed
Direction Holding Level Holding Level Limit
TARTN 015° / Left Hand MSL FL140 230 knots
STIRA 234° / Right Hand 5000 feet FL140 230 knots
EDN 241° / Left Hand 3000 feet 6000 feet 210 knots
294° / Right Hand FL70 -
UW 061° / Right Hand 4000 feet FL140 210 knots
TLA 331° / Left Hand MSL FL140 -
Note 1: MSL is to be determined by the Glasgow QNH.

Note 2: Care should be taken when holding aircraft at or below 6,000ft at STIRA as
this is Class E airspace.
Note 3: The STIRA hold can be used for both Glasgow and Edinburgh arrivals.
32
3.5 Expected Approach Times

Expected Approach Times are to be issued at 5-minute intervals for radar vectored
approaches if the delay is more than 20 minutes.
EATs are not normally passed if the expected delay is less than 20 minutes, instead, the usual
phrases used are “Less than 5 minutes”, “5 to 10 minutes”, “10 to 15 minutes” and “15 to
20 minutes”.
3.6 Inbound Release Procedures

The table below summarises the agreed levels for inbounds transferred from Scottish to
Edinburgh APC. The subsequent sections add further specific conditions.
Via From Agreement
TARTN Talla MSL
STIRA ScAC South MSL lvl STIRA
N864 ScAC South Individually coordinated
During low traffic levels, direct routings may be individually coordinated.

Transfer of control is coincident with transfer of communications unless otherwise stated, as
long as each aircraft is handled in the manner set out in 3.8 below and APC 4.4.
Reduced radar handover format: “Callsign, descending to level, heading, (speed)”.
3.6.1 Arrivals via TARTN

Talla will transfer inbounds via TARTN by silent handover descending to the MSL. Talla shall
endeavour to stream successive inbounds and shall not descend a subsequent inbound to
the MSL until the preceding aircraft has vacated the level. In case this is not possible,
transfer is possible by electronic abbreviated release at ‘stacked’ levels.
3.6.2 Arrivals via STIRA

Arrivals via STIRA may be transferred by silent handover. Due to the shared nature of the
STIRA arrival route with traffic inbound to Glasgow, a reduced radar handover may be
required.
3.6.3 Arrivals via the N864

Inbounds are subject to coordination. PH INT will suggest a routing – likely direct/on a
heading toward the EDN for Runway 24, and as required for Runway 06 – and ScAC South
shall offer a level. ScAC South shall notify Galloway of all inbounds via the N864.
Traffic shall be transferred to PH INT by means of a reduced radar handover no later than
30NM from Edinburgh. Should Edinburgh be unable to descend the inbound to the MSL or
below by the ScAC South and Galloway boundary, they shall notify Galloway and agree a
descent profile.
33
3.6.4 Arrivals from the FIR

FIR arrivals (mainly from the east of the TMA) can normally expect a joining clearance on
track EDN for Runway 24. The routing shall be coordinated when on Runway 06. ScAC South
shall give Edinburgh APC at least 10 minutes notice and transfer traffic as agreed by reduced
radar handover, no later than 30NM from Edinburgh.
3.7 Transfer of Communication Procedures

Transfer of communication should be effected in the correct order of aircraft for each
holding stack.
Aircraft will be transferred to Edinburgh APC in sufficient time for contact to be established
before reaching the facility so that heading or holding instructions may be passed. If this is
not possible the aircraft will be instructed to hold on reaching the facility and APC so
informed.
INT is to ensure that the pilots of inbound aircraft are in receipt of the current ATIS/METAR
report and are to verify the aircraft type.
Any aircraft type which is not as filed must be changed as soon as possible and advised to
any controller who may be reliant on up to date information, say for the provision of wake
vortex separation.
3.8 Descent before Release Point

Edinburgh APC may descend aircraft to the Minimum Stack Level on transfer of
communications, subject to the base of CAS.
34
Chapter 4 Intermediate and Final Approach Procedures

4.1 Local Area
4.1.1 Airspace
Edinburgh APC are responsible for the Edinburgh CTR/CTA and the airspace delegated to
them by ScTMA below 6000 feet – the ‘Edinburgh Local Area’.
Figure 1 – Scottish TMA Airfield Local Areas and 3NM Buffer Zone
35
4.2 Continuous Descent Approaches

The aim of a continuous descent approach is to enable aircraft to make a continuous descent
from above transition altitude to the establishing point on the localiser with the minimum
use of flaps or other high-lift, high-drag devices. The use of a continuous descent, where
level-offs do not occur reduces fuel consumption and noise levels.
ATC Actions
INT will give a descent from above transition altitude at the point at which he/she believes
the aircraft will be able to maintain a continuous 3° glide path during descent. The controller
will pass the estimated track mileage to touchdown, allowing the pilot will then select a
vertical speed which he/she judges will give a continuous descent.
4.2.1 Range from Touchdown

The range from touchdown information should be passed:
▪ When issuing the first clearance to descend to an altitude;
▪ Upon first contact with the Final Director;
▪ If it is judged to help the pilot with their descent planning;
▪ When a previous estimate becomes invalid or inaccurate.
4.3 Speed Control

Speed control may be applied on a tactical basis to the extent determined by the Radar
Controller. For aircraft which are unable to maintain 160 knots, FIN will ascertain the final
approach speed and inform AIR.
4.4 Procedures for Aircraft on Intermediate Approach

4.4.1 Phraseology Requirement
Under normal conditions, PH INT handles the initial vectoring for Edinburgh, Dundee and
Leuchars. PH INT shall confirm the type of approach and runway and airport the aircraft will
be landing at on first contact. If the ATIS code is not reported by the pilot, the pilot should be
informed of the active ATIS letter. The aircraft type should also be confirmed if not given by
the pilot on first contact. On a full release from Scottish TMA, PH INT must confirm the
above information.
Example: “ABC123, vectoring for an ILS approach, runway 24. (You are number # in
traffic)”
4.4.2 Vectoring of Inbounds

All inbounds are released for turns in the same general direction whilst within the airspace of
the transferring unit, until entering the Edinburgh Local Area.
Edinburgh shall duly consider the track of Runway 06 jet departures when vectoring
inbounds from the N864.
36
4.4.2.1 Arrivals via TARTN

Vectoring for Runway 06
Traffic shall be vectored to remain west of the holding pattern/direct route to TARTN. It
must also cross the 180°M track from the UW at or below 6000 feet to remain separated
from the LANAK hold.
Vectoring for Runway 24
Traffic shall be vectored to remain east of the holding pattern/direct route to TARTN, except
when direct routings have been individually coordinated.
4.4.3 Descent of Inbounds

If Edinburgh descend arriving aircraft below MSL, it is then their responsibility to ensure
separation against departures.
4.4.4 Transfer of aircraft from INT to FIN

In a normal traffic situation, aircraft should be transferred to FIN as follows:
▪ Descending to altitude 4000ft
▪ On a base leg (for 06) or a short downwind (for 24).
In all cases, INT shall hand aircraft to FIN with separation ensured against all other known
traffic. Transfer of communication should take place as soon as possible (subject to these
conditions) once the aircraft in question has begun the descent as instructed by INT. Should
the above conditions not be possible, an alternative should be coordinated to ensure the
handover can take place to allow FIN adequate time to integrate the traffic into the final
approach sequence.
4.5 Procedures for Aircraft on Final Approach

4.5.1 Final Approach Spacing
The minimum spacing of aircraft on final approach shall be 4NM. Larger gaps are required to
allow for departures. The following should be used as a guide:
▪ 6NM – 1 departure
▪ At least 8NM – 2 departures
Normal operations will therefore require gaps of 6NM between successive inbounds.
Regular coordination with AIR is required to increase or decrease separation on final
approach is required to maximise efficiency. A minimum of 15NM gap must be used ahead
of and behind a known emergency aircraft.
During LVPs a decreased landing rate will be used.
The final approach spacing between aircraft shall never be less than the prescribed wake
turbulence separation requirements. The pilot reporting that they can accept less than the
required minima is not an acceptable reason to reduce below these spacing requirements.
37
Edinburgh Director (FIN) is responsible for providing the required wake turbulence
separation until 2NM from touch-down in accordance with MATS Part 1 Section 1 Chapter 3.
4.5.2 Non-Precision Approaches

Aircraft flying a non-precision approach will be vectored as usual then depending on the
approach type will be cleared for the procedure as per the relevant chart. QNH should be
restated to the pilot even if previously provided when descending to an altitude.
Example: “EZY113, cleared NDB/DME Approach runway 24, QNH XXXX”
A 10NM range check must be given to AIR. Once on final approach the aircraft will be
transferred to AIR.
4.5.3 Visual Approaches for IFR Traffic

Unless prior coordination has taken place with AIR, INT or FIN may clear aircraft for a visual
approach when the pilot reports visual with the airfield. Where coordination with AIR has
taken place, provided the aircraft has reported visual with the airfield and the position of
traffic permitting, aircraft may be cleared for a visual approach subject to the following
limitations:
▪ Propeller driven aircraft whose MTWA does not exceed 5700kg will not join the final
approach below 1000ft AGL
▪ All visual approaches from the south to Runway 24 by aircraft with an MTWA in
excess of 5700kg are to be made from a position not less than 7NM DME on the
extended centreline. Aircraft are not to descend below 2000ft QNH until after
crossing the Firth of Forth coastline northbound.
▪ All visual approaches from the north to Runway 24 by aircraft with an MTWA in
excess of 5700kg are to be made from a position not less than 4NM DME on the
extended centreline.
▪ Aircraft approaching runway 06 are to join the extended runway centreline not
below 1500ft AGL.
Between the hours of 2230 and 0630 local, when the ILS is serviceable (or localiser and
DME), visual approaches by inbound IFR flights are not to be approved. Aircraft in an
emergency are exempt from this restriction
When clearing an aircraft for a visual approach, if necessary, the pilot may be given a level
restriction to keep the aircraft within CAS. Recommended wake turbulence spacing shall be
passed if the pilot is visually positioning behind another aircraft and wake turbulence spacing
is required.
38
4.6 Missed Approach Procedures

The Standard Missed Approach procedures are published in the UK AIP and detailed below.
Runway Missed Approach Procedure
06 Continuous climb straight ahead to 3000’ then as directed
24 Continuous climb straight ahead to 3000’ then as directed
4.6.1 ATC Actions

▪ AIR will alert APC of the missed approach.
▪ AIR will hold departures and may issue tactical headings using the ATM if required to
ensure the separation of aircraft.
▪ APC may relay a heading and level to give to the AIR controller and a frequency for
the aircraft to contact.
39
Chapter 5 Outbound Procedures

5.1 General
The separation between departing aircraft is the responsibility of Edinburgh ADC and is
normally achieved by the application of timed intervals between successive departures, as
derived from the Departure Speed Group Table (see SEP 1.2).
5.2 Departures Subject to Radar Approval

The Edinburgh AIR controller must obtain departure release from Edinburgh APC before
clearing aircraft in any of the following categories for take-off:
▪ the next IFR departure following an IFR missed approach, touch-and-go or low
approach;
▪ non-airways departures;
▪ VFR/SVFR departures;
▪ when required by Edinburgh APC;
▪ whenever the AIR controller intends to depart successive aircraft which would be
separated by less than the specified time interval;
▪ aircraft types not included in the Speed Groups Table;
▪ whenever the AIR controller requires an aircraft to deviate from the NPR;
▪ aircraft departing immediately prior to and following a change of runway direction.
Edinburgh AIR will normally clear all other departures for take-off without prior reference to
APC. Such departures will be transferred direct to the appropriate Scottish sector, unless
otherwise instructed by APC.
The AIR controller will inform Edinburgh APC if an aircraft is observed to deviate from the
SID to the extent that departure separation may be eroded.
5.3 APC Responsibilities

Edinburgh APC is responsible for monitoring Edinburgh departures and providing radar
and/or vertical separation between:
▪ departures on the same or conflicting routes, when requested by Edinburgh ADC;
▪ inbounds in the EDN, UW, STIRA or TARTN holding patterns that have been
descended below the MSL against departures;
▪ all other inbounds against departures.
5.4 Verification of Mode C

The first radar controller to be in contact with the aircraft is responsible for verifying the
Mode C readout, in accordance with the procedures detailed in MATS Part 1, Chapter 5 -
therefore aircraft must also be instructed to report their passing altitude (if omitted from the
first call) to verify the Mode C readout (readout has to be +/- 200 feet from the reported
altitude).
40
5.5 Non-Airways Departures

Edinburgh APC is responsible for providing a radar service to non-airways departures until
they are clear of controlled airspace and no longer wish to receive a service.
Edinburgh APC is responsible for the issuing of departure clearances for all departures which
are not filed to fly a Standard Instrument Departure. The clearances given by APC must not
modify any instructions given by London AC or Scottish TC and must consider NPRs and
terrain clearance where applicable.
GMC will request clearance from APC for any non-standard IFR, VFR or SVFR departure. It is
GMC’s responsibility to pass the instructions to the pilot and obtain a suitable readback. The
AIR controller will request release from APC when the departure is ready to depart and will
also request release for any subsequent SID departure.
5.6 Standard Instrument Departures (SIDs)

5.6.1 Allocation of GOSAM SID
The GOSAM SID is for jet aircraft only.
5.6.2 Allocation of Talla (TLA) SID

The TLA SID is available to non-jet aircraft at all times.
It is only available to jet aircraft if:
▪ They are routing via the Y96 or leaving controlled airspace via TLA
▪ They are routing via the N57/L612/N864 between 2300-0600 local (See Note)
Note: Given the fact that traffic levels on VATSIM differ from real life, Scottish may
elect to make the TLA SID unavailable for jet departures between 2300-0600. This
shall be coordinated with Edinburgh AIR.
5.7 Transfer of Departures

All outbounds will be transferred on the SID directly to the appropriate Scottish sector in
accordance with the table in ADC 3.8.1.
If Edinburgh APC requires to work departures, they shall coordinate with Edinburgh AIR
which departures they wish to work, the frequency for transfer, and when this arrangement
shall cease.
5.7.1 Silent Handover

If Edinburgh APC elect to work a departure, it may be transferred by silent handover to
Scottish provided it is climbing to the SID altitude, following the agreed route, and separated
from all local area traffic.
Transfer of communications (coincident with transfer of control) must take place before the
local area boundary.
41
5.8 Vectoring of Departures

By Edinburgh APC
Edinburgh is responsible for monitoring departures and ensuring separation against inbound
traffic. In particular, they shall be responsible for conflict detection and resolution between
GOSAM SID departures and GRICE departures/STIRA inbounds, coordinating with Galloway
and/or ScAC South as appropriate.
Departures may be vectored by Edinburgh APC within the local area to achieve separation
without coordination with area control. This traffic must be resumed own navigation on the
SID track by the local area boundary, else coordinated. Edinburgh shall take due care not to
erode the separation provided by the departure interval applied by AIR.
By Scottish
GOSAM departures from Runway 24 are released for right turn provided the aircraft has
passed either 3000 feet or the UW, whichever is sooner. Galloway shall not turn traffic
further right than a track of 290 degrees without coordination with Edinburgh.
All other vectoring or deviation from the SID below MSL is not permitted without
coordination with Edinburgh APC.
5.9 Climb above SID Levels

Edinburgh APC is not to climb outbound aircraft above the SID altitude without prior
coordination with the appropriate Scottish departure sector.
42
Edinburgh vMATS Part 2 – Revision 2020/13 ELL
ELL | Edinburgh Low Level Procedures

Chapter 1 Airspace
1.1 Classification
The Edinburgh Control Zone (CTR) is classified as Class D airspace from the surface up to
6000 feet. Aircraft are permitted to operate in VMC and IMC conditions under either VFR or
SVFR as appropriate.
1.2 Provision of Air Traffic Services

Responsibility for low level traffic within the Edinburgh CTR is with Edinburgh INT.
1.2.1 UK Flight Information Services (FIS)

Edinburgh APC can provide a UK Flight Information Service to aircraft outside of controlled
airspace within 40NM of Edinburgh subject to suitable PSR, SSR and VHF coverage.
Provision of a UK FIS service is optional, and the controller may decline, for example in a
period of high workload.
1.3 Visual Reference Points (VRPs)

The following VRPs are for use by aircraft operating to and from Edinburgh.
VRP VOR/VOR VOR/NDB VOR/DME Fix
Arthur's Seat Talla RDL 016° Talla RDL 016° St Abbs 276°/32 NM
555638N 0030942W Edinburgh EDN
118° MAG
Bathgate Talla RDL 340° Talla RDL 340° Glasgow 088°/27 NM
555410N 0033825W Glasgow RDL Edinburgh EDN
088° 251° MAG
Cobbinshaw Reservoir Talla RDL 341° Talla RDL 341° Talla 341°/19 NM
554828N 0033400W Glasgow RDL Edinburgh EDN
099° 225° MAG
Dalkeith St Abbs RDL Talla RDL 024° Talla 024°/26 NM
555336N 0030406W 270° Edinburgh EDN
127° MAG
Forth Rd Bridge, Nth Talla RDL 359° Perth PTH RDL St Abbs 281°/41 NM
Twr 184°
295° MAG
Hillend Ski Slope St Abbs RDL St Abbs RDL 270° Talla 014°/24 NM
156° MAG
43
Hermiston (M8, J1) Talla RDL 005° Talla RDL 005° Talla RDL 005°/25.6
555530N 0031843W Glasgow RDL Edinburgh EDN NM
087° 197° MAG
Kelty St Abbs RDL St Abbs RDL 291° Glasgow 068°/39 NM
342° MAG
Kirkcaldy Harbour St Abbs RDL St Abbs RDL 293° Glasgow 073°/46 NM
031° MAG
Kirkliston Talla RDL 359° Glasgow RDL 083° Glasgow 083°/36 NM
253° MAG
Kirknewton Talla RDL 357° Glasgow RDL 090° Glasgow 090°/35 NM
221° MAG
Longannet Power Talla RDL 344° Talla RDL 344° Talla RDL 344°/34.9
Station Glasgow RDL Edinburgh EDN NM
560256N 0034057W 069° 290° MAG
Musselburgh St Abbs RDL Talla RDL 023° Talla 023°/29 NM
Racecourse 277° Edinburgh EDN
555650N 0030225W 105° MAG
Penicuik Talla RDL 014° Glasgow RDL 095° Glasgow 095°/41 NM
169° MAG
Philpstoun (M9, J2) Talla RDL 352° Glasgow RDL 080° Glasgow 080°/32 NM
273° MAG
Polmont St Abbs RDL Talla RDL 341° Glasgow 076°/27 NM
275° MAG
West Linton Talla RDL 002° St Abbs RDL 259° Talla 002°/15.2 NM
554510N 0032127W St Abbs RDL Edinburgh EDN
259° 192° MAG
44
Chapter 2 VFR Operations

Aircraft shall normally enter and exit the Edinburgh CTR “not above altitude 2000ft” on the
Edinburgh QNH via either general “compass-point” directions or a published VRP. However,
to permit VFR flight in IMC conditions, an entry/exit lane system has been established (see
ELL 2.2 Entry/Exit Lanes).
Note: Due to terrain, routing via Penicuik or West Linton VRPs will normally be not
above altitude 3000ft.
Details of inbound VFR traffic should be passed to AIR and transfer of control and
communication shall take place when the pilot reports visual with the airfield.
SVFR inbounds will be retained by APC until such time as APC can safely integrate the
aircraft into the inbound stream, maintain standard separation, and when the aircraft has
become number one to land; in order to ensure that it cannot execute any manoeuvre
which will erode the separation against the aircraft ahead.
2.1 Penetration of ATZ

VFR fixed-wing aircraft may only penetrate the ATZ with the prior approval of Edinburgh AIR.
Edinburgh APC will coordinate a course of action with Edinburgh AIR that will facilitate the
safe passing of the aircraft through the ATZ. Any crossing overhead the airfield should be
made at the landing threshold of the runway in use.
2.2 Entry/Exit Lanes

To permit aircraft to operate to and from Edinburgh in IMC but not under, VFR entry/exit
lanes have been established for use under specific conditions:
▪ Polmont Lane: A lane 3NM wide with its centreline on the M9 Motorway from
abeam Grangemouth eastwards, via the Polmont Roundabout, Linlithgow Loch and
Philpstoun to a point where joins the Edinburgh ATZ.
▪ Kelty Lane: A lane 3NM wide with centre-line on the M90 Motorway Kelty
southwards to the M90 Junction 1B, then with centre-line on the A9000 across the
Forth Road Bridge to M90 Junction 1, then with centre-line on the M90 Motorway to
a point where joins the Edinburgh ATZ.
Use of the above lanes are subject to clearance from Edinburgh ATC irrespective of weather
conditions. Clearance must be obtained before entering the lane
Aircraft using these lanes must remain clear of cloud and in sight of the ground or water, not
above 2000ft on the Edinburgh QNH and with visibility of not less than 3km.
Aircraft using the lanes shall keep the centreline on its left unless otherwise instructed by
ATC. Where instructions differ, traffic information will be provided to aircraft concerned.
Pilots remain responsible for ground clearance at all time.
45
2.3 Helicopter Operations

2.3.1 Overflight Procedures
Helicopters wishing to operate in the Edinburgh CTR/CTA will be cleared on direct routings
under VFR (or, when requested at night in the Edinburgh Control Zone, on Special VFR
clearance in accordance with the procedures for Special VFR flights).
VFR helicopters may be only routed overhead with the prior approval of the AIR controller.
Once this approval from the AIR controller has been received, the pilots of helicopters will
receive a required VFR clearance across the airfield with an Edinburgh Squawk.
Note: There is no specific helicopter VRPs, so helicopters obtain entry through a
published VRP then are simply asked to report to the field.
Before the helicopter reaches the ATZ; PH INT is to coordinate the flight with the AIR
controller and confirm; direction of flight, contact frequency after crossing, current squawk.
PH INT remains responsible to pass necessary information for aircraft making IFR approaches
until such crossing traffic is transferred over to ADC.
The Edinburgh AIR controller will retain control of the transiting aircraft until clear of any
conflicts, once the controller is happy that there are no conflicts that may present, the AIR
controller can then transfer the aircraft back to PH INT for leaving clearance via a defined
boundary.
2.3.2 Inbounds and Outbounds

2.3.2.1 Manoeuvring
While helicopters are operating on the manoeuvring area extreme caution must be
exercised regarding wingtip/rotor blade clearance and turbulence.
2.3.2.2 Use of Runways

All helicopters must use the runways for takeoffs and landings. Helicopters may not carry out
direct approaches to or take-off from apron areas or taxiways.
Standard wake turbulence separation requirements must be applied between a helicopter
movement and the traffic which precedes it.
Helicopters landing on Runway 06/24 should normally be instructed to vacate at C1. When
using Runway 06 for arrival, helicopters should be instructed to "land long" to vacate at C1.
2.3.2.2.1 After Landing

After landing, helicopters will ground taxi or air taxi to an allocated parking area (usually an
adjacent stand).
2.3.2.3 Outbound Procedures

Standard MATS Part 1 wake turbulence separation procedures must be applied between a
helicopter movement and the traffic which precedes it. All helicopter traffic must depart
from the active runway. Taxi requirements will be advised by Edinburgh Ground and
departures may be made from an intersection – although care should be taken when taxiing
46
departures via C when Runway 06 is in use due to the potential for conflict with an arriving
aircraft.
2.4 SVFR Procedures

Only one SVFR aircraft is permitted in the visual circuit at a time. The approach controller
should provide a 20NM range check to AIR on the next IFR arriving aircraft. When the IFR
aircraft is approximately 20 track miles from the airport the SVFR aircraft must be instructed
to leave the circuit or land to maintain standard separation between IFR and SVFR aircraft.
SVFR aircraft transiting the zone must route overhead the airfield and remain clear of the
extended centreline. SVFR aircraft are not permitted to fly inside of the Edinburgh CTR if the
reported airport visibility is less than 3km and the cloud ceiling is less than 1000 feet. If the
SVFR aircraft is using one of the entry/exit lanes, then only one SVFR aircraft is permitted in
the lane at one time.
47
Edinburgh vMATS Part 2 – Revision 2020/13 EMG
EMG | Emergencies
1.1 Initial Actions
A - Acknowledge Understand and acknowledge the situation.
S – Separate Establish/maintain separation.
S – Silence Consider imposing RTF silence, runway sterilisation and holds.
I – Inform Inform adjacent ATC units.
S – Support Give maximum support to the crew. (Options, position etc.)
T – Time Allow pilots sufficient time to work on their problem.
1.2 GMC Specific
GMC is to inform aircraft if any delay to start/taxi is to be expected due to an emergency in
progress.
1.3 AIR Specific

The AIR controller is to determine the category of the emergency (MATS Part 1, Section 5,
Chapter 7). Based on the type of emergency, the AIR controller may decide to sterilise the
runway. Once initial actions have been completed, the AIR controller must inform the
appropriate controller(s) - GMC and/or APC details of the emergency (if they are not already
aware) and runway availability. ADC will inform APC of the estimated runway opening time
whenever possible.
When emergency traffic is returning to Edinburgh for landing on a runway not promulgated
as the runway in use, the AIR controller will stop all departures when the emergency aircraft
is 20NM from touchdown.
1.4 APC Specific

The following information concerning emergency aircraft inbound to Edinburgh is required
to be passed to PH AIR:
▪ runway to be used;
▪ aircraft type;
▪ nature of trouble;
▪ aircraft registration or flight number;
▪ persons on board (if known);
▪ ETA.
The transmission of available information to ADC is not to be delayed because any of the
above details are not initially available. As soon as further information becomes known it is
to be passed to ADC.
Edinburgh APC is to provide at least 15NM spacing behind known emergency traffic. INT is to
inform the relevant Scottish Control sectors of the emergency situation and the expected
delay. INT must also co-ordinate any diversions with the relevant area sector.
48

Edinburgh vMATS Part 2 2020 13

Uploaded by

Document Information

Original Description:

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

Edinburgh vMATS Part 2 2020 13

Uploaded by

Copyright:

Available Formats

Edinburgh vMATS Part 2 – Revision 2020/13

Effective 03 December 2020

Edinburgh vMATS Part 2

REVISION 2020/13 - Effective 03 December 2020

Distribution and Scope

Introduction and Structure

SEP | Local Separation Standards ........................................................................................................... 15

ADC | Aerodrome Control ...................................................................................................................... 17

APC | Approach Control ......................................................................................................................... 28

5.9 Climb above SID Levels .................................................................................................................. 42

ELL | Edinburgh Low Level Procedures .................................................................................................... 43

GEN | General Operating Instructions

1.2 Arriving/Transit Aircraft

1.3 QFE Threshold

1.4 Transition Altitude

1.5 Transition Levels and Minimum Stack Levels

1.6 Altimeter Setting Regions

Chapter 2 All Weather Operations

2.1.2 Safeguarding Procedures

2.1.3 Instrumented Runway Visual Range (IRVR)

2.1.4 CAT II/III Holding Points

2.1.5 Arrival Separation

2.1.6 Arriving Aircraft

2.2 Meteorological Information

Chapter 3 Description of Airfield

3.2 ATC Communication Facilities

3.2.1 8.33 KHz Frequencies

3.3 Radio Navigation and Landing Aids

Chapter 4 Use of Runways

4.2 Selection of Runway in Use

4.3 Minimum Runway Occupancy Time

4.4 Runway Vacation

4.5 Land After Procedures

Chapter 5 Use of ATM

SEP | Local Separation Standards

1.2 Speed Separation

1.3 Wake Turbulence Separation

1.4 Route Separation

Chapter 2 Arrival Separation

2.2 Deemed Separations

ADC | Aerodrome Control

1.2 Issuing Clearances

Example: “ABC123, cleared to Ibiza, GOSAM 1 Charlie departure, squawk 0356”

1.2.1 Standard Instrument Departures

GOSAM 1C 1D 6000 feet Jet aircraft only. Minimum climb

TLA 6C 6D 6000 feet Non-jet aircraft. (See ADC 1.6.2

GRICE 3C 4D 6000 feet Minimum climb 3.3% for

1.2.2 Flight Level Capping

1.3 Pre-Departure Clearance (PDC)

1.3.1 Availability of PDC

1.4 Runway Change Procedures

1.5 Stand Allocation

1.6 Departure Restrictions

1.6.1 Allocation of GOSAM SID

1.6.2 Allocation of Talla (TLA) SID

Chapter 2 Ground Movement Controller (GMC)

2.1.1 Departure Handoffs

2.2 Pushback Clearance

2.3 VFR Clearances

2.4 Taxiway Restrictions

2.4.2 Simultaneous Use of Lima and Mike Taxiways

2.4.3 Simultaneous Use of Lima and Golf Taxiways

2.4.4 Taxiway Alpha Loops