But that's the point. That ILS is not in the fmc so I can't select it. How is this in RL, the 737 must be able to fly an ILS without selecting it in the fmc right?

Yep, only he "radio-tuning" is important.Bert Van Bulck

Hi,When an ILS-approach is not in the FMC's database the G/S will not arm (??) after selecting APP mode. I'm not sure this should happen in RL but if so, can somebody explain me how to arm the G/S of an ILS which is not in the database? For example: ESSA RNW26.Kind regards,

Standard FSX scenery works fine. Maybe you have an add-on?Bert Van Bulck

Yep, only he "radio-tuning" is important.Bert Van BulckStandard FSX scenery works fine. Maybe you have an add-on?Bert Van Bulck

Hi Bert,I think you misunderstood me. I know the FSX scenery is fine. The ILS of ESSA RNW26 is fine too, I can fly the ILS without any problem except with the APP-mode of the NGX. The G/S won't arm. Only the LOC.

I've just tried this out at EGUM, runway 29.It does seem an 'FMC' problem.If you try a raw data approach (ie with no route data entered in the FMC, the button APP works (lights up) and the G/S can be captured ok.If you try the same approach with simply EGUM entered as the destination airport in the FMC, you get this problem, APP does not light when selected and the G/S is not armed.There no need to enter a runway, and there are no ILS approaches listed to select. So although radio is tuned correctly it does not work,John Skipsey

Can please somebody of PMDG comment on this?

So you are saying you can fly an ILS approach with the autopilot without setting up the ILS in the FMC? In that case, could you please try ESSA RNW26 as well when you have the time for it?The ILS in FSX is working. Like I said, I can fly the approach raw data without any problem. The thing is that G/S won't get armed in the FMA after selecting APP-mode.

Just tested it: when ILS 26 is not selected is arrival, the G/S won't arm. Maybe it's correct behaviour of the NGX. I also noticed that in the PFD, the ILS and course don't become yellow. Again, I think it might be correct.Bert Van Bulck

I must be a bug.FCOM 4.20.16: After setting the localizer frequency and course, pushing the APP switch selects the APP mode. The APP switch illuminates and VOR/LOC and G/S annuciate armed.I will make a ticket. Lets hope it will be fixed with a next update!

I have noticed this too, last night I flew up to Barrow, AK PABR In FSX and in the real world it has an ILS approach. The FMS data only lists the runways. Approach mode will turn the aircraft on to the localizer course but no GS capture, even with the ILS frequency tuned into Nav1. I have noticed this happen more often at military bases where NAVDATA might not have complete approach information.TJ

The thing with ILS26 ESSA & others(missing from airac) is that the APP mode works if you want to fly it without setting it up in the FMS, say you just want to do practice approaches & tune them manually.But if you create a flight plan to ESSA & chose rw26 & manually set up the ILS26 ESSA, the APP mode wont engage!

Heres the approach info for ESSA Airport which is located in FSX/PMDG/SIDSSTARS Folder as ESSA.txtAPPROACHESAPPROACH VORD19R FIX CD19R 2500 FIX FD19R 2500 FIX DM05B AT OR ABOVE 1500 RNW 19R TRK 190 UNTIL 357 HDG 190 VECTORSAPPROACH ILS01LY FIX 76DME 2500 SPEED 160 FIX OHTNB 1370 RNW 01L FIX 17SSA AT OR ABOVE 537 TRK 005 UNTIL 600 HDG 329 VECTORSAPPROACH ILS01LZ FIX 76DME 2500 SPEED 160 FIX DME04 1370 RNW 01L FIX 17SSA AT OR ABOVE 537 TRK 005 UNTIL 600 HDG 329 VECTORSAPPROACH ILS01R FIX CI01R 4000 SPEED 160 FIX OM01R 1890 RNW 01R FIX ASE1A AT OR ABOVE 537 TRK 005 UNTIL 600 HDG 039 VECTORSAPPROACH ILS19L FIX CI19L 2500 SPEED 160 FIX DLNB 1320 RNW 19L FIX ASE1B AT OR ABOVE 537 TRK 185 UNTIL 600 HDG 149 VECTORSAPPROACH ILS19RY FIX CF19R 2500 SPEED 160 FIX LANB 1400 RNW 19R TRK 185 VECTORSAPPROACH ILS19RZ FIX CF19R 2500 SPEED 160 FIX OM19R 1400 RNW 19R TRK 185 VECTORSAPPROACH LLZ08 FIX CL08 2500 SPEED 160 FIX FL08 2500 SPEED 160 FIX DME03 AT OR ABOVE 1360 RNW 08 TRK 071 VECTORSAPPROACH NDB19R FIX LANB 1400 RNW 19R HDG 185 VECTORSENDAPPROACHESI do not see any info above with Rwy 26 so this is probably why it is not in the FMC. So in this case you would contact Navigraph and ask them to post a fix in the next AIRAC cycle. http://forum.navigra...spx?g=forum&c=2The SIDS and STARs and procedures are provided by Navigraph. The NGX FMC just uses the data that Navigraph provides. If the info is incorrect or missing it is not something PMDG can Fix. In otherwords this is not an NGX Bug.

