Hello,I was doing a transcon flight (Delta 38) from KATL-EHAM a couple a day's ago, and as I was just starting over Ireland (somewhere around Omagh) my screen went black. Then about 15 seconds later CTD. Needless to say after flying for about 7 hours, I was not happy. I remember this occuring to me once before. That time was a FEDEX MD-11 flight from KJFK-LGAV. I had a CTD off the coast of Scottland.When my Delta flight failed, the error was from the Panel.dll. To recreate the fault I reversed the route EHAM-KATL (did not want to wait 7 hours). Once again CTD this time before reaching England. The plane I was using was a B763 using a 757/767 panel. At first I thought it might be a GMT problem, due to the fact it was only happing around England, Scottland and Ireland. I did have Realtime installed and connected.After the second CTD I removed the Realtime and tried it again. CTD around the same place. So I then tried a diffrent plane. B744F with default 747 panel. CTD around same place. This time the error said it was the Facility DLL. After reading the forms on Time Zone problems someone said that the FS9 dll files have trouble with panels that have XML clocks. With this in mind, I looked in the default aircraft panels to see what type of gauges were used. The only "Big" jet with your old style (FS8)clock gauge was the B737. So I tried the B737 default plane. NO CTD!!!! Made it from EHAM well past Ireland. But now I'm sad. No Transcon Flights????I decided to try the default B777, which does not have a clock but that Chriomoter (or whatever it is) which is XML. It CTD around the same place, but the error was from FS1 DLL. So I think this is what is happening. Any plane that has a panel that uses XML clock (or gauge that uses time, made in XML)will cause a CTD around the GMT line. I find it hard to believe that only one out three default "big" jets can cross the GMT!I don't have any UK airport scenery installed, except for PAI AFCAD's. I do have FSGlobal2005 installed. Though I'm sure it's not a scenery problem, due to B737 being able to complete the UK crossing. I have not installed FS9 patch for verious reasons.If anyone has any thoughts on the subject, please post them. I just want to make sure i'm not looking in the wrong place.Thanks.

not sure how to help you, but I know for sure that ive been having massive problems around that area to especially at EHAM i always get a CTD whenever im taxing at EHAM. Touch wood everywhere else is fine, and ive had no problems.I am forever graetfull to MS for FS2004 but I really hope that on the next release or whatever they decide to do, this CTD business is sorted, as it plays havock with Long distance flying and when you get a CTD after 7+ Hours in a plane like the PSS A340 where the panel state cant be saved (NOT A JIBE AT PSS) it kinda puts me off the whole thing.Jason

<< I have not installed FS9 patch for verious reasons.<

Thanks for your reply. I have seen on the forms that the patch can have side effects with FSGlobal2005. I will try out EGGL-KJFK as it is west of where I think the problem area is. Thanks.

If FSGlobal has changed default FS BGL files then perhaps it does but that would surprise me. I'm sure you'll be fine installing it and keeping an eye on the FSG website to see what they say about any possible problems.I've not had one FS crash since installing the patch. I think that speaks for itself. Microsoft rarely release patches and when they do I think you can take it as read that it will solve the problems many have experienced.Cheers,

Ray,Well after thinking about it, I followed your advice and downloaded the patch. Just to be safe I backed up all my add-on stuff. I was so worried about losing my Scenery, AFCAD's, AI Traffic and Add On planes. So then I installed the patch. First I'm happy to report it did fix the CTD off the UK coast. Second my planes, AI traffic, and AFCAD's remained intact. You most likely already knew this but I just stating it for anyone who has not installed the patch yet.But the patch did cause problems with my FSGlobal2005 Scenery. Just a small problems (Like mountain elevation) that I have read can be fixed easly. Oh, and one last thing, it had no effect on my USA Roads.Once again Thanks!

Two areas to look at. The NL2000 scenery can cause CTDs, particularly in the EHAM-EGLL area I don't use it because of that. Another possibility are faulty AFCADs. Disable local AFCADs then add them back one by one until you find the culprit.Lee

TB4iy,I'm pleased to hear it's resolved the lockups. I also have a lot of scenery and other addons which could have been affected but I had enough faith in Microsoft to trust they knew what they were doing.I'm sure the FSG group will release a patch for any mods that are needed.Enjoy your transatlantic hops!

good to see I'm not the only one experiencing crashes flying over the North Sea with NL2000 installed.Another problem with NL2000 is the dislocated waypoints and navaids in the Netherlands. When you fly with the default GPS everything is offset so following a plan to Schiphol will have you end up near Utrecht...