Arrival Load Balancer (ALB)
ALB is an arrival-planning tool for EuroScope. It helps controllers have a shared picture of inbound traffic and flow, monitor via-fix streams (STARs) and landing sequence development, and coordinate timing or sequence corrections before aircraft reach the runway.
In practice, ALB sits between the raw live EuroScope picture and the controller's and FMRs operational plan. It is not a separation tool on its own. It is a planning and coordination aid for live positions, team sessions, and event-style arrival management.

Core ideas
Before going deeper into the site, it helps to know the main ALB planning terms:
EVTO: the estimated time over the relevant via-fix or inbound gate pointEAT: the estimated arrival time - calculated and used for flow and sequencing coordination- EAT is used for both planning modes as release time over the viaFix (typically STAR holding point)
ELT: the estimated landing time branchPLT: the planned landing time in the current ALB plan
Two planning modes matter most in normal use, and relate to how the EAT is calculated:
EAT:LTis the preferred modern method and plans against the landing timelinePLRPlanned Landing Rate (aircraft per hour) - is the rate per airport ALB uses to separate aircraft.EAT:LTnow combines that PLR baseline with WTC-dependent adjacent-pair landing spacing and shows a demand-limitedExpected LRforecast from the resulting canonical PLTs.
EAT:ARis the older rough fallback method and plans more directly by via-fix arrival spacingARArrival Rate - is the rate (minutes separation) per ViaFix ALB uses to separate aircraft per ViaFix (STAR).
Feeder versus runway view is a separate choice:
- it reflects the operational role and picture you want, such as upstream feeder or area work versus TMA or runway-side work
- it does not decide whether the engine mode is
EAT:ARorEAT:LT
Two estimate branches also matter and control the calculation of duration from ViaFix to Landing:
ETA:ESorELT-ESfollows the live EuroScope-style estimate branchETA:ALBorELT-ALBfollows ALB's own corrected estimate branch when that branch is useful
In shared use, one controller may act as FMR:
- Flow Management Responsible
- the controller who is treated as the authority for the shared arrival plan for a destination airport
- the person who normally owns the main planning choices, sequence interventions, and shared timing policy
This documentation is meant to help with three slightly different kinds of work:
- Operational Guide for controllers using ALB during a session
- Configuration & Customization for users editing
alb-config.json, layouts, timelines, and airport setup - Developer / Internals for maintainers working across the ALB code, release, and documentation repos
The installed package uses a small loader/runtime split:
ALB.dllis the EuroScope-facing loaderALBCore.dllis the ALB runtime plugin
EuroScope should load ALB.dll.
For the controller-facing explanation of the current landing-timeline model, see EAT:LT Landing Timeline Planning.
Start Here
Operational Guide
- Quick Intro
- Overview
- Planning Modes Overview
- EAT:LT Landing Timeline Planning
- EAT:AR Arrival Rate Fallback Planning
- Feeder View vs Runway View
- Interface
- Buttons & Menus
- Aircraft Actions
- Workflows
- Collaboration & FMR
- Legend & Status
- EAT Coordination
- Retired: Scenarios
Configuration & Customization
- Config Overview
- Display Fields and Tag Layouts
- ICAO / Airport Setups
- Timeline / Via-fix / Runway Setups
- Config File Reference
- Sample Config File
Developer / Internals
- Technical Overview
- Architecture
- Collaboration Internals
- Sequencing Model
- Backend Transport
- Playback & Recording