FRANKFURT TO HEATHROW: A FLIGHT WORTH UNDERSTANDING
Frankfurt, a parked A320, and a route to Heathrow. The coffee has probably arrived before the flight plan. What matters now is bringing the aircraft, the dispatch information and the departure into agreement. This guide follows that work through the Fenix ceo family, with particular attention to the systems and workflows changed or extended in V3.
This is an intermediate simulator guide. It assumes that you can navigate the cockpit and read its main displays. The useful questions come next: why a source has not taken over, what a mode selection will do to the flight path, which loading figure the MCDU has accepted, and how a revised arrival changes the descent. The explanations connect the procedure with its operational result.
Use the separate checklists for the compact sequence and the chapters here for preparation, crosschecks and practice. The Frankfurt-Heathrow sector provides a continuous example; the workshops let you repeat a particular task without replaying the whole flight. Pause the simulator when an unexpected result deserves investigation, establish what changed, and then continue with a coherent aircraft state.
Original Fenix A320 main panel from the first-officer side. IAE/EPR engine display; the overhead and full pedestal are outside the frame. [1, Source illustration]