Hello Fellow fanatics! Please can you help me out here. I have had the PMDG 737 for over a year now and I have to say I have never completed one sucessful flight yet. Why? well...I am a perfectionist and seeking the ultimate FS experience and I keep tweaking here and there etc all self inflicted. However, I have noticed that I get an error message when I try CAT111 approaches. Basically, it goes something like this... in FSnavigator RWY 1 at Brisbane is 016 if I call recall correctly. However, when I set my 737 it says in the FMS when I tune it to the frequency at Brisbane, it's all set up to land but, the RWY HDG it sets is 015' consequently, I get this error message saying RWY Course error? I have all the latest AIRCS etc. can you please help me?RegardsPaul

Did you perhaps forget to follow the approach checklists for setting the MCP COURSE window to the final approach course? Best Wishes,[h4]Randy J. Smith[/h4]http://www.rawbw.com/~bdoolin/shinault/Animation1.gifCaution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Hi Randy,Thank you for your reply. I have to admit, regretable, I am not exactly sure which check list you are refering to, please excuse my ignorance: If you could point me in the direction of it I'd appreciate it very much.Once again, thank you for your reply.Paul

It should be in any real 737 NG approach checklists as this screenie shows Virgin Blue's SOP. I don't use the PMDG manuals so have no idea if this is in there but since I was the one who nagged this message into the product I suppose it could be ;-) http://forums.avsim.net/user_files/92954.jpg By the way, once you set the course you will never ever see this message. Best Wishes,[h4]Randy J. Smith[/h4]http://www.rawbw.com/~bdoolin/shinault/Animation1.gifCaution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Well it certainly is in the PMDG's manuals under NORMAL PROCEDURES herehttp://forums.avsim.net/user_files/92956.jpgBest Wishes,[h4]Randy J. Smith[/h4]http://www.rawbw.com/~bdoolin/shinault/Animation1.gifCaution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Part of the problem is that the course coded in the NAVDATA files is often not a match - by a few degrees or less - with real-world approach charts from NACO or Jepp.Setting the MCP course to the Jepp setting for instance can sometimes result in the warning.Also, when you're flying around an airport that uses the same localizer frequency for opposite ends of the runway, the logic FS9 uses to decide WHICH localizer you're supposed to be using can cause this error - it usually goes away when by the time you intercept the localizer.In real life, the tower chooses which transmitter is radiating.So, bottom line - set the MCP to the inbound course indicated on your FMC or real-world charts, and then if you get an error, clear it and carry on.Now, I think there is still a minor bug where the frequency/id display for the localizer on the PFD is in yellow (correct) and struck through (incorrect) when you've only got a single radio tuned. It should be white (I think) when dual channel, yellow when single channel, and yellow and struck through when the signal is no good - Im digging through Bulfer now but can't find the reference.

http://forums.avsim.net/user_files/92962.jpg Not sure Tim, this is somewhat vague but does say "TUNED frequencies disagree" amber with line.Best Wishes,[h4]Randy J. Smith[/h4]http://www.rawbw.com/~bdoolin/shinault/Animation1.gifCaution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

It should be white (I think) when dual channel, yellow when single channel, and yellow and struck through when the signal is no good I believe (thought not 100% certain) one still tunes both NAVS for a SINGLE CH approach. The yellow ID with a line refers strictly to the difference on the NAVS. Any drivers hanging around who might comment?Best Wishes,[h4]Randy J. Smith[/h4]http://www.rawbw.com/~bdoolin/shinault/Animation1.gifCaution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

>> I believe (thought not 100% certain) one still tunes both>NAVS for a SINGLE CH approach. The yellow ID with a line>refers strictly to the difference on the NAVS. Your reference certainly seems to back this up. Perhaps it's me - I'm used to flying approaches with an ILS on NAV1 and another navaid tuned to NAV2 for use on the missed approach, or for DME readouts, or for a crossing radial to positively identify a fix. That's how it's done in the little bugsmashers I normally. I'll try tuning both navs to agree and see what happens.I do hope that PMDG "fudged" the course logic as the second MCP course window isn't available in the 2D cockpit.

Paul,2 more possible reasons for your problem:- Richard Stefan from Navdata says, that Navdata gets the data for from DAFIF, which is a military database. These data differ from Jeppesen data.- Also does PMDG, according to Richard Stefan, use true heading, whereas Jeppesen uses magnetic heading.Wolfgang

Thank you Wolfgang, All I know is that I get all my Data from the NAV Data homepage. I download all the data required for SBox, Fsnav etc from there on each new cycle.Paul

Hi - I have a very similar problem. Last night I flew a preplanned course from EGBBA to LEPA using a route planned in FSBuild 2.1 taking me on ILS using UN859 Airway with the MJV(?)at LEPA as the final fix (I hope I've termed that correctly for all you perfectionists out there lol!). Plane was PMDG737/800.I talk to the (inbuilt)ATC during the flight and follow their routing as they direct me, but noticed that at about 100nm out from LEPA they deviated me from the planned course showing on the PFD and sent me out to sea to then turn me around to do a direct in approach to runway 06L maintaining 1900ft until established on the localizer. So far so good, so I tuned both nav1 and nav2 to 109.30 as shown on the fmc (btw yellow dme with strike through showing in top left corner of PFD, set altitude, course, speed, autobrake, flaps as per normaland when in line with the runway shown on the compass display I set vor loc, app and cmd b so that i had vor loc showing in white in the pfd and both cmd a and cmd b illuminated.As I approached the airport I noticed that the plane was not in fact heading to what was visually obviously runway 6L but was the other runway and the plane completely overshot it! Eventually I got the thing down but that was manually and not with the assistance of the onboard electronics.Has anyone else had runway discrepancies? Is there an obvious/easy solution?I'm using AIRAC 0410, latest AIO and latest PMDG sid/stars from their site. The only other thing I had installed just prior to the flight was the ukscenery2000 PART5 British airports with their afcads but I checked and none of those referrd to LEPA. I have also run SCANAFCAD and removed duplicate entries for about 32 airports including LEPA but I have made sure I kept the latest version of afcad in each case.Please helpCheersRick

I get this error too at about 90% of runways. I usally ignore it if I am flying from charts.As far as I am aware the Course selection is for the pilots oreintation and the AP will land you on the runway, even if the course is selected 90 degrees on.