Der Michel

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

@Eddie is this also tracked/forwarded?

That was a WASM Crash. The code of the aircraft stopped working. Follow the report steps Eddi posted, please.

And here issues with FA and VA-leg: 1. 700 in blue and no constraint 2. 700 should have the label VAB270 3. 2600 no brackets and no constraint.

Teh refference is from A320 / A330, but the logic is the same for A350. The ALT of the airport refference has to be indicated in green! The G/S capture altitude at the FAF has to be indicated in green, not magenta. The RWY treshold crossing altitude has to be indicated in green, not magenta. For the DEST there is the ALT CSTR field changed at the VERT REV of the A320/A330. I think that should also happen to the A350, but no idea how it will look like:

Hi, a CD leg has to be indicated as follows: This one is wrong: (HAD-05) Correct would be: HAD/05

There is a problem, how NPA are indicated in the F-PLN. If there is no runway coded in the final approach...there shouldn't be any in the F-PLN! Explanation with JEP Data below: Some examples: EDDV27R with NDB approach. For now ignore the non blue GA part, that is covered in another report. Also the wrong display of CA/FA/CD legs is in another topic covered. MQ27R is the MAP before RWY. In the NAVDATA it is coded as that: What you see, there is no RWY coded! So in F-PLN there shouldn't be any EEDV27R! Other IRL example: VVTS07L VOR approach MA07L is the MAP before RWY and coded: The interesting thing is, that the blue GA line at the ND starts directly at the MAP!!! Picture is from older AIRAC, so different names. Another Example where the MAP is on the RWY! There RW28 is the MAP and coded as: The MAP RW28 is in this case indicated as WARR28 ! And now just an ILS appr to compare. From EDDV27R

Have you tried to increase the null zone around idle in the calibration?

Is it fully downloaded/local installed or streamed? Maybe the terraindatabase has a problem with streaming.

I think you nailed it. FCOM's are often not 100% easy written. But your explanation matches fully with airbus philosophy. So @Eddie it's a bug. One of yout technical advisors should be able to confirm it, with a look into the ESLD document.

I think it’s correct as it is;

1. The MEMOS are in the wrong order. Correct is: PARK BRK ON ELEC EXT PWR N/W STEER DISC GND SPLRs ARMED APU BLEED or APU AVAIL SEAT BELTS NO PORTABLE DEVICES or NO SMOKING or both? NO MOBILE ADS-B TRAFFIC ON maybe as last? 2. Also "GND SPLRs ARMED" shoud have small "s" at the end. 3. Can we please get "NO PORTABLE DEVICES" instead of "NO SMOKING"? Or are both required with this modeled combi switch at the OVHD? If you have an A350 mech in your team, he could check the ELSD document.

Not necessarily a bug! ND: Indicates the highest grid Minimum Off Route Altitude (MORA), in a circular area of 40 NM radius around the aircraft. VD: The VD also displays safety altitudes. However, the VD displays the highest grid MORA or the MSA, along the aircraft trajectory and in the VD range.

The F-PLN shouldn't mess up the upper data area. The F-PLN has to be clipped like the Map-Data.

Hi, I#m not sure about this one, maybe check also your sources.

Wheel numbers are missing

And another example: EDDV27R NDB, The GA has to be blue!

The GA-Wpt have to be drawn in blue also in TMPY-Mode The upper CTV belongs to the GA part:

some more source picture:

@Eddie did you notice my feedback?

@Eddie is this also reported/tracked?