Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

A350 UTC data gone rogue

Featured Replies

Long haul from Kuala Lumpur - 2 hours in and this is the UTC data. What’s going on? If I re-insert the landing airport (EGCC) and STAR then, for a short while, the UTC info corrects, but it goes rogue again quickly after. Why? On Xbox. 

IMG_4666.jpeg

Edited by BoeingSpeedbird

Same issue, on xbox as well. 

Before T/C, all fixes UTCs seemed fine and logical. Only issue was DEST EFOB warning was displaying. Predicted fuel at destination was about -75.  

Fixes after T/C seemed fine as well, until my first step climb, which was displaying UTC times anywhere from -30 to 30. Once auto step climb performed my first step climb, that is when all UTC times went “rogue”. 

I deleted all step climbs from “STEP ALTS” in the perf page and re-inserted STAR and approach. This brought back the VNAV path on the bottom of ND. UTC times are now jumping back and forth between logical times, and somewhere between -30 to 30 with DEST EFOB warnings turning on and off. After a little, it eventually goes back to the way the picture shows above from OP. Only way to fix is to re-insert STAR and approach from which point the cycle repeats itself. 

I purchased the A350 yesterday, and my first flight (KATL-KDFW) to figure the airplane out, did not require a step climb, and everything went smoothly. This leads me to believe it’s an issue with step climb. 

Any help or suggestions would be greatly appreciated!

Update: After going to F-PLN page, clicking destination airport, and only selecting my intended runway (STAR stayed) then inserting into flight plan, everything seems to be normal. I even inserted a step climb later in the route and there are no erroneous UTC times. No more DEST EFOB errors either. Something I didn’t notice either was my cruise speed dropped to M.81, but now is back to M.85.   Honestly not sure what I did, but any explanation/advice to avoid this in the future would be awesome. 

Edited by AirplaneEnjoyer
update

Thank you!

I’m new to this whole forum, where can I check for updates on when it’s fixed?

6 hours ago, IniJamir said:

It's a known issue, being investigated.

 

  • Staff
14 hours ago, AirplaneEnjoyer said:

Thank you!

I’m new to this whole forum, where can I check for updates on when it’s fixed?

 

Usually I try my best to get around to responding with updates on issues as I get informed about them or inquire. It'll either be confirmed in here or with the release of the update changelogs. 

On 3/17/2026 at 12:25 PM, IniJamir said:

Usually I try my best to get around to responding with updates on issues as I get informed about them or inquire. It'll either be confirmed in here or with the release of the update changelogs. 

Was this issue fixed? @IniJamir

Thank you

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.