Just flew into MMMX (Mexico city) using lds 767 from KMIA (Miami)about 1100 miles, landed the aircraft on 23L, at about 25kts all of a sudden a air canada jet just comes out of nowhere, straight across the runway and slams right into the side of me bringing my flight with fs passengers to an abrupt end. I was using UT witht he correct afcad for the airport. As you can imagine this kind of put a big downer on things!Paul.

that's Air Canada for you...

>Just flew into MMMX (Mexico city) using lds 767 from KMIA>(Miami)about 1100 miles, landed the aircraft on 23L, at about>25kts all of a sudden a air canada jet just comes out of>nowhere, straight across the runway and slams right into the>side of me bringing my flight with fs passengers to an abrupt>end. I was using UT witht he correct afcad for the airport. As>you can imagine this kind of put a big downer on things!>>>Paul.That's the downside of the new AFCAD method to allow cross traffic runways. The best thing to do about it at this point is to turn off collisions with other aircraft.

AiSeparation or AiSmooth will also help.

I was using the crossing runways AFCADS for awhile and finally deleted them all as I found it so unrealistic that the benefit of the lessening the traffic problem was not worth it. Instead, I've found that editing the AFCADS for a a more realistic traffic flow really helps. I don't know how much this conforms to reality, but it works most of the time for me with UT at 100%. Basically, at any airport with parallel runways I designate the inner runways as takeoff only, and the outer as landing only. This has GREATLY improved both the air and ground traffic flows, though I still use AISmooth (V1.0!). I used to have a huge problem at Newark, but now that runs great. Also works well for Denver, Orlando, etc. Just takes a bit a time to edit the AFCADS. Mike