Abbreviations, info, parkingspots and runway info

[Key]

And another small amendment: start of fourth outbound peak planned 20 minutes earlier.

Slight amendment since 04may15: switch from outbound to inbound mode at 1520LT i.s.o. 1500.

Summer season 2015 inbound/outbound peak schedule as of 29mar15 below. This is the basis for '2+1 runway use'.

0700 – 0720 LT
0720 – 0920 LT
0920 – 1040 LT
1040 – 1140 LT
1140 – 1300 LT
1300 – 1340 LT
1400 – 1520 LT
1520 – 1600 LT
1620 – 1720 LT
1820 – 2000 LT
2020 – 2200 LT

inbound - outbound

This is the leading time frame, variations may and will occur.

Erik

[polderbaan]

In August the Polderbaan will be closed from Monday 17 August 0930h LT till Tuesday 25 August 1800h LT:

A0832/15 - RWY 18R/36L CLSD. INCL TWY V, Y AND Z BEYOND Z2 CLSD. 17 AUG 07:30 2015 UNTIL 25 AUG 16:00 2015. CREATED: 29 JUN 10:40 2015

Goedemorgen,

ik zie op de LVNL website dat de Polderbaan nog in gebruik is (11.35 uur).
Is dit een foutieve weergave of is de baan inderdaad nog open.
Omdat ik deze week vanuit Groningen een paar keer in de buurt van Schiphol ben wil ik graag weten of de baan inderdaad de rest van deze week dicht is.
Bij voorbaat bedankt.

Groeten van Ab Gobets.

[B767-300ER]

Polderbaan is buiten gebruik nu.

[pvl]

polderbaan is gisterochtend tot ca. 10.30 gebruikt. hij is de rest van de week zowieso dicht. aanstaande maandag + dinsdag is het nog onzeker of de baan dan wel of niet in gebruik is. vooralsnog is in principe de oplevering dinsdag omstreeks 12.00.


31-8 t/m 18-9 is de aalsmeerbaan 18L-36R dicht. mogelijk nog tot 25-9.

[EHAM]

Closure of Aalsmeerbaan from 30 AUG 2015 22.00h LT till 27 SEP 2015 16.00h LT:

A1127/15 - RWY 18L/36R CLSD. 30 AUG 20:00 2015 UNTIL 27 SEP 14:00 2015. CREATED: 26 AUG 07:01 2015

[Key]

It's that time of the year again.
Here is the Winter season 2015-2016 inbound/outbound peak schedule as of 25oct15 below. This is the basis for '2+1 runway use'.
There are at least four moments a day where '2+2' may be applied though: around 07:00, 11:00, 13:00 and 15:00LT.

0700 – 0900 LT
0920 – 1100 LT
1100 – 1140 LT
1220 – 1300 LT
1300 – 1340 LT
1420 – 1500 LT
1500 – 1600 LT
1620 – 1720 LT
1820 – 1940 LT
2020 – 2200 LT

inbound - outbound

This is the leading time frame, variations may and will occur (also in 2+1).

Erik

[Patkee]

Hi Erik,

Is this below correct?
What is the rwy configuratie between 1340-1420?
1300 – 1340 LT
1420 – 1500 LT

inbound - outbound

[B767-300ER]

1+1

[Key]

Correct. So if you have plans for a new service: ask for a slot in that gap.

Erik

[Key]

0700 – 0900 LT
0920 – 1100 LT
1100 – 1140 LT
1220 – 1300 LT
1300 – 1340 LT
1420 – 1500 LT
1500 – 1600 LT
1620 – 1720 LT
1820 – 2000 LT
2020 – 2200 LT

inbound - outbound

The usual slight adjustment has ocurred, see underlined above.

Erik

[Key]

0700 – 0900 LT
0920 – 1100 LT
1100 – 1140 LT
1220 – 1300 LT
1300 – 1340 LT
1420 – 1520 LT
1520 – 1600 LT
1620 – 1720 LT
1820 – 2000 LT
2020 – 2200 LT

inbound - outbound

FWIW, another minor change, again underlined above.

Erik

[Piet Luijken]

New frequencies will be used at Amsterdam, and other airports, according this schedule:
https://www.aopa.nl/uploads/docs/Implem ... enties.PDF

[EHAM]

I doubt if you will hear any difference on your scanner if you will be using the old frequencies instead. Only 5 kHz difference.

[WouterH]

These 'new' frequencies are just new designations. The actual frequency is different from the frequencies on charts and the ones used by controllers. The technique is a bit difficult to explain, but the article below sums it up pretty well.

http://www.lightaircraftassociation.co. ... /radio.pdf

Long story short: don't change anything in your scanner. The frequencies used the last couple of years don't actually change, they just call them differently.

[Key]

Isn't it rather that actual new freqs will be referenced by simplified but also new numbers for ease of use? Don't have the actual new ones for EHAM at hand now but someone else may. I suppose current scanners may not be able to differentiate btn 8.33 kHz channels but general allocation will try and avoid minimal spacing per location anyway.
I.e. when wanting to listen to 118.015 (actually 118.0166) you will probably hear it with your scanner on 118.0 or 118.025 but if only one such freq is used locally you just here that one. Up in the air with reception from a bigger area it's a whole different story of course. And yes, if 118.010 is used locally too that will be a problem.

Erik