DEPARTURE PROGRAMMING, INTERSECTIONS AND LATE RUNWAY CHANGES
Departure programming links the selected runway, SID, transition and first enroute connection. The planned runway, takeoff starting point and performance case must describe the same departure. An intersection changes available runway and potentially the takeoff reference without changing the airport. Our EDDF-EGLL dataset deliberately provides no invented runway, SID, intersection, V-speeds or FLEX value; current charts, clearance and calculation supply them. [66, PDF pp. 113-114,125-128,142-165,331-333]
1. Open the origin's departure revision. Select the actual runway and then the compatible SID and transition as presented. Read complete identifiers and inspect the join to the enroute route. A SID whose final fix resembles the first route fix is not automatically the correct procedure. Check the actual connecting legs and the published path at an appropriate ND range. [66, PDF pp. 113-114,125-128,142-165,331-333]
2. Establish the takeoff starting point. Match the EFB calculation to the runway entry actually intended. TO SHIFT on the MCDU is threshold-to-starting-point distance, not remaining TORA. If the start is displaced, obtain the appropriate distance in the displayed units and verify how it is represented. Do not subtract or insert runway lengths merely to make a number appear familiar. [66, PDF pp. 113-114,125-128,142-165,331-333]
3. Handle a revised runway as a new departure case. Revise the runway/SID/transition combination and inspect all re-stringing, gaps and manually edited departure segments. A procedure change can replace more than the first row. Compare the temporary path with the new chart and clearance before INSERT. Do not assume that manual changes attached to the previous departure remain appropriate or are preserved unchanged. [66, PDF pp. 113-114,125-128,142-165,331-333]
4. Recalculate and read back performance. Check takeoff mass, actual entry point, conditions, configuration and system assumptions in the calculation. Transfer and verify the resulting V-speeds, thrust request, FLAPS/THS and relevant altitudes. Inspect any fields cleared or changed by the runway revision. A correct new path with the old runway's takeoff figures is still an incomplete change. [66, PDF pp. 113-114,125-128,142-165,331-333]
5. Close the cockpit/ground loop. Reconcile the FCU targets and current clearance, intended taxi/runway entry, actual flap/trim configuration and takeoff memo/configuration review. If the change arrives while moving, preserve control and an appropriate stopped or low-workload opportunity for programming. The useful completion point is one coherent revised departure across route, calculation and actual aircraft state. [66, PDF pp. 113-114,125-128,142-165,331-333]