1
The Flight Deck / Re: MOST VATSIM pilots will mess this up. Are you one of them?
« on: March 13, 2024, 03:35:43 AM »On the flip side of this as a controller, I go into an FNO *knowing* that this kind of mistake is going to happen all night long, and regard my responsibility as a controller to adapt accordingly. Surely this mistake didn't just start happening during the event. Frequent controllers of this airspace must have known that this was a common mistake, and likely to be a problem. If that had been me, I perhaps would have been assigning headings off the IAF's as opposed to just giving cleared approach. (eg: instead of "At SEAVU, cleared ILS 25L" I might have done something like "Depart SEAVU heading 245 (or whatever it actually is, I don't have a protractor handy) cross <Whatever fix is appropriate> at or above <some altitude> cleared ILS 25L"). While I get that this does take a touch more time on frequency, and isn't what you would hear in real life; it takes the routing out of the pilots hands. Regardless of what they're flying or how their FMC is programmed, I know that the vast majority can twist a heading into the autopilot and engage heading hold. I know reasonably well at that point what they are going to do. Plus, this is easily followed by even the simplest of default aircraft with no navdata or even no RNAV at all. And yes, I know, there are still going to be pilots that don't actually know where SEAVU is or mess up the turn, but those pilots are going to mess it up no matter what I say, and at least (I hope) it will be a shorter list. Heck, this is why we seem to default to vectors to final in the first place, right? I'd bet the time taken on frequency to give slightly more verbose clearances is offset by the number of pilot mistakes I won't have to fix.
I appreciate you taking the time to post and your openness.
Almost every STAR at ZLA’s popular airports (including LAX, LAS, BUR, ONT, PSP, SAN and SNA) feeds to an instrument approach. Vectors to final are no longer the default.
Pilots are expected to fly these instrument procedures correctly. Using vectors to avoid expected mistakes doesn’t fix the problem. It sidesteps the issue and shifts workload to controllers at the expense of pilot education (and controller sanity).