Main FCOM/QRH/FCTM Changes November 2021

Main FCOM/QRH/FCTM ChangesNovember 2021

Main FCOM/QRH/FCTM Changes

Main FCOM/QRH/FCTM changes included from November 2021

The main FCOM/QRH/FCTM changes described in this document will beavailable in the Operator FCOM/QRH/FCTM manuals, based on theOperator’s revision cycle.

[ PROJECT ] SOP - FCOM Tasksharing 4

[ PROJECT ] SOP - QRH Modification of Tasksharing from PF/PM to CM1/CM2 4

[ PROJECT ] SOP - Radio Set during Preliminary Cockpit Preparation 5

[ PROJECT ] SOP - IR MODE to NAV were Moved from the Cockpit Preparation to thePreliminary Cockpit Preparation 6

[ PROJECT ] SOP - Aircraft Acceptance and Preliminary Performance Determination 6

[ PROJECT ] SOP - Fuel On Board (FOB) Check in Cockpit Preparation 7

[ PROJECT ] SOP - Update of the Pushback/Start Clearance 8

[ PROJECT ] SOP - Thrust Levers IDLE at Engine Start 8

[ PROJECT ] SOP - Update of the Taxi Flow Pattern 9

[ PROJECT ] SOP - Departure Change 9

[ PROJECT ] SOP - Before Takeoff Flow Pattern 10

[ PROJECT ] SOP - Acceleration Flow Pattern 10

[ PROJECT ] SOP - Descent Preparation - Status Check 11

[ PROJECT ] SOP - Descent Preparation - Nav Chart Clipboard 11

[ PROJECT ] SOP - Descent Preparation - Landing Performance Data 12

Page 2 of 26


[ PROJECT ] SOP - Aircraft Configuration for Approach - Cabin Crew 12

[ PROJECT ] SOP - Manual and Automatic Landing 13

[ PROJECT ] SOP - Modification of Parking Phase 13

[ PROJECT ] SOP - New Checklist 14

[ PROJECT ] SOP - New Briefings 14

[ PROJECT ] EFB as Standard Operations 15

Gender Neutral Project 16

eQRH CG TRIM POS Display Enhancement 16

Green Operating Procedures 18

Enhancement of the Autothrust SPEED/MACH Modes Description 18

Configuration and Authoring Enhancement of the Description of the PrecisionApproach Modes 19

Configuration and Authoring Enhancement of the Wing Tip Brakes, Flaps and SlatsDescription 20

Go-Around in Conf Clean 21

Configuration and Authoring Enhancement of the Flags and Messages on PFD 22

New TAB - Missing "NO FLS FOR THIS APPR" Message when FLS Is Not Available 23

New TAB - Inhibition of the Final Approach FPA During Approach Using Final APPGuidance 23

New TAB - Triggering of RAAS Aural Advisory "On Runway XX" 24

New TAB - Display of the LOC Deviation Scale on Ground in RNP AR Departure whenNo LOC Is Available 24

A321neo Flare Law Description 25

Addition of “Fumes” in Smoke Procedures 26

Overspeed Technique 26

Page 3 of 26


1. [ PROJECT ] SOP - FCOM Tasksharing

1.1 EFFECTS ON THE MANUALS

● FCOM○ Introduction of the Procedures / Normal Procedures / Tasksharing.

● QRH○ Update of the Normal Procedures / Safety Exterior Inspection○ Update of the Normal Procedures / Preliminary Cockpit Preparation○ Update of the Normal Procedures / Securing the Aircraft.

1.2 SUMMARY OF THE MODIFICATIONS

A new chapter “Tasksharing” is now included in the FCOM. It contains the entiretasksharing for all flight phases that has been moved from the QRH to the FCOM. Now,the QRH Normal Procedure only contains the tasksharing for three flight phases:- Safety Exterior Inspection- Preliminary Cockpit Preparation- Securing the Aircraft.

These flight phases do not include any action flow. Based on airline policy, the flight crewmay:- Apply these procedures from memory, or- Apply these procedures with the read-and-do method.

2. [ PROJECT ] SOP - QRH Modification of Tasksharing from PF/PMto CM1/CM2

