In VoxATC I've noticed on several occasions (particularly at FlightBeam's KDEN, KPHX, and KMSP) that when there are parallel runways of different lengths, VOX (for me) has assigned on departure shorter runways for takeoff, while AI aircraft are landing on the longer runways.

According to what I know about RW aviation (from direct observation and also various sources -- apologies for not providing links) but RW aircraft generally need all the runway length they can get on takeoff (in case of engine failure or other problems before V1).  Further, aircraft generally do not need as much runway on landing (except maybe heavy's).  Also note that in the RW I've read that, for optimal traffic flow on the ground, departure runways are the closer (usually longer, in my observation) runway to the terminals.

Again, in my observation, VOX does just the opposite (i.e. assigning shorter runways on takeoff and longer runways on landing), which is unfortunately diminishing my sense of immersion (assuming I'm correct in my assertions above)...

Specific examples (with FlightBeam's airports) include VOX assigning to me a taxi to RWY 7R (the shorter runway) while AI aircraft are landing on 7L.  Yesterday at FlightBeam's KMSP I was taxied to 12L (instead of the longer 12R).  In both situations the shorter runways were farther from the terminals than the longer runways. 

Maybe this is an AFCAD problem with FB's airport scenery?  If so, perhaps VOX can overcome that merely by analyzing runway lengths on its own?  I mean, VOX controls the AI traffic, so it shouldn't really matter?

Perhaps someone who is more authoritative on takeoff/landing procedures (at airports like the ones I mentioned above) can verify my assertations about RWY length and proximity to the terminals?

Thank you for listening!

-Tim

I think the solution to this is to allow for the runways (departure and arrival) to be selected and associated with the loaded flight plan along with the SID & STAR. The AI traffic would also be set up to use those runways. Something fot the To Do list.

In my observations, parallel runways can have the same SID.  In this case, runway assignment would not be determined until after taxi instructions are coordinated, which could be well after AI traffic is already departing and landing.  I suppose AI traffic could be adjusted at that point (i.e. runway selection), but perhaps in VOX Settings the preferred RWY would need to be entered prior to loading the sim?  I don't recall that RWY selection is part of the flight plan file (maybe I'm wrong?), and I always spawn at a gate (not a runway).

EDIT:  I see now that Little NavMap creates some sort of runway waypoint on departure.  Not sure though about SimBrief, which is my preferred flight planner.

Edited November 20, 20205 yr by tjahns