I tried other routes with this plane (Airbus 300-600), and the same thing happens. Cargo settings for the route do not in any way affect cargo load/unload times.
I’ve done this on other planes and the times change as they should.
Is there something wrong with this type of plane? Or am I missing something?
EDITED: Corrected airport destionation code (SYX not SYA)
I shortly changed my settings from default to avoid cargo and no bulk. This also set this to any other airline, I had on this server-> it became the new ‚default‘. Was this maybe already your default setting? Could explain this… but can’t open your images on the mobile so not sure…
Sometimes what I’ve found is that some airports don’t react to remote stands, this is because since the airports don’t have jetbridges both settings would mean a remote stand anyway. So if an airport doesn’t have jetbridges then opting out is the same as opting in - therefore t/a’s do not change anything.
Same thing with cargo - some airports simply can’t handle it, or it might be something with either the A/C type, payload % on the route, or again airports themselves.
For A/C - some jets don’t handle cargo and some carry little. You likely know that by now.
For some, if the payload is anywhere below 100% then cargo doesn’t operate. Some aircraft types do partial cargo when the payload isn’t 100%, but some (like my E-jets) don’t do that. Not necessarily sure on the reason.
Then some airports without cargo facilities (again disproportionately the small ones) simply do not accept it.
It depends on the scenario, really/.
The remote stand is a possibility. I wish the airports would display somewhere what they can handle.
The cargo still makes no sense, though. No matter which setting is used with the route (default, avoid bulk, no cargo, no cargo & avoid bulk), the baggage load and unload times remain the same, 32m to load, 37m to unload.
The plane is an AB6, so there’s a fair amount of cargo capacity for the plane.
If there was no cargo capability for the airport or the route, the times should be zero, not 30+ minutes regardless of settings.
I noticed that you mentioned your routes in the USA works as expected. Therefore I assume that this is a connecting flight that you don’t have traffic right. In this case, the flights defaults to cargo only, and the options in the route setup did not apply. I think this could be a bug, as the edge case for a passenger flight without traffic right is automatically assumed as a cargo, and cargo capacity cannot be disabled.
My routes in the US that work as expected are in reference to a different airline I ran where I had to make similar changes, and they worked as expected.
I think that’s because of the aircraft. If you’re using 737/A220, probably there will be a difference. (I’m sure A220 will)
737/CS3 are too narrow to fit any ULD. But A300/A310 are wide-bodies, and can load ULDs, which generally saves some loading time. Remember passengers have baggages, so what you see here probably is for loading baggages, which cannot be shortened. 737/CS3 will have difference - handling only baggages will save some time.
So, there’s three types of cargo not two? Bulk, container, and passenger bags?
To be honest, cargo has always confused me somewhat. There’s only one section for it, but it’s measured two different ways (volume, weight) and there’s two (or three) different types, that all seem to be calculated independently using either volume or weight (or both).
How much of the cargo space goes to passenger bags?
That’s kind of the problem. I’ve heard all sorts of stuff, too, and there are no definitive answers.
When I buy a plane, I have no idea how much cargo it will actually be able to carry. Numbers are all over the place.
For example, I buy a plane with 6988kg of cargo capacity. Sometimes it has 36 units of cargo bookable. Sometimes 24. Sometimes 26.
On some planes, when I adjust the cargo settings, turn around times decrease. Other times, nothing changes.
There’s no apparent reason why any of these things do what they do other than numerous (and sometimes contradictory) messages on the forums that go back 10 years in some cases, so I’m not even sure if they’re relevant anymore.
I wish AS would publish a small article or wiki entry explaining how all these cargo types affect each other, why some are in volume (cubic meters) and some are in weight (kilograms), and how and why all of them affect the turnaround times (or have no affect at all), with a simple example included for one plane on one route. Just something to help clarify things.
A220-300: MPL 19.85t, cargo vol 31m^3, cargo weight 5.267t
If you put 125 pax in, then:
remaining payload = 19.85 - 12.5 = 7.35 t
Assuming 1 cu (bulk) = 1 m^3 = 100 kg, so
remaining payload: 73 cu
cargo vol: 31
cargo weight: 52 cu
so the binding constraint is cargo vol, so you can almost always put 31 cu in CS3 (assuming you’re not stretching the max range). This is consistent with the fact that CS3 has surplus thrust, which makes it a good candidate for airports like LXA, MEX, JNB. And CS3 cannot load any ULD, so if you disable cargo, you’ll save time.
However, if you use A320, which enables ULDs, it will not save time when you disable cargo since it will load all ULDs anyway (to balance the weight).
Containered capacity differs: here it’s the net volume within the containers and weight to volume isn’t straight away 1/6 - thanks to container tare weights.
If turnaround times don’t change when cargo settings are changed, then cargo wasn’t your critical path (click the turnaround fields next to your flights on the flight plan page)
A general read notice for type info:
“main deck” or “lower deck cargo” is containered cargo (a lot faster turnarounds then bulk)
First I changed it while scheduling a flight, and then reloaded the page. This normally changes the turnaround times right away. This has always worked for me before, anyways.
Since that wasn’t working this time, I cleared out the entire flight plan, and scheduled a brand new flight with the cargo disabled, and it still came up with the 32m / 37m times.
