Part A Chapter 8 Operating Procedures Flashcards
8.1.1.1 / Part C 1.1.1 Minimum Vertical Separation to Terrain / Definition of GRID MORA
Except from takeoff or landing, 1000’ from obstacles or terrain up to 5000’ AMSL, and 2000’ from obstacles or terrain higher than 5000’ AMSL, which is the same as respecting Terrain Data shown on APP Charts. (*NOT Minimum Sector Altitude, MSA)
GRID MORA and MOCA ensures 1500’ from obstacles or terrain up to 5000’ AMSL and 2000’ from obstacles or terrain higher than 5000’ AMSL. Therefore respecting GRID MORA or MOCA within 10 nm of track satisfies the above requirement.
8.1.1.1 Minimum Lateral Separation to Terrain
Track well defined by two separate navaids: 10nm either side of track and 10nm beyond reporting or checkpoints
Track NOT well defined by two separate navaids: 20nm either side of track and 20nm beyond reporting or checkpoints
8.1.1.1 / Part C 1.1.1 Safe altitude from En-route and Approach charts
MOCA
MEA
Grid MORA
MA
Terrain Data on Approach Charts
Published route: MOCA (Minimum Obstacle Clearance Altitude): Valid for a corridor extending 10 nm to either side of route centreline and including a 10 nm radius beyond the fix or mileage break with a tolerance of 1500’ above terrain and obstacles up to 5000’ and 2000’ above terrain and obstacles over 5000’.
MEA (Minimum En-Route Altitude): Within entire width of airway, segment or route between Radio Fixes that meets obstacle clearance requirements between those fixes in many countries assures acceptable navigational signal coverage. (Higher than MOCA)
Grid MORA (Minimum Off-Route Altitude): 1500’ from obstacles or terrain up to 5000’ AMSL, and 2000’ from obstacles or terrain higher than 5000’ AMSL when the aircraft Off-route
MA (Minimum Altitude) on STAR Approach Chart: 25 nm MSA (Minimum Sector Altitude) provides 1000’ separation but does NOT guarantee Navaid reception when not following STAR
Terrain Data on Approach Charts: Vertical Clearance of 1000’ from obstacle elevation up to 5000’, 2000’ from obstacle elevation greater than 5000’.
8.1.1.1 When is permitted to operate below safe altitudes
Carrying out published and approved approach procedure
IFR under positive radar control
Operate on IFR plan but in VMC and at least 1000’ on top, or in sight of land and water VFR
8.1.1.1 When MSA (Minimum Sector Altitude) can be replaced
Terminal Arrival Altitude (TAA) in some RNAV approaches, Straight in Area and Base Area both provide minimum IFR obstacle clearance of 1000’ within 25nm (ICAO)
8.1.1.1 Radar Control Separation and Responsibility
1000’ from obstacles within 5 nm either side of track
Position of aircraft must be monitored by Navaids
Radar control does NOT relieves a commander’s responsibility to ensure adequate terrain and obstacle clearance
Loss of communication: Crew assume Responsibility Immediately
8.1.1.1 / 8.1.8.2 Avoidance of Mountain Waves and Minimum Safe Altitude Increment and Minimum Route Altitude (MRA) (NOT Minimum Reception Altitude in this case)
When wave development is forecast or known to be present only: Clearance of at least 5000’ is necessary above mountains which are up to 5000’ in height above the surrounding terrain (minimum clearance same as mountain height for mountains higher than 5000’ in height)
Otherwise: Simply respect GRID MORA or MOCA.
Within 20 nm of terrain with max elevation higher than 2000’, strong winds can affect the accuracy of altimeter.
Safe Altitudes Corrections:
Corrections Required Windspeed in kts
0-30 31-50 51-70 over 70
GRID MORA 2000’-8000’ 500’ 1000’ 1500’ 2000’
GRID MORA Above 8000’ 1000’ 1500’ 2000’ 2500’
CFP MRA None 500’ 1000’ 1500’
EDG MRA None None 500’ 1000’
MRA on CFP and EDG are always UNCORRECTED based on the following assumptions:
GRID MORA on chart takes account into NIL WIND.
CFP MRA are based on obstacles within 10 nm (If no Navaids defined: 20 nm from last waypoint to current waypoint) of track and taken account into 30 kt wind.
CFP MRA = GRID MORA + 1000’ to satisfy CAD Requirement. Therefore CFP MORA is ALWAYS higher than GRID MORA and is MOST conservative.
EDG MRA are based on obstacles within 10nm of track and take account into 50 kt wind. Therefore EDG MRA allows flight below GRID MORA provided that 10 nm allowance is not exceeded.
Example at APAGO (HKGCCU)
GRID MORA CFP MRA EDG MRA
Before Corr 79 out 124; back 89 out 122 back 64
WIND Corr GRID MORA Corr CFP MRA Corr EDG MRA
0-30 kt 84 #out 124; back 89 #out 122 back 64
31-50 kt 89 out 129; back 94 #out 122 back 64
51-70 kt 94 out 134; back 99 out 127 back 69
over 70 kt 99 out 139; back 104 out 132 back 74
No Corrections Applied.
Example illustrating CFP MRA could be different on the same waypoint, and aircraft could fly down to Corr EDG ERA (64) even though it is LOWER than GRID MORA (79).
*EDG MRA is different from EDG GRID MRA. Corr GRID MORA and Corr CFP MRA only matches when Terrain Elevation is above 8000’ AND the waypoint is at the highest GRID along previous segment. Otherwise Corr CFP MRA is at least 500’ more conservative.
8.1.1.2 Corrections to MSA and Altitudes below MSA (Minimum Safe Altitude)
Correcctions to MSA: Ambient Temperature ISA -16 °C to -30 °C +10%
Corrections to Altitudes below MSA: Aerodrome Temperature 0 °C or below (Ball Park: -10 °C or below all altitudes below MSA +10%)
*MSA (Minimum Safe Altitude) refers to 25 nm MSA (Minimum Sector Altitude), MRA, Grid MORA, MEA, MOCA, etc
*Altitude below MSA includes DA(H), MDA(H), IF/IAF/FAF Altitudes, Missed Approach Altitudes, Circling minima and glide slope check altitudes
8.1.1.2 Cold weather + RNAV Modes and Minimas
Cold Weather Corrections: NAV-FPA or TRK-FPA only (FINAL APP Mode is prohibited)
LNAV/VNAV DA has lower temperature limit, if below limit, must use LNAV DA
LNAV/VNAV DA: FINAL APP Mode ONLY
LNAV DA: All modes could be used.
8.1.2.3 Minimum RFF (Rescure and Fire Fighting) Category
A320 A321 A330
Departure and Destination 6(4) 7(5) 9(7)
Alternates 4 5 7
ETOPS Alternates 4 4 4
(): May be used for Temporary Downgrade
8.1.2.4 Precision Approach Lighting System (PALS)
Runway Centreline Lights (RCL)
Alternate Red/White: 900m from Stop End
Red: 300m from Stop End
Alternate Green/Yellow: Runway Exits
Green: Clear of ILS sensitive areas
8.1.3.1 / 8.1.4.2 / 8.3.6.3 Factoring of Visibility
Pre-Despatch only: Equivalent RVR = Reported Visibility x Visibility Factor
Lighting Elements Available Day Night
High Intensity App and RWY Lighting 1.5 2.0
Any type of lighting installation 1.0 1.5
No Lighting 1.0 -
Cannot be used after Despatch
*HIALS could be FALS, IALS, BALS, NALS
Approach Light System includes RWY markings, App and RWY Lightings (Runway Edge Lights (REL), Threshold Lights, Runway End Lights and in some cases Touch-Down Zone Lights and/or RWY Centreline Lights (RCL))
After Despatch, if RVR is not reported, use Chart visibility
- 1.3.1 / 8.3.6.2 Circling to Land Minima, Visibility, Radius and Minimum Visual Reference
- 3.7.1 Conditions allow Descent below Circling Altitude
- 3.7.2 Missed Approach Procedure while Circling
1000’ AAL and 4600 m, or Chart Minima whichever higher
PAN OPS (ICAO) 5.28 nm (CHINA, HONG KONG, some Korea (RKPC, RKSI), etc)
FAA TERPS 2.3 nm (Some Korea (RKPK))
JAPAN TERPS 2.5 nm (Japan)
Minimum Visual Reference: Continuous sight of ground features and Runway Environment (RWY TH, APP Lighting, or other markings identifiable with the RWY) to ensure that aircraft position is maintained within the visual maneuvering (circling) and that the aircraft can be positioned on the approach for the runway in use.
Descent below the Circling Altitude may only occur when the PF:
- Maintains the aircraft within the circling area
- Maintains the visibility along the intended flight path not less than the minimum specified for circling
- Maintains visual contact with the Runway Environment
- Establishes the aircraft in the traffic pattern to a position from which a continuous descent to landing TH using normal rates of descent can be completed whilst maintaining obstacle clearance along the flight path
Missed Approach Procedure while Circling
Make an initial climb turn towards the landing runway until overhead the airport when the pilot will establish the aircraft climbing on the missed approach track for that particular approach, unless otherwise defined on the Port Page.
8.1.3.1 NOTAM regarding serviceability of Navaids
Awaiting Flight Check: Can be used
Unserviceable: Cannot be used
8.1.4.1 / 2.1.2.7 Adequate and Suitable Airport (Pre-Despatch)
Adequate Airport: Performance Requirement, Runway Characteristics (in short, RWY length), ATS, Sufficient Lighting, Communications, Weather Reporting, at least 1 Serviceable Navaid or RNAV(GNSS) or GPS Approach, Adequate Emergency Services (RFF)
Suitable Airport: Adequate + Meteorological Condition meet the Planning Minima.
8.1.4.2 Planning Minima (Pre-Despatch)
Destination Aerodrome: Estimated time of Arrival
Alternate Aerodrome: 1 hr before and 1 hr after Estimated time of Arrival
Takeoff Alternate: 1 hr before and 1 hr after Estimated time of Arrival
8.1.4.2 Destination and Destination Alternate Forecasts Freezing Rains (FZRA) and Freezing Drizzles (FZDZ) (Pre-Despatch)
Destination (ETA +/- 1 hr) Alternate (ETA +/- 1 hr)
(All including PROB/TEMPO/INTER)
No Freezing Precipitation Allows -FZRA, -FZDZ
-FZRA, -FZDZ Allows -FZRA. -FZDZ
FZRA, FZDZ, +FZRA, +FZDZ Does not allow any
To be confirmed…
Does not allow any Any present (if in
TEMPO/PROB
can be ignored)
8.1.4.2 Destination LVO Destination below Landing Minima
Destination LVO: Destination Alternate > CAT1 minima (Anyway minimum requirement is > Alternate Planning Minima)
Destination below Landing Minima: 2 Destination Alternates Filed in ATS Flight Plan, Both > Alternate Planning Minima
8.1.4.2 Minima for Filing as an Alternate Additives
One available approach: DH/MDH/DA/MDA + 400’, RVR/Vis + 1500m
*For LOC app, MUST BE backed up by a further published approach
At least Two available approaches to separate RWY: DH/MDH/DA/MDA + 200’, RVR/Vis + 800m Any time cannot be less than State Alternate Minima
*For LOC app, NO NEED to be backed up by further published approach
8.1.4.2 Alternate Airport not Available (Island Reserve) Definition
No Alternate airport available within 1 hr 45 min
*Use of this Policy Requires Approval from DOM
8.1.4.2 60 minutes flying time (If NOT conduct ETOPS) limit
A330: 434nm
A320: 424nm
A321: 404nm
8.1.4.2 Summary of Pre-Despatch Weather Requirements
Vis Ceiling TEMPO/ TEMPO/
PROB Vis PROB Ceiling
Destination ILS Chart No No No
Destination NPA Chart Chart No Chart
Alternate ILS/NPA Alt Alt Chart Chart
2 ENG ERA/TO Alt Chart Chart Chart Chart
1 ENG ERA/DEPRESS/ Alt Alt Alt Alt
ETOPS/ISLAND RESERVE
*Ceiling is AAL.
2 ENG ERA = 2 Engines En-Route ADEQUATE Airport
1 ENG ERA = 1 Engine En-Route ALTERNATE Airport
8.1.5.2 PROV TAF Validity
Not issued by designated issuing authority (designated MET Office), but has the same validity as any other TAF.
*If data is insufficient, “FORECAST NOT AVAILABLE” will be listed.
8.1.5.5 Criteria for generating TAPS (Turbulence Automated PIREP System) Event and Severity Levels *PIREP = Pilot Report System
TAPS light event (0.1 RMS-G) or greater
Flight to transit within 75nm
Flight within +/- 2000’ of reported altitude
Event issued in past 30 minutes
Turbulence Advisory has not previously been sent
Light: 0.1-0.19g (Food service Possible, recommends seat belt sign on)
Moderate: 0.2-0.29g (Food service Difficult, recommends seating cabin crew and secure cabin)
Severe: >0.3g (Food service Impossible)
*Recommends crew to create LAT/LONG as a waypoint to give visual reference on ND
