Airport Reservation Office (ARO)

All General Aviation (GA) and Business Aviation (BA) operators must obtain an approved runway slot reservation before arriving at or departing from Vancouver International Airport / Aéroport international de Vancouver (YVR), unless the operation is exempt.

YVR’s Airport Reservation Office (ARO) manages GA/BA runway slot reservations through the Online Coordination System (OCS). Operators use OCS to create, manage, update, or cancel their slot reservations.

YVR has established this process to help maximize runway capacity, reduce airfield congestion and delays, and support efforts to reduce greenhouse gas emissions.

Available slots are allocated on a first come, first served basis, subject to runway capacity and operational constraints.

1. Who needs a runway slot reservation

   This process applies to General Aviation and Business Aviation operators using YVR’s runway system. This process does not apply to commercial scheduled, charter, or cargo operators. These operators should continue to submit slot requests through the Airport Coordination Office. There is no change to that existing process. A runway slot reservation for each GA/BA arrival and departure using YVR's runway system, unless the operation is exempt.

2. Before you operate

   Before operating at YVR, GA/BA operators must:

1. Have access to OCS.
2. Submit a runway slot reservation request within the applicable booking window.
3. Receive a runway slot confirmation number.
4. Include the runway slot confirmation number in the flight plan
5. Update or cancel the runway slot reservation in OCS if flight details change.
3. How to get access to OCS

   GA and BA operators require an OCS account to make runway slot reservations.

   • If you already have an OCS account, contact [email protected] to have YVR added to your account.
   • If you do not have an OCS account, download and complete the OCS application form, then submit it to [email protected].
4. When you can book a runway slot

   YVR-based GA/BA operators may book runway slots up to 14 days before operation.

   Itinerant operators, meaning non-YVR-based GA/BA operators, may book runway slots up to 72 hours before operation.

   For the purposes of runway slot booking windows, “YVR-based” refers to GA/BA operators or aircraft based at YVR. “Itinerant” refers to non-YVR-based GA/BA operators.

   All runway slot times should be submitted in local Vancouver time unless otherwise specified in OCS.

5. Confirming your runway slot

   If your requested time is not available, OCS will display the closest available times before and after your requested slot time.

   Operators must select and operate according to an approved available slot time. Submitting a preferred time does not guarantee approval.

   Once a reservation is confirmed, OCS will provide a slot confirmation number. Operators must retain this number and include it in the flight plan.

   Reservations can be made through OCS by clicking here.

6. Changing or cancelling a reservation

   Operators must update their runway slot in OCS if planned flight times change.

   Operators must also cancel the runway slot in OCS if the flight is cancelled.

7. Compliance and on-time performance

   All flights will be monitored for runway slot compliance and on-time performance.

   GA/BA on-time performance is measured against the approved runway slot time using a plus or minus 30-minute threshold. Flights operating more than 30 minutes before or after the approved runway slot time may be considered non-compliant.

   During irregular operations, such as significant weather events, YVR may suspend runway slot on-time performance monitoring. However, operators must still file and maintain slot reservations in OCS, so YVR Operations has an accurate picture of same-day flight demand.

8. Exempt operations

   Exemptions are based on the mission being performed, not the identity of the operator. An operator is only exempt when the aircraft is actively engaged in one of the exempt missions listed below.

   The following operations are exempt from ARO slot filing requirements:

   1. Floatplanes using the water runway
   2. MEDEVAC flights, when operating as a live medical mission
   3. Aircraft performing NAVAID flight checks
   4. Flights engaged in military, customs, or police service operations
   5. Flights with Head of State status
   6. Flights involved in active firefighting operations
   7. Helicopters flying VFR
   8. Aircraft diversions due to weather, mechanical, or medical emergencies
9. Support and contact information

   For OCS account setup, login issues, password resets, or technical support, contact OCS at [email protected].

   For YVR slot process questions, booking windows, exemptions, compliance, or operational requirements, contact the ARO at [email protected].

   The ARO inbox is monitored Monday to Friday, 08:00 to 17:00.

   Outside these hours, urgent same-day operational enquiries can be directed to Airport Flow:

   Phone: 604-303-3193
   Email: [email protected]

   Airport Flow should not be contacted for OCS account setup, login issues, password resets, or non-urgent process questions.

