Pro CompanionRevision 3.1
FNX-FANTHE FLIGHT COMPANIONS
PRO / REVISION 3.1
THE ADVANCED COMPANION · REVISION 3.1

Pro
Companion.

Go deeper into the aircraft behind every decision.

EDDFFRANKFURT ───────→ LONDON HEATHROWEGLL

Advanced systems, detailed MCDU programming and operational reasoning for the Fenix V3 A319, A320 and A321. With Airbus history and the Frankfurt–Heathrow practice flight.

Start reading →

READING THE PRO COMPANION

The Pro Companion: connect the aircraft, the programme and the evidence →How the references, examples and illustrations fit together →

AIRBUS: THE AIRCRAFT AND THEIR HISTORY

Three histories, three different clocks →Before Airbus: making European cooperation practical →The founders: a product and a production system →The A300B: two engines and a wide body →Winning an airline market →The A310 and the changing flight deck →A320: launch, first flight and first delivery →What digital fly-by-wire changed →The A321: adding capacity changed the aircraft →The A319: choosing another capacity point →The A318 and the boundary of the simulated family →Commonality: a fleet idea with operational limits →The A330 and A340: common thinking, different propulsion choices →From a consortium to an integrated company →The A380: ambition at the largest scale →Ending production did not end A380 operation →Sharklets: an aerodynamic change, not an engine generation →The neo programme and the meaning of ceo →The A350: a delivery in2014 and service in2015 →The A220: a different origin inside the Airbus portfolio →The A321LR and XLR: range as an aircraft programme →The industrial aircraft behind the passenger aircraft →History without importing an old operating limit →

THE FENIX SIMULATION: PRODUCT HISTORY

An Airbus that gave people something to talk about →A cockpit becomes a place to spend an evening →V3: the connections behind the indications →

AIRCRAFT AND COCKPIT CONFIGURATION

Confirm the aircraft configuration →Family differences that affect the flight →Arrange the cockpit for the work ahead →

PREPARATION AND SYSTEM VERIFICATION

Establish a known aircraft state →External power: availability and actual supply →Electrical-source priority and transfer →ADIRS: alignment, position and usable references →APU preparation, start and outputs →Pneumatic supply and engine-start air →Air conditioning and cabin-temperature control →Pressurisation: read the cabin trend →Hydraulics: sources, pressure and the PTU →Fuel: reconcile quantity, distribution and feed →Flight controls: verify the command and response →Ice protection and the performance configuration →Fire and oxygen: make the tests diagnostic →Doors, slides and Cabin Ready in V3 →Lights, signs and cabin servicing →

SYSTEMS, ENGINES AND VARIANT ENGINEERING

Define the exact airframe, engine and rating →Wingtip, structural and equipment standards →Electrical generation, contactors and source priority →Essential power, batteries and emergency generation →APU regulation, loading and shutdown logic →Bleed selection, regulation and crossbleed →Packs, mixer and zone-temperature control →Pressure controllers, outflow and destination reference →Avionics cooling, extraction and smoke paths →Air-data and inertial references as independent functions →Position estimation, radio aids and independent height →Hydraulic generation and the limits of PTU assistance →Hydraulic consumers and compound failure effects →A319/A320 fuel feed, transfer and cooling →A321 jet-pump transfer and Additional Center Tanks →Fuel balance, crossfeed and leak interpretation →Engine and APU fire detection, isolation and discharge →Smoke detection and the compartments behind the warning →Crew oxygen, passenger oxygen and pressure indications →Doors, escape slides and cabin-information chains →Gear sequencing, proximity sensing and gravity extension →Normal, alternate and accumulator braking →Nosewheel steering, pedal disconnect and towing →Flight-control computers, actuators and redundancy →Normal-law pitch demand, trim and protections →Roll, yaw and sidestick priority →Alternate law, direct law and mechanical backup →High-lift drive, locks and spoiler functions →CFM56-5B: rotating assemblies and fuel control →V2500: EPR reference and installation-specific behaviour →Starting, ignition and the engine accessories →Thrust rating, autothrust and protection requests →Ice protection, probe heating and rain removal →Radio management, audio paths and intercommunication →Display generation, warning logic and reconfiguration →Lighting, signs and installed cockpit equipment →Potable water, waste and service-state persistence →Traffic, terrain and weather information are different sensors →Recording, fault memory and cross-system diagnosis →

FMGS: THE WORKED-FLIGHT FOUNDATION

MCDU preparation: build a consistent set of data →DIFRIPPS: a structured preparation and review →EDDF-EGLL: the exercise dataset →DATA: aircraft identity and V3 database management →Manual database import and post-activation checks →INIT A: identity, planning assumptions and position →F-PLN: departure, airways and route geometry →Discontinuities, vectors and constraints →RAD NAV: deliberate tuning and independent checks →INIT B: loading, field order and predictions →PROG: navigation and prediction crosschecks →PERF: calculate, transfer and verify →SEC F-PLN: prepare the alternative before it is needed →Route import: retain the operational review →

ADVANCED MCDU PROGRAMMING AND FMGS MANAGEMENT

