Originally Posted by eternaltransit

I also have the same aim, to provide the forum with accurate information - and I sympathise you may not want to take me on my word.

Thus, I've attached a heavily redacted screenshot of the MACS screen in question from a recent flight from an outstation.

As you can see, eligible pax lists are generated centrally by DXB and sent to a station. First a Platinum on a Saver ticket comes first, then Flex by status order. You can see further fare class is a determining factor in a tie.

The load controller will follow that list, absent any specific direction from DXB.

To clarify my earlier posts, you are correct that formally, the ASM or ASOs don't have operational control over loads - they are overseen by DXB. However, in practice, there is a lot of leeway for controllers to listen to ASMs or duty ASOs, e.g. blackballing pax for bad behaviour (or doing an emergency move).

With regards to the manuals - EK segregates information quite well. For instance cabin crew can't access the ground operations manuals, and ground staff can't read the latest Safe Talk.

Similarly you see it in such things like cabin crew only being able to see other cabin crew rosters, and flight crew only being able to see other flight crew rosters (yes, I know that there are ways around it): another one is load information - cabin crew can now only see things 3 days in advance, but ground staff can access specific booking information.

That is why I wouldn't trust non-ground dispatch staff when talking about procedure like this unless they have direct experience.

I hope the screenshot is sufficient proof to show the new system and to back up my posts - I certainly don't spend my time making things up or passing off conjecture as fact. "Groping in the dark" is a waste of time as I'm sure you'll agree - it doesn't help anyone.