Third is the charm, finally I managed to fly with my registration number recognised as a registration number.
I ran into 0 bigger issues, though Approach was always a bit late giving further descent instructions, so I had to 5-7% instead of 3ish. Again no big deal, I’m quite satisfied so far.
Two hours later, as I was trying to demonstrate BATC to my grandson it all went completely borked. Wouldn’t talk to me, kept losing connection and closing with the fatal error and in the end we abandoned it all with better things to do.
I’ll have another go tomorrow when I’m sure it’ll all be okay - it’s not the first time everything goes wrong when he comes round…!
Today I repeated the LIML-LIRF flight which created problems in the approach as BATC never passed me to the Tower.
With last BATC patch of this morning, the flight went very well, correct approach, passage to the Tower and after landing passage to the Ground for the GATE request.
What to say? Thanks to the BATC developers for their efforts in correcting the program’s issues.
Hello everyone,
I have installed the latest version of BeyondATC. - My procedure: I create a flight plan in SimBrief and then load it in MSFS 2020. BeyondATC reports that it is connected to the sim. My pilot ID is also entered. BeyondATC loads the flight plan from Simbrief and off I go.
I take off directly on the runway, so no pushback or taxiing.
But instead of BeyondATC, I only hear the standard ATC from the MSFS 2020 during the entire flight - only at the very end (after touching down on the runway) does BeyondATC speak up and tell me that I don’t have permission to take off here (when landing)…
What am I doing wrong?
Thank you 
Do you therefore just jump straight to the tower/departure channel on BATC? I did this the first time I used it and it messed up the flow of information from BATC. Now I always start with requesting clearance, then ground for start up and pushback, then taxi, finally switch to tower for take off.
You definitely want to turn off all ATC options in the Assistance Settings when using ATC. I don’t recall the list, but I think you can search on “ATC” to find them all.
I think if you want to skip IFR Clearance, Pushback and Taxi, the best solution is to take off and after take off activate BATC, it should take into account where you are and follow you until you land.
Yes, you can do that at any stage of your flight (climb, cruise etc). Handy for VATSIM users too, though I don’t know if it works the other way, ie, flying into a VS-controlled area rather than out of one.
Is it only me, or do you get your descent instructions quite late too? I don’t have many flights yet on BATC, but it always came pretty late. For example today:
I got the initial descent instruction from cruising altitude to FL270, then got left there. I passed a number of waypoints in the STAR (still at 270, while these points had constraints lower than that), so by the time I was told to descend to 9000’ I had to do a 4000fpm dive to catch up with the arrival procedure.
I tried to ask for a lower altitude (as “request further descent” is not something BATC recognise) but was told “unable at this time”.
In all four flights I did with BATC I did tell them I am ready for descend, just a few nm before calculated TOD. I was cleared and descended as per flight plan.
I’ve been getting calls from BATC to inform them when I’m ready for descent perhaps 10-20 nm from the TOD on my flight plan (SimBrief, flying PMDG B737 (BBJ)). Very happy with this as it gives me time to get myself ready, then call ready for descent as the TOD approaches.
No, no, that’s not what I’m talking about. I was cruising on FL430, told ATC I’m ready for descent and got FL270. I got down to FL270 and stayed there even though I passed waypoints where according to the star I should have been below 240 then 220 and then 200 and I was still being kept on 270. Like ATC forgot I existed. Then I got handed over to approach, who still kept me on 270 for a while, I passed even more waypoints with an altitude constraint that I should have been below of and only then I got told to descend to 9000’…
I sometimes think it might be a disconnect with what BATC says vs. what BATC means. I do think there are more than a few instances where BATC tells you to ‘Expect the Vinta3 arrival…’ when in actuality BATC is instructing you to ‘Descend via the Vinta3 arrival…’
We plod along waiting to hear ATC actually clear us to descend not realizing they already did but they used the incorrect phraseology in the initial instruction.
I don’t say this as a 100% certainty, just a suspicion/theory.
Well yeah, thats the biggest problem I have with it. Even if I can start the descent anytime it just give you and intermediar altitude and then just keep you there for way to long and also sometimes at the end it gives you lots of really small step descents. The whole approach system is a mess and its pretty evident if you fly to an airport with no star and it has to do all the calculation itself.
That actually could be the case, but I just wonder how to tell… 
That makes total sense!
Same on the SID. “Climb to FL100”. I’ve climbed straight up, and also tried climbing respecting the SID constraints. BATC doesn’t seem to bother.
Not once have I heard “Climb unrestricted…” or “Climb to FL100 now” which would mean correctly ignoring the restrictions.
I cant completely remember but I think I’ve actually ask ‘are we cleared to descend…’ before and they replied ‘Descend via the XXXXX arrival’. Now that does not necessarily mean it’s what they meant the first time but I think they did in fact specifically instruct me to descend when I questioned the instruction.
Right, it also does it with the initial vectors on departure. It will tell you ‘Turn left heading XXX, vectors to XXXX. Then resume own navigation’. In actuality it is telling you ‘Turn left heading XXX, proceed direct to XXXX…’ It is in fact giving you a clearance to the initial fix it’s just saying it in the wrong way.
I wonder if it’s something to do with the Simbrief flight plan? On the few airliner flights I’ve done (in Europe) I’ve always got the descents on time or a little early, but then been instructed to descend in line with the Star restraints, which are shown in the FMC as well as on the flightplan (I think, never really had occasion to check).
I have tried just using the Vnav and setting the IAF altitude as the target - BATC just seemed to keep up with me, giving me descent instructions at the appropriate times. Got me down for unhurried arrival just fine but I can’t help thinking this isn’t quite right.
The one time it went wrong was low-level IFR in the Bonanza when it gave me descent far too early and as I was in solid IMC the first indication of trouble was when the “500ft” warning went off, I popped out of IMC and immediately slammed into high ground!
