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.

ECON SPD mismatch

Featured Replies

The PFD shows .820, PERF CRZ shows .82, and the FPLN shows .81 for the next and all subsequent waypoints. Does it consider varying ECON speeds as the ISA deviation, head-/tailwind component, FL, and weight change?

Microsoft Flight Simulator 2024 Screenshot 2026.09.23 - 10.22.07.27.png

Microsoft Flight Simulator 2024 Screenshot 2026.09.23 - 10.22.54.03.png

16 hours ago, spottersim said:

The PFD shows .820, PERF CRZ shows .82, and the FPLN shows .81 for the next and all subsequent waypoints. Does it consider varying ECON speeds as the ISA deviation, head-/tailwind component, FL, and weight change?

Microsoft Flight Simulator 2024 Screenshot 2026.09.23 - 10.22.07.27.png

Microsoft Flight Simulator 2024 Screenshot 2026.09.23 - 10.22.54.03.png

This is an issue I have reported on the A350 since release.
It is really disappointing to see yet another aircraft release with the same issue (it is also on the A340).

  • Author
6 hours ago, dectenor2 said:

This is an issue I have reported on the A350 since release.
It is really disappointing to see yet another aircraft release with the same issue (it is also on the A340).

Same here... I would really appreciate it if the team actually committed to fixing these bugs.

  • Staff
On 9/23/2026 at 9:18 PM, dectenor2 said:

This is an issue I have reported on the A350 since release.
It is really disappointing to see yet another aircraft release with the same issue (it is also on the A340).

Can confirm this has been logged and fixed in v1.2.7, along with everything you have previously reported to the team. (I have also made them aware that issue persists on the 340 & 380)

I haven't had the opportunity to thank you for your detailed reports, so Thank you!

Kyle - Community Manager

iniBuilds Ltd. | inibuilds.com

27 minutes ago, iniKyle said:

Can confirm this has been logged and fixed in v1.2.7, along with everything you have previously reported to the team. (I have also made them aware that issue persists on the 340 & 380)

I haven't had the opportunity to thank you for your detailed reports, so Thank you!

Oh that’s just brilliant news.

Thanks so much. Looking forward to trying it when it’s out!

  • 2 weeks later...
  • Author

The latest changelog mentions the following:

FIXED ECON SPD mismatch

Unfortunately, this does not seem correct.

On ground: .83 shown as cruise speed on FPLN page, .85 shown on CRZ page (seems to refer to the speed at/after the first STEP), speed changes with S/Cs

Microsoft Flight Simulator 2024 Screenshot 2026.10.12 - 22.40.38.06.pngMicrosoft Flight Simulator 2024 Screenshot 2026.10.12 - 22.40.40.65.png

In flight: Cruise speed .85, but WPT prior to STEP shows .83 (please verify whether the aircraft resumes the original climb schedule for a cruise climb), no more speed changes throughout the FPLN, regardless of HWC/TWC, ISA, and FL changes.

Microsoft Flight Simulator 2024 Screenshot 2026.10.12 - 23.37.13.76.pngMicrosoft Flight Simulator 2024 Screenshot 2026.10.12 - 23.37.57.87.png

IMG_6968.png

Edited so the info below can be used with shot above.

Edited by dectenor2

@dectenor2

That display value and FMGS calculation are actually correct, let me correct that:

  1. Speed / Mach Calculation: At FL250, an indicated/calibrated airspeed (IAS/CAS) of 281 knots accurately translates to M0.67 (Assuming FL250 ambient pressure of ~376 hPa and a local speed of sound around 602 knots, 280 kt CAS gives roughly M0.672). Rather, my point was the inconsistency in Managed SPD/Mach. At FL250, past the T/C, the system should be holding M0.67 instead of displaying 281 knots, as it ought to be in Mach mode during cruise (Refer to DSC-22-FMS-10-50-20 or Highlighted Picture below).

  2. T/C Target Speed: The Top of Climb (T/C) is the pseudo-waypoint marking the transition from the climb phase to cruise. Therefore, the target speed displayed here should be cruise speed, not climb speed.

  3. SPD LIM Missing: The (SPD LIM) disappears because there is a FLT PLAN DISCONTINUITY in your FMC. Once you clear the discontinuity and connect your flight plan continuously to the destination, the (SPD LIM) waypoint will reappear on the ND/FMC.

Hopefully, this clarifies what's going on each time you fly this route/aircraft.

Cheers!

Screenshot 2026-10-13 054046.png

Edited by OxkyGThaib

  • Author
2 hours ago, OxkyGThaib said:

@dectenor2

That display value and FMGS calculation are actually correct, let me correct that:

  1. Speed / Mach Calculation: At FL250, an indicated/calibrated airspeed (IAS/CAS) of 281 knots accurately translates to M0.67 (Assuming FL250 ambient pressure of ~376 hPa and a local speed of sound around 602 knots, 280 kt CAS gives roughly M0.672). Rather, my point was the inconsistency in Managed SPD/Mach. At FL250, past the T/C, the system should be holding M0.67 instead of displaying 281 knots, as it ought to be in Mach mode during cruise (Refer to DSC-22-FMS-10-50-20 or Highlighted Picture below).

  2. T/C Target Speed: The Top of Climb (T/C) is the pseudo-waypoint marking the transition from the climb phase to cruise. Therefore, the target speed displayed here should be cruise speed, not climb speed.

  3. SPD LIM Missing: The (SPD LIM) disappears because there is a FLT PLAN DISCONTINUITY in your FMC. Once you clear the discontinuity and connect your flight plan continuously to the destination, the (SPD LIM) waypoint will reappear on the ND/FMC.

Hopefully, this clarifies what's going on each time you fly this route/aircraft.

Cheers!

Screenshot 2026-10-13 054046.png

Thanks for your input. It would be great if ini managed to fix this in the A380, A350, and A340 consistently.

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.