PERF: CALCULATE, TRANSFER AND VERIFY
Run the EFB takeoff calculation for the loaded engine variant, mass, actual runway entry point, surface condition, wind, temperature, pressure and intended configuration. Confirm the available runway used in the calculation, especially for an intersection departure. A valid result for another entry point is still the wrong result for this takeoff. [59, PDF pp. 6-8] [74, PDF pp. 8-9]
Transfer the calculated V1, VR and V2, thrust choice and FLAPS/THS to the appropriate fields. Read the accepted entries back against the performance result and compare the actual flap and trim settings with the selected configuration. The useful crosscheck connects the calculation, the MCDU and the aircraft. [66, PDF pp. 125-128]
When the calculation calls for FLEX, enter the specified assumed temperature. A runway, weather, loading or configuration change sends the affected preparation back through the calculation and verification. The example shows the entry workflow; the actual EFB result supplies the takeoff figures for the sector being flown. [66, PDF pp. 125-128] [74, PDF pp. 8-9]
IN PRACTICE: PERF: transfer a valid takeoff calculation
Before you begin: Final load, actual runway/entry point, current conditions and intended configuration are known. Have the current EFB performance result beside the MCDU; this exercise supplies no invented V-speeds or FLEX temperature.
1. Check the calculation’s aircraft and load
Action. Open the EFB takeoff calculation and confirm the A320 CFM configuration and final mass. Check that the selected aircraft profile is the one loaded in the simulator.
Check. The calculation belongs to this aircraft and loading state, not another family member or an earlier version of the load. [66, PDF pp. 125-128] [106]
2. Check runway, entry point and conditions
Action. Confirm the actual runway and intersection/full-length entry, surface condition, wind, temperature, pressure and intended configuration. Include the applicable pack/anti-ice choices in the performance assumptions.
Check. The available runway and conditions used by the calculator agree with the intended departure. A change of entry point has not left a full-length result in use. [66, PDF pp. 125-128] [23, PDF pp. 1063-1064]
3. Review the result before copying it
Action. Run the calculation and inspect its validity and any limiting information. Resolve incorrect inputs or an unsuitable result before transferring figures; do not treat the presence of numbers as approval to depart.
Check. You have a usable result with understood assumptions. The selected takeoff thrust/configuration is supported by that result. [66, PDF pp. 125-128] [23, PDF pp. 1063-1064]
4. Verify the PERF runway
Action. Press PERF and open TAKE OFF. Compare its runway with the departure selected in F-PLN and the EFB calculation. Resolve a disagreement before entering speeds.
Check. Route, performance page and calculation refer to the same runway. A previous runway’s data have not survived behind the new route selection. [66, PDF pp. 125-128] [66, PDF pp. 142-165]
5. Transfer and read back the speeds
Action. Enter the calculated V1, VR and V2 into their respective fields, then read them back individually against the current result. Check the entry accepted by the MCDU, not only the scratchpad you typed.
Check. Each speed matches the calculation and occupies the correct field. No teaching-example speed has been substituted for the actual result. [66, PDF pp. 125-128]
6. Transfer configuration and thrust data
Action. Complete FLAPS/THS from the calculated configuration and trim information. Enter the calculated FLEX temperature only when FLEX is the valid selected thrust method. Verify the resulting configuration/thrust entries against the EFB result.
Check. The page represents the intended flap/trim and thrust preparation. A FLEX field has not been filled with an arbitrary temperature to make the page look complete. [66, PDF pp. 125-128]
7. Review the remaining departure parameters
Action. Check transition altitude, thrust-reduction/acceleration and engine-out acceleration entries against the actual procedure and applicable operating assumptions. For an intersection departure, check TO SHIFT as the distance from the runway threshold to the start-of-takeoff point, in the configured M or FT units; it is not the remaining takeoff run available.
Check. Stored defaults have received a real check. The runway-entry information and departure parameters are consistent with the flight being prepared. [66, PDF pp. 125-128]
8. Set a clear change trigger
Action. After any relevant runway, entry-point, weather, loading or configuration change, recalculate and revisit the affected MCDU entries. Complete the comparison again before treating takeoff preparation as finished.
Check. One coherent result is in use. The aircraft is not carrying a mixture of new route data and old takeoff figures. [66, PDF pp. 142-165] [23, PDF pp. 1063-1064]
Complete when: The takeoff page agrees with one valid calculation for the actual departure. A subsequent relevant change sends the affected preparation back through the same calculation and readback.