• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Exclude or deactivate a single ILS LOC?

Mr.Mo

Mr.Mo

Messages
19
Country
germany
Hello Folks

I have a problem with one of two ILS Localizer of my custom airport I am working on. In the MSFS 2020 stock, the ILS 26 approach works perfect but the 08 approach not. The main problem is, that the stock 08 ILS antenna/Data is positioned about 3/4 length to the end of 08, on the right side of the runway ... not at the end. Thats in the Sim and in real, too. Because this, a correct approach for the 08 will end about 100m right beside the goal. I tried to place the ILS 26 and 08, Glideslope and DME via XML but the result is not really good. I land everytime beside the runway. I tried everything, I moved both ILS from real to unreal but I still cant do a correct ILS approach. The biggest problems I get are the 08 approaches.

Thats what I already tried to implement but with a bad result:
<Ils lat="54.379042" lon="10.149413" alt="29" heading="82.41999816894531" frequency="109.50" magvar="3.0" ident="IKHE" width="5.1" name="CAT I ILS/DME 08">
<GlideSlope lat="54.377870" lon="10.141305" alt="30" pitch="3" range="18.0N"/>
<Dme lat="54.378798" lon="10.145351" alt="30" range="25.0N"/>
</Ils>
<Ils lat="54.378620" lon="10.133357" alt="29" heading="262.4199981689" frequency="109.50" magvar="3.0" ident="IKHW" width="5.1" name="CAT I ILS/DME 26">
<GlideSlope lat="54.78554" lon="10.150051" alt="30" pitch="3" range="18.0N"/>
<Dme lat="54.378798" lon="10.145351" alt="30" range="25.0N"/>
</Ils>

Now to my questions:

1. Is it possible to deactivate and edit a single ILS Localizer via XML or editor (exclude)?
2. Is there another way possible, that an approach via 08 may hit the runway correctly?

Best wishes and hoping for help,
Mo
 
1. No
2. I'd review the positioning like you said

But, for answer 1, it seems like it's not a problem to delete them all, as you've got the code for both (I haven't checked it's correct, but I'm assuming you have), so I'd just keep on working on your ILS code until you get the 08 approach working to your satisfaction. What do the NOTAMs say about the 08 approach, maybe it's beside the runway in real life, too, if you've positioned it where it's supposed to be? Either that or the airport data on file is incorrect? That's not unheard of. I'd look at the airport in Google Earth and see if you can see where the equipment is. Or, just put it where it works and be done with it.
 
EDHK ILS 08 is an offset ILS so it is normal loc antenna is not positionned on rwy axe.
Correct coordinates for this LOC from German AIP are lat=54.379042 lon=10.149433
and true ILS course has to be set to 084.4° that is a 2° offset from rwy axe (82.4°)
I suggest, for maximum realism, you use data are they are in real life so that approach can be performed according to current approach charts
 
Hello Gentlemen :wave:

Thanks for the your replies, thumbs up!

@hervesors
What is the true ILS course for the 26?

In my EDHK approach charts I can see only 84° for the 08 and 261° for the 26 approach

Just changed the XML to this:
<Ils lat="54.379042" lon="10.149433" alt="29" heading="84.4" frequency="109.50" magvar="3" ident="IKHE" width="5.0" name="CAT I ILS/DME 08">
<GlideSlope lat="54.377870" lon="10.141305" alt="30" pitch="3" range="10.0N"/>
<Dme lat="54.378798" lon="10.145351" alt="30" range="25.0N"/>
</Ils>
<Ils lat="54.378620" lon="10.133357" alt="29" heading="261" frequency="109.50" magvar="3" ident="IKHW" width="5.0" name="CAT I ILS/DME 26">
<GlideSlope lat="54.78554" lon="10.150051" alt="30" pitch="3" range="10.0N"/>
<Dme lat="54.378798" lon="10.145351" alt="30" range="25.0N"/>

Another little problem is, I dont know the correct "width" for both ILS. Did you guys have an idea how to fnd these data, too?

Best wishes & keep healthy,
Mo
 
True ILS courses are not always available from AIP data. If ILS is aligned with Rwy, I'll suggest you set it to rwy true course
For offset ILSs, true courses are usually published (but you may have to recalculate them if only mag courses are available). If not, the easiest is to recalculate them from offset angles.
Loc beam widths (BW) are sometimes indicated on AIP. If not they can be calculated using the following standard formula
BW = 2*Atn(350/d) to be converted to degrees
d beeing the distance (ft) between rwy threshold and localizer antenna
Some countries set min/max values to 3.00°-6.00° respectively
For short runways (length <1200 ft) set d=d+3500
 
Last edited:
Hello Hervesors

Thanks for the fast reply & explantation/help. I will give it a try, hopefully I have nothing more to ask then! :)

Regards
Mo
 
You must log in or register to reply here.
Back
Top