PROCEDURES - Streamlined Flashcards
PICTON / BARRIE
Point Outs
The Barrie controller must point out Barrie traffic, which needs to be sequenced, to the Picton controller, who coordinates sequencing.
The Barrie controller must point out all CYYZ, KORD, and Detroit Terminal Area arrival traffic to Picton, so that the Picton controller can coordinate sequencing.
PICTON / BARRIE
Hand Offs
The Barrie controller must hand off aircraft to Picton abeam SANIN or before due to potential crossing track close to the Picton/Barrie boundary.
PICTON / KILLALOE
CYYZ Arrivals
1) Toronto arrivals over YXI/ROSVO shall be sequenced 7 NM in trail, regardless of altitude, for the same bedpost. Hand off must be initiated to Picton no later than at or abeam YXI/ROSVO.
2) Upon completion of handoff and communication transfer, Toronto arrivals are Picton’s control in Killaloe’s airspace for descent and turns to the south.
KILLALOE / PICTON
Point - Outs
5) Point-outs: Killaloe shall point-out to the Picton controller:
a) southwest bound traffic routed via YEE or vicinity
b) KORD arrivals routed over HOCKE.
b) KORD arrivals routed over ECK.
PICTON / KILLALOE
Departures
7) Picton sector shall climb SEDOG departures to FL270. Upon handoff and communication change, aircraft are Killaloe sector’s control for climb.
PICTON / KILLALOE
Toronto Test Flight Areas
8) Toronto Test Flight Areas: For aircraft departing CYZD to enter X, Y, and/or W areas, Picton must climb the aircraft to FL270 or the requested altitude, whichever is lower. Picton must hand off and coordinate verbally for higher with Killaloe, if required. Killaloe must clear the aircraft to work in the appropriate area(s) and determine the aircraft’s EFC.
East Low - Altitudes
The East Low specialty must clear aircraft that flight plan or request a climb into the East High specialty to FL230.
The East High specialty must clear aircraft that flight plan or request a descent into the East Low specialty to FL240.
The REQ ALT function in CAATS may be used to request an altitude in the other specialties airspace.
a) The REQ ALT button is to be used, not the ALT slider.
East Low - Barrie / East Radar Control
East Radar and Barrie do not have control for turns in the other’s airspace
East Low -
East Radar / Barrie -
Direct Routings
East Radar sector must hand off aircraft to Barrie sector either on course or direct any of the following, unless otherwise coordinated: AGNOB, SANIN, IGSEB or TULEG
East Low - CYYZ Arrivals
Hand offs and Control
Picton sector must handoff CYYZ arrivals 100 NM from CYYZ.
Overflights must be clear of arrivals or pointed out prior to handing off arrivals to Simcoe sector.
Simcoe sector has control on CYYZ arrivals in Picton sector’s airspace for speed adjustment, turns and descent.
East Low - CYYZ Arrivals
Sequencing
When CYYZ is landing runways 23, 24L or 26R or runways 05,06L or 06R, similar-type arrivals must be sequenced 7 MIT over each bedpost (one stream 7 MIT over RAGID and a second stream 7 MIT over IMEBA).
When CYYZ is landing runways 15L, 15R, 33L or 33R, PI must sequence similar types 7 MIT to VIDRO, (single stream staggered over the two bedposts). Arrivals must remain over their respective bedposts.
East Low - CYYZ Arrivals
Bedpost Offloading
Where an operational advantage can be obtained, Picton sector may offload an aircraft from one bedpost to the other, provided the NTMU approves the offload, the change is competed more than 80 NM from CYYZ and CAATS is updated with the new STAR.
East Low - CYYZ Arrivals
Runway Changes
East Low must inform East High when the landing runway at CYYZ has changed.
East Low - CYYZ Arrivals
Traffic Balancing
For traffic balancing, Simcoe sector may temporarily delegate the airspace to East Radar sector over the East Radar shelf from 6000’ to FL230. The East Radar controller will work all traffic over RAGID, as well as any other traffic on the PEVNI-ILUSI track (Q806). Simcoe sector will advise East High when the “ER WORKS RAGID” procedure is in effect. East Low will also activate the associated AWF.
East Low - CYYZ Departures
East Low must provide East High with 7 NM in trail spacing between similar types on the same SID or track.
East Low CYTZ Arrivals
Barrie sector may clear aircraft landing CYTZ direct DUSUB without prior coordination with East Radar sector, provided their track takes them south of ILIXU.
East Low - CYXU Arrivals
London Arrivals must be cleared TUKIR Q806 ILUSI YYZ LETOR route.
PI shall handoff CYXU arrivals descending to FL240 and handoff to SI
East Low - CYHM Arrivals
CYHM arrivals must be sequenced 7 MIT to ILUSI.
They are not required to be sequenced with Toronto arrivals; however, they shall be clear of, or above any conflicting Toronto arrival traffic.
East Low - CYOW Arrivals
East Radar sector must point out any jets landing CYOW at FL230 or below to Barrie sector.
Barrie sector must point out any turboprops landing CYOW at FL240 or above to East Radar.
West High - KZOB procedures
Picton and Barrie sectors must ensure that aircraft that enter KZOB at FL260 or below, or that aircraft landing in the West/South specialties, enter the West High at FL 380 or below (or FL360 when Lucan sector is open). East High must ensure that the aircraft does not enter Lucan sector.
This is not in the latest som. Confirm if it’s still relevant
East Low - Other Arrivals
Arrivals to any other destination requiring descent into Simcoe sector must be sequenced 7 MIT for similar types.
West High - Control
All East High sectors have control for turns up to 45° on aircraft they have received from any West High sector. The East High sector initiating any turn is responsible for all coordination and point outs required as a result of their actions.
All West High sectors have control for turns up to 45° on aircraft they have received from any East High sector. The West High sector initiating any turn is responsible for all coordination and point outs required as a result of their actions.
West High - Chicago (KORD) Arrivals
East High must provide West High with one stream 15 MIT (relative to HOCKE), regardless of routing.
East High controllers must leave aircraft on course to enable the West High sectors to determine sequencing requirements for Chicago.
West High - Detroit Area Arrivals
Picton and Barrie sectors will establish 10 MIT, for the same destination, between aircraft destined for the Detroit Terminal area (KDTW, KDET, KYIP, KPTK, and CYQG), unless otherwise coordinated.
Traffic landing at Detroit area airports (Excl. KDTW) and KCLE shall be restricted to cross at or abeam ILUSI or KENLU at FL360 or below.
KDTW is FL380 and below
Montreal - Control
All aircraft will become the receiving sector’s control in the airspace of the initiating sector for turns to a maximum of 30° and altitude changes when the handoff or surveillance TOC is completed, except for aircraft going to Concordia sector.The receiving sector is responsible for all coordination and point outs as a result of their action.
Montreal - Altitude with Concordia
Concordia sector must climb aircraft to FL230. East High must descend aircraft for Concordia sector to FL240.
Montreal - Track Separation
Montreal ACC shall consider aircraft proceeding TUKIR-LIBEM and TORNI- LIBEM as one track for separation purposes.
Montreal ACC shall consider aircraft proceeding LETAK PEVNI and TUKIR GOTIP PEVNI as one track for separation purposes.
Montreal - Barrie Direct Routings
Barrie will not clear aircraft flight planned IPTOS Q921 AGLUK direct AGLUK or points further east (ANCER BAREE CEFOU), without prior approval from Aylmer or Valley sectors. Barrie may seek approval for VERTI direct those points.
Montreal -
Picton and Killaloe
Direct Routings
Picton and Killaloe sectors must ensure direct routings are not issued any further east than ANCER, BAREE, CEFOU, or MIILS.
Montreal -
Ottawa Area Arrivals -
Barrie -
Direct Routings
Barrie sector can assign aircraft direct KANIK without updating CAATS if aircraft remain on or south of the YYZ KANIK track.
Montreal -
Ottawa Area Arrivals -
Barrie
Handoffs
Barrie handoffs to Concordia shall be initiated by 15 NM west of MIVOK (or abeam MIVOK). After a handoff or TOC, aircraft become Concordia sector’s control for left turns to KANIK.
Montreal -
Ottawa Area Arrivals -
Killaloe
Direct Routings
Killaloe sector can assign direct ONDOB without updating CAATS if aircraft remain on or east of the YXI/ROSVO ONDOB track.
Montreal -
Ottawa Area Departures
Spacing
Concordia must provide 5 MIT spacing for similar type aircraft entering the Picton sector on each of the TUKIR TADMO and DESKI ILEMU tracks.
Montreal
Toronto Arrivals
For jet aircraft flight planned FL 230 and below, Concordia is responsible for co-ordinating with Picton by abeam 10nm west of TUKIR to ensure that jet aircraft landing at CYYZ are spaced a minimum of 7 MIT.
When aircraft are flight planned over ILEMU or DUGBU, Concordia may clear the aircraft direct these points without updating CAATS.
West High - Restricted Traffic Flow
Eastbound overflights via MENKO, KENLU, ILUSI, or YSO or that will enter the Picton sector eastbound south of a track from YSO/KENLU to MENKO must be rerouted on tracks either north of MENKO or south into the Barrie sector by Centralia, Oakville, and Lucan.
Eastbound overflights into the East High can go direct TALEB, AGNOB, or SANIN as long as their track remains on or south of the YYZ VOR.
East Low - RNAV Y
The Enroute controller must advise aircraft with an SFI Y to plan for the RNAV Y approach to runway 05 or 23, whichever is on the ATIS.
Box 8 on the FDE allows for the RNAV Y runway assignment. The popup for Box 8 AB will display 23 Y and 05 Y. Select the runway assigned and this will populate to the Simcoe controller’s FDE.
When East High assigns the RNAV Y runway, it will populate on the Simcoe FDE in a lighter shade. The runway assignment can be updated on the FDE if there is a change.
