Toronto Airspace Transition - Pilot Guide



Similar documents
Background on Airspace

Corporate Report COUNCIL DATE: March 31, 2008

WHICH AIR TRAFFIC CONTROLLER TO CONTACT

Pilot Briefing Stockholm/Arlanda

Training program for S2 (TWR) rating

Radio Communications in Class D Airspace by Russell Still, Master CFI

PF3 ATC at its best Version History

ICAO Standard Phraseology A Quick Reference Guide for Commercial Air Transport Pilots

Pilot Briefing for Helsinki-Vantaa Real Flight Event

IFR Operators Briefing Pack. May 2013

Direct Approach Consulting Inc.

2014 NIFA CRM Contestant Briefing Guide San Diego, California

IFR Communication Procedure

VDFP General Aviation Firefighting for Structural Firefighters

Performance-based Navigation and Data Quality

CTAF PROCEDURES GUIDE

Düsseldorf RG Airports

Minneapolis-St. Paul International Airport: Performance-Based Navigation (PBN) Process Recap and Insights

Part 150: Records of Approval

For Flight Simulation purposes only on the VATSIM Network.

COMMUNICATIONS GROUND COMMUNICATIONS OUTLET (GCO)

Security-related procedures and requirements are a fact of life for today's pilots, especially those who operate in the Washington, DC metropolitan

Ref.: AN 13/2.5-09/45 19 June 2009

FLIGHT ADVISORY The Vancouver 2010 Winter Olympics and Paralympics Games

SANTOS DUMONT ENGLISH ASSESSMENT IDENTIFICATION

Amsterdam Schiphol. Real Flight Event 21 st of May Introduction. This document is provided by IVAO-NL Flight Operations Department.

Pilot Information. Vienna int. Airport LOWW

Michael Harrison Aviation Management Associates Alternative PNT Public Meeting Stanford University August Federal Aviation Administration

The Rebirth of Aviation and Air Transportation in Ohio

SECTION 2 - GENERAL. Callsign. Tower Control Service Tower _TWR Active Runway(s) & ATZ/CTR. Approach or Departure or Radar Area or Radar

Airport Guide to Greenland

NAMIBIAN RADIO LICENSE VALIDATION

Airspace classification change

AIRSPACE EXPLAINED. Separation of Traffic

Tauranga, Bay of Plenty

AVIATION INVESTIGATION REPORT A02P0004 OPERATING IRREGULARITY

MANUAL OF S1 CLEARANCE DELIVERY AND GROUNG SERVICE

VATSIM CODE OF CONDUCT

8-1 Chapter 8 Radio Operations: Aviation Spoken Here

Air Traffic Management Services Plan

VATSIM CODE OF CONDUCT

Departures to the south from Runways 16L and 16R.

Deploying Regional Jets to Add New Spokes to a Hub. Ian Savage* and Burgess Scott Northwestern University

You ll soon be arriving in Paris, thank you for choosing our airport for your arrival. This briefing was made to make your arrival as flawless and

Southwest Texas Regional Advisory Council Air Medical Provider Advisory Group (AMPAG)

Area Navigation (RNAV)/Wide Area Augmentation System (WAAS) Instrument Approach Procedures (IAP s) and the New Charting Format.

International Civil Aviation Organization. The Third Meeting of the Regional ATM Contingency Plan Task Force (RACP/TF/3)

Block 0: Capabilities within our Grasp

Federal Aviation Administration. Air Traffic. Flow Management. Presented to: MIT By: Date: FAA Command Center October 5, 2006

SPECIAL RULES ZONE (SRZ) ON BEHALF OF THE TEXEL AIRSHOW 2007

LONDON SOUTHEND AIRPORT CLASS D CONTROLLED AIRSPACE GUIDE

LONDON SOUTHEND AIRPORT AIRSPACE CHANGE PROPOSAL. Executive Summary and About the Consultation Documents and Document Contents

Pilot Professionalism It Isn t Just For The Big Guys

COMMITTEE ON AVIATION ENVIRONMENTAL PROTECTION (CAEP)

Chapter 15. Airports Authority of India Manual of Air Traffic Services Part EMERGENCY PROCEDURES