2.1 EFFECTS ON THE MANUAL

● QRH○ Update of the Normal Procedures / Safety Exterior Inspection○ Update of the Normal Procedures / Preliminary Cockpit Preparation○ Update of the Normal Procedures / Securing the Aircraft.

Page 4 of 26



The tasksharing was modified from PF/PM to CM1/CM2 for the three above-mentionedflight phases. This offers the following:

- It increases flexibility for a later decision on who will be PF/PM based on the latestoperational conditions.

- CM1 workload during preliminary cockpit preparation is reduced to help withmanagement and paperwork related tasks.

- CM1/CM2 simplifies the performance of daily tasks and reduces the possibility oferrors.

3. [ PROJECT ] SOP - Radio Set during Preliminary CockpitPreparation

3.1 EFFECT ON THE MANUALS

● FCOM○ Update of the Procedures / Normal Procedures / SOP / Preliminary Cockpit

Preparation.● QRH

○ Update of the Normal Procedures / Preliminary Cockpit Preparation.


The RMP is now set during the Preliminary Cockpit Preparation, in order to provide away for the flight crew to communicate with ATC and airline operation center at an earlierphase. This also enables the Airport Fire Officer to contact the flight crew (in airportsequipped with a dedicated frequency).

Page 5 of 26


4. [ PROJECT ] SOP - IR MODE to NAV were Moved from theCockpit Preparation to the Preliminary Cockpit Preparation



Preparation.● QRH



The initialization of the ADIRS was moved from the Cockpit Preparation to thePreliminary Cockpit Preparation, in order to complete the alignment as early as possible.The alignment time may be extended depending on geographical location.

5. [ PROJECT ] SOP - Aircraft Acceptance and PreliminaryPerformance Determination



Preparation.● QRH



The acceptance of the aircraft includes the Logbook, MEL/CDL items, the AircraftConfiguration Summary and the OEBs. Both pilots perform these tasks together to

Page 6 of 26


ensure correct and identical awareness of the technical status, equipment and OEBsapplicable to the aircraft.

The Preliminary Performance Determination requests the preparation of the NAVCHARTS, as their availability will help with the next tasks (e.g performance datacalculation, FMS Preparation, etc.)

Both pilots crosscheck the preliminary Takeoff Performance Data.

Both pilots refer to the same chart reference and the same mental picture about theexpected takeoff performance and contingency procedures (e.g. EO SID).

6. [ PROJECT ] SOP - Fuel On Board (FOB) Check in CockpitPreparation

6.1 EFFECT ON THE MANUAL

● FCOM○ Update of the Procedures / Normal Procedures / SOP / Cockpit Preparation.


The FOB check is now also performed during the Cockpit Preparation to ensure that:- The FOB corresponds to the requested amount in accordance with the CFP- Any fuel imbalance is within limits- The real FOB is known and referred to during the departure briefing.

Page 7 of 26


7. [ PROJECT ] SOP - Update of the Pushback/Start Clearance


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Before Pushback or

Start / At Pushback/Start Clearance.


The action BEACON sw…ON replaces the action EXTERIOR LIGHTS….SET, in order tobe more precise about what is expected .Two new conditions “If pushback is required” and “If pushback is not required” wereadded. These conditions take both cases into account, and enable more precision on therequired actions for both scenarios.

8. [ PROJECT ] SOP - Thrust Levers IDLE at Engine Start


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Engine Start.


The thrust levers should be checked at IDLE before the engine start. On some aircrafttypes, the engines start regardless of the thrust lever position. If the thrust levers are notset to IDLE, then thrust rapidly increases to the corresponding thrust lever position. Thiscauses a hazardous situation.

Page 8 of 26


9. [ PROJECT ] SOP - Update of the Taxi Flow Pattern


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Taxi.


Some aircraft have automatic weather radars. In order to adapt a single flow pattern to allaircraft types, the flow pattern does not start with the weather radar but with theautobrake instead. The flow pattern is now a single “U shape” for all the Airbus fleet(except A300/A310).

In addition, the ENG MODE selector action was moved from the Before Takeoff phase tothe Taxi phase, in order to reduce the workload during the Before Takeoff phase.

