PROCEDURES DESIGN
☄️

PROCEDURES DESIGN

WHAT FOR?

The objectives of the procedures are to:
  • Share a common practice, in order to ensure a safe and efficient flight
  • Organize tasksharing and teamworking
  • Guide pilots actions (interface between the flight crew and the aircraft).

GENERAL DESIGN AND UTILIZATION PRINCIPLES

The procedures are consistent with the Airbus aircraft design philosophy.
The procedures are divided into routine, and not-routine procedures.
They are easy to identify and to understand.
The pilots are trained to use and strictly apply the procedures.
The tasksharing and a standard communication process are clearly defined, in order to ensure a safe and efficient use of the procedures.
notion image

NORMAL PROCEDURES - STANDARD OPERATING PROCEDURES (SOP)

GENERAL

During the daily normal operations of the aircraft, the flight crew performs actions frequently.
These actions are identified as routine tasks. The routine tasks are supported by the Standard Operating Procedures (SOPs).

SOP DESIGN PRINCIPLES

SOP are designed according to the following principles:
  • One SOP per flight phase
  • Actions are described in a chronological order
  • Actions are easy to memorize and to apply (cockpit scan, actions flow).
SOP design is effective provided that:
  • All systems operate normally
  • All automatic functions are used normally.
Some SOP actions are checked against checklists.

SOP UTILIZATION PRINCIPLES

The flight crew should perform SOP actions by memory. The flight crew can also decide to refer to the QRH, in order to perform both the Preliminary Cockpit Preparation and Securing the Aircraft procedures.

NORMAL PROCEDURES - SUPPLEMENTARY PROCEDURES

GENERAL
During the daily normal operations of the aircraft, the flight crew may have to perform actions which are not part of the SOP, i.e. not frequently done. These actions are identified as not-routine tasks dedicated to not-routine situation (e.g. airframe deicing/anti-icing procedures on ground, manual engine start). The not-routine tasks are supported by the Supplementary Procedures.
The flight crew must perform not-routine actions, using the READ & DO principle.

SUPPLEMENTARY PROCEDURES DESIGN PRINCIPLES

The Supplementary Procedures are designed according to the following principles:
  • Easy to identify and to understand
  • One Supplementary Procedure for a given situation
  • Actions are described in a chronological order.

SUPPLEMENTARY PROCEDURES UTILIZATION PRINCIPLES

Supplementary Procedures utilization is effective provided that the flight crew performs the Supplementary Procedures using the READ & DO principle (generally done by the PM).

ABNORMAL AND EMERGENCY PROCEDURES

ABNORMAL AND EMERGENCY PROCEDURES DESIGN PRINCIPLES

These procedures are not-routine, classified in abnormal or emergency, and prioritized in accordance with the criticality of the situation.
An abnormal or emergency procedure is initiated following:
  • A system failure, or
  • An operational context.
The design of an abnormal or emergency procedure is defined as:
  • A MEMORY ITEM, when the flight crew has no time to refer to the ECAM/QRH/FCOM to ensure a safe flight path, or
  • AN OEB IMMEDIATE ACTION, when the flight crew has no time to refer to specific OEB actions to ensure a safe flight path, or
  • A READ & DO procedure that is handled via the ECAM, QRH, FCOM, or OEB.
The type of procedure is easy to identify:
[MEM] MEMORY ITEMS
ECAM Procedures
[QRH] Procedures
MEMORY
READ & DO
READ & DO

ABNORMAL AND EMERGENCY PROCEDURES UTILIZATION PRINCIPLES

The utilization of abnormal and emergency procedures follows the here below principle:
WHEN?
HOW?
Memory Items
Immediately
Memory
OEB Immediate Actions
Immediately
Memory
Abnormal/Emergency Procedures ECAM/QRH/FCOM/OEB
When appropriate
READ & DO