NON NORMAL PROCEDURES POLICY Flashcards
In case of discrepancy between the operational manuals, priority should be given to :
- AFM
- QRH
- OMB-PRO
- OMB-QRG
- FCOM
ATC STANDARD COMMUNICATION
in Urgency or Distress
NON-NORMAL OPERATIONS
METHODOLOGY
SEQUENCE OF ACTIONS
FAILURE ANNUNCIATION
Next step is SYSTEM CHECK and FAILURE CONFIRMATION.
SYSTEM CHECK AND FAILURE CONFIRMATION
It is triggered by PF, calling **CHECK SYSTEM **and executed by PM :
- SD PAGE
Displayed, analyzed and understood. - CIRCUIT BREAKERS
- RESET
FOR-DEC
Once checklists are completed, PM reads status (INOP functions) and checks SD pages on PF request. Then PF performs the FOR part of the FOR-DEC loop to summarize the situation.
In case of time-critical Emergency, the FOR part can be performed by the CM1.
FOR
NITS
NITS : Nature, Intention, Time, Special
The recipient must repeat the NITS to acknowledge he received the message correctly.
RESET POLICY
Note : In case of loss of DC SVCE BUS or DC EMER BUS, refer to FCOM
CIRCUIT BREAKER (C/B) RESET POLICY
TAKEOFF ALERT INHIBITION
CRITICAL SYSTEMS
(needing confirmation)
- Power Levers
- Condition Levers
- Fire Handles
- All guarded P/B and switches
DU AND MCDU POLICY
FOLLOWING A NON DU FAILURE
DU AND MCDU POLICY
FOLLOWING A SINGLE DU FAILURE
ABNORMAL NAVIGATION SUMMARY TABLE
ENGINE FLAMEOUT AT TAKE-OFF (NORMAL CONDITIONS) SPEED AUTO CHANGE CONDITIONS
The VFTO speed will be displayed after pushing ALT to FGCP by FMS.
Pushing ALT to FGCP will display VMLB0.
Failure below V1
The Captain should consider discontinuing the takeoff, if any of the following conditions occur :
- Master warning / caution
- Unusual noise or vibration
- ATPCS not armed
- Windshear
- Cabin smoke / fire
- Abnormal acceleration
- Tire failure
- Unsafe / unable to fly
- Engine failure / fire
- Takeoff configuration warning
- Bird strike
- Window failure.
RESUME FAILURE TREATMENT
