I’m trying to do an autpilot ILS approach into Innsbruck. I’m tuning to LOC 111.10 and getting the correct ID. But it always seems to bring me in to the left of the runway. The glide slope is pretty good though. I’ve tried in the Citation and 172 with the same result.
I did notice the 172 is presetting the course to be 258 degs but according to the IFR chart I think it should be 255 degs. But I can’t edit the course on the 172 as far as i can see.
Has anyone managed to do an accurate ILS approach purely on AP into LOWI and have any idea what I might be doing wrong?
Innsbruck does not have an ILS approach. The approach from RTT (Rattenberg) NDB is called the Localizer DME East Approach, because it is not aligned with the runway due to terrain. Additionally the GS on that approach is at 3.8 degrees, which is steeper than standard ILS glide slopes.
Hope this makes sense.
Actually it is incorrect in the sim. The FAC should be 255°, but it is 258° in the sim, parallel to the runway. The approach should have 3° offset. And it is wrong at every single airport with offsets in real life. In the sim every LOC has a FAC same as the rwy track.
So if I understand correctly the approach on the localiser, with the correct offset, should bring the plane to the start of the runway, just not parallel with it?
Sounds like this is something worth raising on zendesk? I could raise a ticket but I don’t really understand what I’m talking about!
Maybe somone using the ORBX payware version of LOWI could check if they at least have it right?
I’m pretty sure you can define the localizer independently of the runway, it’s just that most of the airport’s metadata is not put in manually and probably the process does not account for such approaches.
it’s time to start learn about approaches types and charts for flying. I think that then you’ll understand that thing looks another as you think (send request to Zendesk).
I do have the ORBX LOWI and this has the issue. I wonder if we could just manually override the course on the instruments whether that would at least give a workaround but it doesn’t seem possible on the C172 at least.
These approaches are offsetted and is big chance that your aircraft will be not putted to exact position aligned with runway, simply same app exists on world frequently. VOR app can be also example. In case of some 3-rd party scenery, question is if all is set correctly there or they simply take data from FS.
Then I guess you should file the bug with ORBX, not within Zendesk, since they are responsible for their scenery - even if they use the same data as tha base game does.
So you think the scenery pack should be able to override the course in the approach data for that airport too? I thought scenery was just about making it look pretty but perhaps they can also change the approach data.
Scenery can (and should) fix errors in navaids etc as well. Of course Asobo should have done it right since the standard version has LOWI as a featured airport, but at least from ORBIX I’d have expected that.
The problem is, that NONE of the offset approaches has actual offset in the sim. The LOC antenna positions are correct, but the final approach course is the runway heading everywhere in the sim. (The RNAV procedures are correct at the same time, the problem is with the conventional navaids (LOC))
Here is an example where it is obvious and easy to understand: LDA Z approach for RWY 22 at RJTT airport, picture attached
that was simply what we also discussed before. On other side, this can be also some solution of 3-rd party packages as also in times of FS9 and FSX was prepared. I don’t have idea what is cooperation between NavBlue and MS, simply hope we will see in future…
