No boundary on RWY 4R

[specialist]

For the life of me, I can't understand why no matter what I do, whether keep traffic to a minimum or normal, AI aircraft just don't keep their distance when holding short of runway 4R. Even if I'm the next one on line to enter the runway, AI aircraft keep either running over my plane, or jumping ahead into the runway. I had ATC clear me to line up and wait, and as I started to line up, another place runs right over me and moves in front of me! It's just plane weird. It doesn't happen on any other runway at this airport, except for RWY 4R. Any clue? By the way, I use UT2 from Flight1. I've addressed the issue with them, and they don't think it has anything to do with UT2, because it doesn't happen to me at any other airports, or like I said, any other runway in this airport except the one I've mentioned.

[specialist]

Would any of the FlyTampa forum moderator let me know why this is happening on this particular airport and no other? I also have Tampa and St Maarten, and it's not happening there, so it leave the question why Midway?

[martin[flytampa]]

The problem sounds like something that could be caused by an error in the Afcad. For example missing hold short dot. I'll look into it.

[specialist]

Thanks, I appreciate the effort and will wait for your response.

[martin[flytampa]]

I checked the FSX Afcad and didn't see a problem. Will run it with 4R active and see what happenns here with WoAI.

[specialist]

I checked the FSX Afcad and didn't see a problem. Will run it with 4R active and see what happenns here with WoAI.

Thanks Martin, appreciate it.

[martin[flytampa]]

Are you sitting at the hold short line and waiting for ATC? If so, you may need to move closer to the runway ignoring the visual hold line. What happens is FS has a limited distance that a hold short node must be placed from the runway (in Afcad). This is often shorter at a shorter distance the real world hold short lines are. So we end up placing the visual line correctly where it is in real world, but the same Afcad hold short that controlls AI/ATC does not match and is instead closer to the runway.

If you just sit there eventually ATC and AI start ignoring you and just run you over.

Let me know if the problem is different.

[specialist]

I'll be able to test it tomorrow, and will let you know if that solves the problem.

[specialist]

Martin, the problem continues. As a matter of fact, here are two screenshots at RWY 4R. I was waiting behind the 737 when all of the sudden the small aircraft in front of me ran over me, and went right under the other aircraft. You also see how all the AI aircrafts are just bunching together at the short line. The thing is that it's not happening any where else. I've tested that by changing the wind directions and getting instructions from the ATC to go to those other runways. There all the AI aircrafts work fine. Don't have this issue at any of the other two FlyTampa airports I have, Tampa and St Maarten. I also checked with non FlyTampa airports, and AI works fine too. So the issue has something to do with this runway. Just can't put my finger on it!

[specialist]

Hey Martin, if you can shed some light and tell me what might be wrong with this picture, I really appreciate it. I've been flying several other airports besides FlyTampa, and I'm not having any problem with traffic holding short. For some reason it's just this particular runway.

[martin[flytampa]]

I'm in the dark as far as whats causing it. I managed to see the problem here as well tho. I can only be something in the Afcad, but I haven't found any problems in it yet.

[CEOEAV]

Funny I never noticed it until it was brought up. Weird

[psykie]

This same issue happened to me the other day when departing runway 4 at KMDW to KJAC. Has there been any remedies?

Matthew