"CABIN READY" item missing in T.O memo of the taxi checklist

[MR.TX]

As you can see in the image attached, the current iteration of the taxi checklists T.O memo isn't identical to the T.O ECAM memo due to missing the "CABIN READY" item. 

[Jetmagic]

Hi, Having the same issue here. I can only get the TO CONFIG to clear once the cabin is ready.. You can wait or press the Purser call on the overhead but obviously this shouldnt be the case as the a/c can be configured for take off, minus the cabin ready. 

[Xenon341]

Ini already answered that, it's a real setting that cabin should be ready before TO Config based on their A350 real life pilot feedback.

Edited September 9 by Xenon341

[ool]

On 9/9/2025 at 12:10 PM, Xenon341 said:

Ini already answered that, it's a real setting that cabin should be ready before TO Config based on their A350 real life pilot feedback.

Hi,

This is not true. CABIN...READY should not be required for the T.O CONFIG test to pass, and neither should the AUTO BRK...RTO or SIGNS/SEAT BELTS...ON. FCOM is also very clear about this, and I don't think there are any company variations about this either. 

TO CONFIG test simulates the application of takeoff thrust, and checks that certain parameters that are required for take-off are within limits. If something is not okay, it will give you an ECAM. However, CABIN READY, AUTO BRK RTO or SIGNS/SEAT BELTS are not preventing the TO CONFIG test to pass since they are not something that is required to conduct a safe take-off. 

You can also think about it this way: If you have a ferry flight without cabin crew, you don't have anyone in the cabin to press the CABIN READY button for you from the FAP. In this case, CABIN READY would remain blue in the T.O MEMO. Similarily, you could have your AUTO BRK U/S (as per MEL), and you could still take-off normally. However, the AUTO BRK line would remain blue in that case too, since you wouldn't be able to arm it.

[Xenon341]

I'm just giving you the answer they gave. I'm no 350 pilot nor airbus engineer to confirm or deny.

Edited Saturday at 08:01 AM by Xenon341