10.[ PROJECT ] SOP - Departure Change


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Departure Change.


A new optional Departure Change SOP was created in order to ensure that the flightcrew performs all the necessary steps in one of the following cases:

- Change of takeoff performance data, or- Revised ATC clearance (other than for a change of heading or initial altitude).

Page 9 of 26


11. [ PROJECT ] SOP - Before Takeoff Flow Pattern


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Before Takeoff.


The Before Takeoff flow pattern was modified in order to harmonize the takeoff SOPs ofall Airbus aircraft types (except A300/A310).

The flow pattern was designed from top to bottom, when possible, based on feedbackfrom Human Factors.

For the PM flow, there is no visual link (no line in the illustration) between TCAS (position1 in the flow pattern) and T.O RWY CONFIRM (position 2 in the flow pattern), becauseTCAS TA is not frequently selected during this phase.

12.[ PROJECT ] SOP - Acceleration Flow Pattern


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Climb○ Update of the Procedures / Normal Procedures / SOP / Go-around.


The After Takeoff/Climb checklist was removed as per enhanced checklist philosophy.

Therefore, a new Acceleration flow pattern was created. It is applicable to Takeoff andGo-Around phases.

It recalls the After Takeoff SOP actions that includes a check of the landing gearselection.

Page 10 of 26


13.[ PROJECT ] SOP - Descent Preparation - Status Check


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Descent Preparation.


The status check was moved from Descent to Descent Preparation.It is more appropriate to check the STS page during the Descent Preparation as it is

necessary for the following reasons:- To assess the landing performance- To conduct the Arrival Briefing.

14.[ PROJECT ] SOP - Descent Preparation - Nav Chart Clipboard




Update of the procedure to make it clear that the flight crew should prepare the charts forarrival navigation and for the expected approach procedure. Both pilots should check thatthey refer to the same chart reference.

Page 11 of 26


15.[ PROJECT ] SOP - Descent Preparation - Landing PerformanceData




Update of the procedure to make it clear that both flight crewmembers should comparetheir landing performance calculation to ensure that the results are identical. This willavoid any calculation error.

16.[ PROJECT ] SOP - Aircraft Configuration for Approach - CabinCrew


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Aircraft Configuration

Management / Intermediate/Final Approach.


This change provides some operational flexibility as it separates the SOP actionsassociated with the Landing checklist and the action CABIN CREW…..ADVISE.The Landing checklist is performed when the aircraft is configured for landing and thelanding clearance is obtained.With the previous Landing checklist (with the actions CABIN CREW….ADVISE), the flightcrew informed the cabin crew that landing was imminent before they performed theLanding checklist. This may result in a late performance of the Landing checklist even ifthe aircraft is configured and the cabin is ready.The new checklist enables the flight crew to perform the Landing checklist as soon as theaircraft is configured and the cabin ready, and advise the cabin crew at a later phase,when the landing is imminent.

Page 12 of 26


17.[ PROJECT ] SOP - Manual and Automatic Landing


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Landing / Manual

Landing○ Update of the Procedures / Normal Procedures / SOP / Landing / Autoland.


Following events of undetected autobrake disconnection during landing, a new callout isincluded.When the autobrake is selected, the PM monitors the autobrake during the entire landingroll. The PF calls out MANUAL BRAKING if they use the brake pedals. Then, the PMcalls out AUTOBRAKE OFF if:- The A/BRK does not engage as expected or the A/BRK disengages- The PF did not call out MANUAL BRAKING.

18.[ PROJECT ] SOP - Modification of Parking Phase


● FCOM○ Update of the Procedures / Normal Procedures / SOP / Parking.


Addition of the action to switch off the wing lights to avoid possible damage to the bridgein the SOPs and in the checklist.Addition of the action to switch off the beacon light after all engines spool down.The Parking checklist was moved upward to ensure safety related items are correctlyperformed before other items not related to safety.

Page 13 of 26


19.[ PROJECT ] SOP - New Checklist


● QRH○ Update of the Normal Checklist.


Update of the Airbus Normal Checklists. For more information on the checklistmodifications, please refer to the previous communication available on the AirbusWorldwebsite, in: Content library / Events / Conferences and forums / Flight Operations WebConferences / Webconference on forthcoming SOP, FCTM and normal Checklistchanges.

