Technically either OEV or OEJ at LOWI (can’t remember which one) is also not related to any runway. You’ll pass the airport at 4000 ft or so and then have to circle for either runway 08 or 26…
Yes, and “Technically” Asobo needs to step up, and fix this confusing mess. - but I am not holding my breath …
(after all, it’s all working for me now 
- thanks to the advise of a few technically savvy members of the FS Community)
Sorry, but when you look on the charts this is wrong. @HalberQuacky seems to be right. I have checked a view offset Locs and all, which have no runway assigned are correct in the default data. The others have runway headings instead the offset headings …
Cheers
Richard
Cheers,
Richard
OEJ is the famous/infamous LOWI DME WEST approach,
(commercial pilots used to need a rating for that, but I don’t think commercials fly this anymore, correct me if I’m wrong)
and should have a - steep - glideslope (Charts), this OEJ is unfortunately completely borked in MSFS, a phantom ‘something’ is there instead you cannot intercept. I used to fly DME WEST on VATSIM with a PMDG 737, worked great.
I already reported to Zendesk.
1 Like
@anon50268670 sorry, you’re also right. My fault, the LOCDME approaches into LOWI are also not assigned to the runways. Sorry!
But regardless I assume the finding from @HalberQuacky is right.
Cheers
Richard
Yes I used to fly in and out of Innsbruck. I assume everybody is flying the RNAV now, has been a while since I last been there. You need special training to use the airport at all, not just the west approach, its a CAT-C airport (training in an approved sim or having visited the airport as observer is required). I don’t believe steep approach equipment / certification is required though, both east and west approaches are within 4.5 degrees?
Edit: you are right, it is steeper than 4.5 degrees, I think I have only flown that one in the sim though. The RNPs are less steep.
Well I’m not talking about MSFS, I’m talking about real life. No clue how it is set-up in MSFS, the LOC DME west approach navaid is located far from the airport and not connected to any specific runway, yet is MSFS it has the runway 08 heading assigned as front course…
It is a similar situation with runway 19 at KDCA. Our company (corporate flight department) occasionally flies into there, and if runway 19 is active, always uses the RNAV approach in lieu of either LDA - or even the River Visual approach if visibility is good.
But, those offset localizers and LDA approaches that exist in MSFS should work as they do in the real world for those pilots who choose to use them - and that is not currently the case.
1 Like
And more importantly, KDCA LDA’s are a good example of
(1) Asobo / navBlue getting the ILS/LDA forced to runway heading.
(2) NavBlue being “out of date” and not reflecting the true state of the Nav Aids @ KDCA, while NaviGraph & Jepperson, have their data “up to date”
Its a MESS, and it should be sorted – there is CORRECT Data, and there is incorrect, Obsolete data … should not be that difficult to get it RIGHT.
Last time I checked, MSFS & navBlue had the wrong freq for the VOR @ KOSH.
Navigraph & Jepperson have it right.
After the UK Update ( 2/17/2021) all teh airport bgl files seem to have been update, and are back to the original state of not having the ILS/LDA heading issue fixed (By the previously run Python script)
SO it seems necessary to re-run this script .. Did so, and now everything is back to as it was before, and all LDA now work as expected (With NaviGraph data)
No bad a task, once you remember where the script is and how to run it with the --all parameter.
Would be “nice” if Asobo addressed and fixed the issue, but at least there is a Community “work around”
BTW: The current MSFS NavBlue still has one of KDCA LDAs having a Glideslope (sigh)
1 Like
LOWI loc OEJ is always wrong in course from Asobo scenery.
I download the script but maybe i wrong to run it.
I downloaded python, change the directory into the file with “ c:/…packages/ “ and run in from the cmd
I run it with: “ ils_fix.py --airport LOWI --ident OEJ ”
Now i don’t remember what is the error
Something wrong? 
It works with original and the navigraph navdata?
Where can this script be obtained?
It sounds like a really useful script. However please do not share the actual file for the script (or direct download links to the file) on the forums due to its nature of altering hex codes in files and other possible issues.
There is no issue in pointing to a website/article that contains information about it and a download link from there.
Thanks for cooperation in this matter.
Obviously all usual caveats apply - use at own risk etc but it can be found here:
Post #32 on page 2
1 Like
I’ll try Innsbruck tomorrow, not sure if it is fixed though, the bug fix is under display? And to the end of their path? If the LDA is set to the wrong course then the whole thing is wrong, not only “to the end of their path”.
W’ll find out tomorrow!
Its not fixed for aspen and eagle airport in colorado. So I imagine its not fixed at all.
1 Like
LOWI LOC DME east RWY26 still wrong when using Orbx scenery. Did not test without Orbx.
2 Likes
LOC OEJ Always wrong!! Wtf.
1 Like
@anon50268670 LOWI 111.1 wrong inbound track (still QFU) with the default scenery
3 Likes