bug [LOGGED] VNAV- ILS Appr with SIM DEFAULT

[Der Michel]

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

 

Edited June 25 by Eddie
Title updated to LOGGED

[Der Michel]

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.

Edited June 15 by Der Michel

[Der Michel]

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

Is GSmini implemented?

[Eddie]

Hello,

Forwarded to the team. Thank you

[richboy2307]

Hey,

Thanks for your report. We're working on some of the reported items, but there are also just few things we wanted to clarify that are non-actionable,

On 6/15/2025 at 6:45 PM, Der Michel said:

But to my knowledge it's coded with "at 1460" in navdata.

Checked, it is coded as a window between the intercept alt (3000ft) and 1460ft in the Sim Default navdata unfortunately. Under Navigraph navdata this waypoint doesn't even exist (it goes from DESIM direct to EDDV09L with a 3 deg glidepath). Not much we can do about it, but yes it should not have shown as a 3000 Magenta ALT CSTR on the F-PLN page in this instance which is what team is working on. 

On 6/15/2025 at 6:45 PM, Der Michel said:

At the ND the ALT constraints shouldn't be indicated after the FAF for ILS APPR

Team is working on this.

On 6/15/2025 at 8:02 PM, Der Michel said:

- DME distance is not indicated

For this particular approach, it is just an ILS-LOC, not an ILS-LOC-DME so that is correct behaviour in this instance. The DME information for this approach is to be received via VOR1/2 tuned to the HAD (113.95).

On 6/15/2025 at 6:45 PM, Der Michel said:

At the APPR selection page the ILS freq and IDENT is not shown

That is dependent on the scenery as that is where the information is pulled from. If the scenery has not assigned ILS Freq/station to the runway, then it won't get pulled with the procedures for it.

On 6/15/2025 at 8:02 PM, Der Michel said:

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

The plane is not in go-around phase, hence no go around indications on the PERF or anywhere else. For the LNAV however, this is an "artefact" of sim-default navdata, in the way that its been re-done now such that the Go-Around waypoints start from right after the MAPt in the database, rather than *after* the runway waypoint. As the leg from MAPt to runway gets sequenced, its already in the "go around legs" segment and hence its turned green. 

The triggers are different for LNAV vs the rest of the go around logic, and there is no easy way to get around this for sim default navdata without also introducing other complications with sequencing. It is on the docket but unlikely something that can receive a quick turnaround. Ideally though the sim would revert to the old way of defining go-around segment legs. 

On 6/15/2025 at 8:09 PM, Der Michel said:

Is GSmini implemented?

Yes it is. If you're having issues, please provide video reference of observed behaviour in-sim for team's perusal.

Thanks!