display combi range limits based on total cargo weight rather than on pax

[sanabas]

This is just a QOL/misleading info thing. If I attempt to create a route for RJTT-KLAS via PACD, the return leg is shown as limited to 163 pax on a DC8-33, 24,786 kg on a DC8-54AF. So I know the ESAD of the longest leg is ~3140NM.

So the DC8-54CF I'm going to use on the route will be limited to ~29,300kg overall, or pax + about 23,000kg of cargo. Its actual cargo capacity is ~35,000kg, so payload is clearly limited by the range. But because the maximum number of pax it can carry is 84, and because this route allows me to carry more than 8,400kg in total, the route creator incorrectly says 'no payload limits' for the combi.

When creating a route, I have no idea if I can carry 65 pax + 2,000kg, or 65 pax + 35,000kg, because the route creator says no payload limits for both. As the point of using a combi is to carry cargo, my cargo payload limit is extremely important. 23,000kg for 3140 ESAD is worth flying. 5,000kg for 4100 ESAD is probably not worth it. Would really like to be able to see that on the create route screen instead of employing workarounds.

[LemonButt]

+1 for this--I don't recall seeing any range variants for Combis that would throw things off so I think this should be pretty straightforward.  The thing I don't like is that even if your range is 3000nm the wind component can stretch it out to 3200nm which means you have to dig even deeper to get the correct value to plug in to the range chart, so if this could be synthesized/displayed on the route screen it would eliminate several steps.

[DanDan]

why not standardize all the distance-information to a common standard:
- MTOW with maximum fuel loaded

or possibly three values, the additional ones being:
- MTOW with max cargo/pax
- MTOW without cany cargo/pax

[LemonButt]

why not standardize all the distance-information to a common standard:
- MTOW with maximum fuel loaded

or possibly three values, the additional ones being:
- MTOW with max cargo/pax
- MTOW without cany cargo/pax

We have this on the range charts already--attached is the MD-11C which shows max cargo/pax at ~3600nm and pax only at 6580nm.  The issue is if you fly between 3600nm and 6580nm then the notice will say the MD-11C can fly this route without any limitations, which is clearly not true.  If the aircraft were pax or cargo only, it will display the limited range, but if it's a combi it doesn't show the cargo limit unless you fly past 6580nm and the pax number is less than the max.  That is where the contention is.

Additionally looking at the MD-11C there are 3 different engine variants which will make this not so straightforward, so not sure the best way to implement this.  My other complaint with scheduling combis is that the cargo allocations are based on volume and not weight, which I also understand from a mathematical standpoint, but when you're trying to "right size" the cargo for a route across cargo types, to some extent you're throwing darts at a board you can't see and just requires trial/error to get the ratios right--especially if you're flying in that 3600-6580nm window where you are payload limited, adding another factor to account for.

Ultimately any displayed numbers would end up being wrong (maybe show a range or the worst case scenario?), but will ultimately be better than what we have now which is no immediate numbers/information.