Hi again,
I have now looked deeper into the specification … this approach is primarily designed/coded as localizer dme approach and can also be used as back course approach. Therefore it´s coded as L (= localizer) with the prefix BC-A …
Here from the FAA, which is exactly what we have in our database
The problem now is the limitation in MSFS, because the MSFS doesn´t follow the standard ARINC rules - they use an very old/none standard format which has a very limited structure. In this case, I can´t set the exact “procedure-identifier” and therefore the BC part is missing, even if we have it in our data.
Sorry, but that´s a MSFS limitation (in general, not only in the G3000).
Cheers,
Richard