
- •1. ОБЩИЕ ПОЛОЖЕНИЯ
- •1.1. Основные принципы организации работы экипажа - GOLDEN RULES
- •1.2. Распределение ответственности и обязанностей.
- •1.3. Принцип «стерильной кабины» (STERILE COCKPIT RULE):
- •1.4. Работа с Контрольными листами (NORMAL CHECKLIST)
- •1.5. Принятие решения
- •1.6. Передача управления
- •1.7. Использование автоматических режимов управления
- •1.8. Условия стабилизированного захода на посадку
- •1.9. Установка и использование подвижных индексов
- •1.10. Установка высотомеров и перекрестный контроль
- •1.11. Процедуры занятия и выдерживания заданных высот полета
- •1.12. Навигация по маршруту полета.
- •1.13. Требования к оборудованию ВС для выполнения посадки по САТ II/III ICAO
- •1.14. Предполетная, предпосадочная информация, брифинг на эшелоне
- •1.15. Взаимодействие при выполнении полетов увеличенным составом экипажа.
- •1.16. Взаимодействие летного и кабинного экипажа
- •1.17. Порядок оповещения пассажиров
- •1.18. Правила ведения радиообмена.
- •1.21. Предполетная подготовка
- •2. ПОДГОТОВКА К ПОЛЕТУ
- •2.1. TECHNICAL CONDITION OF THE AIRCRAFT
- •2.2. WEATHER BRIEFING
- •2.3. NOTAMS
- •2.4. FLIGHT PLAN AND OPERATIONAL REQUIREMENTS
- •2.5. NAT MNPS AIRSPACE OPERATIONS
- •2.6. OPTIMUM FLIGHT LEVEL
- •2.7. FUEL REQUIREMENTS
- •2.8. CABIN CREW BRIEFING
- •2.13. COCKPIT PREPARATION
- •PEDESTAL
- •* FMGS DATA INSERTION
- •* WHEN BOTH PILOTS SEATED
- •* GLARESHIELD
- •LATERAL CONSOLES
- •CM 1/2 INSTRUMENT PANELS
- •3. ВЫПОЛНЕНИЕ ПОЛЕТА
- •3.1. BEFORE PUSHBACK or START
- •3.2. AUTOMATIC ENGINE START
- •3.3. AFTER START
- •3.4 TAXI
- •3.6. 180º TURN ON RUNWAY
- •3.7. BEFORE TAKEOFF
- •3.8. TAKEOFF
- •3.10. CLIMB
- •3.11. CRUISE
- •Methods for checking accuracy:
- •3.12. DESCENT PREPARATION
- •3.13. DESCENT INITIATION
- •3.14. DESCENT MONITORING
- •3.15. DESCENT ADJUSTMENT
- •3.16. ILS APPROACH
- •3.17. INITIAL APPROACH
- •Methods for checking accuracy:
- •3.18. NTERMEDIATE/FINAL APPROACH (ILS Approach Entered in the F- PLN)
- •CAT II / CAT III APPROACH
- •3.19. Non Precision Approach - NPA
- •3.20 ADDITIONAL NPA PREPARATION
- •3.21 Initial Approach
- •3.22 INTERMEDIATE / FINAL NON PRECISION APPROACH
- •(S) FOR SELECTED VERTICAL OR SELECTED LATERAL AND VERTICAL GUIDANCE
- •3.23. CIRCLING APPROACH
- •3.24. VISUAL APPROACH
- •3.25. VISUAL CIRCUIT INITIAL/INTERMEDIATE APPROACH
- •3.26. LANDING
- •3.27. GO AROUND
- •4. РУЛЕНИЕ НА СТОЯНКУ И ПОСЛЕПОЛЕТНЫЕ РАБОТЫ ЭКИПАЖА
- •4.1. AFTER LANDING
- •4.2. PARKING
- •4.3. SECURING THE AIRCRAFT
- •5. СТАНДАРТНЫЕ ФРАЗЫ
- •5.1. CHECKLIST CALLOUTS
- •5.5. FLIGHT PARAMETERS IN APPROACH
- •5.7. FLAPS OR GEAR CONFIGURATION
- •5.8 PF/PNF DUTIES TRANSFER
- •5.9. ABNORMAL AND EMERGENCY CALLOUTS
- •SUMMARY FOR EACH PHASE
- •6. ПРИЛОЖЕНИЯ
- •6.1. Standart Operating Procedures
- •6.2. Normal Сhecklist
- •6.3. Briefing items

