I consider myself luckey that I was able to download the SU2 update this quickly. Installation went smooth and I am just planning/setting up for a trial flight. Looks fantastic so far!When selecting my departure runway at CYHZ I noted only 2 of the 4 runways were listed (06, 24). Runways 15 and 33 were missing. A check of the CYHZ.txt file shows this under runways:RNWSRNW 06RNW 24ENDRNWSThis explains why only two are listed. I checked a few of the other files, such as Toronto (CYYZ) and found missing runways there as well.My question is this...Is there a reason why these runways are not in the txt files?Would I be safe to add the missing runways?Thanks for your hard work!

Yes you can add them. I am not very good with SID-STARS maybe Lee or someone can explain why they are not there and how to put them back in there.[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

>Is there a reason why these runways are not in the txt files?Yes there is. The DAFIF data I use only has procedures for the two runways.>Would I be safe to add the missing runways?Sure it's safe. Have a look at my tutorial in the "Aircraft Operating Manuals" folder for help in doing so.>Thanks for your hard work!You are welcome.Terry

DAFIF is apparently terribly deficient for Canadian airport procedures and unless an alternate source of data is found, users are going to have to create custom made procedure files for the Canadian airports... I believe PMDG is working on a place in the new website for people to upload and share these files with other users...Ryan

Thanks for the reply guys. Guess I'll study up on the new SID/STAR manual and start putting together some procedures.Sounds like a good idea to have a place on the web site to exchange the files!

Terry, I don't think only keeping runways that have procedures is a good idea. As you can see, folks cannot enter the runway for visual approach that way. You're probably filtering out a lot of runways this way.(In my own personal DAFIF procedures, I kept all runways at least 4500 feet, whether or not they have a procedure attached.)Lee Hetherington (KBED)http://www.precisionmanuals.com/images/betaimg.jpg

AGREED! You don't always use procedures in the real world.........[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

Hi All,Please bear in mind that DAFIF the source of Terry's database is a US military database. Can someone in Canada check something which came through my mind. Is there a regulation in Canada which stipulates that some runways at large airports are prohibited for use by the military?. Lee, although I agree with the parsing and minimum runway lengths you mentioned, it does not do any good if the incriminated missing runways are not included in BOTH the TRM seg AND the RWY txt files of DAFIFT. Terry and Lee, the DAFIF database has it known deficiencies this is why we are now compiling datas from several databases to get more accuracy. This however means that in some caes missing TRMs have to be entered manually when none of the database used show an existing terminal procedure. One thing is sure using several database bring down the number of terminal procedures to be entered manually to a manageable number. As to the parsing for runway lengths we are doing it at the end of the process not at the beginning only because the same database will be used for different aircraft types with different requirements.Last but not least, I am in no way trying to critizise the excellent work Terry is doing. Knowing quite well the difficulties in building accurate terminal procedure database it is already an extraordinary achievement for the PMDG users. Michael

>Can someone in Canada check something which came through my>mind. Is there a regulation in Canada which stipulates that>some runways at large airports are prohibited for use by the>military?. There is no such regulations here in Canada.Nick - CYUL