Turbo Arrow unable to lock onto ILS
-
With the latest Arrow update, I have now tried four flights in a row where the ILS LOC and GS came up on the instruments, but the plane completely ignored. I made sure I was on the right track, switched from gps to nav and pressed the approach button, each time the aircraft ignored the loc and the gs until I disconnected and hand flew all the way down. What am I doing wrong? This worked fine before the updates.
-
With the latest Arrow update, I have now tried four flights in a row where the ILS LOC and GS came up on the instruments, but the plane completely ignored. I made sure I was on the right track, switched from gps to nav and pressed the approach button, each time the aircraft ignored the loc and the gs until I disconnected and hand flew all the way down. What am I doing wrong? This worked fine before the updates.
-
Yes you are right about the GS, it is advisory only. However the plane is not capturing the LOC which it should do so. It just veers away.
I think the problem is on Asobo's end with regards to navaid data because I see the same LOC tracking problem with the default steam gauge 172. Some ILS and LOC approaches work fine while others exhibit a noticeable offset from the centerline.
Searching the MSFS forums for 'offset localizer' brings up various threads reporting the same issue.
-
I think the problem is on Asobo's end with regards to navaid data because I see the same LOC tracking problem with the default steam gauge 172. Some ILS and LOC approaches work fine while others exhibit a noticeable offset from the centerline.
Searching the MSFS forums for 'offset localizer' brings up various threads reporting the same issue.
@planview-symbols said in Turbo Arrow unable to lock onto ILS:
I think the problem is on Asobo's end with regards to navaid data because I see the same LOC tracking problem with the default steam gauge 172. Some ILS and LOC approaches work fine while others exhibit a noticeable offset from the centerline.
Searching the MSFS forums for 'offset localizer' brings up various threads reporting the same issue.
Yeah MSFS Is notorious for ILS issues.
-
@planview-symbols said in Turbo Arrow unable to lock onto ILS:
I think the problem is on Asobo's end with regards to navaid data because I see the same LOC tracking problem with the default steam gauge 172. Some ILS and LOC approaches work fine while others exhibit a noticeable offset from the centerline.
Searching the MSFS forums for 'offset localizer' brings up various threads reporting the same issue.
Yeah MSFS Is notorious for ILS issues.
I have noticed this when attempting to lock onto the localizer at a number or airports - this also shows up on Plan-G, which shows to offset localizer beam (in this case Valley on Anglesey).
It was also the same in FSX, so I am not sure whether this is a bug or mirrors real life? (although I am unsure what use an offset localizer would be?)
-
I have noticed this when attempting to lock onto the localizer at a number or airports - this also shows up on Plan-G, which shows to offset localizer beam (in this case Valley on Anglesey).
It was also the same in FSX, so I am not sure whether this is a bug or mirrors real life? (although I am unsure what use an offset localizer would be?)
@jake_mazar said in Turbo Arrow unable to lock onto ILS:
I have noticed this when attempting to lock onto the localizer at a number or airports - this also shows up on Plan-G, which shows to offset localizer beam (in this case Valley on Anglesey).
It was also the same in FSX, so I am not sure whether this is a bug or mirrors real life? (although I am unsure what use an offset localizer would be?)
This does mirrors real life. You will find this every so often. The reason for offset Loc / ILS is usually due to terrain, obstacle avoidance. Eg. There could be a mountain in the final approach path of the runway. So they purposely offset the ILS to avoid the terrain. This will also usually end up with higher minimums. In this case 310 AGL. Where as most cat 1 ILS approaches straight in are 200 agl. The approach chart will always publish the offset so you'll know ahead of time. As in here is the case "loc crs offset 3 degrees "
-
@jake_mazar said in Turbo Arrow unable to lock onto ILS:
I have noticed this when attempting to lock onto the localizer at a number or airports - this also shows up on Plan-G, which shows to offset localizer beam (in this case Valley on Anglesey).
It was also the same in FSX, so I am not sure whether this is a bug or mirrors real life? (although I am unsure what use an offset localizer would be?)
This does mirrors real life. You will find this every so often. The reason for offset Loc / ILS is usually due to terrain, obstacle avoidance. Eg. There could be a mountain in the final approach path of the runway. So they purposely offset the ILS to avoid the terrain. This will also usually end up with higher minimums. In this case 310 AGL. Where as most cat 1 ILS approaches straight in are 200 agl. The approach chart will always publish the offset so you'll know ahead of time. As in here is the case "loc crs offset 3 degrees "
@chase1399 Very informative - many thanks for taking the time to explain.