|
РПП Часть В |
Стандартные эксплуатационные процедуры |
Издание: 05 |
|
|
Airbus-319/320/321 |
Standard operating procedures(SOP) |
Изменение: 00 |
For RNAV approach WITH GPS
(“RNAV(GPS)”; “RNAV(GNSS)”; “RNAV(RNP)” is published in the approach chart).
Before flight, the GPS PRIMARY availability MUST BE VERIFIED, using the PREDICTIVE GPS MCDU page, UNLESS an instrument approach procedure, NOT REQUIRING GPS/GNSS/RNP, IS AVAILABLE at destination or destination alternate (and at required takeoff alternate, and en route alternate).
Before starting the approach, check that GPS PRIMARY is available on both MCDU: two navigation systems must be operative: 2 FMS and 2 GPS.
DISCONTINUE THE APPROACH:
If the GPS PRIMARY LOST indication appears on the ND during the approach, unless GPS PRIMARY is lost on only one FMGC, the approach can be continued, using the AP/FD associated to the other FMGC.
If the FM/GPS POS DISAGREE ECAM caution is triggered;
If the FMS1/FMS2 POS DIFF message is triggered, unless radio NAVAID raw data is available and indicates correct navigation to continue the approach by using the AP/FD associated to the non-affected FMGC side.
3.20ADDITIONAL NPA PREPARATION
Before top of descent, during DESCENT PREPARATION:
VAPP as SPD constraint at the FAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTER PF
Enter VAPP as SPD constraint at the FAF, with a vertical revision of the F-PLN page.
3.21Initial Approach
FLIGHT PLAN SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK BOTH PNF should always keep flight plan sequenced during approach on PF request.
ENG MODE selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AS RQRD PNF
Select IGN if the runway is covered with standing water or heavy rain or if severe turbulence is expected in the approach or go around.
APPROACH PHASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK/ACTIVATE PF
If the aircraft overflies DECEL pseudo waypoint in NAV mode, APPR phase activates automatically. If in HDG/TRK mode, ~ 10 NM from FAF activate APPROACH phase on MCDU.
POSITIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MONITOR PF
In NAV mode, use VDEV information on PFD and PROG page.
In HDG or TRK modes, use the energy circle displayed on ND representing the required distance to land.
MANAGED SPEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK PF
If ATC requires a particular speed, use selected speed. When the ATC speed constraint no longer applies, return to managed speed.
SPEEDBRAKES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AS RQRD PF
The landing gear may always be extended out of sequence to facilitate deceleration.
RADAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AS RQRD PF
Дата 01.02.2013 |
ВЫПОЛНЕНИЕ ПОЛЕТА |
cтр. 81 |

|
РПП Часть В |
Стандартные эксплуатационные процедуры |
Издание: 05 |
|
|
Airbus-319/320/321 |
Standard operating procedures(SOP) |
Изменение: 00 |
GPS PRIMARY on PROG page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK AVAILABLE PNF If GPS PRIMARY is not available:
NAV ACCURACY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MONITOR PNF
Check the PROG page to ensure that the required navigation accuracy is appropriate to the phase of flight. Perform a navigation accuracy check.
ND MODE and RAW DATA . . . . . . . . . . . . . . SELECT AS APPROPRIATE BOTH
If the approach is stored in the navigation database, determine the strategy to be used for the final approach, according to the table below:
NAVIGATION ACCURACY |
Approach |
|
|
ND |
AP/FD |
TERR |
|
|
|
|
|||||
guidance |
PF |
|
PNF |
mode |
P/B |
||
|
|
||||||
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
GPS PRIMARY |
|
|
|
|
NAV-FPA |
|
|
NAV ACCUR HIGH |
|
|
ARC |
|
|||
Managed*** |
|
or APP- |
|
||||
|
or ROSE NAV* |
ON |
|||||
NAV ACCUR LOW and |
or selected |
NAV/FINAL |
|||||
with navaid raw data |
|
||||||
NAV ACCUR check ≤ 1NM |
|
*** |
|
||||
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
GPS PRIMARY LOST and |
|
|
|
ARC or |
|
|
|
NAV ACCUR LOW and |
|
|
|
|
|
||
|
|
|
ROSE NAV |
|
|
||
NAV ACCUR check > 1 NM |
|
|
|
|
|
||
|
ROSE |
|
or ROSE |
|
|
||
|
Selected |
|
TRK-PFA |
OFF |
|||
|
|
||||||
GPS PRIMARY LOST |
VOR** |
|
VOR** |
||||
|
|
|
|
||||
|
|
|
with navaid |
|
|
||
and aircraft flying within |
|
|
|
|
|
||
|
|
|
raw data |
|
|
||
unreliable radio navaid area |
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
|
(*)For VOR approaches, one pilot may select ROSE VOR.
(**)For LOC approaches, select ROSE ILS.
(***) Managed vertical guidance can be used, provided the approach coding in the navigation database was validated.
Note:
1.During approach in overlay to a conventional radio navaid procedure, monitor raw data. If raw data indicates unsatisfactory managed guidance, revert to selected guidance.
2.The flight crew can continue to fly a managed approach after receiving a NAV ACCUR DOWNGRADED message, if raw data indicates that the guidance is satisfactory.
APPROACH CHECKLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COMPLETE BOTH CABIN REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OBTAIN PNF
cтр. 82 |
ВЫПОЛНЕНИЕ ПОЛЕТА |
Дата 01.02.2013 |

