A320 Status page understanding difficulty
........You ask ATC to get the current weather and runway state of your destination airfield plus a couple of others, (or you listen to a few ATIS yourself if they are within range), to give you options as part of DODAR, (other mnemonics are available). That's what we always do in the Sim and no TRE has ever told us not to.
If you descend all the way down and approach an airfield, but only then - when getting the ATIS - you find the runway is too short for your particular failure, you have wasted time, fuel and potential energy.
Join Date: Jun 2009
Location: Mars
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
In the picture I posted above, you also have a fuel penalty. To take it into account, just like Vilas said with one more step:
- Complete ECAM actions
- Review FCOM proc(s) time permitting
- When workload allows, recall status and:
- Note if there is a fuel penalty (FUEL CONSUMPT INCRSD is displayed) and load your FPLN for the destination/diversion as accurately as possible to determine FMS EFOB. Use the QRH to determine the fuel penalty factor and the real EFOB (if FUEL CONSUMPT INCRSD is displayed)
- Determine Landing Perf (if LDG DIST PROC APPLY is displayed)
- Decide
- Communicate
Last edited by CrazyStuntPilot; 26th May 2022 at 13:35.
Join Date: Jun 2007
Location: Wanderlust
Posts: 3,407
Likes: 0
Received 0 Likes
on
0 Posts
In the picture I posted above, you also have a fuel penalty. To take it into account, just like Vilas said with one more step:
- Complete ECAM actions
- Review FCOM proc(s) time permitting
- When workload allows, recall status and:
- Note if there is a fuel penalty (FUEL CONSUMPT INCRSD is displayed) and load your FPLN for the destination/diversion as accurately as possible to determine FMS EFOB. Use the QRH to determine the fuel penalty factor and the real EFOB (if FUEL CONSUMPT INCRSD is displayed)
- Determine Landing Perf (if LDG DIST PROC APPLY is displayed)
- Decide
- Communicate
Join Date: Jun 2014
Location: Village of Santo Poco
Posts: 876
Likes: 0
Received 0 Likes
on
0 Posts
Yes, it is confusing.
They are basically saying that the different blocks of information are separated by a full height blank line - if you look on the diagram of the STATUS page above, it gives a MAX SPD..........250/ .85 then a full height blank line, then the next block, starting APPR PROC
What they mean is that each block is separated from the others by a full height blank line, so everything before the next full height blank line applies to the current block. Confusingly, they seem to use a half height blank line to separate actions or information which are part of each block, but not in the next block !
So, on the top diagram, the CAT 1 ONLY and the SLATS SLOW applies to the APPR PROC block, not the next block.
They are basically saying that the different blocks of information are separated by a full height blank line - if you look on the diagram of the STATUS page above, it gives a MAX SPD..........250/ .85 then a full height blank line, then the next block, starting APPR PROC
What they mean is that each block is separated from the others by a full height blank line, so everything before the next full height blank line applies to the current block. Confusingly, they seem to use a half height blank line to separate actions or information which are part of each block, but not in the next block !
So, on the top diagram, the CAT 1 ONLY and the SLATS SLOW applies to the APPR PROC block, not the next block.
Last edited by Amadis of Gaul; 29th May 2022 at 18:20.