20.[ PROJECT ] SOP - New Briefings


● FCTM○ Introduction of the new section Airbus Operational Philosophy / Tasksharing

Rules and Communication / How to Conduct Briefings.


Update of the Airbus Operational Philosophy, in order to add the new section "How toConduct Briefings" that describes the revised guidance and technique to performbriefings.

For more information on the briefings, please refer to the previous communicationavailable on the AirbusWorld website, in: Content library / Events / Conferences andforums / Flight Operations Web Conferences / Webconference on forthcoming SOP,FCTM and normal Checklist changes.

Page 14 of 26


21.[ PROJECT ] EFB as Standard Operations


● FCOM○ Update/removal of links and references to request the use of the EFB PERF

application for performance computation.● QRH

○ Performance / All Engines Operative / Cost Index for Long Range CruiseSpeed section moved to Operational Data / Cost Index for Long Range CruiseSpeed

○ Complete Performance / In Flight Performance chapter removed○ Abnormal and Emergency Procedures / MISC / 00010864 Overweight

Landing was replaced by 00023120 Overweight Landing. Modification of thecontent by the removal of Performance Information in the Overweight LandingAbnormal Procedure

○ Update/removal of links and references to request the use of the EFB PERFapplication for performance computation.

● FCTM○ Removal of the following sections that describes the method to determine

aircraft performance at landing, in Procedures / Normal Procedures / SOP /Descent Preparation:

■ Method to Determine Aircraft Performance at Landing without or withFailure

■ Landing Performance - Normal Operations■ Abnormal Operations.

○ Update/removal of links and references to request the use of the EFB PERFapplication for performance computation.


Airbus aims to establish operations based on the Electronic Flight Bag (EFB) as theAirbus standard operations for the A320, A330 and A340 families. This intention wasannounced as follows:

- In the FOT 999.0059/18 Rev 00 dated July 31, 2018- In the FOT 999.0089/19 Rev 00 dated December 9, 2019- During webinars at the beginning of 2020- In the Airbus and Navblue Flight Operations Regional Conferences (October 2020).

As announced in FOT 999.0070/20 Rev 00 dated October 8, 2020, the removal ofperformance data from the QRH was delayed due to the COVID-19 crisis. Theperformance data was removed from the QRH in the November 2021 general revision.

Page 15 of 26


The main changes are the following:

- Removal of performance data- Update/removal of links and references to request the use of the EFB PERF

application for performance computation.

22.Gender Neutral Project


Following customer feedback, Airbus decided to initiate a project to update the Flight Opsmanuals to comply with the gender neutral guidelines. All FCOM and FCTM occurrencesof “he”, “she”, “he/she”, “his”, “her”, “his/her” were removed to appropriate nouns (e.g.“the flight crew”, “the PF” etc.). These modifications can be identified with the followinghighlight “Wording enhancement in order to comply with the Airbus Policy regarding thegender neutral documentation”.

23.eQRH CG TRIM POS Display Enhancement


● QRH○ Update of the back-cover, Takeoff CG/TRIM POS.

23.2 SUMMARY OF THE MODIFICATION

The Takeoff CG/TRIM POS section was modified in order to take advantage of the eQRHsoftware. As a result of this enhancement, if the Operator uses the eQRH V3.4 software,an application replaces the previous Takeoff CG/TRIM POS PDF scale. There was notechnical change.

Page 16 of 26


Before the eQRH V3.4 and the eQRH CG/TRIM POS display enhancement:

After the eQRH CG/TRIM POS display enhancement with eQRH V3.4:

Page 17 of 26


24.Green Operating Procedures


● FCOM○ Update of the Procedures / Normal Procedures / Supplementary Procedures /

Engines / One Engine Taxi - General.● FCTM

○ Update of the Procedures / Normal Procedures / Supplementary Procedures /Green Operating Procedures - General.


Green Operating Procedures (GOP) (e.g. one engine taxi) may reduce the redundancy ofsome aircraft systems. Therefore, Airbus reminds that the flight crew should decide toapply GOPs in accordance with the Operator’s guidelines and the flight conditions of theday, including the technical status of the aircraft.