Melbourne city area noise information pack

on a dark night departure

A Dynamic Programming Approach for 4D Flight Route Optimization

Area Navigation (RNAV) and Required Navigation Performance (RNP)

Flight information that keeps pilots a step ahead.

AIP Supplement - 04/2015 Page 1 TEXEL AIRSHOW GENERAL 2 TEXEL AREA 3 FLOW CONTROL MEASURES

Frequently Asked Questions

FLORIDA STATE COLLEGE AT JACKSONVILLE COLLEGE CREDIT COURSE OUTLINE

Airspace. Chapter 14. Introduction

BEFORE YOU GET STARTED

Tulsa Riverside Tower (RVS) Pilot Information Handbook

While flight plan calculations are necessary for safety and regulatory compliance, they also provide airlines with an opportunity for cost

UK AIRSPACE Introduction

IBAC Bulletin B00-2 Pacific Implementation of RVSM and RNP 10/50NM Lateral

Familiarisation Briefing for Jet and Multiengine Aircraft Crews.

Safety Bulletin Newsletter

Flight Plan and related messages

Global Data Center. Worldwide Aircraft Communications and Flight Support Services


Second opinion on the application of CDAs at Schiphol Airport Final report

REVIEW OF AIP SUPPLEMENT. (Presented by Singapore) Attached is a copy of the AIP SUPP for review by the Meeting.

A Strategic Vision of Air Traffic Management in New Zealand to 2025

National Transportation Safety Board Washington, DC 20594

Instrument Pilot Rating Course (ASEL) Training Syllabus FAR Part 61

TORONTO PEARSON INTERNATIONAL AIRPORT TRANSPORTATION AND PARKING

AIRCRAFT NOISE ABATEMENT OPERATING PROCEDURES AND RESTRICTIONS

Airspace Change Communications and Consultation Protocol Protocol

2 Purpose and Need. 2.1 The Need for the Proposed Action Description of the Problem

39 IFR AERONAUTICAL CHART SYMBOLS

SITA AIRCOM Service (VHF & Satellite)

AERONAUTICAL SERVICES ADVISORY MEMORANDUM (ASAM) Focal Point: ASD

Garmin GNC 300XL Pilot s Quick Reference Guide

Safety Verification of the Small Aircraft Transportation System Concept of Operations

Do you know exactly how the communication with an aerodrome controller in a foreign country should look like? No? If not, this list might help you.

Pricing Framework July 2012

SESAR Air Traffic Management Modernization. Honeywell Aerospace Advanced Technology June 2014

Oostwold Airshow 2015

1.1 The circumstances of each aircraft emergency can vary to such an extent that detailed instructions cannot be given for every situation.

AVIATION INVESTIGATION REPORT A00O0057 MIDAIR COLLISION

Ms. Jarrette reported that operations at OEA, with inquiries/complaints. These approaches to runways 07 and

per day, air traffic controllers help a pilot by performing a

Existing Facilities. Current and Forecast Demand

AIR TRAFFIC INITIAL ENVIRONMENTAL REVIEW

HUNGARY. HungaroControl Pte. Ltd. Co. Hungarian Air Navigation Services Aeronautical Information Service H-1675 Budapest, POB 80

MASTER PLAN PREPARATION

Transcription:

