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: