AirwaySim
Online Airline Management Simulation
Login
Username
Password
 
or login using:
 
My Account
Username:
E-mail:
Edit account
» Achievements
» Logout
Game Credits
Credit balance: 0 Cr
Buy credits
» Credit history
» Credits FAQ

Author Topic: [-] Variable turn time based on pax carried on route  (Read 254 times)

Offline swiftus27

  • Members
  • Posts: 4395
[-] Variable turn time based on pax carried on route
« on: July 16, 2013, 08:50:59 PM »
An A380 set up as a cattle car should take longer than norm.
An A380 with 60 suites in it (or whatever) should take shorter than norm.  

With that said, assume turn times are based on the standard setup.... more pax, more time.  
« Last Edit: December 27, 2013, 03:21:18 PM by sami »

Offline EsquireFlyer

  • Members
  • Posts: 1327
Re: Variable turn time based on pax carried on route
« Reply #1 on: July 17, 2013, 08:53:45 PM »
An A380 set up as a cattle car should take longer than norm.
An A380 with 60 suites in it (or whatever) should take shorter than norm. 

With that said, assume turn times are based on the standard setup.... more pax, more time.   

I don't see how this is possible within the UI given that the specific AC is not known when designing the route, but maybe it can be done on the backend? (similar to payload restrictions when an AC has many range variants available)

When calculating actual delay % for a given flight, consider the # of pax the AC is designed to carry in its current config, and adjust the delay % up or down accordingly. And the delay % shown on the route design screen can be either worst-case scenario, or can be using the factory default config (with a note explaining that).

Offline swiftus27

  • Members
  • Posts: 4395
Re: Variable turn time based on pax carried on route
« Reply #2 on: July 17, 2013, 09:00:26 PM »
It can take into account that pax load has on range so it has to be possible


Offline EsquireFlyer

  • Members
  • Posts: 1327
Re: Variable turn time based on pax carried on route
« Reply #3 on: July 17, 2013, 09:08:13 PM »
It can take into account that pax load has on range so it has to be possible



That is done after a specific airframe is locked in, not on the route scheduling page (which is currently the only place where delay likelihood % is currently shown). So I think it can be done on the backend, I'm just saying it can't be displayed on the front end in the current UI (unless this aspect of the UI is redesigned).

Online schro

  • Members
  • Posts: 3068

 

WARNING! This website is not compatible with the old version of Internet Explorer you are using.

If you are using the latest version please turn OFF the compatibility mode.