I flew into KDEN 16R today in the NG. The FMC Approach Ref page gave me freq 111.90, course 171 deg. I tuned accordingly. The PFD read ILTT/169. Just after being turned to the LOC by LNAV, when the GS failed to activate using APP, I moused over the FSNavigator moving map and found that the freq for ILTT was 110.10, course 169. During descent I got a scratchpad annunciation "RW/APP Tune Disagree."Is there a way to fix this freq error in the FMC? (Not a major issue, just a detail of interest to me).Thanks!Jonathan

Hi Jonathan,I checked the latest approach plates for KDEN you can access them at http://www.airnav.com/airport/KDEN and the wpNavAPT file of the 0411 Airac cycle for PMDG. There is no discrepancy. From your message I noted that you intended to land on 16R but you mentioned ILTT which is the LOC for 16L. The LOC for 16R is IDQQ with a frequency of 111.90.So as far as I can see everything is as it should be that is:16R magnetic bearing 169, LOC IDQQ, freq 111.90, true bearing 18016L magnetic bearing 170, LOC ILTT, freq 111.10, true bearing 181Michael

Jonathan,KDEN is my home airport, which I fly out of almost daily. When you have the proper ARINC cycle installed in the PMDG 737NG the freq are correct.Runway 16R freq are 111.9, with an ident of IDQQ and loc of 170. Runway 16L is has a freq of 111.1, ident of ILTT and loc of 170. Have you upgraded to the latest ARINC cycle? They are all correct. Also do you have the matching procedure from Terry Yingling (spell) which match the ARINC.Now there is a couple of degree differences from the plate to the PMDG data, but use the ARINC cycle data for the ILS in the FMC to the MCP approach heading.If you still have a problem just let us know here in the forum.Bob JohnsonKDEN

Wow, this is very strange. I must check out the FSNav map again and see what happened. Thanks for posting.JS