Set the aircraft into a known pre-start state, start the EFBs, confirm the eQRH/EFB version, initialise ACARS when used, and verify the basic aircraft/FMGS identity for the planned sector.

Use the simulator’s current dispatch/logbook state, airfield data and preliminary loading to establish and cross-check initial takeoff-performance data before the walkaround/cockpit preparation is complete.

Configure the overhead, central and pedestal panels for the flight, prepare the navigation/FMS data, set barometric/FCU references as appropriate, and complete the normal cockpit preparation before moving to the before-start flow.

Fenix's import workflow expects an OFP to have been generated first. If you plan to use the Fenix SimBrief integration, confirm the current flight has a generated OFP before moving on.

The Fenix workflow uses the SimBrief username entered in the EFB settings. Check it if this is a new install, profile change or import is not behaving as expected.

The Fenix checklist is built into the EFB under Pilot Brief > Documents. RFoV now carries contextual knowledge itself, while the built-in list remains useful for the full normal sequence.

Fenix models fan icing. In this simulator context, inspect for fan ice/frost and use the Fenix EFB Ground Services fan-heating function when the documented icing conditions make it relevant.

Fenix provides thrust-lever and flap calibration through MCDU MENU > CONFIG > CONTROLS CONFIG. This is normally a setup/change check rather than something to repeat every sector.

In the Fenix EFB MY FLIGHT tab, use IMPORT FLIGHT FROM SIMBRIEF after the current OFP has been prepared.

After importing/planning the flight, use the MASS AND BALANCE workflow and LOAD AIRCRAFT. Choose the desired loading method/speed or GSX integration as appropriate for the simulator session.

Use the Fenix EFB SEND TO MCDU function once loading is complete so the final weight and centre-of-gravity data are available on the MCDU Init B page.

Check the selected measurement units in Fenix settings against the units used by the current SimBrief plan.

The Fenix Charts app can sync airport fields from the imported SimBrief route and can automatically star departure/arrival/ground charts for quicker access.

The Fenix Pilot Brief app brings the operational flight plan, weather briefing, NOTAMs, checklist, QRH and other documents together in one place.

Where de-icing/anti-icing is relevant, make sure critical surfaces and the areas around the air-data probes are free of simulated ice/snow before takeoff; if de-icing was used, retain the associated report/context for the departure.

Check the final load/fuel picture and make sure final takeoff performance/FMS data still reflects the current departure conditions before completing the before-start flow.

Complete the normal before-start cabin/aircraft readiness checks, including doors/windows and the relevant ground/parking configuration, before obtaining pushback or start clearance.

Select the start configuration, start the engines in the QRH sequence, and confirm each engine reaches a stable idle before continuing.

Return the engine-mode/start systems to their normal post-start state, set anti-ice as required, check ECAM status, and configure spoilers, flaps and trim for taxi/takeoff.

The Fenix EFB Ground Services page provides engine fan heating. Use it when the simulated fan condition/icing context warrants it, before committing to engine start.

Fenix documents engine anti-ice as required when icing conditions are encountered or anticipated. Apply that developer guidance to the current simulator conditions rather than relying on a generic RFoV rule.

Fenix provides its QRH in the EFB Pilot Brief documents. RFoV does not reproduce abnormal procedures; this is a location reminder only.

Use the Fenix GROUND SERVICES tab for the services needed by the current simulator turnaround; the same area provides pushback controls.

After taxi clearance, configure the exterior lights, release the parking brake, check normal braking and complete the flight-control check while taxiing as conditions permit.

If runway, weather or other takeoff conditions changed after the original calculation, recompute the final takeoff performance and cross-check/revise the FMS takeoff data before departure.

Confirm the takeoff briefing and ATC clearance, set the required departure/FMS/FCU configuration, and verify the takeoff configuration/memo before completing the first part of the before-takeoff checklist.

Fenix notes that extended idle/low-thrust operation can increase fan-ice accumulation risk. Keep this in mind during a long taxi when the simulated conditions are icing-prone.

If thrust response or vibration suggests fan ice, use the engine-specific ice-shedding procedure described by Fenix rather than improvising a generic response.

RFoV has identified night/dawn/dusk context at the departure. Use the normal Fenix taxi checklist with extra attention to external-lighting and taxi-awareness items.

The Fenix Ground Services workflow includes integrated pushback controls for connecting and steering the tug.

At the runway/line-up stage, finish the remaining before-takeoff checks: aircraft/cabin secure, runway/traffic awareness, relevant TCAS and brake/fan state, and line-up clearance.

Set takeoff thrust as planned and monitor the flight-mode/engine/primary-flight indications through the initial roll, using the normal callout sequence as reference.

Once positive climb is established, raise the landing gear and continue the normal thrust-reduction/flap-retraction sequence toward the after-takeoff configuration.

For the CFM variant, the supplementary procedure calls for a three-minute engine warm-up before takeoff. Treat this as a simulator-specific readiness consideration, especially after a rapid start-and-taxi.

Fenix's simulator icing model can affect the engines. Before takeoff, make sure your anti-ice configuration matches the developer's icing guidance for the conditions you are actually simulating.

Fenix documents wing anti-ice as condition-dependent rather than an always-on action. Apply the developer guidance if icing is detected or anticipated.

Current RFoV context: {context_summary}. Use this to focus the normal Fenix checklist on what is unusual about this departure.

In Departure Performance, set the departure airport, runway and runway condition; sync the loadsheet values and live weather as required, calculate, then transfer the result to the MCDU.

Rain or snow is present in RFoV situational context. Confirm the Fenix departure-performance calculation uses the runway condition and current weather appropriate to the simulated departure.

Complete the after-takeoff checklist, then at the transition altitude set/cross-check standard barometric reference and continue the normal climb configuration, including anti-ice and exterior lights as required.

The normal after-takeoff/climb checklist includes confirmation that the landing gear is up. RFoV can show the generic SimConnect gear-handle report alongside the manual checklist; the checklist itself remains authoritative.

Periodically review ECAM/system pages, flight progress, fuel state, navigation accuracy and radar configuration during cruise.

Obtain current arrival/weather information, confirm landing conditions, compute/cross-check landing performance, prepare the FMS and charts, and complete the approach briefing before descent.

Monitor the descent, set/cross-check the barometric reference when appropriate, and complete the normal 10,000-ft lighting/sign/navigation configuration.

Activate/confirm the approach phase, monitor managed speed and navigation, then extend flaps/gear progressively and arm the normal landing systems as the approach develops.

Before final approach, confirm the aircraft is in the intended landing configuration, the landing memo has no outstanding blue items, and the landing checklist is complete.

On a normal manual landing, transition from flare to idle thrust, use reverse/braking as required, maintain directional control and stow reverse as taxi speed is reached.

After vacating the runway, disarm spoilers, retract flaps, reconfigure exterior lights/radar/TCAS and anti-ice as required, then check brake temperature/fans and start the APU when needed.

The normal after-landing checklist calls for flaps at zero. RFoV can display the generic flap-handle report as corroborating simulator evidence.

At the final stand, set the parking brake, shut down the engines, disarm slides, reconfigure lights/signs/ATC/fuel systems and complete the parking checklist.

The parking checklist includes engines off. RFoV can display the generic engine-combustion report as corroborating simulator evidence.

When fully securing the aircraft, close the EFB applications, switch off the remaining aircraft systems/power in the documented sequence and complete the securing checklist.