<![CDATA[HOLD is a mess]]>Hello,

I tried to execute a non-published hold inbound LFBD LMG2L instructed by IVAO ATC (MARRE FL240 RIGHT TURN 1min30), I initially set up the speed to be 210kts then decided to change the hold speed to 240kts before starting first turn, the aircraft had huge issue to fly the hold, it made a very shallow right turn before trying to catch an imaginary nav on the left (in downwind, so I had to select heading to force it into the right turn back to MARRE), then when I tried to re-programmed it while turning right (as it was totally off set), selected direct to MARRE, it removed the whole approach setup and bugged out the hold by becoming a square that the airplane kept overshoot 😕 the square allows the aircraft to fly the hold after a few pattern but in a very innacurate behavior (it keeps trying to catch up with 90° nav turn so the flight path looks like a giant peanut, see image bellow).

Screenshot 2026-06-28 221000.png
Screenshot 2026-06-28 222155.png

]]>https://community.justflight.com/topic/10799/hold-is-a-messRSS for NodeMon, 29 Jun 2026 10:36:52 GMTSun, 28 Jun 2026 20:23:49 GMT60<![CDATA[Reply to HOLD is a mess on Mon, 29 Jun 2026 02:23:22 GMT]]>Just wanted to share a very specific example of the holding pattern issues some of us have been discussing, in case anyone else can replicate it or has seen something similar.

I was flying the ILS X approach for RWY 15 down here at my home base in Curitiba (SBCT). I executed a missed approach, and initially, the LNAV tracked the profile perfectly towards the CT171 missed approach holding fix.

1e93bf79-451e-4265-9b7d-7402e5476347-image.png

Screenshot (1050).png

However, upon reaching CT171, the system completely failed to establish the hold. Even worse, instead of initiating the published left-hand turns, the aircraft inexplicably banked to the right. After that wrong turn, it completely ignored all time constraints for the holding legs and essentially just flew in endless, uncoordinated circles.

Screenshot (1053).png

It seems the LNAV logic completely breaks down during this specific transition. Bizarre.

]]>https://community.justflight.com/post/51482https://community.justflight.com/post/51482Mon, 29 Jun 2026 02:23:22 GMT<![CDATA[Reply to HOLD is a mess on Mon, 29 Jun 2026 00:45:09 GMT]]>Same happened here, in all cases, published and non published holds, direct, paralel, drop entries, L turns, R turns
I'd say that's a basic for this level of aircraft...

]]>https://community.justflight.com/post/51480https://community.justflight.com/post/51480Mon, 29 Jun 2026 00:45:09 GMT<![CDATA[Reply to HOLD is a mess on Sun, 28 Jun 2026 23:30:28 GMT]]>I agree with both of you. That holding profile does not look right at all.

]]>https://community.justflight.com/post/51479https://community.justflight.com/post/51479Sun, 28 Jun 2026 23:30:28 GMT<![CDATA[Reply to HOLD is a mess on Sun, 28 Jun 2026 21:22:54 GMT]]>@AlexEtz

I attempted two holding patterns during an approach yesterday and also experienced very poor execution from the aircraft, particularly on parallel and teardrop entries. Direct entries weren't as problematic, but honestly, it's surprising to see such a glaring error in an add-on of this level.

It makes you wonder how no one noticed something this basic during the beta tests.

FYI, I've already submitted a support ticket to Just Flight reporting this inconsistency.

]]>https://community.justflight.com/post/51471https://community.justflight.com/post/51471Sun, 28 Jun 2026 21:22:54 GMT