In my Custom KBGM Test Validation. The latest WED 1.5b4 is tagging all of the Active Red zones as incorrect and asks that the last green taxiroute segment before the red segment spanning the RW Hold, be tagged red to allow the Validate to be approved. I believe this is a false error.
The first segment of a red zone is the segment which spans across the RW hold toward the Runway access, as I understand it.
The starting point of this segment must be far enough away from the edge of the runway to accommodate half the width of the Aircraft Size rating of the Runway. Runway holds need to be located a minimum of this distance toward the Taxiway to be in the proper position and can then be further away. This then sets a minimum distance that the start of the Red segment can be located (and it can again be greater and always located on the insided of the Hold.) No extra red segment is required inside of this first point, as is incorrectly required by the b4 Validate, in my opinion
Actually, new in WEDb4, the hot zone extends laterally/sideways 10m (runways shorter than 1500m) or 30m (others) past the edge of the runway. This is for wingtip cleanance for aircraft landing and includes some allowance for aircraft landing off the centline of the runway. Its about 1/3 of what the FAA requires.
Its NOT depending on the runway taxi route size class, as X-plane does not determine the allowed size of landing AI aircraft from that, either.
Landing at 150 knots with gusty crosswinds requires a bit more clearance than taxiing to a gate ...
I took a look at the attached pack. The first taxi segment that got flagged was A at the very southern end of rwy 16.
Hot zones are located from hold short lines to the runway at real airports. The hold short lines visible in Google Maps at KGBM are much further away from the runway than in your pack. Thus, I believe WED is correctly flagging segments that should be hot zones.
If you move your hold short lines back to reflect the real world layout, I believe the hot zones WED wants will match.
In my Custom KBGM Test Validation. The latest WED 1.5b4 is tagging all of the Active Red zones as incorrect and asks that the last green taxiroute segment before the red segment spanning the RW Hold, be tagged red to allow the Validate to be approved. I believe this is a false error.
The first segment of a red zone is the segment which spans across the RW hold toward the Runway access, as I understand it.
The starting point of this segment must be far enough away from the edge of the runway to accommodate half the width of the Aircraft Size rating of the Runway. Runway holds need to be located a minimum of this distance toward the Taxiway to be in the proper position and can then be further away. This then sets a minimum distance that the start of the Red segment can be located (and it can again be greater and always located on the insided of the Hold.) No extra red segment is required inside of this first point, as is incorrectly required by the b4 Validate, in my opinion
Jennifer Roberts September 22, 2016 8:48 AM
Please provide a copy of the WED file.
An unknown user September 22, 2016 10:31 AM
Actually, new in WEDb4, the hot zone extends laterally/sideways 10m (runways shorter than 1500m) or 30m (others) past the edge of the runway. This is for wingtip cleanance for aircraft landing and includes some allowance for aircraft landing off the centline of the runway. Its about 1/3 of what the FAA requires.
Its NOT depending on the runway taxi route size class, as X-plane does not determine the allowed size of landing AI aircraft from that, either.
Landing at 150 knots with gusty crosswinds requires a bit more clearance than taxiing to a gate ...
EBOB_MARSH September 22, 2016 8:56 PM
I will send the WED File you ask for. If you need the full Custom AP, let me know. ERM
Jennifer Roberts September 23, 2016 10:06 AM
I took a look at the attached pack. The first taxi segment that got flagged was A at the very southern end of rwy 16.
Hot zones are located from hold short lines to the runway at real airports. The hold short lines visible in Google Maps at KGBM are much further away from the runway than in your pack. Thus, I believe WED is correctly flagging segments that should be hot zones.
If you move your hold short lines back to reflect the real world layout, I believe the hot zones WED wants will match.
Runway 10 is always active regardless of wind direction. It appears that there are flows designed for each runway, but they all use runway 10.
MrGeeBee October 6, 2017 3:56 PM
Cleaned up the the Taxi/Rwy's, removed the flow since they didn't work. But with correct Taxi/Rwy it should work better with auto assignment.
Runways from 52885 is constructed from Taxiway objects, which creates problem. This followed into 55761. Updating all runways into a new package.
B doesnt exist in the correct place, you cant go in a straight line from 16 if you exit right on B