OnCourse Software

ThomasAH wrote:

By the way, in my default FSX version of EGTE the taxiway F exists, but is closed.
In the EAD chart (AERO INFO DATE 18 FEB 15) it is usable.
And PF3 did not tell you to use F, so if your add-on scenery includes a usable taxiway F, you still need to run the database update.

The current eurocontrol charts show that taxiway (taxiway foxtrot) to be open. Holding point F1 appears to be too far away from the runway for sim purposes that is. The hold short node circle should intersect the boundary between the taxiway and the runway. So you need to move it further along. There are lots of airports where this is a problem. Even at LIMZ I had to add a "sim" holding point as the true holding point is too far back. Airport scenery is not designed with ATC addons in mind.
Load up the airport afcad and check all the hold short limits and adjust them if necessary not forgetting to update makerwys and PF3 after.

JohnY wrote:

Thanks Thomas. You've just added a runway I never knew existed - F!.

I've never heard of runways being designated with a letter - only numbers.

Taxiway F, not runway F
(and I did not know before that you can mark taxiways as existing, but closed in FSX etc.)

ThomasAH wrote:

JohnY wrote:

Thanks Thomas. You've just added a runway I never knew existed - F!.

I've never heard of runways being designated with a letter - only numbers.

Taxiway F, not runway F
(and I did not know before that you can mark taxiways as existing, but closed in FSX etc.)

The default afcad has taxiway F as closed. So that could also be misread.