The layout of the FCOM “One Engine Taxi - General” section was changed and itscontent enhanced to ensure understanding.

25.Enhancement of the Autothrust SPEED/MACH ModesDescription


● FCOM○ Update of the Aircraft Systems / Auto Flight - Flight Guidance / Autothrust /

A/THR Modes.


For aircraft equipped with Flight Guidance (FG) pre I8/C8, a clearer description of theautothrust behavior below 150 ft during approach was introduced in the FCOM.

For aircraft equipped with FG I8/C8 and subsequent, even if this system behavior is lesssignificant, it can still occur on some aircraft types.

Therefore, the FCOM was updated to describe this autothrust behavior on those aircrafttypes. In addition, in order to simplify the configuration management of theSPEED/MACH Modes description, some structural modifications were done.

Page 18 of 26


26.Configuration and Authoring Enhancement of the Description ofthe Precision Approach Modes


● FCOM○ Update of the Aircraft Systems / Auto Flight - Flight Guidance / AP/FD

Common Modes / Approach / Precision Approach.


Following customer feedback, Airbus decided to enhance the Precision Approach AP/FDmodes section and to change the structure of this section, as follows:

BEFORE AFTER

This change was also an opportunity to complete the FMS H3 authoring for which theEnhanced LOC capture function is inhibited.

Page 19 of 26


27.Configuration and Authoring Enhancement of the Wing TipBrakes, Flaps and Slats Description


● FCOM○ Update of the Aircraft Systems / Flight Controls / Flaps and Slats /

Description.


The Description section was enhanced and its structure was changed to ensureunderstanding, as follows:

BEFORE AFTER

Page 20 of 26


28.Go-Around in Conf Clean


● FCTM○ Update of the Procedures / Normal Procedures / SOP / Go-Around / AP/FD

GO-AROUND PHASE ACTIVATION○ Update of Preventing Identified Risks / Risks Related to Flight Phases.

28.2 SUMMARY OF THE MODIFICATION

Following in-service events, addition of information to explain the behavior of the aircraftwhen the SRS mode does not engage, during a go-around initiated with the flaps lever at0. The risk and the effect of the flaps lever at 0 when the go-around is initiated are nowdetailed.

Page 21 of 26


29.Configuration and Authoring Enhancement of the Flags andMessages on PFD


● FCOM○ Update of the Aircraft Systems / Indicating/Recording Systems / Indications

on PFD / Flags and Messages Displayed on PFD.


The layout and structure of the Flags and Messages Displayed on PFD section waschanged and its content was enhanced to ensure better understanding, with notechnical change, as follows:

BEFORE AFTER

Page 22 of 26


30.New TAB - Missing "NO FLS FOR THIS APPR" Message whenFLS Is Not Available


● FCOM○ Update of the Aircraft Systems / Auto Flight - Flight Management / Temporary

Abnormal Behaviors / FMS2 Thales Temporary Abnormal Behaviors○ Update of the Temporary Abnormal Behaviors / Temporary Abnormal

Behaviors Table.


The modification is applicable to S8/S8A Thales FMS standards with the FLS/FinalAppCoexistence function installed.

If the flight crew selects an approach expecting FLS guidance while FLS is not available,the “NO FLS FOR THIS APPR” message is not displayed on the MCDU scratchpad.

The related existing TAB was revised to include a reference to FCOM Procedures /Normal Procedures / SOP / Descent Preparation, as the flight crew should notice theautomatic reversion to FINAL APP mode during this flight phase. The StandardOperating Procedures ask the flight crew to check the FLS data and the other approachrelated information displayed on the PERF APPR page.

31.New TAB - Inhibition of the Final Approach FPA DuringApproach Using Final APP Guidance


● FCOM○ Aircraft Systems / Surveillance / Head-Up Display (HUD) - 2nd Generation /

Temporary Abnormal Behaviors.


The Final Approach FPA displayed on the Head Up Combiner Unit (HCU) indicates thereference slope of the approach from the current aircraft altitude. From HUD L7 standard,if a minimum FMGC standard is installed, for approaches that use FINAL APP guidance,the Final Approach FPA is as defined in the FMS database.