But even if it is not an NGX bug as you put it, this means that the NGX cannot capture a glideslope on any airport that is not listed under the Navigraph data, such as those in more remote areas, or ones that Navigraph lacks data for.Even with appropriate ATC support, and custom fixes entered to simulate the ILS approach, as long as it is not under Navigraph the GS is useless for the NGX? To me that seems quite a big limitation. Even other 'less functional' airplanes can capture the glideslope at those custom approaches just fine, and it isnt any less realistic in these cases.Marcus Jian

Is it possible to actually capture a glidescope in the real 737-800 just by tuning to the correct frequency even if the ILS info is not in the FMC? If it can be done in the real world then yes I agree it should be accurately modeled in the NGX. If it can't be done then that is why it is not modeled.PMDG is not going to add unrealistic options to a plane just because you can do it in other FSX planes. If it can't be done in the real world why would they add it as an option to a plane that is supposed to based on the real thing?In the real world if there was not an ILS what would the pilot do? Do a visual approach and hand fly it. Visual approaches are a lot more fun than autolands. Anyone that can't do a visual approach in the NGX needs to go back to flight school.

It is a bug in Airac 1110 and 1111.look over at Navigraph forum.i have sent a +1 last weekMichael Moe

Posted: Saturday, November 12, 2011 3:21:17 PM According to our data provider the reason why ESSA ILS RWY 26 approach is missing is because it was not coded correctly in the AIP. In the AIP the approach was coded to set down on the missed approach point in front of the threshold rather than on the threshold itself. Since this did not adhere to the ARINC 424 specification the approach was removed entirely from the dataset by our data provider. At the moment, neither we or our data provider have any information about when the approach will be reinstated as our data provider requires the approach to be coded correctly in the AIP before it can be included.We've searched for NOTAMs that might give an idea of how/when the approach in the AIP will be corrected, but so far we haven't found any additional information.Since we don't have a date if/when the approach will be available again, we are discussing an alternative option in which we might be able to have a tailored approach made for us, separate from the AIP. More information will follow here. http://forum.navigra...?g=posts&t=2839RegardsMagnus

I don't think its ESSA related because I just tried this at EBBR, RWY25R. Some thing: when no ILS approach selected in the FMC, the plane doesn' capture the G/S.With an ILS app selected, it does, even when it's another ILS approach then the one you are flying. Does this has anything to do with the integrated approach navigation? (FCOM2, page 1093)Bert Van Bulck

Just to avoid confusion were talking about 2 different things here.1) The reason the ESSA Rwy 26 is not in the FMC as a Runway option is because it was intentionally removed as stated in the post above.2) It's obvious the glidescope is not gonna work unless the runway is in the FMC and is selected with GS set to On. Since the runway is not in the FMC well you can figure out why it is not working. Whether or not this is how the real world airplane works I do not know cause nobody that does know has chimed in yet. But in the real world the Runway would already be in the FMC and this issue would be moot.In the Tutorial it shows you how to setup for capturing the Glidescope. Both Nav Radios must be set, Both Courses Set and Runway selected in FMC along with GS set to On. That has always been how it was done since the NGX was released. So why are you expecting it to be any different now? So you got 3 choices.1) Contact Navigraph and get them resolve the runway issue2) Choose another Runway3) Do a visual approach.