London Heathrow to Paris CDG

beginner
πŸ“ Route: EGLL β†’ MID β†’ BOGNA β†’ HARDY β†’ XIDIL β†’ BIBAX β†’ LFPG (via L612, M605, UM605)⏱ ~7 minutesπŸ“Š 23 stepsπŸŽ“ Flight Plans & Routing

A complete short-haul setup, gate to gate on paper: London Heathrow to Paris Charles de Gaulle, the sector every A320 pilot in Europe has flown a hundred times.

What this scenario covers

This is the full pre-flight sequence rather than one page in isolation. INIT for the city pair and cruise level, F-PLN and AIRWAYS to build the route south through Midhurst and across the Channel on L612, M605 and UM605, then PERF for the takeoff numbers. Each page hands off to the next in the order a crew actually works.

The route itself is short enough that everything fits on one or two F-PLN pages, which makes it a good first look at how the flight plan is displayed: waypoints in sequence, with the FMGS filling in distances and predicted times as soon as it has enough data to compute them.

Route map for London Heathrow to Paris CDG
The EGLL β†’ LFPG route this scenario programs.

How it applies in flight ops

EGLL–LFPG is around 200 nautical miles and barely an hour block to block, so the box work is compressed: the same programming a transatlantic crew spreads over a long briefing gets done between doors closed and pushback. That pressure is exactly why the sequence is standardised β€” crews do not invent an order on the day.

Short sectors also make the cruise phase almost incidental. The aircraft levels off, and very shortly afterwards the descent planning starts, which is why getting the arrival end of the flight plan right at the gate matters more here than on a long haul where there is time to fix it.

Start this scenario

Opens the SimTuts A320 MCDU trainer with β€œLondon Heathrow to Paris CDG” already running, so you can walk through it step-by-step on the simulated keypad.

Open trainer β†’

