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?

Hi,

Thanks for your report. I will forward this to the team for further clarification.

Thanks again!

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?

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).

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.

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!

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!

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

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.

This page in general across all the ini airbus fleet is very buggy and error strewn.

Here from the A380:

Predicted speeds in cruise given in IAS - 281. Until at ELIVA where it suddenly goes to 0.67 Mach for no reason.

Also inconsistent use of “ for indicating the same speed as above.

The first waypoint on the page should always give the speed numerically. Then it should always be ‘’ unless there is a change of flight phase or speed. Or if you were to climb higher than here, at the first waypoint where the predicted speed would be in Mach rather than IAS.

Again which is tied to when the IAS becomes equal to the target Mach, not just at some predefined altitude.

Likewise the display on the FCU and FMAs of speed or Mach, the correct one is displayed depending on whether the aircraft is targeting a speed or a Mach number, it doesn’t just change from one to the other at some pre defined altitude.

This is bugged on a350 as well of course, as are the things like those mentioned above on the F-PLN page, but really hoping they’ll be fixed in 1.2.7

So in this shot going down the waypoints it should be

306

“

281

“

“

303

“

250

I actually need to check what the speed at T/C should be. I can’t remember off hand whether T/C is still predicted at the climb speed or whether it is the cruise speed.

But I think it’s correct as T/C predicts climb speed and not cruise speed. Though of course here it should be indicated by “ and not the numeric value.

Oh and the speed limit pseudo waypoint is complete missing. Which should show the altitude at which the aircraft will begin to decelerate to 250kt for the 10000ft restriction.

It’s sad to see such basic systems in a page that is used all the time in flight to be so full of bugs yet again.

This is just looking at one page, and the aircraft is full of things like this on many other pages and displays.

Edited 5 hours ago5 hr 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!

Edited 44 minutes ago44 min by OxkyGThaib