dectenor1

I have to disagree here based on real world experience and what the FCOM states, but lets leave it for now, there are more important issues upon which to focus. As ever, thanks for engaging and speaking to the dev team, and thank all for continued work on the A350, we'll get there eventually!

Yeah they can take a bit of working out. But I am pretty sure I am correct here, plus rw experience of course. Would be great if @Eddie could acknowledge the change of opinion and forward this one!

Same. I can't access it.

Look at the waypoint GOLNI. The aircraft is basically at that waypoint, and, according to the F-PLN page the aircraft should be at M0.84, but then according to the PERF CRZ page the aircraft should be cruising at M0.85... The aircraft is, in fact, targeting M0.85 as can be seen on the PFD. This suggests the F-PLN page is incorrect and producing spurious numbers.

My understanding is that this is not correct behaviour. If ADS-B TRAFFIC is set to OFF on SURV page you should never get the ADS-B TRAFFIC ON ECAM memo because the ADS-B TRAFFIC is not ON. It is OFF. The ADS-B TRAFFIC ON memo would appear if XPDR/TCAS is in STBY, but ADS-B TRAFFIC is set to ON on the SURV page. - Non-normal. Normally in TCAS/XPDR STBY, the ADS-B TRAFFIC would be OFF, and so the memo ADS-B TRAFFIC ON is telling you that you have turned ON ADS-B TRAFFIC on the SURV page. Note there would not be a ADS-B TRAFFIC OFF memo, in a normal situation, because it is expected to be OFF Your shot from the FCOM is if ADS-B TRAFFIC on SURV page is set to ON, not to OFF, whist it would be expected to be OFF - i.e. XPDR/TCAS in STBY. As the FCOM shows here: You should actually get ADS-B TRAFFIC OFF as an ECAM memo if the ADS-B TRAFFIC button is OFF but only if XPDR in is Auto and you manually turn off the ADS-B TRAFFIC. Or if the TCAS or XPDR are on STBY in flight - non-normal. Basically any ADS-B TRAFFIC ON or OFF memo is due to a non-normal situation. So as I said it is the wrong way around in the iniBuilds aircraft. We should never see any ADS-B TRAFFIC memo unless we are in a non-normal situation. When it is appearing in the inibuilds is wrong, there should be no MEMO at all. This is because the ADS-B TRAFFIC is OFF on the ground with the XPDR/TCAS in STBY. When we turn the XPDR/TCAS to AUTO, the ADS-B TRAFFIC should turn on (the switch not the MEMO), but there should be no MEMO as it is expected to be ON with XPDR/TCAS in AUTO. If we were then to manually turn OFF the ADS-B TRAFFIC, we should get a ADS-B TRAFFIC OFF MEMO. Conversely, when in XDPR/TCAS in STBY. We should only ever get a MEMO saying ADS-B TRAFFIC ON, if we manually turn on the ADS-B TRAFFIC switch on SURV page. Sorry I am waffling. To summarise. XPDR/TCAS in STBY - Default is ADS-B TRAFFIC switch OFF - Only get a MEMO if we manually turn ON ADS-B TRAFFIC switch on SURV page - MEMO would be ADS-B TRAFFIC ON. XPDR/TCAS in AUTO - Default is ADS-B TRAFFIC switch ON- Only get a MEMO if we manually turn OFF ADS-B TRAFFIC switch on SURV page - MEMO would be ADS-B TRAFFIC OFF. I hope that make sense....

I notice the GW display here is also flickering, so it is probably related to the aircraft thinking that its weight is changing, resulting in different target managed speeds.... Hope that is useful for diagnosis and fixing.

Here on the PF MCDU page you can see that there are various altitude predictions given in FLXXX format. However, on the PM MCDU page you can see the Transition Level is FL130, this means that the altitude predictions below this level on the F-PLN page should be given as an altitude not a FL. For example, RUDBI should show 8000 not FL080.

You can see the same issue further along the flight here. The level-off arrow is showing being at FL130 before NOSKO, yet on the F-PLN page, the aircraft is predicting it will be higher than FL130 at NOSKO.

The level off-arrow is pretty badly bugged in many cases and different scenarios. Here is one example: The aircraft is in managed speed and managed descent mode, so the level-off arrow on the ND in this case should show the point at which the aircraft predicts it will reach the FCU selected altitude as shown in Cyan under the Altitude tape on the PFD as there are no 'at or above' constraints higher than this selected altitude. Here you can see that the level-off arrow is showing the aircraft will be at FL180 just before TERSA. However, on the F-PLN page, you can see that the aircraft is predicting it will be at FL200 at TERSA. Therefore, either the level-off arrow is incorrect, or the F-PLN page altitude predictions are incorrect. Based on experience with the level-off arrow being incorrect in numerous cases, it is likely the F-PLN page is correct and the aircraft will be at FL200 at TERSA, and it is the level-off arrow that is incorrect. It is possible that the level-off arrow is being calculated based on current speed and VS, whereas, in managed mode, it should be calculated based on the predicted calculated path of the aircraft, as shown on the F-PLN page. There are other issues with the level-off arrow in other scenarios, and I will post these here as i come across them again.

Sorry, feel free to delete to clean up forums. As an aside, I think the starting fuel of 24000KGs is way too much. Something like the amount the aircraft would have landed with like 8000KGs or something might be more realistic. Many thanks for the teams continued work on the a350!

You can see here the MORA displayed on the ND and on the VSD do not match up.

The MANAGED SPD targets such as green dot, S, F, econ climb etc, are bugged and keeping jumping and changing.

The T.O CONFIG TEST on the Checklist goes green when all the conditions for the TO CONFIG TEST have been bet, but the ECAM one stays blue and does not go green until the CONGIF TEST has actually been performed, thus you get this discrepancy.

It would be great if the Loadsheet Screen on the OIS displayed the current ZFW GW FOB etc of the aircraft. At the moment, if you load and fuel the aircraft via GSX rather than directly instantly importing the payload and fuel straight in from Simbrief, there is no way to see on the EFB what the various weights are.

Yes also seeing this, the first waypoint of GA is still in Green for me here, and also showing a -3.0 path.