Frequently Asked Questions

How do I secure a GA/BA runway slot at YVR?

GA/BA runway slots must be booked through the Online Coordination System (OCS). Operators may book their own runway slots using an OCS account or, if they are infrequent users of YVR, request that their Fixed Base Operator (FBO) make the booking on their behalf. Booking through an FBO is at the discretion of the FBO and is not guaranteed.

Do I need an OCS account to book a runway slot?

If you plan to book your own runway slots, you will need an OCS account. Operators who have their FBO manage bookings on their behalf do not require their own account.

Please visit the ARO landing page on yvr.ca to learn how to apply for an account.

What is my booking window to secure a runway slot?

Based operators (operators whose aircraft are physically based at YVR) have a 14-day booking window.

Itinerant operators (operators whose aircraft are physically based elsewhere) have a 3-day (72-hour) booking window.

What is the window of validity for my slot time?

GA/BA runway slots are valid within ±30 minutes of the confirmed slot time. Any future changes to this tolerance will be communicated to operators.

What happens if my desired runway slot time is not available?

If your requested slot time is not available, OCS will automatically suggest two alternative available times before and after your requested time. Once an alternative is selected and accepted, the system will confirm the booking and generate your slot ID.

When do I need to update my runway slot time?

If your planned arrival or departure time changes, you should update your runway slot in OCS as soon as practical. Unused slots should be cancelled so they can be made available to other operators. Slot utilization is monitored as part of YVR's compliance program.

Are flights being monitored for compliance?

Yes. Compliance with runway slot requirements is monitored. The three primary measures include:

• GA/BA On-Time Performance
• GA/BA Booking Compliance
• GA/BA Slot Utilization

Why is it that I have a confirmed runway slot time, but I am being asked to hold due to YVR flow control measures or Air Traffic Control Flow Measures (ATCFM)?

A confirmed runway slot means runway capacity was available when the flight was planned. On the day of operation, factors such as weather, runway configuration, staffing constraints, equipment outages or other operational conditions may reduce available runway capacity.

When this occurs, YVR or NAV CANADA may implement traffic management measures, such as a Demand Management Program (DMP) or Ground Delay Program (GDP), which can result in delays even when a valid runway slot has been issued.

What is the difference between a runway slot and my flight plan?

A runway slot and a flight plan serve different purposes. A runway slot reserves access to runway capacity during a planned time window, while a flight plan is submitted to NAV CANADA for air traffic management on the day of operation.

An approved runway slot does not guarantee an exact arrival or departure time, as day-of operational conditions may require additional traffic management measures.

Are GA/BA operators the only traffic segment that require runway slots?

No. All operators using YVR's runway system require pre-approved runway slots prior to operating. This includes scheduled passenger airlines, cargo operators, charter operators and GA/BA operators.

As an IATA Level 3, Slot-Coordinated Airport, runway capacity is allocated across all users to ensure safe and efficient operations.

Are Runway slots unique to YVR?

No. Airport slots are a global standard implemented at congested airports to reduce delays, manage congestion and improve operational predictability.

YVR is an IATA Level 3, Slot-Coordinated Airport. During peak periods, demand for runway access exceeds available runway capacity, requiring the use of a coordinated slot allocation process.

Are there any exemptions to runway slot requirements?

Yes. There are a few exemptions to the runway slot requirements. A complete list of exemptions is available on the ARO landing page on yvr.ca.

Examples include aircraft operating on a live MEDEVAC mission, aircraft using the water runway and helicopters operating under VFR.

During IRROPS (i.e. extreme weather event) what happens to runway slots and runway slot monitoring?

Operators are still required to obtain and maintain runway slots during IRROPS. Compliance with runway slot booking requirements will continue to be monitored; however, on-time performance will not be assessed, recognizing that delays during IRROPS are often outside an operator's control.

Maintaining accurate runway slot information remains essential to provide airport operations with a clear picture of planned demand and support effective management of the disruption.

Can I operate at YVR without a runway slot?

Except where an exemption applies, all aircraft operating on YVR's runway system must have a confirmed runway slot prior to arrival or departure. Operators without a valid runway slot may be subject to operational restrictions or delays.