Flying into KSEA using the ILS 16's I noticed no Autoland using one approach configuration?

If the approach selection is Heading / VOR/LOC / APR I get a normal VOR/LOC G/S Rollout/Flare autoland (screenshot).

If the approach selection is LNAV/APR I get a B/CRS G/P Single CH with no autoland (screenshot).

Note:
KSEA ILS 16L 110.3 I-SNQ
KSEA ILS 34R 110.3 I-SEA

I use Orbx Global , Orbx Northern California, Orbx Pacific Northwest

 

 

 

3 minutes ago, vonmar said:

If the approach selection is LNAV/APR I get a B/CRS G/P Single CH with no autoland

Hi Vaughan:  I assume you are aware that you only get AUTOLAND if a number of conditions are present so I will assume your question is regarding the FMA status and why don't you get ILS16L.  Having the same localizer frequency on opposing approaches is not unusual and the way the simulator platform elects which of the two possible ILS systems to use depends on aircraft position with reference to runway center point.... so logically the only way that you should be receiving the ILSBC 34R when on short final to 16L is if the 16L system is missing.  Open the P3D map and select the airport and drill down to the window that shows frequencies and verify your scenery has ILS 16L.  The Orbx PNW scenery includes a KSEA but I've turned mine off because I am using the one from Taxi2Gate.

I notice your MCP CRS is set to 343 in the 16L approach picture... didn't know that this could cause the aircraft to switch systems but try the ILS 16L with the correct course setting.  That would be an ah ha moment if that is the problem.

Hi Dan,

 

" notice your MCP CRS is set to 343 "

That was automatically set.

Edited October 17, 20187 yr by vonmar

KSEA MAP info looks good (screenshots).

 

 

Any chance you are arming approach before the simulator has selected the 16L ILS?  For example, are you arriving on a downwind and the aircraft is in a position where the simulator (it's the simulator, PMDG doesn't do this because it merely uses the ILS signal that the simulator gives it) has selected the 34R system?

Describe the approach.  Which arrival or direction are you arriving from? Are you waiting for live LOC/GS indications before arming APP?

I armed the approach prior to LOC near Paine (screenshot).

 

 

 

That is probably the issue then.. you are arming approach when you are North of the field for a 16L approach.  The simulator is selecting ILS 34R.

Don't arm the approach mode until you are receiving the ILS 16L LOC and GS signals... you can tell you are receiving those signals because the deviation indicators on the PFD for the LOC and GS will appear.  The LOC normally appears first but you have to wait for the GS to appear otherwise your FMA will indicate G/P instead of GS.

Hope this makes sense.

I did approaches to all the 16's and got the same issue.

 

I did approaches to the 34's ... mirror image if the approaches to the 16's and all ok.

2 hours ago, downscc said:

That is probably the issue then.. you are arming approach when you are North of the field for a 16L approach.  The simulator is selecting ILS 34R.

Don't arm the approach mode until you are receiving the ILS 16L LOC and GS signals... you can tell you are receiving those signals because the deviation indicators on the PFD for the LOC and GS will appear.  The LOC normally appears first but you have to wait for the GS to appear otherwise your FMA will indicate G/P instead of GS.

Hope this makes sense.

Dan,

You were correct.

I waited to ARM and all ok.

Thanks.

 

edit:

My previous flight VORLOC captured the LOC ok at the higher altitude and autoland went ok from there.

 

 

The KSEA 34's capture LOC higher.

 

 

 

Edited October 17, 20187 yr by vonmar

Don't land on 16L - IT'S CLOSED FOR CONSTRUCTION!

😉

Ok, I won't do 34R either.

Arm approach mode only when you‘re on intercept heading <90 degrees. This might not be necessary in the real airplane (I don‘t know) but it keeps you out of most trouble 🙂

Edited October 19, 20187 yr by Ephedrin

9 hours ago, Ephedrin said:

Arm approach mode only when you‘re on intercept heading <90 degrees. This might not be necessary in the real airplane (I don‘t know) but it keeps you out of most trouble 🙂

Have you tried the KSEA ILS 16L (LNAV/VNAV) inbound from the PAE vor at 5000 feet and then selected APP ?

Edited October 19, 20187 yr by vonmar

Vaughan, good point.  You are within one degree of final course on the transition from PAE; however, I think the problem was the simulator world usually fixes the maximum distance of an ILS at 27-30 nm (unrealistic in some cases) and the GS range is less than that.  That's why I suggested you wait for the deviation indicators for both LOC and GS to be visible before arming APP.  I assume they are there by KENMO.

I was puzzled as to why you would get the opposite direction ILS system until just now.  The ILS 34R transmitter is closer to you than the ILS 16L because the localizers are usually at the opposite end of the approach, and the default ILS in the simulators always have backcourse enabled regardless of if they exist real world.  Therefore you were within range of the 34R backcourse before you are in range of the 16L front course.  Another good example of why in the simulation world one has to be observant of when to arm approach.

Edited October 19, 20187 yr by downscc

1 hour ago, vonmar said:

Have you tried the KSEA ILS 16L (LNAV/VNAV) inbound from the PAE vor at 5000 feet and then selected APP ?

many times with the 737 and 777. Never had that issue. But I use the Taxi2Gate scenery too. I've never flown into the default Seattle airport.