Hi Mark, I'm trying to get me head around the lvars in the Vulcan which I got yesterday so I'll come back to this in a little while. I think from your reply you may have missed what I was trying to point out and that is, this only happens if I spawn at the runway ready for take off or use the efb ready to take off option. If I go through the rear cockpit config then through the startup in the front cockpit of course then this problem does not happen, so to me it's not a control assignment as it's the same in both cases. I've come of the Vulcan now to look again at the Hawk configs. I do have SET ENGINE 1 FUEL VALVE on my left eng switch and GTS/Apu on the right eng switch of the TCA Airbus quadrant.

We're not aware of any GPS issues in our PA28s with the latest builds. My first suggestion would be to complete a fresh reinstall of the affected product(s), ensuring that you have the latest version installed. The latest version of the Arrow III is v0.11.3. If the issue persists, then I would recommend trying this with only the Arrow III in your Community folder. That will then tell us if there is a conflict with another mod. If you rename your Community folder something like "Community.old" and then create a new one named "Community" and run the Arrow III installer, that will allow you to test this with an empty Community folder and then revert back to your old Community folder without having to reinstall everything. If the GPS powers on normally without anything else in your Community folder, then that points towards a conflict with another mod in your the "Community.old" folder. If the above solutions don't work, could we kindly ask you to raise a ticket with Just Flight Support at the following link, and one of our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

A little update and I don't understand the results, the ctrl + G has worked in the vulcan but in FBW A320 for example, it's never worked and I'm fairly sure I tried it in the JF Hawk and it didn't work there either. I'll retest that. I have reloaded the FBW A320-Dev and ctrl+G does not work so it seems to be aircraft specific whether it works or not, is this something down to the publishers? Just Flight replies appreciated on this thought.

I dont know why it showed the wrong airport- I have 2 profiles and both were giving the same error even though I was parked at the gate of major airports (One was KATL, the other KMEM). Im going to create a 3rd profile and see if it keeps doing it...

@kityatyi said in British Aerospace ATP: I am hoping Just Flight will at some point consider developing a study-level ATP. That would be amazing! A study-level ATP from Just Flight would definitely be a great addition to the sim world.

@Mark Thank you for your reply, personally and reading the forums it seems that the stability and performance in general have improved in SU16. Hopefully this is the right update that was needed to bring fs traffic to Xbox. Thanks again.

Hi, Ticket filed. Cheers Stefan

Thanks Mark. Indeed I'm wrong, the speed is TAS not KIAS. Kind regards.

Thank you, Mark!

@galeair Just as an FYI if you'd like to include the LF 507 data in your spreadsheet, I have included them in my checklist (it's not currently live at time of posting but should be within 12hrs). BAe 146-RJ70/RJ85/RJ100 Normal Checklist

@DrZGard I thought you were joking but it really stands for North America Not as per the manual.

I think the reason why you're seing small airfields in the current build is because some of your add on airports are in the small category. This is a known issue and has been fixed in the next build. The work around is to remove LOLK or any other small catgeory airports from your airport manager and they wont be included in your routes. Not ideal but its the current fix. As mentioned, this will be fixed in the next update.

I see it! My palate thanks you.

Thank you! That’s great, means I can still use Navigraph weather/runway data, etc. I like this approach.

Silly me - thanks Pete. Ticket created.

Your best bet would probably be to contact Just Flight Support. They can probably provide an answer to this kind of problem. https://community.justflight.com/topic/2/product-support

There’s a site called the Internet Movie Plane Database, which you can check out, for these kinds of questions.

Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage.

Fixed, luckily another user had the same problem and he posted this solution and it worked for me Create directory "Microsoft Flight Simulator" inside directory "C:\Users%USERNAME%|AppData|Roaming" Copy file "UserCfg.opt" from "C:\Users%USERNAME%\AppData\Local|Packages\Microsoft.Limitless_8 wekyb3d8bbwelLocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove