SLUGO Contingency Procedure (Arrivals Sample Clauses

SLUGO Contingency Procedure (Arrivals. During events on VATSIM, traffic levels can exceed the normal capacity of TNCM. Exceptionally, holding at SLUGO and suspension of the standing agreement for inbounds may be required due to airfield capacity. Normally, each inbound not operating in accordance with the standing agreement would require individual coordination. On VATSIM, the following procedure is agreed to reduce the amount of individual coordination required. Xxxxxxx Approach must coordinate with San Xxxx Center to active this procedure as required using the phrase: “SLUGO contingency procedure”. Subsequent arriving traffic to TNCM must be transferred level separated (lowest FL110), 20NM in trail, constant or increasing to facilitate possible holding. Traffic is still released for descent on turns on transfer of communications. Note: Initially, when using the contingency procedure, holding may not be required. Xxxxxxx Approach must notify San Xxxx Center when holding at SLUGO begins and subsequent arriving aircraft to TNCM must be provided with SLUGO hold details and instructions to hold at SLUGO by San Xxxx Center. “H/SLUGO” should be entered into the scratchpad of arriving traffic once holding details and instructions have been acknowledged by the receiving aircraft.
AutoNDA by SimpleDocs

Related to SLUGO Contingency Procedure (Arrivals

Time is Money Join Law Insider Premium to draft better contracts faster.