September 1, 20241 yr I think something that would help with the vector issues is being able to report 'filed in sight' much further out instead of only giving that option a couple miles away. That would alleviate the need for the bad vectors and you can position yourself visually or intercept LOC, etc. Eric i9-12900k, RTX 5070ti OC, 32GB ddr5 5600 RAM, 2TB 980 Pro SSD, Titan 240RX AIO, Samsung CRG90 49", Win 11
September 1, 20241 yr 3 hours ago, Flic1 said: I think something that would help with the vector issues is being able to report 'filed in sight' much further out instead of only giving that option a couple miles away. That would alleviate the need for the bad vectors and you can position yourself visually or intercept LOC, etc. That's just a work around though, if you have to do that you may as well just ignore ATC and do your own thing. Which is what I tend to end up doing on descent anyway using BATC. G Gary Davies aka "Gazzareth" Simming since 747 on the Acorn Electron
September 1, 20241 yr 5 hours ago, Flic1 said: I think something that would help with the vector issues is being able to report 'filed in sight' much further out instead of only giving that option a couple miles away. That would alleviate the need for the bad vectors and you can position yourself visually or intercept LOC, etc. Exactly my thoughts. 99% of places you’re going to flying regularly in an airliner will have an ILS or some kind of instrument approach, so once you’re within range you can just sort yourself out. Usually that still means arming the LOC and GS etc but not necessarily under vectoring control. Like you, I’d rather take control of my approach than aimlessly drawing circles in the sky with vectors that will never get me down.
September 2, 20241 yr I hardly fly in the US. But with the few flights I had, I can confirm that vectoring for visuals was impracticable (not representative 🙂 ). Vectoring for ILS works much better (by now). Although BATC still has it's vectoring issues, when your route lets you approach an airport (around) the same hdg, the landing rwy has. Letting the pilot simply fly straight in and get him down to a feasible height in time seems to be still a problem then. I wonder what's the best distance for your last (route) waypoint from the destination airport to help BATC handle these approaches. Near the airport (within 20NM)? Or farer away (60NM or more)? Also BATC still has it's issues with SIDs and STARs when it is changing the active rwy. Sometimes the chosen procedures are way off. But as already said, BATC is improving, and I hope for more updates and patches. 🙂
Create an account or sign in to comment