On an approach and landing at KJFK 31R, LOC/G/P appeared above the top left corner of the ADI on the PFD. I have probably done 50 landings on this runway and never seen this before. I have always seen ILS displayed. I have read FCOM2 10.11.14 about this indication but it really says nothing about what triggers this or how to get out of it. Anyway, this resulted in a GA and a LAND3 on the same runway at KJFK. The only other time I saw this indication was KLAX 24L several months ago. Unfortunately that one resulted in a crash as opposed to a GA and landing. That’s what happens when you don’t know what LOC/G/P means and you press on and try to land anyway. Any ideas on this subject?Michael

Interesting that you brought this up, because I just noticed this a few minutes ago while flying into KLAX (24R). I also noticed the plane doing strange things, but the way I fly it, that's not surprising..lol.I'll try that same approach (from KLAS) and see if it happens again.

Interesting that you brought this up, because I just noticed this a few minutes ago while flying into KLAX (24R). I also noticed the plane doing strange things, but the way I fly it, that's not surprising..lol.I'll try that same approach (from KLAS) and see if it happens again.

RonI don't believe the airport or runway has anything to do with LOC/G/P. I believe it is some parameter the plane is operating in that causes this indication.. At KJFK, I was in LNAV, and V/S or ALT HOLD just prior to pressing the LOC button and pressing the APP button once the VOR/LOC was green. It was almost impossible to get the NGX slowed down from 240 at 18 miles from the runway. At 18 miles I started to dial the speed back and lower the flaps. Extended the speedbrakes. Almost no effect on the speed. Finally I set the speed at VREF+5, lowered the gear and set the flaps to 40. Still to fast a 1/4 mile from the runway. That's when I started the GA.Michael

OK, looks like we're both on the same page here. I re-did the KLAS-KLAX flight, and the same thing happened (to an extent). I saw the "LOC G/P" indication, and the plane wasn't slowing down from 240kts. This is the 24R ILS approach. It's worth noting that the approach starts almost 40nm out (on the RIIVR transition), so that might have something to do with it. Once the plane was within range, however, and I was able to press the APP button, the plane slowed down, and I was able to land normally.

As far as I know, selecting APP before you're within range of the glideslope (40nm out should be well outside of the range) results in the glidepath mode (G/P) getting active, rather than the glideslope mode (G/S). Check your PFD for the diamond-shaped glideslope indicator. If you can't see it yet, but only see the localizer indicator, try selecting VOR/LOC first. Only if you come within range of the glideslope you may select APP. That should do it.Regards,OliOliver BranaschkySent from my iPhone using Tapatalk

As far as I know, selecting APP before you're within range of the glideslope (40nm out should be well outside of the range) results in the glidepath mode (G/P) getting active, rather than the glideslope mode (G/S). Check your PFD for the diamond-shaped glideslope indicator. If you can't see it yet, but only see the localizer indicator, try selecting VOR/LOC first. Only if you come within range of the glideslope you may select APP. That should do it.Regards,OliOliver BranaschkySent from my iPhone using Tapatalk

OliverWhat you are saying makes sense. Do not press APP unless you are receiving the GS signal. On a RIVIR2, 24L at KLAX the LOC comes in at about 26.5 mile and the GS at about 22 miles. However I have a different situation at KJFK. The IAF for 31R at KJFK is CATOD which is about 15 mile from the airport. I set up a fix at KJFK134/19 as an IAF which should be well inside the range of a GS signal. And although I can’t say with 100% certainty that signal was coming in when I pressed APP it probably was. I picked up the habit of paying close attention to the GS signal from flying the MD-11 because there is only one button (LAND ARMED) and I don’t press until I see both the localizer and glideslope on the PFD.Michael

LOC/GP means that instead of following the localizer and the glideslope -a typical ILS approach - the airplane is being commanded to follow the localizer and glidepath, which is an FMC-computed -3.00º glidepath from the FAF to the RWY, simulating a glideslope. In other words, you´re no longer flying an ILS approach, but rather an Rnav approach using the NG´s IAN (Integrated Approach Navigation). Make sure that the glideslope function is enabled in the approach page of the CDU.And also, like someone else said, be sure to only arm approach after capturing the localizer (in other words, within range of the glideslope radio signal)