True, but in order to fly online (vatsim, ivao) in Brazilian territory ther's a catch. In June 2004 the Brazilian "FAA" decided to go and rearrange Brazilian airspace and routing - all of it. This means new ATS and Rnav airways were created, old ones modified or scratched, and along with these changes came the terminal changes. All existing SIDs STARs and IAPs were thrown on the waste basket, and new ones were created for every single airport. Thus my need to create new procedures for the major Brazilian airports. The virtual controllers really appreciate it when a/c in their airspace are familiarized and up-to-date with real-world procedures. Cheers, Victor

Hi Victor,Sorry I did not reply earlier about your question relating to altitude constrains. Here you raise two issues:1. a general issue about altitude constrains as indicated in the Jeppesen charts. Here there has been much debate about the need to program some of them. I recommend you read the following thread in that respect: http://forums.avsim.net/dcboard.php?az=sho...d=72467&page=15You will see that in some cases it may not be necessary to program the AT or BELOW altitudes.2. The second issue is a syntax one. To the best of my knowledge it is not possible to program an AT or BELOW and AT or ABOVE for the same waypoint. Terry may have a better solution but my first reaction would be to say take an average altitude between both and program it as a hard constrain.Hope this help.Michael

>the following: I used some "at or below" and "at or above">commands coupled in some fixes to get that "between altitudes>restriction".Hi Victor. Combining the two to get a between should work but I believe the order they are used was important, if I recall right. Use "AT OR ABOVE alt AT OR BELOW alt". If that doesn't do it let me know and I'll bug the programmer about it. And you are using version 1.3, correct?RegardsTerry

Once again my thanks to Michael and Terry for the replies. and yep, using version 1.3. I'll test my soft constraint endeavours tonight. Cheers, Victor

Can you explain the all in one package from the navdata website? You have a 0501 cycle airac and then sid start 0501 and now an AIO?Thanks !

>Can you explain the all in one package from the navdata>website? >You have a 0501 cycle airac and then sid start 0501 and now an>AIO?Hi Joe. The AIRAC cycle 0501 is an update of all the navaids, intersections, airways and airport data. This happens every 28 days. 05 is for 2005 and the 01 stands for the first cycle of 2005.I'm not sure what "sid start 0501" is but probably you are referring to the DAFIF terminal procedures cycle 0501 or SID/STAR cycle 0501. This is an update every 28 days of all of the SIDs, STARs and IAPs and it uses the DAFIF as the data source. The DAFIF is a database that contains amongst other things, world wide terminal procedures. The AIO (All In One) file just contains all the terminal procedures that 737NG users have written and uploaded to navdata.at. They may or may not be current depending if the author checks them or not. It is not updated on the 28 day cycle. Generally the AIO contains airports and procedures that are not included in the DAFIF database.Please read the "Updating Terminal Procedures explained.txt" file that comes with the DAFIF terminal procedures download. It talks about all this and how to best update the procedures.RegardsTerry

Thanks Terry for your explanation there is one last thing that confuses me about this when updating what do you suggest i do overwrite all the contents of the sid/star folder or delete everything in the folder and then just copy and paste in the folder.The read me states one thing and the "Updating Terminal Procedures explained.txt" says the other.What is the Fsbuild airac for?

Hi Joe>do overwrite all the contents of the sid/star folder or>delete everything in the folder and then just copy and paste>in the folder.Either way will work. Each has it's own advantages. It's easiest to just let the unzip program overwrite all the other files. However, infrequently I've noticed that the total number of airports may vary a few. This being the case one would have to delete all of the old files first so as to get an accurate install. Personally I think its not worth the extra effort to do this though as the major airports are always in there. Now remember I am talking about only my terminal procedures here. Throw in any other airport files and it gets slightly more complicated.>What is the Fsbuild airac for?If you have FsBuild than that AIRAC will update that navdata.RegardsTerry

Understood, if there is an airport that has not been updated and i choose to do the overwrite procedure any airport that is new or not in the latest cycle but in the past cycles should not give me any problems right, I ask this because i see everybody mention to make sure that the sid/star is updated with the same cycle but yet some airports are part of old cycles and/or the AIO package may not have been updated in awhile.

Terry,Every time I install a new Airac and SIDS/STARS I lose Glasgow ! As soon as I put EGPF into the FMC it says "GLA not found" or something like that. I've always fixed it before by using the EGPF stuff from Simon's site - but that's gone now so this time I can't fix it. As everything elase works Ok I don't think its an instal problem. Anybody else had this please ? (737-700 / FS2004)

Hi Joe>everybody mention to make sure that the sid/star is updated>with the same cycle but yet some airports are part of old>cycles and/or the AIO package may not have been updated in>awhile.Ahhh Yes, you see the problem. The reason it is important to insure you keep the cycles in sync is because of a runway and navaid issue. In the real world navaids change and runway numbers change. These changes are then passed along in the AIRAC cycle. The 737NG FMC reads the AIRAC data and that becomes the data that it uses to fly with. Now if a SID, STAR or IAP comes along and uses an old runway number or navaid, an error is spit out by the FMC. So, by using the same AIRAC cycles this sort of error is avoided. Now the AIO file. This is a valuable service because most of those procedures are for airports the DAFIF does not have data for. With this in mind realize that the AIO package is just a collection of user written procedures that have been upload there over many months. The data used to write those procedures came from charts whose data may have been superceded by now. Therefore you can run into this problem. All is not lost though because the cure is to contact the author and request they update their procedures or to update the procedures yourself. RegardsTerry

Hello I've started a list where I will update you directly with my files.Please contact me via my site http://homepage.ntlworld.com/simon.butler2...usefulfiles.htmI am hoping to really concentrate on certain areas and keep you updated.Simon

Is there an easy way of knowing from cycle 0412 to 0501 what the files that are missing are (airports). In past updates i've verified the total number of files compared to the new cycle and it sems i've always lost airports now it happened again, i understand most major airports are always there but i did have problems with CYYZ in the 0412 cycle with missing RWYS. So this airport has been updated in this cycle and I would like to know what other airports have been updated, added or removed from the cycle, is there a list out there. I ask this because i'm now showing 83 extra airports in my pmdg sid/star folder compared to the 1720 that came with the last cycle, this of course by overwriting contents not deleting anything and no 3rd part files or AIO.Thanks Terry your a great help!

Hi again Joe.>Is there an easy way of knowing from cycle 0412 to 0501 what>the files that are missing are (airports). Not that I know of unless you keep a list.>ask this because i'm now showing 83 extra airports in my pmdg>sid/star folder compared to the 1720 that came with the last>cycle, this of course by overwriting contents not deleting>anything and no 3rd part files or AIO.Could those other airports have been downloaded from navdata.at sometime in the past? I don't keep a record of how many airports are done each cycle but I happen to have the last 3 cycles on my HD. 0412 had 1721 airports, 0413 had 1718 and 0501 has 1718 also. I know there is a variance but I don't think it is anywhere near the 83 you have.RegardsTerry

>>Could those other airports have been downloaded from navdata.at >>sometime in the past? No i think it was from the original when i bought the pmdg aircraft.