AI Traffic: Difference between revisions

Jump to navigation Jump to search

AI Traffic (view source)

Revision as of 23:35, 5 December 2020

645 bytes added ,  5 December 2020
m
ICAO Reference for RWYUSE Crosswind and Tailwind
mNo edit summary
m (ICAO Reference for RWYUSE Crosswind and Tailwind)
Line 503: Line 503:
= Runway Usage Configuration =  
= Runway Usage Configuration =  


ICAO.rwyuse.XML dictates which runway(s) should be used for AI take off and which ones accept AI landings (Runway Configuration Pattern), based on the time of the day and wind conditions. Examples below taken from the Amsterdam Schiphol EHAM.rwyuse.xml file.
ICAO.rwyuse.XML dictates which runway(s) should be used for AI take off and which ones accept AI landings. These instructions are organised in multiple sets (or configurations) and ordered by preference of use.


Schedules can be defined so different runway configurations can be used at different time of the day. Different Sets can also be applied to the General Aviation and Commercial traffic.


Wind conditions are stored at the beginning of the file and indicate the maximum values of Crosswind and Tailwind acceptable to authorise take off and landing at the airport. These values vary with each airport and shall be sourced from published data.  
Each set of runway configuration is tested against the wind conditions and applies only if the crosswind and tailwind are within tolerance. If not, the next set in the order of preference, will be picked.
 
Examples below taken from the Amsterdam Schiphol EHAM.rwyuse.xml file.
 
Wind conditions are stored at the beginning of the file and indicate the maximum values of Crosswind and Tailwind acceptable to authorize take off and landing at the airport.


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
Line 513: Line 518:
</syntaxhighlight>
</syntaxhighlight>


{{quote|As well as aircraft, airports have operational crosswind and tailwind limits. [] The values vary but crosswind limits are normally 15-25 kts and tailwinds are normally no more than 10 kts.|ICAO|AMOFSG/10-SN No. 14}}


Each pattern (schedule) activation is determined by the < time > table in the file.
The < time > table defines the hours of activation for a particular Schedule. Each schedule contains a 'Pattern' ie a fixed number of runways allocated to either take off or landing).
For instance, at EHAM, the commercial "inbound" schedule/pattern is active from 06:20 to 08h30 UTC, at a time where there is more inbound than outbound traffic and the airport needs to allocate more runways to landing than to take off.
 
For instance, at EHAM, the commercial "inbound" schedule is active from 06:20 to 08h30 UTC, at a time where there is more inbound than outbound traffic and the airport needs to allocate more runways to landing than to take off.


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
Line 532: Line 539:




The different patterns of runways allocation are listed in each < schedule > table by order of preference and can be read/deciphered vertically as ”columns” delimited by commas.
The different sets of runways allocation are listed in each < schedule > table by order of preference and can be read/deciphered vertically as ”columns” delimited by commas.
When wind conditions do not allow the use of a pattern, the next one will apply (next “column”).
 
When wind conditions do not allow the use of a set, the next one will apply (next “column”).


Still using the EHAM.rwyuse.xml file as example, from 06:20 to 08:30 UTC, when the Inbound schedule applies; AI traffic will preferably use runway 36L for take-offs, and both 06 and 36R for landings (first “column” of data).
Still using the EHAM.rwyuse.xml file as example, from 06:20 to 08:30 UTC, when the Inbound schedule applies; AI traffic will preferably use runway 36L for take-offs, and both 06 and 36R for landings (first “column” of data).
Line 545: Line 553:
</syntaxhighlight>
</syntaxhighlight>


Shall wind conditions prevent the use of this configuration (Tailwind or Crosswind values exeeding the ones defined in <wind> above), the next pattern or “column” will apply ie 24 for take-offs, and 18R + 18C for landings.
Shall wind conditions prevent the use of this configuration (Tailwind or Crosswind values exeeding the ones defined in <wind> above), the next set (or “column”) will apply ie 24 for take-offs, and 18R + 18C for landings.
 
Again, if wind conditions prevent this configuration use, the next set will be used (18L for take-offs, 18R and 18C for landing).


Again, if wind conditions prevent this configuration use, the next pattern will be used (18L for take-offs, 18R and 18C for landing).
This test of runway sets against wind values will continue with the rest of the sets in the schedule until a valid one is found and applied.
This test of runway patterns against wind values will continue with the rest of the patterns until a valid one is found and applied.


It is necessary for each of the <takeoff> and <landing> entries to have an equal number of runway values, per schedule, so each pattern contains the same number of runways.
It is necessary for each of the <takeoff> and <landing> entries to have an equal number of runway values, per schedule, so each set contains the same number of runways.


[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMbEsE46ontK4G43zmrEqLEk%3D8ZK5sQ-vxZup%3DNjpaUDgb-ASw%40mail.gmail.com/#msg37166996 Source from Durk post in Devel]
[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMbEsE46ontK4G43zmrEqLEk%3D8ZK5sQ-vxZup%3DNjpaUDgb-ASw%40mail.gmail.com/#msg37166996 Source from Durk post in Devel]
BecOzIcan
86

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/129392"

Navigation menu