Toronto Airspace Transition - Pilot Guide Contents Overview... 1 Airways... 1 STARs... 2 SIDs... 4 Preferred Routes... 5 Frequently Asked Questions (FAQs)... 6 Overview On Feb 9, 2012, NavCanada implemented Phase I of the Windsor-Toronto-Montreal (W-T-M) airspace redesign. Recent analysis of filed flight plans indicates over 98% of aircraft flying this airspace are RNAV equipped. NavCanada is taking advantage of this by adding new parallel RNAV routes to reduce congestion and increase capacity and efficiency between Toronto and Montreal. The changes consist of new airways, and new Standard Terminal Arrivals (STARs) and Standard Instrument Departures (SIDs) for Toronto and Montreal, along with a new set of preferred routes. This document explains the changes to the airspace and procedures as they pertain to pilots flying in the Toronto Flight Information Region (FIR). Airways Most of the existing airways between Toronto and Montreal are being revoked, and being replaced with a series of RNAV airways. Despite the changes, the basic traffic flows remain the same: eastbound traffic remains over or south of Campbellford VOR (YCF), whereas westbound traffic remains north of YCF. The new RNAV airways are designated Q or T, as follows: Q Airways are high level RNAV airways, replacing the traditional J airways. T Airways are low level RNAV airways, replacing the traditional V airways. Two existing airways, V98 (eastbound) and V300 (westbound) remain for those not equipped for RNAV airways. All other airways have been revoked. The RNAV airways have been assigned numbers indicating their preferred direction of flight. The numbering scheme matches the altitude assignment scheme: Eastbound flights should use odd altitudes and odd airways. (eg Q951, T781) Westbound flights should use even altitudes and even airways. (eg Q806, T614)

Most of the airways that have been designated have specific origins/destinations intended. For more information, see the Preferred Routes section of this document or the separate Preferred Routes List. The following diagram shows the new Q and T routes between Toronto and Quebec City. This illustrates the scope of the area affected by the airway changes. STARs As of Feb 9, Toronto will have 10 STARs instead of the previous 8. The 10 STARs will cross over 5 outer bedposts. Each outer bedpost now features 2 STARs, one for jets, and one for props. In each case, the lateral routings and waypoints for each pair of STARs are identical. The only difference between a jet and prop STAR is the altitude and speed restrictions. The 5 outer bedposts and their associated STARs are (clockwise): YWT (from West): YWT4 (Jets), ROKTO4 (Props) YMS (from North): YMS5 (Jets), FLINE1 (Props) IMEBA (From East): IMEBA1 (Jets), VIBLI1 (Props) RAGID (From East): RAGID1 (Jets), UDNOX1 (Props) LINNG (From South): LINNG3 (Jets), VERKO1 (Props) (See the diagram on the next page for a better idea of where the STARS and outer bedposts are around Toronto.) One of the key differences of these new/revised STARs is that at most points on the STAR, crossing heights allow for a range of altitudes, instead of a single fixed altitude. This will allow

Continuous Descent Approaches, which provides a more efficient flight profile and subsequent fuel savings. It is very important for pilots to check these altitude and speed restrictions. Once cleared for a STAR, you are expected to abide by all restrictions published on the STAR unless you are explicitly told the restriction is cancelled. For example, when arriving for runway 24R on the ROKTO STAR, ATC will normally give you clearance to descend to 12,000 when you re many miles away from ROKTO. However, you must cross ROKTO between 14,000 and 16,000, and only complete the descent to 12,000 once past ROKTO. Controllers will not state these restrictions when giving you the clearance.

Sample Phraseology: Air Canada 123, Centre. Descend 12,000. Even though you ve been cleared to descend to 12,000, you must still cross ROKTO at or above 14,000, because you have a clearance that includes the STAR. You will be told if an altitude or speed restriction indicated in the STAR is cancelled. Sample Phraseology: Air Canada 123, Centre. Descend 12,000. Altitude restriction at ROKTO cancelled. Another major difference for the 4 new RNAV based STARs from the east (IMEBA/VIBLI and RAGID/UNDOX) is that these STARs begin at the FIR boundary (with Montreal). Inbounds to Toronto from the east will no longer fly airways within the FIR, but will be on a STAR from the moment they cross our FIR border, resulting in easier separation from overflight (airway) traffic. SIDs On Feb 9, a number of new RNAV SIDs will be introduced at Toronto. These SIDs are in addition to the existing Vector SIDs we re all used to, and will be used to improve traffic flow out of the SID in popular directions. For traffic departing south (OAKVL), southwest (ANCOL), west (ARTHR), and northwest (CALON), the traditional vector SIDs will continue to apply. (Green in the Arrival/Departure diagram on the previous page.) Aircraft departing other directions will use the new RNAV SIDs. (Blue on the Arrival/Departure diagram on the previous page.) The new SIDs are hybrid SIDs that involve some vectors as well as fixed RNAV routes. The initial departure instructions for each RNAV SID is the same as the vector SIDs (approx. runway heading to 5000 ). Pilots can expect vectors to one of the RNAV fixes and continue the RNAV route from that point. The RNAV SIDs will aid pilots in getting away from arrival corridors quickly so climbs can continue sooner. The following is a basic overview of which SIDs to use. (For more specific information, consult the Preferred Routings section later in this document or the separate Toronto FIR Preferred Routings document.) Eastbound: DEDKI1 (Jets), VERDO1 (Jets), BOMET1 (Props) Southeastbound: BULGE1 (Jets), RIKEM1 (Props) Northbound: TONNY1 (Jets), MATES1 (Props) Northeastbound: SEDOG1 (Jets) The eastbound and northeastbound SIDs are very long, providing outbound aircraft with a climb route away from other airways all the way to the FIR boundary. The sheer volume of traffic going eastbound has resulted in two separate Jet SIDs being created for eastbound routes, one