The programming contract: data, trajectory and guidance →Entry grammar, field semantics and display conventions →DATA and A/C STATUS: identity before computation →V3 navigation databases: download, validate, activate →Manual database import: file selection and failure isolation →INIT A: route identity, economic inputs and initialization effects →Position initialization and independent position monitoring →INIT B: mass, CG, fuel and reserve semantics →After start: FUEL PRED, gross-weight correction and sensor labels →Company routes and INIT REQUEST: reception is not review →Reading F-PLN A/B and the pseudo-waypoint model →TMPY: an explicit transaction with INSERT and ERASE →Departure programming, intersections and late runway changes →Airway construction and an enroute route replacement →Insert, delete and collapse waypoints without losing intent →DUPLICATE NAMES: select the geographic object, not the nearest text →Discontinuities and MANUAL legs: two different problems →Fly-by, overfly and sequencing at the active leg →STARs, transitions and approach VIAs: controlled arrival stringing →Approach programming and protected final-segment data →LAT REV and NEW DEST: diversion from a defined revise point →DIR TO and ABEAM PTS: immediate trajectory revision →Radial interception: geometry and implementation boundaries →Pilot-defined positions: latitude/longitude, PBD and PB/PB →Along-track points and pilot-route storage →Speed limits and waypoint speed constraints →Altitude constraints, windows and their deletion consequences →UTC constraints: model, feasibility and V3 verification boundary →Holding-pattern creation: database, computed and pilot-defined →Hold exit, resume and a sequencing discrepancy →Lateral offsets and the return to the original route →Wind profiles: manual entry, uplink and update commitment →PROG, RNP and the displayed position estimate →RAD NAV: manual priority, automatic tuning and ILS validation →PERF TAKE OFF: a validated calculation expressed in cockpit fields →PERF CLB and CRZ: predictions, preselection and cost index →STEP ALTS: plan the change, then command it →PERF DES and the descent profile: study mode and model together →PERF APPR: pressure, temperature, wind, minima and configuration →Flight-phase transitions: approach activation, go-around and return →ALTERNATES and ENABLE ALTN: stored airport versus usable diversion →SEC F-PLN: copy, independent preparation and controlled activation →Fuel predictions, reserves and holding time →AOC/ACARS and the FM boundary →CPDLC: provider setup, request, response and flight-plan action →Messages and fault isolation: repair the state that produced the message →V3 programming recovery: targeted repair or a deliberate clean rebuild →IDLE and PERF factors: a controlled prediction study →

STARTING THE ENGINES

Before start: close the preparation loop →Engine start: follow the sequence to stable idle →CFM56-5B and IAE: interpret the installed engine →Thrust detents, rating and autothrust →After start: establish the taxi configuration →

TAXI, GUIDANCE AND TAKEOFF

FMA: the guidance and thrust crosscheck →FCU selections: clearance, target and mode →Taxi: control the geometry and workload →Before takeoff: reconcile data, aircraft and clearance →Takeoff: verify the response while flying the aircraft →Thrust reduction, acceleration and cleanup →

CLIMB AND CRUISE

Managed climb, open climb and level capture →Cruise: keep the predictions connected to the flight →

PREPARING THE DESCENT

Prepare Heathrow before the descent workload arrives →PERF APPR: references, minima and approach speed →Descent modes and energy management →V3 descent logic and level deceleration →Vectors, DIRECT TO and holding →

APPROACH AND LANDING

ILS: identification, capture and missed-approach setup →Configuration and deceleration on the approach →Stabilisation and the decision to continue →Flare, thrust reduction and touchdown →Rollout: confirm deceleration and retain control →Go-around: establish the new path before the new plan →Autoland, non-ILS and visual approaches →

BACK AT THE GATE

After landing and taxi to the stand →Shutdown, power transfer and the next sector →

REVIEW AND REFERENCE DISCIPLINE

Hardware calibration and reproducible troubleshooting →ECAM: indications, actions and the remaining status →ACARS, loadsheets and loading reconciliation →Use the EFB as part of the workflow →Debrief the result and choose the next exercise →V3 build notes - 26 October 2026 →

ADVANCED OPERATIONS, PERFORMANCE AND FENIX WORKFLOWS

Define the aircraft before accepting the answer →Weight, balance and the last-minute load revision →Runway distance is a starting assumption →Thrust and configuration choices spend different margins →A rejected takeoff is a decision with a stopping plan →Engine-out departure: protect the flight path first →Choose modes by the task they control →Manage descent as an energy and geometry problem →ILS capture and autoland capability are separate assessments →RNAV and nonprecision approaches need their own vertical plan →Circling and visual flight need a protected geometry →Landing performance connects the approach to the full stop →Read weather information without overreading the radar →Icing and turbulence change more than a switch position →ECAM completion is the beginning of the next assessment →Unreliable airspeed: diagnose information, not a reassuring display →Hydraulic and electrical failures change the landing plan →Fuel and engine indications need a trend and a mechanism →Cabin pressure and oxygen define the emergency-descent problem →Design a failure exercise that can answer a question →Treat installation and runtime as separate systems →Validate the inputs before interpreting the flight model →Display and audio quality affect what the crew can observe →A panel state is a starting point that must finish applying →Use the EFB as an integrated operational workspace →Cabin readiness is an event sequence with separate evidence →Airline Packs personalise the cabin without replacing its logic →Company messaging and ATC messaging have different authority →Ground-service integration needs one coherent loading state →A livery can select an aircraft standard →Use a release note as a dated diagnostic record →Read community evidence with the aircraft still in view →

VARIANT AND SOURCE COVERAGE REGISTER

How the technical coverage is organised →Read the implementation status with the explanation →V3-only operating instructions and community evidence →A professional rehearsal plan →

VERIFICATION CARDS