Substantial obstacles are depicted visually on the Arrival and Departure Route chart (see EVRS AD 2.24.17).

1. AERODROME REGULATIONS

1.1 Spilve Aerodrome and circuit training flights over aerodrome are strictly PPR with mandatory FPL for any flight.

1.2 Permission shall be obtained by e-mail (info@spilve.org) not later than 12 HR prior the flight, however contacting AD administration for permission exactly 12 HR prior the flight does not warrant granting a permission and submission of a request should be planned timely.

1.3 The permission number must be included in the FPL Item 18 as a remark "PPR CONFIRMED XXXX" where XXXX is 4-digit PPR number.

1.4 FPL or CHG messages without PPR number in the Item 18 of the ICAO flight plan will be rejected by Riga ATS. The pilot shall open the FPL and report the actual time of departure to the nearest ATS unit.

1.5 Spilve ATZ shall not be used by aircraft unable to comply with the circuit procedures detailed in EVRS AD 2.22 .

1.6 Aircraft not equipped with two-way radio and/or pilots unable to use RTF, are not accepted.

1.7 For flights in Spilve ATZ an ACFT must carry a serviceable SSR transponder and the pilot shall operate the transponder at all times during the flight, regardless of whether the ACFT is within or outside the airspace where SSR is used for ATS purposes. The pilot shall set Mode C with Code 2000 unless instructed otherwise by ATC. The pilot shall not operate the IDENT feature unless requested by ATS.

2. GROUND MOVEMENT

2.1 The pilot-in-command remains responsible for his/her own separation whilst manoeuvring on the ground regardless of the provision of a marshalling assistance.

2.2 At the intersections of TWY A and B, all movements shall be kept to the right of the taxiway (EVRS AD 2.24.1-1).

2.3 Before occupying the runway (line-up or crossing), the pilot-in-command shall always stop the aircraft before a runway taxi holding position, visually assure that the runway is free and no aircraft are on final approach, announce the intention to occupy the runway (stating the runway designator is required when lining up for take-off) via CTAF on 124.380 MHz and only then commence the actual line-up manoeuvre (EVRS AD 2.24.1-1).

2.4 After landing, aircraft shall vacate the runway via the nearest taxiway as soon as possible.

3. USE OF RUNWAYS

3.1 Line-up and vacation:

PROCEDURE	RWY14	RWY32
Take-off	From THR, line-up via TWY N	Line-up via TWY A for a rolling take-off
	From RWY centre, line-up via TWY M	From THR, line-up via TWY S
Landing	Vacate straight via Stopway onto TWY A	Vacate via TWY M or TWY N

3.2 RWY 32 landings are only allowed beyond the displaced threshold markings. Violation of this rule endangers other aerodrome users as well as lowering the approach path below the safe altitude.

4. OTHER

4.1 The aerodrome is extensively used for training flights.

4.2 No provision is made for aerobatic flights or turbo-prop/turbo-fan aircraft training flights.

1. AIRSPACE

1.1 Spilve ATZ Class G airspace is intended to be used for traffic arriving to/departing from Spilve Aerodrome or airfields located within the lateral limits of Spilve ATZ or for circuit training only.

1.2 Riga AD (EVRA) QNH shall be used for altimeter setting.

1.3 The maximum altitude for Spilve ATZ traffic in sectors A1 and A2 is 600 ft MSL(EVRS AD 2.24.14 and EVRS AD 2.24.17). Occasional ultralight activity takes place in Spilve ATZ Sector A2. This airspace shall not be used by other traffic. Setting the maximum MSL for this sector does NOT imply permission for ultralight aircraft to fly over built- up areas other than for take-off or landing.

1.4 Maximum altitude for Spilve ATZ traffic in sector B is 1000 FT MSL (EVRS AD 2.24.14 and EVRS AD 2.24.17).

1.5 There are four standard entry/exit points for Spilve ATZ from/to the surrounding airspace:

Entry/Exit point	Visual reference	Coordinates	Surrounding airspace	Flight altitude
CLUB	Jaunciems Yacht Club Harbour	570231N 0241020E	G	1000 FT MSL
BRIDGE	0.5 NM East of the road bridge across the railway	565854N 0241045E	G	1000 FT MSL
SARPS	Located at centre point of RWY 14/32 (the ARP)	565931N 0240428E	C (Riga CTR)	1000 FT MSL
RIVER (exit point only)	Confluence of the Daugava and Sarkandaugava rivers	570127N 0240519E	C (Riga CTR)	500 FT MSL

2. CIRCUIT PROCEDURES

2.1 All circuits shall be flown to the North East of RWY 14/32 (left-hand circuit for RWY 14, right-hand circuit for RWY 32).

2.2 The standard circuit altitude is 1000 FT MSL on downwind.

2.3 Joining aircraft shall give way to circuit traffic.

2.4 Arriving ACFTon base leg or final shall have priority over ACFT preparing for take-off.

2.5 Circuit joining:

