hello guys, i realise this is a navigraph problem, but they have no answer and suggested maybe some simmer has had the same experience as me and managed to resolve it. i live in the u.k. and the airport concerned is here. i have been flying the md11 since available without any real problems. last night i loaded the md11 and tried to insert the route into the init page, eghi(southhampton)- egpf(glasgow) approx.350nm. when i pressed lsk 1r the message in the scratchpad stated - not in data base. the airac in use at this time was 0905 so i deleted this file and downloaded and installed the current airac 0906 into the fs9 md11, loaded it up again at EGHI and got the same message -not in data base. i then tried the same route into the 737ng and it was accepted. so the airac 0906 works for the 737 but apparantly not the md11. could some of you try loading you fs9 md11 with the route EGHI - EGPF and see what happens, and if some of you have had the same experience as me and solved it, please let me know. thanks. richard welsh.

hello guys, i realise this is a navigraph problem, but they have no answer and suggested maybe some simmer has had the same experience as me and managed to resolve it. i live in the u.k. and the airport concerned is here. i have been flying the md11 since available without any real problems. last night i loaded the md11 and tried to insert the route into the init page, eghi(southhampton)- egpf(glasgow) approx.350nm. when i pressed lsk 1r the message in the scratchpad stated - not in data base. the airac in use at this time was 0905 so i deleted this file and downloaded and installed the current airac 0906 into the fs9 md11, loaded it up again at EGHI and got the same message -not in data base. i then tried the same route into the 737ng and it was accepted. so the airac 0906 works for the 737 but apparantly not the md11. could some of you try loading you fs9 md11 with the route EGHI - EGPF and see what happens, and if some of you have had the same experience as me and solved it, please let me know. thanks. richard welsh.

Just fishing in the dark: Is it possible that an airprt is deleted in the database if airports are set above 6000 ft runway length or so? On my system the setting is in this manner and I also have the not in database message. I am in flight at the moment and don

Just fishing in the dark: Is it possible that an airprt is deleted in the database if airports are set above 6000 ft runway length or so? On my system the setting is in this manner and I also have the not in database message. I am in flight at the moment and don

So I tested it, set the runway lenght to more than 6000ft and EHGI is in the database...BestSteffen

hi Steffen, i suppose you meant EGHI, you meant well, thanks for the reply. richard welsh.

So,For the MD11 and NavData cycle 0906 in question here.Is it true that:Both the PMDG MD11 and the PMDG727 use the same NavData files?EGHI is in the database.EHGI is not an airport and not in the database.Ref:PMDG MD11 manual page, FMS.40.41Runway length / NavData / via PMDG FMS Menu/can filter out short runway airports.EGHI runway is 5649 feet long.PMDG MD11 FMC (via menu) can filter out airports with runways ... say ... less than 6000 feet long (not in database).PMDG737's FMC accepts EGHI without error.PMDG737's FMC cannot filter out short runways.

hi Steffen, i suppose you meant EGHI, you meant well, thanks for the reply. richard welsh.

Yes I meant EGHI sorry for the mismatch...BesatSteffen

hi guys, thanks for all your help and advice but iam pleased to say that i have solved the problem. i looked at the reply from Vormar and when the md11 was loaded i went to the pmdg drop down in the task bar and the box stating - airport shows runways longer than ....ft i reduced the figure to 4500ft and the data for eghi - egpf was accepted. so the saying alls well that ends wells rings true. what a relief. richard welsh.