I've seen quite a lot of posts about runways, but probably not all so if this has been covered I grovel. What I'm concerned with are the runways which are in the Nav database but dont show up in the FMC. It simply doesn't pick them up.An example - today I made a flight from Manchester UK EGCC to Schiphol EHAM. The FMC acknowledges that Manchester is an airport but when I look at DEP it has no runways listed at all, although these are included in the database. OK I enter the active in the route page - no problem. At the other end, I'm cleared to Ry 1L - check the ARR page, 1L is not included in the 3 pages of Rys, nor is 1R.I got the same thing flying from Luton UK EGGW. Its two Rys are included in the Navdat but do not show up on the DEP page of the FMC.It seems there is no problem with the database. The FMC has probs picking up the data stored there. Kindof spoils yer flight!Bud

Hi bud,This is not due to the NAVDATA database. The runways and SIDs and STARs on the DEP and ARR pages are to be located in the SID/STAR files which should be located in PMDGSIDSTARS.Do you have file in that folder called EGCC.TXT or EGGW.TXT? Then you have something erroneous in the files. If not you can probably get them from PMDG web site, or create them your self.If you do a seacrh with some clever keywords you should get a lot of hits about this subject.Hope it helps,

>Hi bud,>>This is not due to the NAVDATA database. The runways and SIDs>and STARs on the DEP and ARR pages are to be located in the>SID/STAR files which should be located in>PMDGSIDSTARS.>>Do you have file in that folder called EGCC.TXT or EGGW.TXT?>Then you have something erroneous in the files. If not you can>probably get them from PMDG web site, or create them your>self.>>If you do a seacrh with some clever keywords you should get a>lot of hits about this subject.>>Hope it helps,Put another way, the problem is due to a conflict between the data in the NavData datafiles and the SID/STAR files. The surest way to check it is to move your *.txt files from the SID/STARS directory, and see if the FMC performs correctly and shows the runways.If it does, you need to edit the appropriate SID/STAR file, removing any "extra" runways that arent in the NavData, and be sure that the single numbered runways have the leading zeros (03, 04, 05, 07, etc).

Thanks a lot guys. I'll have a look at my folders.Bud

Thanks again for the advice. I checked the folders tonight. There are no txt files in the SID/STAR collection for EGCC or EGGW. Does this mean that there is no conflict between the two sets of data, unless, perhaps, their absence from one constitutes such a conflict.As I understood the advice, the absence of a txt file should have allowed the FMC to work correctly. Perhaps I've got the wrong end of the stick.Bud

Hi Bud,A fellow VA pilot has completed the EGCC SID/STARs, see this thread.http://forums.avsim.net/dcboard.php?az=sho...id=19669&page=1I started work on the Luton ones (our home base) but got into difficulties (the LUT NDB was displayed wasy out of position) so still have to finish and check them, once done I will send them to Simon so he can add them to his list.Hopefully they will be ready by this weekend, but no promises.RgdsDave

Dave,Many thanks. Odd thing is, I put a txt file together from info I already had on Manchester. It still didn't show up in the FMC. I assumed it was because I had made a pig's ear of the txt. Probably true.Bud

Normally if you get it wrong Bud the FMC will show in the scratchpad "err, FIX line 13', obviously the 'FIX' and line number would be different.However if you get it completely out of whack then I guess it just won't show.If you still have your version of Manchester compare it to the one Simon produced, EGCC.TXTJust been testing the Luton SIDs and the converted version needed some work, hope to do the STARs over the weekend.HTH

Cheers Dave, I was getting something like "Program error", can't quite remember what else. Anyway, I did compare my file with the one produced by Simon and discovered that he is far, far better at this sort of stuff than I am!Bud