LOREL Holdings

peter7373

Hi all,

Has something changed for the LOREL sector and the EGGW arrivals , because i can't seem to match what is in the sector information manual to what is happening in the sim, or the actual current charts, i see holdings at ZAGZO or MUCTE, for instance for Flight WUK8622 he is not overflying ABBOT nor LOREL so unable to let him hold there. Please advise.

CloggyUk

Hi. Big change! The sector manual for Lorel is not applicable anymore.

Let me get my laptop fired up and will type up a bit more detail later today!

Cheers, C

Graham

The sector manual is now horribly outdated for so many sectors, so exercise caution when controlling because, as CloggyUk says, so much has changed. We WILL get round to updating it in the fullness of time, but that is a huge task because the file is locked and that means we will essentially have to start from scratch. I'm sure you can see how extensive a job it's going to be! In the meantime, the XFL document on the website should give you some assistance and we have some additional process charts to share in the coming days, thanks to the efforts of another LC user.

CloggyUk

Hi again

As Graham says, the LC team are working on updated sector manuals and maps for all sectors. But for now here is a quick explanation how LOREL works since the New Luton airspace (Airspace Deployment 6) was introduced. (For more info just search the web).

I have all the info from the LC data files and other info available on Eurocontrol websites. LOREL controls the LOREL hold (EGSS) and the ZAGZO hold (EGGW). Traffic into ABBOT goes directly from REDFA to SSDIR. Traffic comes from 3 directions into LOREL: East from REDFA sector, South from VATON sector or west from BNN sector.

BNN to LOREL: This is how it was. Standing Agreement is FL130 from BNN to LOREL for all GW/SS/SC traffic.
VATON to LOREL: Standing Agreements are FL150 lvl 5 nm before BPK for SS/SC traffic and FL150 lvl OZZOT for EGGW traffic. There is a level restriction to keep traffic 120 or above until 7 nm after BPK. So do not descent below 120 until inside LOREL airspace.
REDFA to LOREL: Standing Agreement is FL140 lvl OFJES.

LOREL has to merge the Luton inbounds to ZAGZO and hand them off to GW DIR. Of course you can give traffic shortcuts etc, provided you stay inside your airspace.

Hope this helps, C

peter7373

Awesome.

Thing is, i coordinates min stack plus 1000 to next sector, after a direct to waypoint on transition, after handover traffic climbed in holding back to FL140z

CloggyUk

Hello again.
Difficult to know what happens, are you able to post a screenshot perhaps?

peter7373

Seems like i did something wrong previously, everything works like it should. Cool sector to bandbox with LAM.

On a side note, how would you know as a controller if departures are waiting on a single runway airport? So you know whether or not to increase separation.

CloggyUk

peter7373 The tower controller specifies what spacing he/she needs on single runway/mixed mode airports. Roughly 3-4 nm for a pack (no dep) or 5-6 nm for a gap (1 dep). Also alternates gap/pack/gap/pack/etc are used. When packing and a departure starts/pushes back, they work out where they would go in the sequence and request a departure gap. If the amounts of deps and arrivals are roughly equal, it’ll be ‘gaps’ all the way.
Unfortunately this can’t be simulated in LC. I remember there being some guidance in the old sector information. Pause your game, press <F2> and you can look through the sectors. Look at Gatwick or Stansted/Essex, there are bits in there if I recall correctly.

Cheers, C

Addition: Approach units also have a screen that shows them what departures are active, so they know when traffic is pushing/starting.
If running SSDIR in LC, you get the Utava and Nugbo deps in your tactical list, so they will be departing at some point.