OK can anybody help me with some problems i am encountering?when I build a flight plan for say Just flights 737 PIC from XXXX to YYYY (I am not giving specific airports because it appears to be the same at a number of places)the whole planning loading fuel/passangers programming FMC goes ok, I take off, up to crusie no problems, now the fun startsas I plan the approach.I build the approach sellect a runway and a transition to an ILS, but the approach just does not work, not allways but quite often the ILS just does not work or a waypoint is missing (not a disco i understand them and how to remove).I think what i am asking is how do i know that the navaid database in FSX matches the airac i am using as it appears they do not match currently, I am on airac 908. How do you guys make sure the appoarch you plan works?Phil

OK can anybody help me with some problems i am encountering?when I build a flight plan for say Just flights 737 PIC from XXXX to YYYY (I am not giving specific airports because it appears to be the same at a number of places)the whole planning loading fuel/passangers programming FMC goes ok, I take off, up to crusie no problems, now the fun startsas I plan the approach.I build the approach sellect a runway and a transition to an ILS, but the approach just does not work, not allways but quite often the ILS just does not work or a waypoint is missing (not a disco i understand them and how to remove).I think what i am asking is how do i know that the navaid database in FSX matches the airac i am using as it appears they do not match currently, I am on airac 908. How do you guys make sure the appoarch you plan works?Phil

I am a bit confused with your description but will try to answer. If you are using airac 0908 and have entered the ILS properly in the arrival page of the FMC and you made sure there's no disconnects in the legs page, then you should be able to capture the ILS. However, as I recalled, the 737 PIC needs to down to about 2000 feet before it "sees" the ILS. So that might be the reason why you sometimes capture the glideslope and sometimes you don't. I have removed the 737 PIC from my system because I have had some issues with the FMC. I remember setting up my landing at ILS 28L at SFO once and it got to the bridge just before the runway then suddenly veered off to the left and I looked at all my FMC data and everything was showing correctly so I had to take over the flight manually and retry. Some of these "old" aircraft or aircraft orginally made for older FS versions need the FSUIPC.dll properly installed and, as I recalled, this turned out to be my problem. I'm a little long in my explanation but the FSX navaid database does not apply if you have airac 0908 properly installed in the 737 PIC Nav database.Best regards,Jim

The database FSX uses is years old, any current AIRC data you use will reflect the new data and it wont always match FSX if things have changed. FSX will only recognize the freqs, fixes etc in its own database which may be why things don't always work for you.

I am a bit confused with your description but will try to answer. If you are using airac 0908 and have entered the ILS properly in the arrival page of the FMC and you made sure there's no disconnects in the legs page, then you should be able to capture the ILS. However, as I recalled, the 737 PIC needs to down to about 2000 feet before it "sees" the ILS. So that might be the reason why you sometimes capture the glideslope and sometimes you don't. I have removed the 737 PIC from my system because I have had some issues with the FMC. I remember setting up my landing at ILS 28L at SFO once and it got to the bridge just before the runway then suddenly veered off to the left and I looked at all my FMC data and everything was showing correctly so I had to take over the flight manually and retry. Some of these "old" aircraft or aircraft orginally made for older FS versions need the FSUIPC.dll properly installed and, as I recalled, this turned out to be my problem. I'm a little long in my explanation but the FSX navaid database does not apply if you have airac 0908 properly installed in the 737 PIC Nav database.Best regards,Jim

Thanks for the answer, Its not only the PIC 737 but any plane Just Flights 757 has the same issue.Will test the 2000 feet issue you mentioned that might explain some issues.CheersPhil

The database FSX uses is years old, any current AIRC data you use will reflect the new data and it wont always match FSX if things have changed. FSX will only recognize the freqs, fixes etc in its own database which may be why things don't always work for you.

Thank you for the replyI think this would explain it, but how can I get around this, or do i just have to work around it?Phil

Thank you for the replyI think this would explain it, but how can I get around this, or do i just have to work around it?Phil