Active runway	Direction	Joining altitude	Procedure
RWY14	From VRP “CLUB”	600 FT MSL	Directly to base leg
	From SARPS	1000 FT MSL	Join downwind leg at 45 degrees
RWY32	From VRP “BRIDGE”	1000 FT MSL	Directly to base leg
	From SARPS	1000 FT MSL	Join downwind leg at 45 degrees

2.6 Prior to entering Spilve ATZ from the surrounding Class G airspace, the flight crew shall monitor the CTAF (124.380 MHz) to determine the runway-in-use and accordingly choose the correct entry point.

2.7 If there is no activity on CTAF (124.380 MHz), the pilot-in-command shall choose the runway-in-use.

2.8 A circuit flight shall be performed in a rectangular pattern, as close as practicable to the depicted circuit pattern on the Visual approach chart (EVRS AD 2.24.17).

3. DEPARTURE FROM SPILVE AD TO RIGA CTR

3.1 File FPL as per standard procedures. The pilot shall open the FPL and report the actual time of departure to nearest ATS unit.

3.2 Point SARPS shall be filed as a standard entry point from Spilve ATZ to Riga CTR.

3.3 Before lining up on the RWY, the crew shall:

a. establish communication with Riga Tower (118.105 (8.33 channel)) in order to receive ATC clearance;

b. announce the departure and intentions on CTAF (124.380 MHz).

3.4 Take-off, climb to 1000 FT MSL within the circuit.

3.5 Once airborne, reestablish radio communication with Riga Tower (118.105 (8.33 channel)).

3.6 Leave circuit from downwind leg across the centre of RWY 14/32.

3.7 Depending on traffic situation in Riga CTR, Riga Tower controller may issue additional instructions and/or amend ATC clearance.

4. ARRIVAL TO SPILVE AD FROM RIGA CTR

4.1 Point SARPS shall be filed as a standard point to enter Spilve ATZ from Riga CTR.

4.2 Approach Spilve ATZ in accordance with ATC instructions. 4.3 After crossing over the centre of RWY 14/32, join downwind and continue in accordance with circuit procedures.

5. DEPARTURE FROM SPILVE AD TO THE WEST VIA NORTH TRANSIT ROUTE

5.1 File FPL as per standard procedures. The pilot shall open the FPL and report the actual time of departure to the nearest ATS unit.

5.2 Point RIVER shall be filed as an entry point to Riga CTR.

5.3 Before lining up on the RWY, crew shall establish communication with Riga Tower (118.105 (8.33 channel)) in order to receive ATC clearance.

5.4 Before lining up on the RWY, announce the departure and intentions on CTAF (124.380 MHz).

5.5 Depart as per circuit procedures.

5.6 Once airborne, reestablish radio communication with Riga Tower (118.105 (8.33 channel)).

5.7 RWY 14 - leave from downwind leg via point RIVER at 500 FT MSL. RWY 32 - leave from crosswind leg via point RIVER at 500 FT MSL.

5.8 Proceed over the river Daugava at 500 FT MSL till the river delta (visual reference point DELTA), after passing Marine lighthouse turn left and proceed along the North Transit Route at 500 FT MSL.

6. VFR COMMUNICATION

CTAF (124.380 MHz) shall be used by pilots for self-announcing their positions and intentions or for air-air communications in order to exchange traffic information.

6.1 Inbound traffic:

• “Spilve Traffic”, call sign, altitude, intentions, place of crossing the established ATZ boundary prior to entering;

• RWY to be used for landing;

• entering traffic pattern (downwind, base leg and final), circuit direction and altitude;

• vacating the RWY.

6.2 Examples of self-announcing for inbound traffic:

• Spilve Traffic, YLLCF, entering via point BRIDGE at 1000 feet;

• Spilve Traffic, YLLCF, joining right-hand base RWY 32, altitude 1000 feet;

• Spilve Traffic, YLLCF, RWY vacated.

6.3 Outbound traffic:

• intentions for departure;

• RWY to be used for take-off;

• intended flight direction and altitude.

6.4 Example of self-announcing for outbound traffic:

• Spilve Traffic, YLLCF, departing Spilve RWY 32;

• Spilve Traffic, YLLCF airborne, right turn, climbing to 1000 feet, proceeding to point CLUB.

1. AIR NAVIGATION WARNINGS

1.1 Spilve ATZ is located in close proximity of Riga CTR, 2500 FT MSL/GND. All flights must be conducted with utmost care to avoid incursion into Riga CTR.

1.2 Ultralight ACFToperating in sector A2 shall NOT fly over built-up areas other than for take-off or landing.

1.3 To avoid creating nuisance to other traffic, very slow ultralights may use the airspace along the Southern border of Spilve ATZ for transit between Spilve AD and the surrounding Class G airspace to the East of Riga CTR.

1.4 Approaches to RWY 32 and departures from RWY 14 should beware of the port cranes and marine vessels navigating the Daugava river.