|
РПП Часть В |
Стандартные эксплуатационные процедуры |
Издание: 05 |
|
|
Airbus-319/320/321 |
Standard operating procedures(SOP) |
Изменение: 00 |
3.22INTERMEDIATE / FINAL NON PRECISION APPROACH
FOR RNAV APPROACH
GPS 1+2 on GPS MONITOR page . . . . . . . . . . . . . . . . . . . . CHECK BOTH IN NAV PNF GPS PRIMARY on PROG page . . . . . . . . . . . . . . . . . . . . . . . . . CHECK AVAILABLE PNF RNP for approach . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . CHECK/ENTER PNF
For RNAV IAP “0.5”, for RNP IAP “0.3 ” must be in REQUIRED field on MCDU PROG PAGE
HIGH accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK PNFIf HIGH accuracy is lost on both FMGCs:
“UNABLE RNAV” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REPORT ATC PNF
WHEN CLEARED FOR APPROACH:
TRK/FPA display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SELECT PF
AT GREEN DOT SPEED
Extend flaps, landing gear in sequence, decelerate to Vapp.
(M)FOR MANAGED VERTICAL GUIDANCE , if not specified on the chart, min OAT -15°C)
For approach in managed vertical guidance (M):
APPR pushbutton on FCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PRESS PF
Once cleared for the approach, press the APPR pushbutton when flying to the FAF Check:APPR NAV is engaged, FINAL is armed,
VDEV scale is on the PFD,
Correct TO waypoint on the ND,
Blue descent arrow at FAF and the correct F-PLN,
Correct Vertical Flight Path deviation indication.
Upon reaching the FAF: |
|
|
|
|
|
|
|
|
|
|
|
|
|
||
FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . . . . . . . . . . . |
. |
. CHECK |
PF |
|
||
FINAL APP green is engaged, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Correct TO waypoint on the ND, |
|
|
FINAL APP |
||||
Correct blue track on the ND, armed for Missed Approach, |
|
|
|||||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
GO AROUND ALTITUDE . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . . . . . . . . . . . . . . . SET |
PF |
|
||||
Set, when below the go-around altitude. If any altitude constraints set lowest one. |
|||||||
|
|
|
|
||||
POSITION/FLIGHT PATH . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . . . . . . . . MONITOR |
BOTH |
|
For approach in overlay to a conventional radio navaid procedure:
Use radio navaid raw data and altitude to monitor the lateral and vertical navigation. If the navigation is not satisfactory, revert to selected guidance.
In particular, monitor the vertical guidance, using altitude indication versus radio navaid position, and be prepared to revert to NAV-FPA, if the vertical guidance is not satisfactory.
For RNAV approach:
Monitor VDEV and FPV (on the PFD) and XTK error (on the ND).
Use altitude indication versus distance to the runway to monitor the vertical navigation. If the vertical guidance is not satisfactory, revert to NAV/FPA or consider the go-around. If the lateral guidance is not satisfactory, perform a go-around.
Дата 01.02.2013 ВЫПОЛНЕНИЕ ПОЛЕТА cтр. 83

