I’m noticing a lot more traffic activity at various airports. Good to see Ini EGCC is making use of the new terminal fingers too. 
I have no idea if any of this was in the patch notes, however, but I’ll take it.
It is based on location, so you will probably get the same shortening logic applied to local aircraft at this stage
I found this helpful guide on their Discord. Somehow I missed it when @GhostlyFrend posted it a couple of days ago.
4 Likes
Is there any official roadmap regarding VFR?
If you’re looking for a specific timeline, I think the devs would say it doesn’t exist. They’ve described where things are and what is next in a couple posts above (@DialexCH , @GhostlyFrend). The track record of the devs for getting things done efficiently is pretty darn good, IMO.
2 Likes
I’m going to bore you all with, what is looking to be, repetitive praises for BATC.
I am enjoying VFR so much right now. It’s beyond cool to be mid-field downwind, request a touch and go with my voice, get clearance, perform the T&G, get mid-field downwind again, request a stop and go, get clearance, hear an IFR flight request departure, hear them get clearance, perform the S&G as the IFR is taking off on a parallel runway, and repeat this sort of thing altering the types of requests and loving the enjoyment of it all.
I’m so excited to see how VFR evolves.
BATC, regardless of its issues, has been such a monumentally important part of my flight simming experience. It is important to not be myopic about it, and remain focused on the big picture here. I’m so grateful for this product.
15 Likes
Not boring at all. Always loved your passion for this hobby sir and it’s great to we’ve reached another step in the ladder of progress.
It’s only going to get better.
2 Likes
As someone who is mainly flying in Europe and South America, I’d like to know if US/UK/AUS must be perfectly finished before they are willing to expand over the globe. Just trying to figure out if i have to wait years, months or weeks before it makes sense for me to buy it. 
2 Likes
I’m flying to KSNS VFR and I made first contact with Tower to inform them I am inbound for landing.
“Super busy here, will get back to you.” was the reply.
That’s interesting.
What is extra weird is I hear no activity on the frequency, so what’s the busy?
Definite wage theft going on there. 
On SayIntentions, I once was VFR and trying to enter PHNL/Honolulu’s Class B for full stop, and got denied, assumedly because it’s too busy and my little prop plane is not priority. I wonder if BATC is mimicking that behavior?
I haven’t yet tried BATC’s VFR, but will do so and compare to SI, though SI was first built for VFR and IFR added later, which is the exact opposite of BATC’s approach. Should be interesting!
2 Likes
Haven’t seen an answer to that question. You might ask on their Discord channel if you don’t get an answer here.
It’s still not decided when new regions will be added. It will depend on how development goes and when it will make more sense to start expanding the regions without slowing down the whole process. However, you can still fly VFR anywhere, it will just default to the UK procedures at this time.
2 Likes
Minor Version 1.9.1 Experimental
General / IFR
Improvements
Taxi Phraseology — FAA & ICAO Split - Taxi and runway crossing instructions now use distinct phraseology for FAA and ICAO regions, making ground communications more realistic for both standards.
Taxi Pathing - tune taxi pathing parameters to improve gate to runway pathing
Runway allocation - Improved runway allocation to better balance traffic across available multiple runways at busy airports
Approach Vectors - Fixed an issue where a “leave on heading” instruction at the end of a STAR could be immediately followed by a contradicting vector call. ATC will now wait until the aircraft reaches the waypoint before issuing the next heading if its required.
Descent Planning - Descent detection now scales based on aircraft speed giving more accurate top-of-descent timing for both fast and slow aircraft.
Data update - Updated runway threshold length data
Data update - Updated airport transition altitude/level data
Data update - Latest airline and pronunciation data from Pilot Portal
Bug Fixes
Traffic Deadlocks - Fixed head-to-tail taxi deadlocks where two aircraft could block each other
Traffic Deadlocks - Fixed departure queue deadlocks that could leave aircraft stuck at hold short points
Traffic Deadlocks - Fixed aircraft removal safety timers not triggering in certain deadlock situations
Traffic Departure - Fixed traffic aircraft failing to push back when assigned active runway changed between IFR clearance and taxi request
Visual Approaches - Depending on approach fix a call to align to localizer which could prevent a proper handoff to tower for visual approaches
Descent Planning - Fixed an issue where altitude changes mid-flight could fail to recalculate top of descent.
CPDLC - Fixed unnecessary POLL request logging in the CPDLC system
Ops Updates
DAOO, LICJ, EDDF, KBZN, KMIC, RJOO
VFR Specific
VFR Circuit
Fixed an issue where ATC could advise a different circuit runway than the one assigned, causing an unexpected runway change on the downwind leg.
Removed orbit count from hold instructions (US/AUS) until the system is more robust.
VFR Arrivals
Fixed the “Request Join” button not appearing when the departure and destination airports are very close together. The button now always shows and validates against the specific airport being called.
Fixed a potential crash when landing at an arrival airfield and requesting taxi back to the runway.
Aircraft Mapping
Added: Carenado C182RG, Carenado C182Q, T-34A, T-34B, ICP Savannah-S, Vision Jet and Kodiak
Initial patch build post release for most common reported issues. More to come!
7 Likes
Minor Version 1.8.7 EA
Improvements
Taxi Phraseology — FAA & ICAO Split - Taxi and runway crossing instructions now use distinct phraseology for FAA and ICAO regions, making ground communications more realistic for both standards.
Taxi Pathing - tune taxi pathing parameters to improve gate to runway pathing
Runway allocation - Improved runway allocation to better balance traffic across available multiple runways at busy airports
Approach Vectors - Fixed an issue where a “leave on heading” instruction at the end of a STAR could be immediately followed by a contradicting vector call. ATC will now wait until the aircraft reaches the waypoint before issuing the next heading if its required.
Descent Planning - Descent detection now scales based on aircraft speed giving more accurate top-of-descent timing for both fast and slow aircraft.
Data update - Updated runway threshold length data
Data update - Updated airport transition altitude/level data
Data update - Latest airline and pronunciation data from Pilot Portal
Bug Fixes
Traffic Deadlocks - Fixed head-to-tail taxi deadlocks where two aircraft could block each other
Traffic Deadlocks - Fixed departure queue deadlocks that could leave aircraft stuck at hold short points
Traffic Deadlocks - Fixed aircraft removal safety timers not triggering in certain deadlock situations
Traffic Departure - Fixed traffic aircraft failing to push back when assigned active runway changed between IFR clearance and taxi request
Visual Approaches - Depending on approach fix a call to align to localizer which could prevent a proper handoff to tower for visual approaches
Descent Planning - Fixed an issue where altitude changes mid-flight could fail to recalculate top of descent.
CPDLC - Fixed unnecessary POLL request logging in the CPDLC system
Ops Updates
DAOO, LICJ, EDDF, KBZN, KMIC, RJOO
Initial patch build post release for most common reported issues. More to come!
7 Likes
First time with the new and improved BATC. Fired up a flight from KDCA to KPVD. Taxying to the active (RW 19), the aircraft in front of me was cleared to line up and wait. As it sat on the runway, a landing jet (flying straight in to RW19, instead of actually flying the river approach as is standard) landed directly in front of it. Before it cleared the runway, the jet holding got permission to take off.
After I took off, things were normal until approaching the ILS for RW23 at KPVD. Instead of the standard vectors used in RL (downwind, followed by a 90 degree base turn, followed by a single vector to intercept the LOC), I received a series of 9 vectors within a couple of minutes. Turn right 30 degrees, a few seconds later turn left, a few seconds later, turn again, etc, etc.
Not impressed…
Hmm… that was a bug they had a few versions ago. I wonder if it sneaked back in.
Be sure to submit log files to them via the BeyondATC Discord - the more they get, the more likely they are to address issues.
1 Like
I do not know about you, but this whole GA mode seems to take a wrong turn for me. So I got this batc 1.8.6 version and my staple flight is KLAS-KSAN. There were some issues a couple of versions back when aircraft would pile up at KSAN RWY27 and the controller giving you endless go arounds - somehow it was fine lately. Not anymore.
I am flying A320 on LUCKI1 approach, which is for airliners only. At LUCKY I get this new command from the controller “minimum approach speed” - i can see on my TCAS another plane around 5-7 miles ahead of me on the approach - Wow, I am excited already! - despite getting full flaps and 127knots at 5 miles from the threshold I overtake a Cessna which was flying LUCKI1 approach this whole time and 2 miles from the threshold I get “go around” with clear runway in sight.
That is not all. I follow the SoCal instructions, which gets me all the way back to LUCKY (why?), instructs to go to 3600, which is below the published minimum of 4000 and forgets about me while I am still flying back north to Las Vegas.
Do not get me wrong - it was fun the entire time!!! Just not super realistic.
