Choppermech1986 wrote: ↑Thu May 23, 2024 1:55 pm
Pre-Covid they had their quirks but were generally reasonable with a few experienced folks that would run a squeeze play when they knew it would work. Now they seem like they're all trainees.
I have a few questions that I'd appreciate a serious answer to, is there an e-mail address that NavCanada has for complaints or do we just do what we've done forever and accept that it is what it is?
1. They're not using the North runway to depart aircraft, so they have US departures taxiing from just about the button of 26R across the airport to depart off 26L and land Corporate and south terminal traffic on 26R only to have them taxi across the airport (and an active runway). This simple problem alone adds a huge amount of workload to tower controllers who are also working ground. Last winter I counted 12 aircraft waiting to depart 08R. Can anyone educate me or direct me to the document that outlines why 26R/08L is not used for departures in YVR, I would imagine it's not NavCanada's fault, but surely they can lobby YVR for say 25 departures off the north side a day to help with congestion?
2. Why no visual approaches? Instead of a controller giving multiple vectors and taking up brain capacity, why not just issue a visual approach clearance?
3. Why not combine both tower frequencies and both ground frequencies instead of North Tower/North Ground and South Tower/South Ground?
4. Why no intersection departures? A good controller would be able to read the play a little and get aircraft out when there was an opportunity instead of taking them all the way down an 11,000' runway.
5. Why when flow is active do I switch across to terminal and it's a ghost town?
6. Why does Terminal hold onto traffic until a 6 mile final? Switch them across to tower early and give South Terminal traffic half a chance of getting the sidestep.
7. Have many of these controllers worked other facilities? As an outsider looking in, I feel as though it would be beneficial for them to see how other facilities are run and the opportunities for improvement.
https://www.navcanada.ca/en/contact-us.aspx Here’s a way to get in touch and ask questions. You can also call the ACC as Braun suggested if you want to talk.
1. Correct, not NAV’s fault. North runway was designed and implemented based on strict guidelines seen here
https://www.yvr.ca/-/media/yvr/document ... ations.pdf
NAV could lobby YVRAA and they can lobby Transport. It’s not lost upon anyone that there are two good paved surfaces to depart from but the airport sets rules and NAV plays within them. Tomorrow, if YVRAA said no more arrivals on the north side, then we deal with it. Will NAV complain? Probably, but the airport and its pavement belongs to YVRAA and they can decide how it’s used.
As for US departures taxiing around, blame it on poor airport design. Why is the domestic terminal on the south side when the rest of Canada is to the north, and why is US/International on the north side when most of the traffic is from the south?
2. Because visual approaches keep blowing through final and causing problems with parallel traffic. As I understand, Transport took that away and not NAV. Controllers know that it’s less workload intensive to pass some traffic, say cleared for the visual approach, and put that responsibility of separation on the pilot, but if someone blows right through and (almost) hits someone, it’ll still be everyone’s collective problem.
3. Tower/Ground North faces north, Tower/Ground south faces south. Controllers look to see what’s going on. It would be comical to have towers and grounds combined and having controllers criss-crossing the cab to see what’s going on. It would be hard to combine these functions and work it all from one chair; the cab is larger than you think.
4.
https://www.tsb.gc.ca/eng/rapports-repo ... p0073.html Here’s your reason - sad to say it actually happened in Vancouver. Thought it happened elsewhere and Vancouver was just a collateral victim. Also, if Transport had their way, there would be no more intersection departures in Canada at all. You’d know that mitigations in aviation typically happen as a response to something bad happening.
5. Skip - don’t have the background or knowledge to speak to this.
6. I don’t think Tower is allowed to offer a sidestep until the plane is within the tower control zone anyway, which is about 6 mi final.
7. Yes, most of these controllers have worked other units. Things like traffic mix, geography, procedures and staffing challenges are all unique to a unit and these add complexities. I don’t think you can learn ways to deal with geography and staffing just by watching others work.
Respectfully (and I mean it, since you’re looking for serious answers), when the system doesn’t work, it’s easy to just say that it’s NAV/controllers’ fault because they’re the front-line worker pilots deal with on a daily basis, but there are usually underlying reasons for why we can’t do something to make the system more effective. Doing the job daily, you can bet that we all think of ways to make things better but usually, restrictions invalidate our creative thinking.
And as a side note, while “squeeze plays” seem to make the system work more effectively, they are also a calculated risk that take mental capacity to monitor and execute even for experienced folks. If it’s not a calculated risk, it’s probably not a squeeze play.
In a system that is constrained by staffing and a fatigued workforce (I will admit fully that this is 1000% NAV and Transport’s fault), would you rather a controller play it safe and make no mistakes, or be risky and make a few mistakes? As a member of the flying public myself, I think there’s only one correct answer here.