Can anyone help with this meassage. When trying to pick an arrival runway there are none availible.

You are aware already that you must sign your posts, please do so, thanks. That is a STAR error. I do not make stars so cannot help you but maybe someone can send you one corrected?? [h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-8/196432/winglets_lg.jpg [h3] AMD XP 2200 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF2 MX 32 MEG and still runs GOOD!|WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"[/h3]

Yes I am aware, sorry I missed it I was in a hurry.Is there anyone who can help me with this. I guess I can still fly there just no runway info for the FMS.Andrew

Your problem has to do with an inaccuracy between the STAR/SID and the Navdata.In the past Richard had modified the 767PIC Navdata (the one used by the PMDG 737) to remove runways that a 767 could not land at - i.e. too short. Worked nicely for the 767PIC guys to clear up clutter on the FMC for runways you couldn't get a 767 into if you sold your soul. :)In any case, the SID/STAR database does not remove the same runways - nor was it built with the exact database from the available navdata. Therefore the SIDs/STARs list runways that are not in the NAVdata - hence the error.Richard is currently beta testing the next version of the Navdata and has lowered the restriction to 3000' for runways. That should help a great deal - if not remove the problem entirely.In any case - there is a way you can remove the error - by manually editing the SID/STAR with any text editor (i.e. Wordpad) and removing the runways NOT listed in the Airports file of the Navdata.I've done this myself with no ill effects whatsoever and am now able to use the DEP/ARR page without errors.Oh, just an FYI, from personal experience, make sure you check the ENTIRE SID/STAR for any entries of the runway that you're removing. It can be listed quite a bit :)Best of luck!

Hi Howard,>Oh, just an FYI, from personal experience, make sure you check the ENTIRE SID/STAR for any entries of the runway that you're removing. It can be listed quite a bit:).Cheers,Gosta.http://hifi.avsim.net/activesky/images/wxrebeta.jpg

Hi,I have been working closely with Richard on the wpNavAPT text file. It looks like now we have taken into account shorter runways to accomodate the B737-XXX. It is my recollection however that the restriction has been lowered to 2,000 feet but I may have missed a late info on that point. A lot more localizer headings and frequencies will also be taken into consideration. One should recognize once for all that one of the main difficulties of the exercise is the FS database which has its own downfalls. So if and when Richard decided to publish a new cycle there will still be some discrepancies between the sources of the datas used and the FS database shortcomings.Having said that there will be hopefully a perfect match possible between a given navdata cycle and the Sids and Stars database. I am in the process of writing a note to PMDG and Terry in particular about this. Michael

>>>>>I used to do that too, but then I decided to see what happens, if I just removed the offending runways from the 'RNWS' section at the top of the SID/STAR file. Works like a charm - no need to go through all the rest .Yep, that's the same thing I do and it works for me too.