Der Michel

Performing flight at CRZ FL FL370, 4000NM+ to go. Set FCU to 36200. Aircraft is switching to vertical mode DES. FMS remains in CRZ. When reaching the new Altitude ALT* the FMS suddenly switches to DES. That's wrong. It has to remain in CRZ !!!! The distance to the destination airport has to be equal or less then 200NM for the FMS to switch to DES in this case.

Auto import of STEP CLB does only import CLB and not STEP DES. Simbrief Steps and what was imported:

just as addition to my first point in opening topic. The last vertical line is done vice versa currently. It has to be dashed when the arrow is displayed top right and solid when there is no arrow.

Just to add more info: A CA, VA or FA can never be at an other altitude in the vertical profile as it's name indicates, because it's vertical fixed. Never indicate constraint values, circles or asterix (magenta, amber, white) in F-PLN or ND. At VD the wpt symbol can only be a regular white diamond.

With the T.O SURV button at OVHD it should be possible to deactivate all TOS2 checks. That are the ones reported with the topics: T.O Surveillance issue #2 T.O Surveillance issue #3 T.O Surveillance issue #4

ECAM warning is missing:

Warning is missing:

The following FMS message is missing during Cockpit Preparation. This TOS2 check is performed a second time at engine start. Based on the TORA (selected RWY and entered T.O Shift) the FMS will cross check with the calculated Lift Off Distance (LOD) and trigger the message. The LOD is also required to corretly display the starting point of the vertical profile at the VD. The associated T.O Config test ECAM is also missing: And the ECAM warning at T.O Power is missing:

The following FMS message is missing during Cockpit Preparation: I assume VMU and VS1G are known, because they are used to calculate T.O speeds and VLS for example. A350-941: A350-1000: Also the associated T.O Config test ECAM is missing:

The Runwaylength is not necessarily the max TORA. As in this EDDL example. EDDV for example has a TORA extension larger then regular runway length. EDDL has a 23L Runway of 3000m with 300m stop margin. So the max TORA is 2700m. Not all charts offer ASDA and TODA, but TORA. The import of the correct TORA would be fantastic. Do we need to indicate ASDA and TODA? EDDL23L example: ASDA with 2998 almost correct -> Chart 3000 TORA with 2998 wrong -> Chart 2700 TODA with 2998 wrong -> Chart 2760 When I manually enter TORA 2500 for L2 int the system calculates wrong T.O SHIFT, TODA and ASDA. Correct T.O SHIFT is 200 (TORA full - TORA L2) Correct ASDA is 2800 (ASDA full - T.O SHIFT) Correct TODA is 2560 (TODA full - T.O SHIFT)

I had baro at Std, then FL is correct.

Also the APPR was somehow a wild ride up and down, while the airplane was trying to keep speed and glideslope. Is GSmini implemented?

Some more items during APPR: - DME distance is not indicated - GA is green instead of blue at the ND (maybe because the system thinks I'm doing a GA, but then PERF should show the GA page and F-PLN should also an activated GA F-PLN, no longer blue and with predictions.) So the GA logic is also somehow not working correct.

During CLB it was then indicated....at FL119....it's set at FL100 at the CSTR page !?!

SIM DEFAULT navdata. RWY part of GA, is wrong as already known. But where do the 3000 for HAD54 come from? If it's a WINDOW constraint...in F-PLN has to be a magenta "WINDOW". But to my knowledge it's coded with "at 1460" in navdata. At the ND the ALT constaitns shouldn't be indicated after the FAF for ILS APPR At the APPR selection page the ILS freq and IDENT is not shown note: I changed the constraint type at HAD54 manually

After loading (Set ZFW) LOADSHEET we have 31.75 ZFWCG According AOC message we have 29.88 ZFWCG What is correct?

After I deleted the not required "CI09L" The FLAP appeared, but SPDLIM still missing.

FCOM: The constraint value and the constraint symbol have identical color coding. If the circle is amber, the value should also be amber

Fehlerhafter Anwendungsname: FlightSimulator2024.exe, Version: 1.4.20.0, Zeitstempel: 0x00000000 Fehlerhafter Modulname: FlightSimulator2024.exe, Version: 1.4.20.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000003892905 Fehlerhafte Prozess-ID: 0x42CC Fehlerhafte Anwendungsstartzeit: 0x1DBDDC771F74C28 Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Fehlerhafter Modulpfad: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Berichts-ID: 0688ec88-ff4c-4562-b778-3ec8d3e79ae4 Vollständiger Name des fehlerhaften Pakets: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe Fehlerhafte paketbezogene Anwendungs-ID: App

PSEUDOWAYPOINTS missing for: - descent (SPDLIM) at FL100 - FLAP 1, FLAP 2 for the CDA function Appr: ILS 09L at EDDV

Yep....I had yesterday endless FALRE, but no autoland....

With TCAS in STANDBY and TRAF pressed at EFIS CP, the TCAS ARC has not to be drawn, but instead a dashed circle. The GS has to be right alligend, not left. See top left corner

Might be yes, but believe me, system devs can forget, miss or just shortcut a lot. And they did it correct for the red version:

Following is wrong for the VD. a.) the vertical line at the end of the scale has to be solid, not dashed. Dashed it's only, when ND has ARC greater 160 or ROSE greater 320. b.) vertical MORA line has to be horizontal aligned with 0 range line c) if the constrained is missed, the constrain symbol has to be amber with an dotted line: d) if alt constraint is ignored, it has to be white in the VD: 1. empty FMS: VIEW ALONG ACFT TRK is missing Aircraft should be at the bottom of the VD no green arrow would be correct, as no f-pln avail currently MORA is missing if SIM DEFAULT is used, but NAVIGRAPH is linked RADIO HEIGHT indication is missing 2. citypair/route entered FMS: MAGENTA AREA missing...distance to airport reference coordinate GREY AREA for the remaining VD RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD 3. runway and SID entered FMS, but no perf data avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD green arrow should still be indicated, because no predictions are avail 4. runway and SID entered FMS, but perf data now avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing green arrow should still be indicated, because aircraft does not follow the FMS trajectory or the selected trajectory vertical profile has to start at the calculated takeoff point In selected mode the VD is not showing the Vertical Cut along the TRACK and should show the selected vertical track not the arrow.

Let's look again at the CA-Leg type in conjunction with VD-ND-FPLN. - at the ND the 600 wpt is behind the runway - at VD it's in the middle of the runway And again the CA WPT is still indicated as a regular lateral fixed WPT with constraint. THAT'S WRONG !!!!!!!!!!!!!!! 1. A CA or VA or FA is only vertical fixed. Lateral it is linked to the aircraft performance - VNAV. So depending on the climb performance the lateral position has to be adjusted!!!!!! 2. There shouldn't be any asterix next to it in the F-PLN. Because it's NO regular constraint !!!!! 3. The vertical profile can't start at the rwy treshold, calculate the required takeoff roll and the point of lift off !!!!!