5 miles south of the other to accommodate the traffic. Also of interest, the eastbound prop SID is on a third distinct route, separate from the two jet SIDs. The northeastbound SID is also of interest because it has no prop counterpart. This SID is intended for NAT traffic, and as such no props are expected to depart in this direction.- Preferred Routes The Toronto FIR has published a Preferred IFR Routes document, that is located on our website s Pilot Zone ( www.czyz.ca/pilotzone ). Preferred IFR Routes are just that: preferred. They are not 100% mandatory, but guarantee less delays and less reroutes if you use the same routes as everyone else. This list does not contain every possible airport combination, but covers many of the more common routes. If you can t find a route within this document, try to find routes to/from similar locations. If you re ever unsure of a preferred route, you can always ask one of our friendly controllers to select a route. They may not be able to help you outside of our FIR boundaries, but will gladly provide advice on preferred routes within the Toronto FIR. Included here are some of the most common routes that have been changed with this airspace update: CYYZ Departures Southeast, South, Southwest, West, Northwest, North. Most of the preferred routes from CYYZ to points to the southeast clockwise to the north have not changed (other than RNAV SIDs for BULGE and TONNY). Traffic should exit the terminal via the traditional waypoints: BULGE, OAKVL, ANCOL, ARTHR, CALON, TONNY. Northeast Departures to the northeast (primarily North Atlantic traffic) should used the SEDOG1 SID or otherwise file over YXI. East The following are the preferred routes for the common destinations. In general, props will use the BOMET1 SID; jets to CYOW, CYQB and points northeast will use the VERDO1 SID; jets to CYUL and points east will use the DEDKI1 SID. CYOW (Jet) VERDO1 KANIK CAPTL Arrival (Prop) BOMET1 MIVOK CAPTL Arrival CYUL (Jet) DEDKI1 HABBS Arrival CYMX,CYHU (Jet) DEDKI1 REEDO KAVSU ARVIE HABBS COMAU CYQB VERDO1 Q921 PESAC PESAC Arrival East Coast via MIILS VERDO1 VERGA Q907 ATENE MIILS via TALNO DEDK1 Q951 ALONI DAVDA SAVAL TALNO Q975

CYYZ Arrivals As with departures, little has changed for arrivals from the southeast clockwise to north. Use the jet or prop STAR as appropriate (see the STAR section). For arrivals from the east, traffic for the arrivals should be allotted as follows: IMEBA1/VIBLI1 from YXI, YVO, CYOW RAGID1/UDNOX1 from CYUL area, east coast (overflying YUL), CYGK, CYTR Toronto Satellites Departures As with CYYZ, preferred routings west of Toronto have not changed much. Eastbound routes have been revised. The following are basic guidelines. See the Preferred Routes document for specifics. CYHM Eastbound File over SN, then UKPAG SANIN or TESUK BOMET to join an appropriate eastbound route/airway. CYKF/CYXU Eastbound File over YYZ (YWT first for CYXU), then Q905, Q951, Q907 as appropriate. CYKZ/CYTZ Eastbound File DAVSI T781/Q921 as appropriate. A few specific routes: CYOW DAVSI T781 BOMET MIVOK CAPTL arrival CYUL DAVSI T781/Q921 TIGET MIGLO HABBS arrival CYOO Eastbound File TESUK, then T781, BOMET, or TAILS as appropriate Frequently Asked Questions (FAQ) 1. How does this airspace change affect me? The biggest change pilots will see is a whole bunch of new routes being used for anyone flying between Toronto and Montreal. This includes anyone entering or leaving Toronto Terminal airspace to the north, northeast, east, and southeast of Toronto. 2. So how do I know which route to file? Almost any route in the airspace between Toronto and Montreal has been revised to accommodate the revised traffic flow patterns around Toronto. We have published a document that contains preferred IFR routes for traffic departing from or arriving into the Toronto FIR. Please consult this document. If your particular combination of airports is not in this document, try to pick something logical based on airports near to your departure/arrival points. If in doubt, ask a controller to suggest a route.