The only way around it I know of is to check the info in FSX to ensure it matches the AIRC, but that can be tedious. In my case, I just plan every approach with the expectation that the instruments will fail and get ready for a manual visual approach, using the VASI's if available. The great thing about FSX is you can 'bust minimums' and the FAA won't pull your ticket :(

The simplest approach is to use an "old ARIAC cycle" when flying off-line. Preferably one that comes close to matching the sim's database!

The simplest approach is to use an "old ARIAC cycle" when flying off-line. Preferably one that comes close to matching the sim's database!

Which Cycle is that?

Which Cycle is that?

I am absolutely confused by some of these responses and apologize in advance if I have provided any wrong info above but my assumption with payware or freeware aircraft addons that have a working FMC is that they do not use FSX AIRAC's (I don't think FSX default uses AIRAC's but the ILS frequencies are built into the AFCAD bgl's). AIRAC's for commerical addons are usually included with the aircraft which include additional info like SID and STARS. You can update these commercially or free at Terry Yingling's website: http://planepath.com/. If anything, it might be wise to update the airport's AFCAD to update frequencies and to provide more landing opportunities that might be limited due to crosswinds. One of the things that could be messing up airports is the addition of a commercial AI program that installs and uses AFCAD's made for earlier versions of FSX. These may (I emphasize May) need to be found and renamed to XXXX.old to remove any conflicts. Hope this helps.Best regards,Jim

I too am confused as to why people need to use the latest ARIC's, unless places like VatSim require them. FSX will only read what FSX has, not whats in the AIRC's.My home base of PBI is a prime example. Since I can remember, and we are talking decades, PBI has 09/27 R and L. 9L and 27R are the main rwys, and the 'marker for 9L has always been named 'Ruben'.Recently the FFA has not only changed Ruben to ZISUR, but also changed all the names of all the fixes AND changed the rwy numbers to 10L/280R, a full 10 degrees difference.Guess which info FSX uses, the OLD info, and this is just one example. Fortunatly they didnt' change freq's yet, but that's not the point. The AIRC's use the latest info and FSX doesn't, so anytime an approach doesn't work, thats my first suspect.'Database is out of date' message on a FMC is a good thing in my book, the older the better for flying in FS.

Which Cycle is that?

Approximately May of 2005.

...my assumption with payware or freeware aircraft addons that have a working FMC is that they do not use FSX AIRAC's (I don't think FSX default uses AIRAC's but the ILS frequencies are built into the AFCAD bgl's). AIRAC's for commerical addons are usually included with the aircraft which include additional info like SID and STARS.

Your assumption is correct. FMC/FMS units usually require an external database - the so-called AIRAC cycle file(s) - which are the "most current." I say usually because there's at least one currently under development that will use either a "current AIRAC cycle database" or the FS9 database or the FSX database, which should hopefully satisfy everyone's needs.The sim of course uses a "fixed-in-time database" that cannot (easily) be updated, and then only on an airport-by-airport basis. Because of this, quite often there is a disconnect between what the FMC/FMS is presenting and the sim is presenting. To my thinking, there could be nothing more disconcerting at the end of a long flight to have been directed to use either a non-existent runway or a mis-aligned runway, but maybe that's just me... :(

Your assumption is correct. FMC/FMS units usually require an external database - the so-called AIRAC cycle file(s) - which are the "most current." I say usually because there's at least one currently under development that will use either a "current AIRAC cycle database" or the FS9 database or the FSX database, which should hopefully satisfy everyone's needs.The sim of course uses a "fixed-in-time database" that cannot (easily) be updated, and then only on an airport-by-airport basis. Because of this, quite often there is a disconnect between what the FMC/FMS is presenting and the sim is presenting. To my thinking, there could be nothing more disconcerting at the end of a long flight to have been directed to use either a non-existent runway or a mis-aligned runway, but maybe that's just me... :(

That's what I thought. Thanks Bill for helping me maintain my fragile sanity on this issue. I think it will help the OP too as your description is clear and well stated.Best regards,Jim

Thanks allThat has helped a lot, I guess its best to just go back to the default navDB that comes with each AC "CLS757" for example, that would appear to be best matched to the FS world.So much for all the effort to get the lates AIRAC!Once again thanks for the help Avsim is a fantastic resource and help to a wannabee like meCheersPhil

at the moment I'm using Airac 1001, having no problems even at EGCC where the runway heading have altered in real life but will remain the same in FSX.you can always check the ILS as it is given on the Approach page , (with the runway ID) when you set the Vref flaps for landing.click on map and click on the airport to get FSX ILS and compare. ( I suppoes you could alter it manually if not)I understand the 737PIC is not allowed to land VNAV or LNAV so check on the nav radio to see if the ILS is up and press the APP button, the ADi should indicate in white and at capture it will turn to green.if you have set the Vref flaps on the app page then this speed + 5knts will be transfered to the speed indicator on the MCP, make sure you have Vref flaps extended before capture of glideslpoe, the ADI will again change from white to green. of corse you need to have the second autopilot on if autoland is being used.at touchdown, show 'flare' in white and then change to green as well.at caputure of ILS and GS the LNAV and VNAV will go off.