CTD with cycle 0704 KJFK procedures

[B777ER 2,484]

Loaded up the 0704 procedures into the LVL-D 767 from your website. I then loaded up the FMC as I always do and finally got to the point to input the DP for JKF. I selected runway 31L. I then selected the BET.CRI departure which of course stands for the BETTE3 departure with the Canarsie climb. As soon as I selected it, I was staring at my deskop. Did not even get the chance to hit the EXEC button. I reloaded a older JFK procedure file overwriting the one I got from you and it worked fine. Soemthing is big time amiss with the new JFK file for 0704 Level-D 767. thanks

[Guest staang]

Hello Eric,When looking at the xml file I do not find a BET.CRI. I see a BET.CAN which is the same thing. There is a BET.BRI though. If you see a BET.CRI then the file is not mine. In any case I tried the BET.CAN for the Canarsie climb since that is the one you described. First I rechecked the whole airport xml file for errors using the checkproc.exe program from Level-D and it did not find any errors. So I loaded up the 767 in FS04, put her at KJFK, selected 31L and then selected BET.CAN. I did not get a CTD. The route was displayed and I could step through it. Perhaps there is something else going on. Without being able to reproduce the problem I am unable to troubleshoot.Are you using the 0704 AIRAC file from navigraph? Just checking because I've heard the AIRAC file has caused problems in the past. I am using the last free AIRAC file from navdata.at. RegardsTerry

[B777ER 2,484]

Terry,Yes, it was BET.CAN..sorry, I was thinking of the actual VOR id when writing. Yes, I am using the latest from navigraph...I bet that is the problem. There have been airway changes and new waypoints added for the NAT routes as I use the real ones and thus need to stay with the latest AIRAC. Oh well. Thanks anyways.