mSparks43
commented
5 years ago KSFO is going to be one of the "problem" ones. What a maze... Couple of things I notice / thoughts (which I'll have to test when developing airport procedures further)
- Possibly leaving rogue taxi nodes on the runway
- missing definitions of taxiway/runways
- Really looking like the best way forward will be to pull airport map data out of OSM, and this is going to have to be a priority for future AI server updates
- AI planes need to always hold short of runways
- While AI planes re routing to sneak a round each other is mildly amusing, more complex (insane) airports like this are going to need some conversation and special attention around operational safety
KSFO gets special mention in SOIA proceedures https://www.faa.gov/air_traffic/publications/media/AIP_amd2_dtd_12_10_2015.pdf
As Flight model (FM) and taxi improvements have gone in, these kind of bugs are getting more rational. The above gridlock is caused by approving start/up and taxi when doing so will cause a taxiway way conflict.
KSFO Taxi to 28L via Z U C causes aircraft to turn on 1R/19L instead of crossing 1L/1R on C toward the end of 28L. This puts them in the mother of all bad places, pretty much where 28L/R, and 1L/R all converge with their wonderful # sign configuration. It considers this place to be the hold short of 28L, and then when instructed to take the runway, they taxi down 28L and turn around at the end.
Some aircraft are also confused as to the frequency they are on. One of them contacted the tower for taxi clearance [on the gnd frequency], and ground gave it instead of saying... wrong frequency or "this is ground."