3. Which STAR should I choose for CYYZ? STARs are chosen based on two criteria: Direction you re arriving from, and whether you are flying a prop or jet. For each arrival direction, there is a major gateway fix close to the entry to the terminal airspace that both the prop and jet arrivals pass over. You should plan to join the STAR at or before this point. The following table lists the various directions, the gateway fixes, and the 2 STARs you can choose for each. Direction (from) Gateway Fix Jet STAR Prop STAR North YMS YMS5 FLINE1 Northeast IMEBA IMEBA1 VIBLI1 East RAGID RAGID1 UDNOX1 South LINNG LINNG3 VERKO1 West YWT YWT4 ROKTO4 4. Which SID should I choose at CYYZ? This depends on a three factors: direction of flight, RNAV capability, and type of aircraft (jet or prop). Controllers will assign the following vector SIDs if one or both of the following is true: You are NOT RNAV equipped, or You are exiting to the South (via OAKVL THORL) Southwest (via ANCOL) West (via ARTHR) Northwest (via CALON BIGBE) Runway(s) SID Procedure 05 / 06R / 06L / 23 / 24R / 24L LESTER8 15R / 15L 33R AVRO6 PEARSON9 If you are RNAV equipped and departing north, northeast, east, or southeast. Pilots need to file the following: Direction Type SID Procedure SID Transitions (Endpoints) North Jets TONNY1 TONNY North Props MATES1 TONNY Northeast Jets SEDOG1 YXI East (CYOW, Nfld) Jets VERDO1 KANIK, BERIK, or VERGA East (CYUL, East Coast) Jets DEDKI1 ART, MIGLO, or OLABA East Props BOMET1 BERIK, MIGLO, or OLABA

Southeast Jets BULGE1 AIRCO Southeast Props RIKEM1 AIRCO 5. What do I do if I don t have RNAV capabilities? What do I do if I don t have an upto-date database of IFR fixes? If your aircraft is not equipped for RNAV, NavCanada has left two Victor (VOR-to-VOR) airways intact: V98 (YWT-YYZ-YCF-MSS) for eastbound flights, and V300 (YOW VIE YSO ARTHR ECK) for westbound flights. Please select one of these two airways depending on your direction of flight. If your route is not parallel to or near these airways that you can use them, file an route using navaids/fixes you can use. Controllers will amend your route or provide vectors as needed around the major routes through Toronto airspace. If you do not have an updated database with the new fix coordinates as of Feb 9, 2012, the best suggestion is to not file as an RNAV capable aircraft. Follow the instructions above for non-rnav aircraft. This will ensure you get a route made up of older/immovable waypoints (ie VORs) that are in your database. This is necessary because some of the fixes in the old database moved a couple of miles on Feb 9 but retained the same name. 6. Where can I get the new charts? As always, charts are available on our website, www.czyz.ca. All the charts within the Toronto FIR on our site are now up-to-date, and we encourage you to download and use these new charts. 7. What do I do if I m still confused or I have another question? We are always happy to answer questions. We realize some of these changes are confusing (they took us a while to get them sorted out too). You can ask any of our friendly controllers online, visit our forum at www.czyz.ca, or email either the FIR Chief ( chief@czyz.ca ) or the Events Coordinator ( ec@czyz.ca ).80