RIMCAS

RIMCAS provides advisory runway-conflict prediction and movement-state alerts using the active airport, AVISO runway geometry, target state, and EuroScope runway context.

Warning

vSMR RIMCAS does not replace controller observation, local procedures, or a validated operational safety system. Test every airport configuration away from live traffic.

Configure an airport

Open Control Center — Alerts, then:

1. Select the intended alert types.
2. Review both NORMAL and LVP timing values.
3. Set Visibility deliberately.
4. Verify the automatically listed runway pairs and read-only ARR/DEP state against EuroScope. Set manual Closed state where required.
5. Test representative movements and conflicts.

Runway pairs and ARR/DEP assignments always follow the active airport's EuroScope runway selection. There are no All ARR, All DEP, Add runway pair or deletion controls. Closed remains independently editable; Open all clears manual closure state without changing EuroScope.

Runway geometry comes from the active AVISO document. If a conflict appears in the wrong place, verify the airport and geometry before changing timing values.

Movement alerts

Alert	Trigger summary	Class
NO PUSH	Reversing above 2 kt without Push, Taxi, or Line Up status	Caution
NO TAXI	Forward movement above 5 kt without Taxi, Departure, or Line Up status	Caution
NO TKOF	Above 35 kt on a runway without Departure status	Warning
STAT RPA	Departure-authorized aircraft remains stationary after the 25-second grace period	Warning
RWY INC	Aircraft is on a runway without Departure or Line Up status	Warning
RWY TYPE	Movement above 3 kt on a runway whose ends are reported arrival-only	Caution
RWY CLSD	Movement above 3 kt where both runway ends are reported closed	Warning
HIGH SPD	Non-departure movement off runway above 35 kt, or 25 kt in LVP	Caution
EMERG	Squawk 7700	Warning

These are implementation summaries, not clearance authority. A movement alert requires a correlated flight plan and a valid target position. Incorrect ground status can suppress an expected alert or create an inappropriate one.

RWY TYPE and RWY CLSD use EuroScope's live per-end runway activity. Conflict prediction uses the synchronized ARR/DEP monitoring state plus the independent manual Closed flags. Do not confuse manual conflict-monitor closure flags with EuroScope's per-end activity used by these movement alerts.

When several movement conditions are true, vSMR keeps the first match in this order: RWY CLSD, RWY TYPE, RWY INC, STAT RPA, NO PUSH, HIGH SPD, NO TKOF, NO TAXI, EMERG. A higher item can therefore mask a lower one.

Colors and display modes

Edit Stage One, Stage Two, caution, and warning colors under Control Center -> Display -> Colors -> RIMCAS. Check their legibility against all available AVISO palettes, normal and detailed tags, and main/SRW views. An EMERG target uses the fixed red emergency presentation and warning-class band.

A mode can hide an airborne target from the main display or insets because of altitude or speed limits. RIMCAS still processes that target; a hidden target does not prove that an alert is stale.

See Control Center — AVISO for map geometry, Control Center — Alerts for alert configuration, and Control Center — Profiles for profile activation.