Takeoffs not being recorded in logbook when using 3rd party ATC (ie not using MSFS default ATC). Landings are counted

User Support Hub User Interface & Activities
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

Yes

Brief description of the issue:

When using Beyond ATC I do not need to contact MSFS ATC for departure, or taxi etc. Not sure if this is the reason why, but every flight I use Beyond ATC, the takeoff is not recorded in the MSFS logbook. It seems as if the flight hours are counted and the landings are counted, but for some reason, not the takeoff.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

When using Beyond ATC I do not need to contact MSFS ATC for departure, or taxi etc. Not sure if this is the reason why, but every flight I use Beyond ATC, the takeoff is not recorded in the MSFS logbook. It seems as if the flight hours are counted and the landings are counted, but for some reason, not the takeoff.

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

? It is occurring in the current build @ 10/10/24

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

2

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

It’s not a Beyond ATC issue. It’s an Asobo default ATC issue. I wrote a post about this a few years back.

Logbook not updating after patch - #497 by hobanagerik

The sim tracks progress of your flight, and the current stage of your flight can be see in that “Objectives” top toolbar menu item. If you take off, but the sim doesn’t think you are ready to take off, chances are it won’t log that as the “Objectives” window will still say you should call tower to request clearance. You didn’t because you either don’t use Asobo ATC, or are using an external tool, so it doesn’t log. I have found that landings tend to log more reliably than take-offs do. For example, I might be doing traffic pattern practice, and I might see 1 take off but 23 landings. Very common for me.

Another example is at un-towered fields. Let’s say you startup, and taxi towards the runway, and you have the blue guidance chevrons on. If you don’t follow those precisely, it won’t detect when you enter the runway, and consequently it won’t log you taking off. You may even see those chevrons from the air. If you follow them, right up to the point you enter the runway, and they disappear, it will log your takeoff, and you should see in the Objectives top menu this change in status as you do so.

In some rare cases, and this is greatly affected by the airstrip layout, even when you drive through those chevrons they sometimes don’t disappear. I have ended up taxiing around trying to get them to go, and sometimes it takes traversing the runway from one end to the other to find the sweet spot where your Objective status changes from taxiing to the runway, to entiering it, then taking off.

I hope 2024 has made some progress with unhooking what should be a simple process of detecting when your wheels have left the ground from the ATC workflow.

If relevant, provide additional screenshots/video:

1 Like
3

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

4

I know that other thread I linked to has been marked as resolved, but this issue still exists. But I wouldn’t go so far as to say it is a bug, more a design issue. As in it may be working as intended, but it was designed poorly from the get go, and needs tearing up, and re-doing after a new design is thoroughly researched.

There are many hoops to jump through because the ATC system is tightly wrapped up in the status of your flight, and that in turn is linked to log book data being recorded or not. And you can get it to work, reliably even, but you have to jump through its hoops.

It should be much simpler than it is, really.

1 Like
5

I have noticed this a lot for multi-leg flights using the A300 and A20N v2. The first leg will always register and show as 1 takeoff and 1 landing when I end the flight which pulls up the logbook entry. But if I chose continue to do another leg without exiting to the menu and use the default MSFS ATC to properly request the takeoff, all subsequent legs will show up as 0 takeoffs and 1 landing. So I don’t think it is completely limited to just 3rd party ATC causing the problem. Prior to sim update 15, I had been able to do this and it would register the takeoffs if I used the default ATC but no longer

6

I’ve experienced this, primarily (but not exclusively) when using BATC. I reported it on the BATC Discord channel maybe a month ago. But @Hobanagerik’s post made me remember other occurences I’ve seen without BATC.

1 Like
7

Yes, BATC’s involvement here is coincidental. Think of it more as “not using the Asobo ATC”, and it would apply to any external tool, such as SayIntentions.

The Objective status of your flight is updated through a number of mechanisms. Contact with Tower/Ground/CTAF initially, then as your plane shuffles about the airport it auto-updates, till you reach the hold short point that the sim expected you to follow. If you don’t have those blue chevrons on, that can also cause the sequence to trip up, such as taxiing to the wrong end of the runway, or using an intersection part way along it.

8

Ah now hang on. I have a shortcut key to toggle the chevrons if needed and I noticed that they don’t appear after the first landing, even after requesting taxi clearance and being given the departure runway and taxi routing by the default Asobo ATC for the second takeoff. When I get to the runway it seems to know as I can then request takeoff but still the chevrons don’t show up for entry onto the runway

9

Do you have the same issue if you follow the OP’s steps to reproduce it?

YES

Provide extra information to complete the original description of the issue:

Issue with MSFS and the lack of recorded takeoffs in our logbook has been ongoing for ages. Without proper communication with MSFS ATC, the takeoff will not be recorded. User @hobanagerik has explained this well, so I won’t repeat it.

10

If its a long runway, you may find the turn off is not where you expect. I’ve had some where I had to taxi for a minute or so after landing before I could see the blue chevrons in the distance.

11

I never use ATC to request a landing or indeed after landing to request taxi to gate as it then won’t let you request a new takeoff once parked at the gate - gets stuck on ground services window. In-built ATC really needs fixed but doesn’t sound like it ever will be

12

Flying GA I have stopped at the parking spot, and then requested taxi to the runway, but it may be airport dependant. There are a few where it behaves very oddly. Like being handed off to Ground, but the Ground menu doesn’t exist, and you can’t pick anything. Thrown into a logical dead end.

1 Like
13

I have just recently started flying the Inibuilds A320 V2 and have experienced the same thing. I assumed it was because the aircraft uses Simbrief for flight planning, so I did nothing with the built in flight planning or ATC. Landings are being logged OK.

Quite frankly it does not bother me but yes, it could/should be made better.

1 Like