NavCanada recently issued an Aeronautical Information Circular that all controllers should be aware of: AIC 12/21 https://www.navcanada.ca/en/5aic_eng_2021_12.pdf
To summarize, due to operational irregularities that have occurred, controllers cannot create a transition from an open STAR to an RNAV Approach.
(An open STAR is any STAR that does not share a common waypoint with an IFR approach procedure, but usually ends with either a vector or a hold.)
If there is no common waypoint between the approach and the STAR, the controller MUST VECTOR the aircraft towards the final approach course.
As an example, consider an aircraft on the DISCO arrival for CYYJ (Victoria, BC). (All diagrams are posted below.) If the aircraft is planning an ILS to 09, there is no transition point to the ILS 09 that is on the STAR, so the controller MUST vector the airplane to final. Conversely, if the aircraft is planning ILS to 27, LAFFO is on the ILS 27 and thus a controller may clear the aircraft "Cleared ILS Rwy 27, LAFFO transition."
Example of what is not permitted: "After OMINU, direct BRANY, cleared ILS 09." This transition must be made using vectors.
By contrast, many airports are now publishing transitions to the approach, such as CYWG (Winnipeg, MB). If an aircraft is on the BEFAN2 for the ILS 36, note that the waypoint BOTUR is on both procedures, the STAR and the approach. Therefore, a controller can clear an aircraft "Cleared ILS Z Rwy 36, BOTUR transition."
Basically, we cannot create transitions that have not been published.
(Another further aside, and one of the reasons we can't do this, is that turns made at a fix using RNAV cannot exceed 90degrees, whether published or controller made. We cannot issue a direct-to a fix that would require an aircraft to make a greater than 90degree turn to join the next leg of the flight plan or instrument procedure. Published procedure turns and Radius-To-Fix legs are exempt from this limit as they are specifically evaluated for their turn radius.)
I hope I made this explanation fairly clear. please feel free to ask questions if something does not make sense.
Can I also highlight one other thing: Please ensure you DO NOT CLIMB UNTIL CLEARED BY ATC.
It is appreciated if you file your step climbs, as we can work that information into our planning. But do not commence the step climb without authorization from ATC.
And hand-in-hand with that, please don't expect ATC to always read or remember your step climb requests. Just make the request with ATC when you are ready for your step climbs. (Different fuel burns/last minute load changes can cause step climbs to be delayed, so we won't automatically issue one until it is requested.)
"Moncton Centre, ACA123, request climb FL380."
You may be told to standby (briefly), while we ensure that level is clear above you and ahead of you.
Hopefully that went without saying for most, but I hope someone reads that and learns something. 🙂
Hello VATCAN, Our VATCAN TeamSpeak is being relaunched! This relaunch and revamp will allow for additional integrations to take place between our TeamSpeak server and the VATCAN website. But we need your help to do it. Effective 11:30pm EDT 13th September 2021, all members connecting to the VATCAN TeamSpeak will need to integrate their VATCAN.ca Profile to the VATCAN TeamSpeak. Here is the steps on how to connect: 1. Ensure TeamSpeak is not running. 2. Visit https://vatcan.ca/my/integrations and login if required. 3. Under the TeamSpeak section click on Generate Code. 4. Click on Connect Now. If clicking Connect Now does not work, continue with the following steps. 5. Note the generated code, you will need it later. 6. Open TeamSpeak. 7. From the Connections menu, click Connect or press CTRL+S. 8. Under Server Nickname or Address, enter ts.vatcan.ca. 9. Under Nickname, enter the generated code you noted in Step 3. 10. Click Connect. Once your VATCAN.ca Profile is linked to TeamSpeak, you can re-connect using your preferred nickname. We hope this added integration between VATCAN.ca and the VATCAN TeamSpeak server will benefit the VATCAN community and its membership. If you have any questions do not hesitate to contact the VATCAN Executive or your FIR Staff. Thank you, VATCAN Executive
VATCAN Tech Team - Position Posting
VATCAN is currently looking to grow our tech team to work on some unique projects. Some of the projects include the current VATCAN website, the VATCAN bookings system, and a few other upcoming projects.
Existing VATCAN Webmasters: Should you choose to apply, you will not need to leave your current FIR, you can help out VATCAN on the side.
Experience working with Php, HTML and CSS or
Experience working with .NET and/or React
Experience working with SQL (MySQL / MariaDB)
Intimate knowledge of PHP, HTML and CSS; or
Intimate knowledge of .NET and/or React (SignalR is a plus)
Experience working with separate frontend & backend applications is a plus.
Note: Don’t be afraid to apply! We are not specifically seeking individuals with real-world credentials, while having them is a plus, it is not a requirement. You won’t know until you try!
How to apply:
Send an email to VATCAN7 (email@example.com). Email should include the following:
Name and CID
Any previous experience (GitHub, Gitlab)
Summary of your programming skillset.
If you're planning on changing either your altitude or cruising speed, you need to write your cruising speed AND your planned altitude following the forward slash even if you're only changing one of them. For example, you would write "TRN/N0450F370".