Page 23 of 26


32.New TAB - Triggering of RAAS Aural Advisory "On Runway XX"


● FCOM○ Aircraft Systems / Surveillance / GPWS / Temporary Abnormal Behaviors.


On ground, for aircraft with the Runway Awareness and Advisory System (RAAS)function not activated, and the Altimeter Setting Monitor (ALTSM) function activated thefollowing applies:

- The triggering of the RAAS aural advisory “On runway XX” (where “XX” is the runwaynumber) can occur

- The status message RAAS-OK-M is displayed on the ND for some seconds when theEGPWS powers up or when the ND range is changed.

Following in-service events, a TAB was published to provide the flight crew with theoperational recommendations to disregard the advisory and the status message.

33.New TAB - Display of the LOC Deviation Scale on Ground in RNPAR Departure when No LOC Is Available


● FCOM○ Aircraft Systems / Surveillance / Head-Up Display (HUD) - 2nd Generation /

Temporary Abnormal Behaviors.


From HUD L7 standard, during taxi and takeoff roll, when an RNP AR departure isplanned and no LOC is available, the LOC deviation scale without yaw bar is displayedon the Head Up Combiner Unit (HCU).

Following an in-service event, a TAB was published following an in-service event toprovide the flight crew with the operational recommendation to disregard the display onthe HCU of the LOC deviation scale without yaw bar.

Page 24 of 26


34. A321neo Flare Law Description


● FCOM○ Update of the Aircraft Systems / Flight Controls / Flight Control System /

Normal Law / Pitch Control / Flare Mode.● FCTM

o Update of the Procedures / Normal Procedures / SOP / Landing / Flare andTouchdown.


The design of the Flare law was changed on A321neo equipped with ELAC L102 or laterstandards.

Following the A321neo certification with ELAC L101, Airbus identified some areas thatneeded to be enhanced with regard to the Flare law (e.g. the resilience to turbulence andaircraft reactivity).

With the ELAC L102, the new Flare law is a pitch attitude demand control law, with adirect relationship between the sidestick input and the elevator position. Therefore, theaircraft is more reactive to the pilot input on the sidestick. The aircraft responds muchmore like a conventional aircraft, especially in the cases of windshear, gusts, orcrosswind.The Flare law is enabled at 100 ft radio altitude.

With this Flare law, the flight control system of the aircraft does not automaticallycompensate for the ground effect that induces a nose down effect.In addition to this, the thrust reduction also induces a pitch down moment.These effects may be perceivable by the pilot during the Flare with the new law.

However, it is important to remember that, although the design of the law is different, theFlare technique was not changed, and remains a closed loop handling between aircraftpitch and sidestick input.

Airbus recommends Operators to communicate this information to their flight crews toconsolidate their knowledge and increase awareness of the new Flare law introduced ontheir A321neo equipped with ELAC L102 and later standards.

Page 25 of 26


35.Addition of “Fumes” in Smoke Procedures


● FCOM○ Update of the Procedures / Abnormal and Emergency Procedures / Smoke /

[QRH] Smoke / Fumes/AVNCS Smoke○ Update of the Procedures / Abnormal and Emergency Procedures / Smoke /

[QRH] Removal of Smoke/Fumes.● QRH

○ Update of the Abnormal and Emergency Procedures / Smoke /SMOKE/FUMES/AVNCS SMOKE

○ Update of the Abnormal and Emergency Procedures / Smoke / REMOVALOF SMOKE/FUMES.

● FCTM○ Update of the Procedures / Abnormal and Emergency Procedures / Smoke.


The SMOKE/FUMES/AVNCS SMOKE procedure takes into account any case of smokeor fumes with or without odors.

The message was reinforced by the addition of “fumes” to the word “smoke” each time itis applicable.

36.Overspeed Technique


● FCTM○ Update of the Procedures / Abnormal and Emergency Procedures / MISC /

Overspeed.


Addition of illustrations in the FCTM, in order to illustrate the overspeed preventiontechnique and the overspeed recovery technique.

Wording is enhanced in the entire section.

Page 26 of 26

Main FCOM/QRH/FCTM Changes November 2021

Documents