Subject: EGNM Infrastructure: The N1/L1 "Fog" Factor and TORA Recovery
For those tracking the airfield side of LBA:REGEN, the real "hidden" win isn't just the terminal—it’s the projected relocation of the CAT II/III holding points at N1 and L1.
Currently, LBA suffers from a "double penalty" during Low Visibility Procedures (LVPs). Not only do you have slower flow rates, but you often lose usable runway for departures because of where aircraft are forced to hold to protect the legacy ILS signal.
The Problem: The "Holding Back" Penalty
N1 (Runway 14 End): In CAT I or VFR, you can hold right at the threshold. But under current CAT II/III conditions, the ILS critical area for Runway 32 can extend quite far. If an aircraft is landing on 32, a departing aircraft at N1 can interfere with the signal.
L1 (Runway 32 End): Similar issue for 14 arrivals. If you're forced to hold back at Bravo or Charlie because L1 is "inside" the protected zone for a landing aircraft, you lose significant TORA (Take-Off Run Available). For a B738 or A321 heading to the Canaries, those few hundred meters are the difference between a full load and a seat cap.
The Solution: "Lowering" the ILS & Capture Effect Antennas
The upgrade to a Capture Effect Localizer (part of the 2025/26 airfield works) changes the physics of the signal:
Narrower "Stay Clear" Zones: Modern antennas are far more directional. They don't "splash" signal off taxiing aircraft as easily.
Relocating the Holding Points: This allows the airport to move the CAT II/III stop bars closer to the runway centerline.
Current: Standard CAT III holds are often ~150m from the centerline.
Target: Reducing this to the ICAO minimums (often ~90m-107m depending on the aircraft code) by stabilizing the signal.
Why this matters for the "Start of Roll"
If LBA can move the L1 and N1 CAT III holding points just 40-50 meters closer to the thresholds, they essentially "reclaim" that distance for every departure in the fog.
Runway 32 Departures: Entering via a modernized L1 means you aren't losing the first ~200m of concrete that happens when you're "held back" during an arrival's short final.
The "N1 Loop": Clearing the N1 area faster means the "next in line" can move up sooner without tripping the ILS sensitive alarms for the guy on the glideslope.
The Bottom Line:
When we talk about "Lowering the ILS," it’s not just about the glidepath; it’s about shrinking the "invisible bubble" around the runway. This allows N1 and L1 to stay active as full-length entry points even when the RVR (Runway Visual Range) drops through the floor. It turns LBA from a "fair weather" short-runway airport into a much more resilient CAT III operation.
Quick Nav Reference for the Post:
N1: Northwest end (Rwy 14 Thr).
L1: Southeast end (Rwy 32 Thr).
The Move: Bringing the CAT III stop-bars closer to the runway to prevent "intersection-only" departures in LVPs.
i am not sure i understand what that is supposed to relate to - "lowering the ILS" makes no sense.
is it supposed to mean re-basing it and effectively moving the touchdown zone?
also why is it talking about TORAs when the changes are to the ILS? TORA is take off runway available, ILS is for landing, why would changing the ILS change the amount of runway available for takeoff?
is there some actual legible and coherent source for any of this?
I understand it to be the localiser, hopefully we can get this confirmed. It does make sense.