|
РПП Часть В |
Стандартные эксплуатационные процедуры |
Издание: 05 |
|
|
Airbus-319/320/321 |
Standard operating procedures(SOP) |
Изменение: 00 |
(S) FOR SELECTED VERTICAL OR SELECTED LATERAL AND VERTICAL GUIDANCE
At FAF:
FPA for final approach on FCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET PF FMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK PF
After the FAF:
GO AROUND ALTITUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET PF
Set, when below the go-around altitude. If any altitude constraints, set lowest one.
POSITION/FLIGHT PATH . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . MONITOR PNF POSITION/FLIGHT PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MONITOR / ADJUST PF
▪ For approach in overlay to a conventional radio navaid procedure:
Use radio navaid raw data to monitor the lateral navigation.
Altitude deviations at check points . . . . . . . . . . . . . . . . . . . . CHECK/ANNOUNCE PNF
Using altitude indication versus radio navaid position, adjust the FPA, as necessary, to follow the published descent profile, taking into account the minimum altitudes.
Do not use VDEV on the PFD. If the lateral navigation is not satisfactory, revert to TRK/FPA.
▪ For RNAV approach:
Monitor XTK error on ND.
Using altitude indication versus distance to the runway, adjust the FPA as necessary to follow the published descent profile, taking into account the minimum altitudes.
If the lateral guidance is not satisfactory, perform a go-around.
FINAL APPROACH
A/THR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK IN SPEED MODE OR OFF PF
WING ANTI ICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OFF PNF
Switch WING ANTI ICE ON if severe icing conditions only.
SLIDING TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STOW BOTH LDG MEMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK NO BLUE LINE BOTH LANDING CHECKLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COMPLETE BOTH FLIGHT PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHECK BOTH
PF announces any FMA modification.
PNF calls out if:
“SPEED” if the speed decreases below the speed target – 5 knots, or increases above the speed target +10 knots.
SINK RATE”, when V/S is greater then – 1000 feet/minute.
“BANK”, when the bank angle goes above 7 degrees.
“PITCH”, when the pitch attitude goes below -2.5°, or goes above +10°.
“COURSE”, when the course deviation is greater than 1/2 dot
or 2.5 degrees (VOR), or 5 degrees (ADF)
“_____FT HIGH (LOW)” at altitude checkpoints.
cтр. 84 |
ВЫПОЛНЕНИЕ ПОЛЕТА |
Дата 01.02.2013 |

|
РПП Часть В |
Стандартные эксплуатационные процедуры |
Издание: 05 |
|
|
Airbus-319/320/321 |
Standard operating procedures(SOP) |
Изменение: 00 |
AT MINIMUM STABILIZATION HEIGHT:
ONE THOUSAND (IMC) or FIVE HUNDRED (VMC) . . . . . . CHECK or ANNOUNCE PNF
"STABILIZED" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANNOUNCE PNF
Continue approach.
• If the A/C is not stabilized at minimum stabilization height or below and PF does not take immediate corrective action to control the exceeded parameters back into the defined stabilized conditions and there is doubt that stabilized conditions will be recovered early enough prior to landing:
"NOT STABILIZED-GO AROUND" . . . . . . . . . . . . . . . . . . . . . . . ANNOUNCE PNF GO AROUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INITIATE PF
AT ENTERED MINIMUM + 100 FT:
HUNDRED ABOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MONITOR or ANNOUNCE PNF AT ENTERED MINIMUM:
MINIMUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MONITOR or ANNOUNCE PNF
• If ground references are visible: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
“CONTINUE” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
ANNOUNCE |
PF |
|
||||||||
|
|
|
|
|
|
|
|
|
|
||
AP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . . OFF |
PF |
|
||||||||
Continue, as with a visual approach. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
“FDs OFF” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . ORDER |
PF |
|||||||||
|
|
|
|
|
|
|
|||||
FD on own side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . OFF |
PF |
|
|
|||||||
|
|
|
|
|
|||||||
FD on own side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . . OFF |
PNF |
|
||||||||
|
|
|
|
|
|||||||
“SET RW TRACK” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . ORDER |
PF |
|
||||||||
|
|
|
|
||||||||
RW TRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
. . . . . SET |
PNF |
|
||||||||
• If ground references are not visible: |
|
|
|
|
|
|
|
|
|
|
|
"GO AROUND/FLAPS" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . |
ANNOUNCE |
PF |
|
||||||||
Initiate a go-around. |
|
|
|
|
|
|
|
|
|
|
|
Note: 1. When FINAL APP mode is engaged, the AP/FD will disengage under the following conditions, depending on which one occurs first:
–At the minimum minus 50 ft (if entered) or at 400 ft AGL (if no minimum is entered), or
–At the Missed Approach Point (MAP).
2. In selected guidance, if ground references are not visible when the aircraft reaches minimum, the flight crew should make an immediate go-around. However, if the distance to the runway is not properly assessed, a step descent approach may be considered and a level-off at mininum may be performed while searching for visual references.
If the flight crew has no visual reference at MAP, at the latest, they must initiate a go-around.
Дата 01.02.2013 |
ВЫПОЛНЕНИЕ ПОЛЕТА |
cтр. 85 |