Step-by-step: London Heathrow to Paris CDG

  1. Start by entering your route. Type EGLL/LFPG into the scratchpad, then press the 1R line select key to enter it into the FROM/TO field.

    EGLL is London Heathrow, LFPG is Paris Charles de Gaulle. These ICAO codes come from your Operational Flight Plan (OFP) β€” the document dispatch provides before every flight.

  2. Enter your flight number. Type BAW304 into the scratchpad, then press 3L.

    Your callsign from the OFP. BAW = British Airways ICAO code, 304 = flight number. ATC uses this to identify you on radar.

  3. Set the cost index to 35. Type 35 and press 5L.

    Short-haul flights often use a lower cost index than long-haul because fuel savings per hour are smaller over short distances. Your airline's dispatch sets this value on the OFP β€” it's not a pilot decision.

  4. Set your cruise flight level. Type FL230 and press 6L.

    For a 45-minute flight you won't spend long at cruise anyway, and the route sets the ceiling: the UK Standard Route Document caps the Midhurst routing to Paris at FL245, and the French airways it joins are flown at odd flight levels. FL230 is both. The OFP specifies the level.

  5. Good. Now press the F-PLN key to build your route.

    The F-PLN page shows your route as a sequence of waypoints. After entering FROM/TO, the FMS creates a skeleton route with a gap (discontinuity) between departure and destination. You now build the route through it.

  6. You can see EGLL at the top, a discontinuity, then LFPG. Heathrow's Paris traffic leaves to the south, via the Midhurst VOR. Type MID into the scratchpad and press 2L β€” the key next to the discontinuity β€” to put MID after EGLL.

    In the real aircraft you would leave Heathrow on a SID to MODMI and follow airway M185 to Midhurst (MID). The trainer does not carry Heathrow's SIDs, so MID stands in for that whole departure here: it is where this route joins the airway structure. A waypoint typed onto the flight plan goes in at the line you press and leaves a discontinuity after it β€” the Airbus FCOM says a directly inserted waypoint "creates a discontinuity" β€” so the gap is still there, now below MID.

  7. Now the first airway. Type L612 into the scratchpad and press 2L (next to MID). This opens the AIRWAYS page, with L612 as the VIA from MID.

    Airways are published routes in the sky, like highways, and your OFP names the ones dispatch filed. L612 runs from Midhurst south to BOGNA, on the south coast. The FMS checks that the airway actually passes through the waypoint you start it from β€” no airway contains an airport, which is why the route needed MID first. One thing to know about the gesture: typing the airway straight onto the waypoint's line is a trainer shortcut. The Airbus FCOM documents one way in β€” a lateral revision at the waypoint (its key with an empty scratchpad, then AIRWAYS at 5R) β€” and does not describe this one either way; the AIRWAYS scenario teaches the documented path.

  8. You're on the AIRWAYS page, revising from MID with VIA L612. Enter where you leave the airway: type BOGNA and press 1R.
  9. Now press 6R (INSERT*) to insert L612 into your route β€” BOGNA drops in after MID.

    When you insert an airway, the FMS fills in every waypoint between the point you revised from and the TO, from its navigation database. MID to BOGNA is a single leg of L612, so here that is just BOGNA β€” two airways from now you will see a waypoint appear that you never typed.

  10. From BOGNA the route goes direct to HARDY, out over the Channel. Type HARDY and press 4L β€” the key next to LFPG β€” to insert it before LFPG.

    Not every leg is an airway. In the routing ATC expects for this flow, BOGNA to HARDY is a direct (DCT) leg, so HARDY goes in as a plain waypoint. Typing a waypoint and pressing a waypoint's line key inserts it ahead of that waypoint β€” the one you pressed slides down, behind a discontinuity, because the FMS never assumes the two join.

  11. Next, the airway across the Channel. Type M605 and press 4L (next to HARDY) to open the AIRWAYS page from HARDY.
  12. M605 runs from HARDY to XIDIL, on the boundary between London and Paris airspace. Type XIDIL and press 1R.
  13. Press 6R (INSERT*). XIDIL drops in after HARDY.
  14. In French airspace this route continues on UM605. Type UM605 and press 5L (next to XIDIL).

    In France the airway is split by level: M605 runs from FL065 to FL195 and UM605 from FL195 upwards, both on the same track from XIDIL to BIBAX. At FL230 you are on UM605. The FMS flies the same line either way; the name matters to the flight plan ATC holds, and the OFP names the one that matches your level.

  15. UM605 runs XIDIL β†’ PETAX β†’ BIBAX. Type BIBAX and press 1R β€” the fix where the Paris arrivals begin.
  16. Press 6R (INSERT*). This time the FMS adds a waypoint you did not type: PETAX, between XIDIL and BIBAX.

    This is why you insert an airway rather than typing its waypoints: everything between your start and your TO comes from the navigation database, in order, so nothing can be skipped or mistyped.

  17. The enroute route is complete: EGLL β†’ MID β†’ BOGNA β†’ HARDY β†’ XIDIL β†’ PETAX β†’ BIBAX β†’ LFPG. Press the PERF key to set up takeoff performance.

    In the real aircraft an arrival (STAR) from BIBAX into Charles de Gaulle would come next; this scenario stops at the enroute part. The PERF (performance) page is where you enter takeoff speeds and configuration. This data is critical for safe takeoff β€” the FMS uses it for speed callouts and flight director guidance during the takeoff roll.

  18. Enter V1 speed. Type 145 and press 1L. V1 is your decision speed β€” above this, you're committed to takeoff.

    V1 comes from takeoff performance tables or an EFB calculation. It depends on aircraft weight, runway length, temperature, altitude, wind, and surface condition. Below V1, you can still abort the takeoff. Above V1, there isn't enough runway left to stop β€” you MUST continue. A wrong V1 can mean a dangerous rejected takeoff or continuing when you should have stopped.

  19. Enter VR (rotation speed). Type 148 and press 2L. This is the speed where you pull back to lift off.

    VR (rotation speed) is also from performance tables, based on the same factors as V1. At this speed, the pilot flying pulls back on the sidestick to lift the nose. Rotating too early risks a tail strike; too late wastes runway. VR is always at or above V1.

  20. Enter V2 (takeoff safety speed). Type 152 and press 3L. V2 guarantees safe climb if an engine fails.

    V2 guarantees a minimum climb gradient even with one engine failed. For the A320, it must be at least 1.13 times the stall speed in takeoff configuration. If V2 is wrong, you might not clear obstacles on the departure path during an engine-out emergency.

  21. Set takeoff flaps to 1. Type 1 and press 3R.

    Flap setting is selected based on runway length, obstacles, weight, and temperature. Flaps 1 gives good performance with moderate runway requirements. Higher settings (2, 3) allow lower speeds but increase drag. Your performance calculation recommends the optimal setting β€” at Heathrow's long runways, Flaps 1 is usually fine.

  22. Takeoff performance is set. Press RAD NAV to set up your navigation radios.
  23. You've completed the essential preflight programming. In the real aircraft, you'd also set up INIT B (weights and fuel) and fine-tune the RAD NAV frequencies. Press INIT to return to the beginning.

    In a real cockpit, you'd also complete INIT B (zero fuel weight, block fuel), review the secondary flight plan, crosscheck with the other pilot, and run the FMGS preflight checklist before pushback.

What to take away

  • Work INIT β†’ F-PLN β†’ PERF; the pages depend on each other in that order.
  • Heathrow–CDG leaves south via Midhurst: L612 to BOGNA, direct HARDY, M605 and UM605 to BIBAX. UL9 via Dover and KONAN is the Brussels exit, not the Paris one.
  • On a sector this short, everything is programmed before pushback or not at all.
  • The F-PLN page fills in times and distances only once the FMGS has the data to predict them.

The rest of Flight Plans & Routing

Background reading

← Back to all scenarios