# LAI 1 - Vagar
## 1. Vagar Airport (EKVG)
Vagar Airport is a hybrid of many sorts. Before controlling at EKVG you must:
- Hold an S3+ rating or be S2 with an endorsement
- Complete the material on Procedural Airport
- Be confident with AFIS operation
- Read and understand the EKVG part of the ATC training handbook of Iceland, to have clear
understanding of Oceanic procedures
EKVG\_I\_TWR - 118.325
BIRD\_E1\_CTR - 126.750
| **Runways** | **Type of APP** | **Missed Approach** | **Type of Departure** | **Noise Abatement** |
| 12 | LOC, NDB, RNP-AR | Refer to active charts.
Many different ones, depending on active procedure
| SID (RNP-AR)
Or
Visual Departure
| NIL
|
| 30 | ILS, LOC, RNP-AR |
## 1.1 ATC clearance & Ground operation
| **Airspace limits** | **Airspace class** | **Climb clerance** | **ACC Sector** | **Descend clerance** |
| GND - FL75 (60 nm.) | G | 7000' | BIRD\_E\_CTR | 7000' |
Vagar airport is AFIS meaning you must use AFIS phraseology and clearance structure, However at EKVG controller may issue startup clearance, due to oceanic clearance being needed before startup can be commenced.
All ATC clearances must be obtained from Reykavik control, before start-up is issued. Issue should be obtained from BIRD\_E\_CTR, if online. If not, revert to BIRD\_CTR or BICC\_FSS
Airport is condenced and all departure and arrivals must backtrack the active runway, so keep concentrated and issue appropriate information.
For more information regarding Oceanic clerance: [Iclandic Wiki - Clerance](https://wiki.vatsim-scandinavia.org/books/operating-procedures-wjo/page/delivery)
## 1.2 Arrival Procedures
EKVG AFIS (EKVG\_I\_TWR) will provide Arrival Information including:
- Runway in use
- Local QNH
- Transision Level
- Turbulence expectation (See table below)
- Any other relevant information
EKVG\_I\_TWR is a TIZ zone which extends from GND-7500’. Refer to [AFIS Procedures](https://wiki.vatsim-scandinavia.org/books/quick-reference-be0/page/afis)
Aircrafts should be handed over from BIRD\_E\_CTR, if online. If not expect handover from BIRD\_CTR or BICC\_FSS. Aircrafts are cleared:
| **Runway 12** |
| **Direction** | **Point** | **Altitude** | **Procedure** |
| East | MY
| 7000' | Enter Base turn to descend 3700 to exec. LOC 12 |
| South |
| West | Enter holding to descend 3700 to exec. LOC 12 |
| North |
| **Runway 30** |
| **Direction** | **Point** | **Altitude** | **Procedure** |
| East | ROBUR | 7000' | Straight in ILS Z Runway 30 |
| South |
| West | VG | Full procedure ILS Z Runway 30 |
| North |
Note RNP-AR is covered in its own topic.
### 1.2.1 Turbulece chart
[](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-10/yL8image.png)
Live updated turbulence information can be found [here](https://vats.im/twi)
### 1.2.2 MSA
MSA is 4000' in 25 nm. radius
### 1.2.3 Approach procedures
[](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/QS7image.png)
[](https://wiki.vatsim-scandinavia.org/uploads/images/gallery/2023-12/Psmimage.png)
As AFIS you recommend the appropriate procedure, and recommend the descend, and asks them to Report Beacon outbound in the procedure/baseturn (VG or MY) and then Beacon inbound (MY) or on final (Rwy 30).
## 1.3 Other arrival procedures
### 1.3.1 RNP Approaches
EKVG has RNP-AR (Required Navigation Performance – Approval Required) procedures applicable to some airlines in order to perform approaches and SIDs. At this point this is limited to:
\- A319 & A320 with Atlantic Airways
\- A319 & A320 & A32N with SAS
Other airlines may get these on request only, and should be limited to Airbus & Embraer aircraft, as others may not have these capabilities.
In case of RNP-AR following procedures are applicable.
| **Runway 12** |
| **Direction** | **Point** | **Altitude** | **Procedure** |
| East | ROBUR | 7000' | Full procedure RNP V or RNP W |
| South | SUDUR |
| West | MAGNI |
| North |
| **Runway 30** |
| **Direction** | **Point** | **Altitude** | **Procedure** |
| East | ROBUR | 7000' | Straight in ILS V, RNP W, RNP V or RNP U |
| South | SUDUR | RNP W, RNP V or RNP U |
| West | MAGNI | Full procedure ILS V, RNP W, RNP V or RNP U |
| North |
See charts for ILS V, RNP V, RNP U and RNP W layout.
### 1.3.2 NDB Visual approach
NDB visual approaches is available on pilot request only during daylight hours. This approach
transitions to two available visual segments.
- Waterfall visual approach: Only for VFR & RNP-AR approved A/C (1.3.1)
- Standard visual segment: Available for everyone
## 1.4 Departure procedures
EKVG has established SIDs which are given as pr. BIRD instructions however appropriate SIDs should be assigned.
| **Directrion** | **Runway 12** | **Runway 30** | **Initial climb** |
| **Other A/C** | **SID (RNP-AR)** | **SID (RNP-AR)** | **Other A/C** |
| East | Visual Departure | ODEVA2P/2N | LUVEK2S/2T/2W | Visual departure | 7000' |
| South | RAKUP2P/2N | RAKUP2S/2T/2W |
| West | MY2P/2N | MY2S/2T/2W |
| North |
### 1.4.1 Visual Departure
All aircraft which does not live up to 1.3.1 RNP-AR requirements must perform a VFR departure, and hence visibility must be more than 3KM, and no clouds below 3000’ AGL
If the pilot is aware of this, and wishes to bust the VFR minima, it is his discretion.
A visual departure is given by stating:
\- After Departure climb visually, when clear of terrain, proceed direct to \[Point\]
### 1.4.2 SID-AR departures
For Airbus & other capable aircrafts, SID-AR are available.
Different ones are available, and must be used according to wind direction
| **Wind direction** | **SID name depending on direction of departure.** |
| **Runway 12** | **Runway 30** |
| 020 - 040 | ODEVA/RAKUP/MY **2S** departures | ODEVA/RAKUP/MY **2P** |
| 040 - 150 | RWY not in use |
| 150 - 200 | ODEVA/RAKUP/MY **2T** departures |
| 160 - 200 | ODEVA/RAKUP/MY **2W** departures |
| 200 - 230 | ODEVA/RAKUP/MY **2N** departures |
| 230 - 260 | RWY not in use |
| 260 - 020 | ODEVA/RAKUP/MY **2P** departures |
After departure, when aircrafts are reporting airborne they should be transferred to the appropriate controller (BIRD\_E\_CTR, BIRD\_CTR or BICC\_FSS)