Unfortunately, we have little control over how the jetway connects to the aircraft. We assign contact points that should allow for the jetway floor and hood to sit flush with the aircraft, but the actual jetway connection behaviour seems to vary from jetway to jetway, scenery to scenery. Sometimes we can even see different jetway behaviour just by connecting > disconnecting > connecting the jetway. It is something we are aware of, and we would like to have it improved, but we're unsure if there's anything further we can do from our side. Mark - Just Flight

Thanks for the feedback. We do have this logged on our internal trackers to improve in a future update. Mark - Just Flight

It's tricky to know what the exact cause is without seeing the exact behaviour in the sim, but under the IAS/M window, if one were to set the NORMAL/V2 selector to V2 when in flight, that would cause dashes "---" to appear on the IAS/M window. In that scenario, the only way to rectify that would be to move the selector back to NORMAL. Mark - Just Flight

Thanks for the feedback. At the moment, we don't have any plans to integrate the MSFS 2024 EFB features into our EFB/tablet, however, we have logged this on our internal feature request tracker for our development team's consideration in future updates. Mark - Just Flight

If you generate a SimBrief OFP, at the very bottom of the page there should be a "Flight Plan Downloads" list and in it a "Just Flight F70/F100" download option: [image: 411e791c-b24b-4a6f-9366-2e84ef976c76.png] That option will download a .RTE file in the format used by the F70/F100. Hope that helps. Mark - Just Flight

It all depends how effectively you can equalize your middle ear pressure by manually opening your Eustachian tubes. For pilots who have trained their muscles to open their Eustachian tube on command, then even 3,000 ft/min should be doable as along as you don't have a cold or a stuffy nose. However, for uninitiated passengers, the differential created by climbing or descending at 1,000 ft/min for only a few minutes can become considerably painful. I hope that answers your question This is also a great example of what draws me to aviation, because few other hobbies require knowledge of engineering, navigation, human biology, and fine motor skills, all in one place.

@Mark Ok so that setting was selected. In this new flight I've deselected it and the constant calling has ceased! many thanks!

@ScotchMist OK, lets put it differently. In all other aircraft I cab select the ILS27 final, starting with TIDVO. With this aircraft, I always get the SPL, AMSxxx waypoints in between. How do I load the ILS27 approach with a direct to TIDVO instead of the SPL as first point?

Thanks for replying. Will keep an eye out.

We'll pass your comments on to our exterior artist, as artwork is all dark arts to me! Regarding points 3/4, the headrest visibility is toggled using the livery_config.ini file that can be distributed with your livery. Instructions on that file and how to distribute it can be found in the Paintkit FAQ: https://support.justflight.com/en/support/solutions/articles/17000151438-f70-f100-professional-msfs-paintkit Mark - Just Flight

It looks like the correct TACAN frequency for the LKH TACAN is 39X. Mark - Just Flight

I'm not able to replicate PROF mode disenaging if clicking the T-P fix in the flight plan, however, I suspect you may be describing a similar behaviour that is reported here: https://community.justflight.com/post/51616 That is something we have logged on our internal trackers and is actively being worked on. Mark - Just Flight

The Navaid Remote Tuning will tune into any Navaid that is within range of the aircraft; then the Navaid will remain tuned until it is out of range of the aircraft, at which point the aircraft will start to search for new navaids that are within range. Having a quick look at this in the sim, the ABA VOR has a range of approx. 190nm, so if the aircraft is out of range of any other navaids, the aircraft should automatically tune into ABA VOR when it is within 190nm. It did automatically tune for me, but I only did a quick local flight rather than the same flight as you mentioned. I've wanted to do some Caribbean flying in the F70 for a while, so I'll add that flight to my list and keep an eye out for any oddities with the Navaid Remote Tuning! Mark - Just Flight

@Mark I had it set to have GSX take care of ground handling and I cannot disconnect the jetway manually under that circumstance, so that’s probably why. It didn’t disconnect before pushback if I recall correctly

Never mind. Avionics is configured through the EFB. Problem solved.

I'd gladly pay for the tbm to be at the other BS aircraft level

I experienced this for the first time. I was flying in the Caravan without cargo pod, with no GPS, VOR to VOR. [image: 5b593bd9-5172-4279-846a-ba4bf391b734.png] At #1, it switched to ROL for the first time. It took me a while to realize what was wrong, but I was eventually headed in the right direction. Then it switched to ROL again, by #2. Back on track, and no further problems. As I flew over the VOR (#3), it switched to ROL, but this is, as I understand it, the correct behavior, when briefly losing the signal. As I was slightly adjusting the heading away from the VOR, I had an idea. The first two times it switched to ROL, the heading bug was still pointing north, as thas was my takeoff heading. After the second disconnect, I finally centered the heading bug, and had no problems after that. So I now set the heading bug 90° to the right, just to test. It again switched to ROL at #4. I, yet again centered the heading bug, and I reached my destination without any more disconnects. Anecdotal, of course, and it might be purely coincidental, but for all my unexpected switches to ROL mode, the heading bug was not centered, and while it was centered, I had no switches. Further testing needed.