AC 120-29A Criteria for Approval of Category I and Category II Weather Minima for Approach
This AC provides an acceptable means, but not the only means, for obtaining and maintaining approval of CAT I & II Weather Minima including the installation and approval of associated aircraft systems.
This document is cancelled. Cancelled by 20-191. Check the official source before relying on it.
AC 120-29A
August 12, 2002
CRITERIA FOR APPROVAL OF CATEGORY I AND CATEGORY II WEATHER MINIMA FOR APPROACH
Page i
Forward. This advisory circular (AC) provides an acceptable means, but not the only means, for obtaining and maintaining approval of operations in Category I and II Landing Weather Minima including the installation and approval of associated aircraft systems. It includes additional Category I and II criteria or revised Category I and II criteria for use in conjunction with RNAV, Required Navigation Performance (RNP), VNAV, xLS, satellite navigation systems (GLS), Head up Displays (HUD), and Category II during certain engine inoperative operations. This revision also updates and incorporates provisions of the former AC 120-29 through Change 3 into the revised AC 120-29A.
This revision incorporates changes resulting from the first steps toward international all weather operations (AWO) criteria harmonization taken by the Federal Aviation Administration (FAA), European Joint Aviation Authorities (JAA), and several other regulatory authorities. Subsequent revisions of this AC are planned as additional all weather operations harmonization items (AHI) are agreed and completed by FAA JAA, and other regulatory authorities.
/s/ Nicholas A. Sabatini Associate Administrator for Regulation and Certification
Page ii
TABLE OF CONTENTS
Par Paragraph Titles
1 PURPOSE
2 RELATED REFERENCES AND DEFINITIONS 2.1 Related References 2.2 Definitions
3 BACKGROUND 3.1 Major Changes Addressed in this Revision 3.2 Relationship of Operational Authorizations for Category I or Category II and Airborne System Demonstrations 3.3 Applicable Criteria 3.4 Category I, II, and III Terminology. 3.5 Requirement for Evaluation Prior to Operations
4 OPERATIONAL CONCEPTS 4.1 Classification and Applicability of Minima 4.2 Takeoff 4.3 Landing 4.3.1 Approach and Landing Concepts and Objectives 4.3.1.1 Operational Safety Evaluation 4.3.1.2 Primary and Supplementary Means of Navigation and Required Navigation Performance (RNP) 4.3.1.3 Use of ICAO Standard NAVAIDs 4.3.1.4 Standard Instrument Approach Procedures (SIAPS) 4.3.1.5 “Steep Approaches” and Approach Path Descent Angle Constraints 4.3.1.6 “Normal Maneuvering” Considerations 4.3.1.7 Non-Normal Events or Configurations 4.3.1.8 Go-Around Safety 4.3.2 ILS, GLS, or MLS (xLS) Instrument Approach Operations 4.3.3 Instrument Approaches other than ILS, GLS, or MLS (xLS) 4.3.4 Applicability of a DA(H), MDA(H) or RA 4.3.4.1 Application of a DA(H) for Category I 4.3.4.2 Application of an MDA(H) for Category I 4.3.4.3 Application of a DA(H), or equivalent (i.e., Inner Marker), for Category II 4.3.4.4. “Specified Visual Reference” Requirements for Category I or Category II.
4.3.5 Visibility and RVR minima 4.3.6 Visibility Assessment and RVR Equivalence for Landing 4.3.7 General Requirements for Category I Operations and Minima 4.3.7.1 Category I Definition, Background, Classification, and General Criteria 4.3.7.2 “xLS” Procedures - Minima not less than 200 feet DA(H) 4.3.7.3 “3D” RNAV Procedures - Minima not less than 200 feet DA(H) 4.3.7.4 “3D” RNAV Procedures - Minima not less than 250 feet DA(H) 4.3.7.5 “2D” RNAV Procedures (e.g., VOR/DME-based RNAV, or GPS-based RNAV) - Minima not less than 250 ft. MDA(H) 4.3.7.6 Procedures other than xLS or RNAV (e.g., VOR, NDB, LOC, Back Course LOC, or ASR Procedures) - Minima not less than 250 ft. DA(H) 4.3.7.7 Other Special Procedures or Authorizations 4.3.7.8 Previously Approved Category I Operations or Use of Previous or New Category I Criteria 4.3.8 Requirements for Category II 4.3.8.1 General Category II Requirements 4.3.8.2 Specification of a Category II DA(H) 4.3.8.3 Eligibility for Category II minima not less than 100 ft. DA(H)
Page iii
4.3.8.4 Use of Inner Marker 4.3.8.5 Barometric Altimeter DAs not currently used for 14 CFR parts 121 or 135 Category II 4.3.8.6 Category II on U.S. Type I ILS 4.3.8.7 Category II using RVR 300 “Meter” Minima 4.3.8.8 Precision Approach Radar (PAR) 4.3.8.9 Previously Approved Category II Operations or Use of Previous or New Category II Criteria 4.3.9 Runway Field Length Requirements and Runway Clutter 4.3.10 NAVAIDs or Landing System Sensors and Aircraft Position Determination 4.3.10.1 Instrument Landing System (ILS) 4.3.10.2 Microwave Landing System (MLS) 4.3.10.3 Global Navigation Satellite System (GNSS) Landing System (GLS) 4.3.10.4 Satellite Systems 4.3.10.4.1 GPS/GLONASS and Reference Datum Information 4.3.10.4.2 Local Area Systems 4.3.10.4.3 Wide Area Systems 4.3.10.5 LOC/LDA/SDF/Back Course 4.3.10.6 VOR Authorized Procedures 4.3.10.7 DME 4.3.10.8 NDB Authorized Procedures 4.3.10.9 Radar Systems (e.g., PAR, ASR) 4.3.10.10 Other Systems, Procedures, and Special Systems.
4.3.10.11 Circling Approaches 4.4 RNAV/Flight Management Systems (FMS) 4.4.1 FMS Use for xLS Procedures 4.4.2 FMS Use for Procedures other Than xLS or RNAV 4.4.3 FMS Use for RNAV 4.4.3.1 Use of a Single RNAV Airborne System 4.4.4 FMS Use for RNAV with RNP 4.4.4.1 Standard RNP Qualification 4.4.4.2 “Fleet Qualification” For Use of RNP 4.4.4.3 Assessment Credit for RNP-qualified aircraft flying “non-RNP” based RNAV Procedures 4.4.4.4 Assessment of Expected Levels of ANP for RNP-qualified aircraft flying “RNP” Procedures.
4.4.5 FMS VNAV 4.4.6 FMS Use for International Procedures 4.4.7 FMS RNAV Use for Substitution for VOR, DME, NDB, or Marker Beacon NAVAIDs or Fixes 4.4.8 Inhibiting RNAV System Use of Inoperative or Unsuitable VOR, DME, VORTAC, TACAN, or NDB NAVAIDs 4.5 Required Navigation Performance (RNP) 4.5.1 RNP Levels or Types 4.5.2 Other RNP Levels or Types 4.6 Flight Path Definition 4.6.1 Landing and Rollout Flight Path 4.6.2 Runway Datum Point (RDP) 4.6.3 Flight Path Alignment Point (FPAP) 4.6.4 Flight Path Control Point (FPCP) 4.6.5 Datum Crossing Height (DCH) 4.6.6 Glide Path Angle (GPA) 4.6.7 Glide Path Intercept Reference Point (GIRP) 4.6.8 Approach and Missed Approach Segments 4.6.9 Procedure Design Related Waypoint Definitions and Use
5 AIRBORNE SYSTEM REQUIREMENTS 5.1 General 5.1.1 Airborne Systems 5.1.2 Non-Airborne Systems (e.g., NAVAIDS or equivalent GNSS Capability)
Page iv
5.1.3 Flight Path Specification 5.1.3.1 Lateral 5.1.3.2 Vertical 5.1.3.3 Longitudinal 5.1.3.4 Typical Wind and Wind Gradient Disturbance Environment 5.2 Airborne Equipment for Category I 5.3 Airborne Equipment for Category II 5.3.1 Standard Category II Minima 5.3.2 Special Category II Authorizations 5.4 Automatic Flight Control Systems and Automatic Landing Systems 5.5 Flight Director Systems 5.6 Head up Display Systems 5.7 Enhanced/Synthetic Vision Systems 5.8 Hybrid Systems 5.9 Instruments, Systems, and Displays 5.9.1 Instruments, Systems, and Displays for Category I. 5.9.2 Instruments, Systems, and Displays for Category II. 5.10 Annunciations 5.11 Auto Aural Alerts 5.12 Navigation Sensors 5.12.1 Navigation Sensors for (xLS) - ILS, GLS, or MLS. 5.12.2 Navigation Sensors for Approaches other than ILS, GLS, or MLS.
5.12.3 Aircraft Navigation Reference Points, Wheel to Eye Height, and Wheel to Navigation Reference Point Height 5.12.4 Threshold Crossing Height (TCH) 5.13 Supporting Systems and Capabilities 5.13.1 Flightdeck Visibility 5.13.2 Rain and Ice Removal 5.13.3 Miscellaneous Systems 5.14 Go-Around Capability 5.15 Excessive Deviation Alerting 5.16 Rollout Deceleration Systems or Procedures for Category I or II 5.16.1 Stopping Means 5.16.2 Antiskid Systems 5.17 Engine Inoperative Category II Capability 5.18 Special Airports with Irregular Pre-Threshold Terrain 5.19 Airborne System Evaluation and Approval 5.19.1 “Operator Use Suitability” Demonstrations-Applicability 5.19.2 Airborne Equipment Operational Validation 5.19.2.1 Category II Assessments 5.19.2.2 Flight Technical Error (FTE) Assessments 5.19.3 Data Collection and Analysis for an Airborne System Evaluation 5.19.3.1 FTE Data Collection and Analysis 5.19.3.2 Data Collection for a Category II Demonstration 5.19.3.3 Definition of a Successful Approach for a Category II Demonstration 5.20 Ground Proximity Warning System (GPWS) or
Terrain Awareness Warning System (TAWS) Interface 5.21 Flight Data Recorder (FDR) Interface 5.22 Takeoff, or Dispatch, with Inoperative Navigation Receivers, Instruments, or Displays for Category I or II. 5.22.1 Inoperative System Departure or Dispatch For Category I. 5.22.2 Inoperative System Departure or Dispatch For Category II. 5.22.3 Inoperative System Departure or Dispatch For Either Category I or Category II. 5.23. Continuation of Flight After Navigation System Failure Enroute, or During Approach, for Category I or II. 5.23.1 Continuation of a Flight After Failures For Category I. 5.23.2 Continuation of a Flight After Failures For Category II. 5.23.3 Continuation of a Flight After Failures For either Category I or Category II.
Page v
6 PROCEDURES 6.1 Operational Procedures 6.1.1 AFM Provisions 6.1.2 Crew Coordination 6.1.3 Monitoring 6.1.4 Use of the DA(H) and MDA(H) 6.1.5 Call Outs 6.1.6 Configurations 6.1.7 Compatibility between Category I, Category II, and Category III Procedures 6.1.8 Procedure Considerations During Non-Normal Operations 6.2 Category I or Category II Instrument Approach Procedures 6.2.1 Acceptable Procedures for Category I 6.2.2 Acceptable Procedures for Category II 6.2.3 Standard Obstacle Clearance for Approach and Missed Approach 6.2.4 Special Obstacle Criteria 6.2.5 Irregular Pre-threshold Terrain Airports 6.2.6 Airport Surface Depiction for Category I or II Operations 6.2.7 Continuing Category I or Category II Approaches in Deteriorating Weather Conditions 6.2.8 “Approach Ban” Applicability 6.2.9 Approach Operations at Non-US Airports when Weather is Reported “Below Minima” 6.2.10 IFR Approaches or Low Visibility Takeoffs in Class G Airspace 6.2.11 Wind Constraint Applicability 6.2.12 Crosswind Component Determination at Airports with Significant Magnetic Variation (Polar Regions) 6.2.13
Unusual or Extreme Temperatures or Pressures 6.2.13.1 General Cold Temperature Considerations 6.2.13.2 Temperatures below those used in Procedure Design 6.2.13.3 Segments which may need to be Corrected for Temperature 6.2.13.4 Uncorrected Procedures 6.2.13.5 VNAV Path and Visual Guidance (VGSI) Temperature Considerations 6.2.13.6 Unusual Cold Temperature Operations within the United States 6.2.13.7 Unusual Cold Temperature Operations outside the United States 6.2.13.8 Use of Standard Cold Temperature Table (Table 6.2.13-1) 6.2.13.9 Use of other Cold Temperature Correction Tables 6.2.13.10 Altimeter Settings 6.2.13.11 Altimeter Settings (Not Recent) 6.2.13.12 Precautions for Unusually High or Low Temperatures or High or Low Pressures 6.2.14 Metric Altitudes 6.2.15 International “Approach Procedure Title” Requirements for or Limitations on NAVAID Use 6.2.16 “U.S. TERPS” or “ICAO PANS-OPS” Obstacle Clearance Procedural Protection Limitations 6.2.17 Navigation Reference Datum Compatibility (e.g.,WGS-84/Other Datum) 6.2.18 Alternative Use Of FAA/JAA Harmonized Minima 6.2.19 Assessment of
Threshold Crossing Height (TCH), Approach Descent Gradient, and Runway Slope.
7 TRAINING AND CREW QUALIFICATION 7.1 General Knowledge (Ground) Training for All Weather Operations (AWO) 7.1.1 Ground Systems and NAVAIDs for Category I or Category II 7.1.2 The Airborne System 7.1.3 Flight Procedures, Operations Specifications, and Other Information 7.2 Maneuver or Procedure (Flight) Training for All Weather Operations (AWO) 7.2.1 Initial Qualification 7.2.2 Recurrent Qualification 7.2.3 Qualification in Conjunction with Advanced Qualification Programs (AQP) 7.2.4 Re-qualification
Page vi
7.2.5 Upgrade Qualification 7.2.6 Differences Qualification - Addressing Cockpit or Aircraft System Differences 7.2.7 Recency of Experience 7.3 Checking or Evaluations 7.3.1 Checking For Category I Qualification 7.3.2 Checking For Category II Qualification 7.3.3 Combined Checking For Simultaneous Category I/II or I/II/III Qualification 7.3.4 Checking For Low Visibility Takeoff Qualification 7.4 Experience with Line Landings 7.5 Crew Records 7.6 Multiple Aircraft Type or Variant Qualification 7.7 Aircraft Interchange 7.8 Training Regarding Use of Foreign Airports for Category I or Category II Operations 7.9 Initial Operating Experience (IOE)/Supervised Line Flying (SLF) 7.10 Line Checks, Route Checks, LOE, LOS, or LOFT 7.11 Special Qualification Requirements for Particular Category I or Category II Operations 7.11.1 HUD or Autoland 7.11.2 Use of Lowest Category I Minima at Certain Obstacle Limited or Restricted ILS Facilities 7.11.3 Simultaneous Operations Using PRM Radar 7.11.4 Simultaneous Operations with Converging Approaches and Coordinated Missed Approaches 7.11.5 Simultaneous
Runway Operations 7.11.6 Special Qualification Airports 7.11.7 Special Qualification Instrument Procedures or Types of Instrument Procedures 7.12 Special Qualification Requirements for Category II Operations at Certain U.S. Type I ILS Facilities 7.13 Simultaneous Training and Qualification for Category I and II 7.14 Simultaneous Training and Qualification for Category I, II, and III 7.15 Credit for “High Limit Captains” (Reference Sections 121.652, 125.379, 135.225) 7.16 Particular Approach System/Procedure Qualification 7.16.1 Autoland Qualification 7.16.2 Head Up Display Qualification 7.16.3 RNAV Approach Qualification 7.16.4 Category I or II Operations with an Engine Inoperative 7.16.5 Enhanced Vision Systems (EVS), or Synthetic Vision Systems (SVS), or Independent Landing Monitor (ILM)
8 AIRPORTS, NAVIGATION FACILITIES, AND METEROLOGICAL CRITERIA 8.1 Use of Standard Navigation Facilities 8.2 Use of Other Navigation Facilities or Methods 8.3 Lighting Systems 8.4 Marking and Signs 8.5 Low Visibility Surface Movement Guidance and Control System (SMGCS) Plans 8.6 Meteorological Services and RVR 8.6.1 Meteorological Services 8.6.2 RVR Availability and Use Requirements 8.6.2.1 RVR Availability. 8.6.2.2 RVR Use. 8.6.2.3 Alternate RVR Requirements For Short Field Length Operations. 8.6.2.4 International RVR Reporting and Use Equivalence Considerations. 8.6.3 Pilot Assessment of Takeoff Visibility Equivalent to RVR 8.7 Critical Area Protection 8.8 Operational Facilities, Outages, Airport Construction, and NOTAMs 8.9 Use of Military Facilities 8.10 Special Provisions for Facilities Used for ETOPS Alternates or EROPS Alternates 8.11 Alternate Minima 8.12 Dispatch or Release to Airports That are Below Landing Minima
Page vii
8.13 Temperatures and Temperature Extremes 8.14 Pressures and Unusually High or Low Pressures
9 CONTINUING AIRWORTHINESS / MAINTENANCE 9.1 Maintenance Program General Provisions 9.2 Maintenance Program Requirements 9.3 Initial and Recurrent Maintenance Training 9.4 Test Equipment/Calibration Standards 9.5 Return to Service Procedures 9.6 Periodic Aircraft System Evaluations 9.7 Reliability Reporting and Quality Control 9.7.1 Reliability Reporting - Category I 9.7.2 Reliability Reporting - Category II 9.8 Configuration Control/System Modifications 9.9 Records 9.10 Part 129 Foreign Operator Maintenance Programs 9.10.1 Maintenance of Part 129 Foreign Registered Aircraft 9.10.2 Maintenance of Part 129 Foreign Operated U.S. “N” Registered Aircraft
10 APPROVAL OF U.S. OPERATORS 10.1 Operations Manuals and Procedures 10.2 Training Programs and Crew Qualification 10.3 Dispatch Planning (e.g., MEL, Alternate Airports, ETOPS) 10.4 Formulation of Operations Specification Requirements (e.g., RVR limits, DA(H) or MDA(H), equipment requirements, field lengths) 10.5 Operational/Airworthiness Demonstrations 10.5.1 Aircraft System Suitability Demonstration 10.5.2 “Operator Use Suitability” Demonstration 10.5.2.1 Data Collection For Airborne System Demonstrations 10.5.2.2 Data Analysis 10.5.3 Use of Autoland or Head up Guidance at US Type I Facilities or Equivalent (e.g., Type I ILS). 10.6 Eligible Airports and Runways 10.7 Irregular Pre-Threshold Terrain and Other Restricted Runways 10.8. Category II Engine-Inoperative Operations and ETOPS or EROPS Alternates based on Category II. 10.8.1 General Criteria for Engine Inoperative Category II Authorization 10.8.2.
Category II Engine Inoperative “Flight Planning” 10.8.3 Category II Engine Inoperative En Route 10.8.4 Category II Engine Failure During Approach, Prior to Decision Altitude (Height) (DA(H)) 10.8.5 Category II Engine Failure After Passing Decision Altitude (Height) (DA(H)) 10.8.6 Operators using Combined Category II and Category III Engine-Inoperative Approach Provisions.
10.9 New Category II Operators 10.10 Experienced Category II or Category III Operators for New Category II Authorizations 10.10.1 Category I or II at New Airports/Runways 10.10.2 Category II with New Aircraft Systems 10.10.3 Adding a New Category II Aircraft Type 10.11 Category II Program Status Following Operator Acquisitions/Mergers 10.12 Initiating Combined Category I and II, or Category I, II, and III Programs for New Equipment Types 10.13 U.S. Carrier Category I and II Operations at Foreign Airports 10.14 Category I and II Operations on Off-Route Charters 10.15 Approval of Category I and II Minima 10.16 Operations Specification Amendments 10.17 Use of Special Obstacle Clearance Criteria (e.g., MASPS, or non-standard RNP Criteria) 10.18 Proof-of-Concept Requirements for New Systems/Methods 10.19 RNP Qualification and Authorization
Page viii
11 FOREIGN AIR CARRIER CATEGORY I WITH SYSTEMS OTHER THAN ILS OR CATEGORY II AT U.S. AIRPORTS (PART 129 OPERATIONS SPECIFICATIONS) 11.1 Use of ICAO or FAA Criteria 11.1.1 Acceptable Criteria 11.1.2 Foreign Operator AFM Provisions 11.1.3 Foreign Operator Category II Demonstrations 11.2 Issuance of Part 129 Operations Specifications 11.3 Use of Certain Restricted U.S. Facilities
12 OPERATOR REPORTING, AND TAKING CORRECTIVE ACTIONS 12.1 Operator Reporting 12.2 Operator Corrective Actions
APPENDIX 1 DEFINITIONS AND ACRONYMS
APPENDIX 2 AIRBORNE SYSTEMS FOR CATEGORY I 1 APPENDIX 2 PURPOSE 2 APPENDIX 2 GENERAL 3 APPENDIX 2 INTRODUCTION 4 APPENDIX 2 TYPES OF APPROACH OPERATIONS 4.1 APPENDIX 2 Operations based on a Standard Landing Aid 4.2 APPENDIX 2 Operations based on Required Navigation Performance (RNP) 4.2.1 APPENDIX 2 Standard RNP Types 4.2.2 APPENDIX 2 Non-standard RNP Types 4.3 APPENDIX 2 Operations based on Area Navigation System(s) 5 APPENDIX 2 TYPES OF APPROACH NAVIGATION SERVICE 5.1 APPENDIX 2 Instrument Landing System (ILS) 5.1.1 APPENDIX 2 ILS Flight Path Definition 5.1.2 APPENDIX 2 ILS Airplane Position Determination 5.2 APPENDIX 2 Microwave Landing System (MLS) 5.2.1 APPENDIX 2 MLS Flight Path Definition 5.2.2 APPENDIX 2 MLS Airplane Position Determination 5.3 APPENDIX 2 GNSS with Ground Based Augmentation (GLS) [PoC] 5.3.1 APPENDIX 2 GLS Flight Path Definition 5.3.2 APPENDIX 2 GLS Airplane Position Determination 5.3.3 APPENDIX 2 Data link [PoC] 6 APPENDIX 2 BASIC AIRWORTHINESS REQUIREMENTS 6.1 APPENDIX 2 General Requirements 6.2 APPENDIX 2 Approach System Accuracy Requirement 6.2.1 APPENDIX 2 ILS 6.2.2 APPENDIX 2 MLS 6.2.3 APPENDIX 2 GLS [PoC] 6.2.4 APPENDIX 2 RNP 6.2.5 APPENDIX 2 Flight Path Definition 6.2.6 APPENDIX 2 Area Navigation Systems 6.3 APPENDIX 2 Approach System Integrity Requirements 6.3.1 APPENDIX 2 ILS 6.3.2 APPENDIX 2 MLS 6.3.3 APPENDIX 2 GLS 6.3.4 APPENDIX 2 RNP 6.3.5 APPENDIX 2 Area Navigation Systems 6.4 APPENDIX 2 Approach System Availability Requirements 6.5 APPENDIX 2 Go-around Requirements 6.6 APPENDIX 2 Flightdeck Information, Annunciation, and Alerting Requirements
Page ix
6.6.1 APPENDIX 2 Flightdeck Display Information Requirements 6.6.2 APPENDIX 2 Annunciation Requirements 6.6.3 APPENDIX 2 Alerting 6.6.3.1 APPENDIX 2 Warnings 6.6.3.2 APPENDIX 2 Cautions 6.6.3.3 APPENDIX 2 System Status 6.7 APPENDIX 2 Multiple Landing Systems and Multi-mode Receivers (MMR) for Category I 6.7.1 APPENDIX 2 General Requirements 6.7.2 APPENDIX 2 Indications 6.7.3 APPENDIX 2 Annunciations 6.7.4 APPENDIX 2 Alerting 6.7.5 APPENDIX 2 Multi-mode Receivers (MMR) 6.7.5.1 APPENDIX 2 “ILS Look-alike” Definition Applicable to MMR 6.7.5.2 APPENDIX 2 General Certification Considerations 6.7.5.2.1 APPENDIX 2 Certification Process 6.7.5.2.2 APPENDIX 2 Equipment Approval 6.7.5.2.3 APPENDIX 2 Aircraft Installation Approval (14 CFR Part 25) 6.7.5.2.4 APPENDIX 2 Alternative Means of Compliance using JAR-AWO 6.7.5.2.5 APPENDIX 2 Recertification of an ILS function following the Introduction of a New or Modified ILS Navigation Receiver Installation 6.7.5.2.5.1 APPENDIX 2 New or Modified ILS Impact Assessment 6.7.5.2.5.2 APPENDIX 2 New or Modified ILS Failure Analysis 6.7.5.2.5.3 APPENDIX 2
New or Modified ILS Autoland or HUD Guidance Landing Function Flight Testing (if necessary) 6.7.5.2.5.4 APPENDIX 2 New or Modified ILS Documentation 6.7.5.2.6 APPENDIX 2 Recertification following the Introduction of an MLS or GLS Navigation Receiver Installation 6.7.5.2.6.1 APPENDIX 2 MLS or GLS Introduction Impact Assessment 6.7.5.2.6.2 APPENDIX 2 MLS or GLS Failure Analysis 6.7.5.2.6.3 APPENDIX 2 MLS or GLS Statistical Performance Assessment 6.7.5.2.6.4 APPENDIX 2 MLS or GLS Antenna or Navigation Reference Point Location 6.7.5.2.6.5 APPENDIX 2 MLS or GLS Introduction Flight Testing (as necessary) 6.7.5.2.6.6 APPENDIX 2 MLS or GLS Introduction Documentation 6.8 APPENDIX 2 Steep Angle Approaches 7 APPENDIX 2 APPROACH SYSTEM EVALUATION 7.1 APPENDIX 2 Performance Evaluation 7.2 APPENDIX 2 Safety Assessment 8 APPENDIX 2 AIRBORNE SYSTEM REQUIREMENTS 8.1 APPENDIX 2 General 8.2 APPENDIX 2 Autopilot 8.3 APPENDIX 2 Head Down Guidance 8.4 APPENDIX 2 Head Up Guidance 8.5 APPENDIX 2 Hybrid HUD/Autoland System [PoC] 8.6 APPENDIX 2 Satellite Based Approach System 8.7 APPENDIX 2 Aircraft
Navigation Systems 8.8 APPENDIX 2 Autothrottle 8.9 APPENDIX 2 Data link [PoC] 9 APPENDIX 2 AIRPLANE FLIGHT MANUAL (AFM)
APPENDIX 3 AIRBORNE SYSTEMS FOR CATEGORY II 1 APPENDIX 3 PURPOSE 2 APPENDIX 3 GENERAL 3 APPENDIX 3 INTRODUCTION 4 APPENDIX 3 TYPES OF APPROACH OPERATIONS 4.1 APPENDIX 3 Operations based on a Standard Landing Aid 4.2 APPENDIX 3 Operations based on Required Navigation Performance (RNP)
Page x
4.2.1 APPENDIX 3 Standard RNP Types 4.2.2 APPENDIX 3 Non-standard RNP Types 5 APPENDIX 3 TYPES OF APPROACH NAVIGATION SERVICE 5.1 APPENDIX 3 ILS 5.1.1 APPENDIX 3 ILS Flight Path Definition 5.1.2 APPENDIX 3 ILS Airplane Position Determination 5.2 APPENDIX 3 MLS 5.2.1 APPENDIX 3 MLS Flight Path Definition 5.2.2 APPENDIX 3 MLS Airplane Position Determination 5.3 APPENDIX 3 GNSS with Ground Based Augmentation (GLS) [PoC] 5.3.1 APPENDIX 3 GLS Flight Path Definition [PoC] 5.3.2 APPENDIX 3 GLS Airplane Position Determination [PoC] 5.3.3 APPENDIX 3 Data link [PoC] 6 APPENDIX 3 BASIC AIRWORTHINESS REQUIREMENTS 6.1 APPENDIX 3 General Requirements 6.2 APPENDIX 3 Approach System Accuracy Requirements 6.2.1 APPENDIX 3 ILS 6.2.2 APPENDIX 3 MLS 6.2.3 APPENDIX 3 GLS [PoC] 6.2.4 APPENDIX 3 RNP 6.2.5 APPENDIX 3 Flight Path Definition 6.3 APPENDIX 3 Approach System Integrity Requirements 6.3.1 APPENDIX 3 ILS 6.3.2 APPENDIX 3 MLS 6.3.3 APPENDIX 3 GLS 6.3.4 APPENDIX 3 RNP 6.4 APPENDIX 3 Approach System Availability Requirements 6.5 APPENDIX 3 Go-around Requirements 6.6 APPENDIX 3 Flightdeck Information,
Annunciation, and Alerting Requirements 6.6.1 APPENDIX 3 Flightdeck Display Requirements 6.6.2 APPENDIX 3 Annunciation Requirements 6.6.3 APPENDIX 3 Alerting 6.6.3.1 APPENDIX 3 Warnings 6.6.3.2 APPENDIX 3 Cautions 6.6.3.3 APPENDIX 3 System Status 6.7 APPENDIX 3 Multiple Landing Systems and Multi-mode Receivers (MMR) for Category II 6.7.1 APPENDIX 3 General Requirements 6.7.2 APPENDIX 3 Indications 6.7.3 APPENDIX 3 Annunciations 6.7.4 APPENDIX 3 Alerting 6.7.5 APPENDIX 3 Multi-mode Receiver(s) (MMR) 6.7.5.1 APPENDIX 3 “ILS Look-alike” Definition applicable to MMR 6.7.5.2 APPENDIX 3 General Certification Considerations 6.7.5.2.1 APPENDIX 3 Certification Process 6.7.5.2.2 APPENDIX 3 Equipment Approval 6.7.5.2.3 APPENDIX 3 Aircraft Installation Approval (14 CFR Part 25) 6.7.5.2.4 APPENDIX 3 Alternate Means of Compliance using JAR-AWO 6.7.5.2.5 APPENDIX 3 Recertification of an ILS function following the introduction of a New or Modified ILS Navigation Receiver Installation 6.7.5.2.5.1 APPENDIX 3 New or Modified ILS Impact Assessment 6.7.5.2.5.2 APPENDIX 3 New or Modified ILS Failure
Analysis 6.7.5.2.5.3 APPENDIX 3 New or Modified ILS Autoland or HUD Guidance Landing Function Flight Testing (if necessary) 6.7.5.2.5.4 APPENDIX 3 New or Modified ILS Documentation 6.7.5.2.6 APPENDIX 3 Recertification Following the Introduction of an MLS or GLS Navigation Receiver Installation
Page xi
6.7.5.2.6.1 APPENDIX 3 MLS or GLS Introduction Impact Assessment 6.7.5.2.6.2 APPENDIX 3 MLS or GLS Failure Analysis 6.7.5.2.6.3 APPENDIX 3 MLS or GLS Statistical Performance Assessment 6.7.5.2.6.4 APPENDIX 3 MLS or GLS Antenna or Navigation Reference Point Location 6.7.5.2.6.5 APPENDIX 3 MLS or GLS Introduction Flight Testing (as necessary) 6.7.5.2.6.6 APPENDIX 3 MLS or GLS Introduction Documentation 7 APPENDIX 3 APPROACH SYSTEM EVALUATION 7.1 APPENDIX 3 Performance Evaluation 7.2 APPENDIX 3 Safety Assessment 8 APPENDIX 3 AIRBORNE SYSTEM REQUIREMENTS 8.1 APPENDIX 3 General 8.2 APPENDIX 3 Autopilot 8.3 APPENDIX 3 Head Down Guidance 8.4 APPENDIX 3 Head Up Guidance 8.5 APPENDIX 3 Hybrid HUD/Autoland Systems [PoC] 8.6 APPENDIX 3 Satellite Based Approach System 8.7 APPENDIX 3 Reserved 8.8 APPENDIX 3 Autothrottle 8.9 APPENDIX 3 Data link 9 APPENDIX 3 AIRPLANE FLIGHT MANUAL (AFM)
APPENDIX 4 WIND MODEL FOR APPROACH SIMULATION
APPENDIX 5 OBSTACLE ASSESSMENT FOR RNP FOR CATEGORY I OR CATEGORY II
1 APPENDIX 5 Obstacle Assessment for Standard Required Performance (RNP) Types (e.g., Linear Values of RNP) 1.1 APPENDIX 5 Obstacle Assessment for RNP Approaches and Missed Approaches 1.1.1 APPENDIX 5 General 1.1.2 APPENDIX 5 Final Approach (FAS), Missed Approach (MAS) and other Related Segments 1.1.3 APPENDIX 5 Approach and Missed Approach Conditions To Be Assessed 1.1.4 APPENDIX 5 Touchdown Zone 1.2 APPENDIX 5 Obstacle Criteria 1.2.1 APPENDIX 5 Obstacle Identification Surface Between Point Of Lowest DA(H) and the Runway 1.2.2 APPENDIX 5 Obstacle Identification Surface Between the Point of Lowest DA(H) and a Missed Approach 1.2.3 APPENDIX 5 Obstacle Identification Surface Between the End of the TDZ and a Missed Approach Waypoint 1.2.4 APPENDIX 5 FAS Turn Construction 1.2.4.1 APPENDIX 5 FAS Turn Construction for Fly-by Waypoints 1.2.4.2 APPENDIX 5 FAS Turn Construction for Fly-over Waypoints 1.2.5 APPENDIX 5 MAS Turn Construction 1.2.5.1 APPENDIX 5 MAS Turn Construction for Fly-by Waypoints 1.2.5.2 APPENDIX 5 MAS Turn Construction For Fly-over Waypoints 1.2.6 APPENDIX 5 RNP
Reductions 1.2.7 APPENDIX 5 Coordinate Systems 1.2.8 APPENDIX 5 Obstruction and Terrain Charts 1.2.8.1 APPENDIX 5 Recommended Use of USGS Charts 1.2.8.2 APPENDIX 5 Vertical Clearance Adjustments for Certain Topographical Charts 1.2.8.3 APPENDIX 5 Tree Heights 1.2.8.4 APPENDIX 5 Assumptions for Terrain Elevations 1.2.9 APPENDIX 5 Man-Made Obstacle Data 1.2.10 APPENDIX 5 Wheel to Navigation Reference Point or Longitudinal Navigation Reference Points 1.3 APPENDIX 5 Examples of completed RNP Forms 2 APPENDIX 5 FINAL APPROACH OBSTACLE ASSESSMENT - NON-STANDARD LEVELS OF RNP 2.1 APPENDIX 5 Obstacle Assessment For Non-Standard Levels of RNP 2.2 APPENDIX 5 OBSTACLE CRITERIA
Page xii
2.3 APPENDIX 5 USE OF THESE CRITERIA FOR AIRBORNE SYSTEM AIRWORTHINESS DEMONSTRATIONS WITH NON-STANDARD LEVELS OF RNP 2.3.1 APPENDIX 5 LATERAL PERFORMANCE 2.3.2 APPENDIX 5 VERTICAL PERFORMANCE 2.4 APPENDIX 5 OTHER CONSIDERTIONS
APPENDIX 6 GROUND SYSTEMS AND OBSTACLE CLEARANCE CRITERIA FOR CATEGORY II AND CATEGORY III OPERATIONS
1 APPENDIX 6 PURPOSE 2 APPENDIX 6 GENERAL 3 APPENDIX 6 SUPPORTING NAVIGATION AIDS OR SENSORS FOR CATEGORY II PROCEDURES 4 APPENDIX 6 OBSTACLE CLEARANCE CRITERIA
APPENDIX 7 OPERATIONS SPECIFICATIONS
1 APPENDIX 7 General 2 APPENDIX 7 14 CFR Part 121 Operations Specifications - PART A 3 APPENDIX 7 14 CFR Part 121 Operations Specifications - PART C C051 APPENDIX 7 OpSpec C051, Terminal Instrument Procedures C052 APPENDIX 7 OpSpec C052, Basic Instrument Approach Procedure Authorization - All Airports C053 APPENDIX 7 OpSpec C053, Straight-in Category I Approach Procedures other than ILS, MLS, or GPS and IFR Landing Minimums - All Airports C054 APPENDIX 7 OpSpec C054, Limitations and Provisions for Instrument Approach Procedures and IFR Landing Minimums C055 APPENDIX 7 OpSpec C055, Alternate Airport IFR Weather Minimums C056 APPENDIX 7 OpSpec C056, IFR Takeoff Minimums, Part 121 Airplane Operations - All Airports C059 APPENDIX 7 OpSpec C059, Category II Instrument Approach and Landing Operations C061 APPENDIX 7 OpSpec C061, Flight Control Guidance Systems for Automatic Landing Operations Other Than Categories II and III C062 APPENDIX 7 OpSpec C062, Manually Flown Flight Control Guidance System Certified for Landing Operations Other Than Categories II and III C074 APPENDIX 7 OpSpec C074, Straight-in Category I, ILS, MLS, or GLS Approach Procedures and IFR Landing Minimums - All Airports C075 APPENDIX 7 OpSpec C075, Category I IFR Landing Minimums - Circling Maneuvers C076 APPENDIX 7 OpSpec C076, Category I IFR Landing Minimums - Contact Approaches C078 APPENDIX 7 OpSpec C078, IFR Lower Than Standard Takeoff Minimums, 14 CFR Part 121 Airplane Operations - All Airports C090 APPENDIX 7 OpSpec C090, Required Navigation Performance (RNP)
APPENDIX 8 USE OF ALTERNATIVE OPERATING MINIMA
1 APPENDIX 8 General 2 APPENDIX 8 Terminology 3 APPENDIX 8 “Go-Around” Transition To A Missed Approach When Using a DA(H) or MDA(H) 4 APPENDIX 8 Alternative RVR/Visibility Value Table 5 APPENDIX 8 Approach and Runway Lighting Systems Definition, Classification, and Equivalence 6 APPENDIX 8 Applicability to Various Classes of Instrument Approach Procedures 7 APPENDIX 8 Transition Provisions 8 APPENDIX 8 Authorized RVR Minima Conversions between “Feet and Meters” 9 APPENDIX 8 Acceptable Meteorological Visibility or RVR Equivalence or Conversion
1. PURPOSE. This advisory circular (AC) provides an acceptable means, but not the only means, for obtaining and maintaining approval of Category I and II Weather Minima including the installation and approval of associated aircraft systems. This AC is applicable to Title 14 of the Code of Federal Regulations (14 CFR) parts 121, 135, and those part 125 operators not exempted under section 125.1 or not having received an applicable deviation authorization under section 125.3. Certain aspects of this AC are applicable to 14 CFR part 129 operators. Many of the principles, concepts, and procedures described also may apply to 14 CFR part 91 operations and are recommended for use by those operators when applicable.
a. This AC provides some guidance that may be applicable to operations conducted by civil helicopters and powered-lift aircraft. Supplementary guidance for those aircraft may be provided by other FAA or industry documents.
b. Mandatory terms used in this AC such as “shall” or “must” are used only in the sense of insuring applicability of these particular methods of compliance when the acceptable means of compliance described herein is used. This AC does not change, add, or delete regulatory requirements or authorize deviations from regulatory requirements.
c. Major changes introduced in this revision include new provisions for Required Navigation Performance (RNP), Vertical Navigation (VNAV), Flight Management System (FMS), Global Navigation Satellite System (GNSS), Head Up Display (HUD), Global Positioning System (GPS) or GNSS Landing System (GLS), revised obstacle assessment criteria related to RNP, and revised airborne equipment requirements for Category I and II.
d. With issuance of AC120-29A, the former AC 120-29, Criteria for Approving Category I and Category II Landing Minima for FAR 121 Operators, dated December 3, 1974, is canceled.
2. RELATED REFERENCES AND DEFINITIONS.
2.1. Related References.
a. Regulations. 14 CFR part 91, sections 91.175, and 91.189; 14 CFR part 121, sections 121.579, and 121.651; 14 CFR part 125, sections 125.379, and 125.381; 14 CFR part 129, section 129.11; and 14 CFR part 135, section 135.225; 14 CFR part 25, sections 25.1309, and 25.1329.
b. ACs. Current editions of: AC 120-28, Criteria for Approval of Category III Landing Weather Minimal; AC 20-129, Airworthiness Approval of Vertical Navigation (VNAV) Systems for Use In the U.S. NAS and Alaska; AC 20-130, Airworthiness Approval of Navigation or Flight Management Systems Integrating Multiple Navigation Sensors; AC20-138, Airworthiness Approval of GPS Navigation Equipment for use as a Supplemental Navigation System; and AC 25-15, Approval of Flight Management Systems in Transport Category Airplanes.
c. Orders. FAA Orders 8400.8, Procedures for Approval of Facilities for FAR Part 121 and Part 135 CAT III Operations; 8400.10, Air Transportation Operations Inspector’s Handbook; 8400.13, Procedures for the Approval of Category II Operations and Lower Than Standard Category I Operations on Type I Facilities; and 6750.24, Instrument Landing System (ILS) and Ancillary Electronic Component Configuration and Performance Requirements.
d. OpSpecs. Standard Operations Specifications Part A and C.
e. Foreign. Joint Aviation Authority (JAA) ACJ AWO 231, Flight Demonstration (Acceptable Means of Compliance) dated August, 1996.
2.2. Definitions. A comprehensive set of definitions pertinent to Category I and II is included in Appendix I.
3. BACKGROUND.
3.1. Major Changes Addressed in this Revision. This advisory circular includes additional Category I and Category II criteria or revised Category II criteria for use of Head up Displays, use of Required Navigation Performance (RNP), satellite based navigation, and “engine inoperative” Category II approach procedures. This revision expands information regarding Category I approach procedures, and now includes material pertinent to types of approach procedures other than ILS, MLS, or GLS (e.g., also addresses approaches previously considered as non-precision approaches).
a. This AC also clarifies existing criteria to address frequently asked questions.
b. This revision incorporates changes resulting from the first steps toward international all weather operations (AWO) criteria harmonization taken by the FAA, European JAA, and several other regulatory authorities. Subsequent revisions of this AC are planned as additional all weather operations harmonization items (AHI(s)) are agreed and completed by FAA and JAA, or internationally.
3.2. Relationship of Operational Authorizations for Category I or Category II and Airborne System Demonstrations. Approach weather minima are approved through applicable operating rules, use of approved instrument procedures and issuance of Operations Specifications (Op-Specs)*. Airworthiness demonstration of aircraft equipment is usually accomplished in support of operational authorizations on a one-time basis at the time of Type Certification (TC) or Supplemental Type Certification (STC). This demonstration is based upon the airworthiness criteria in place at that time. Since operating rules continuously apply over time and may change after airworthiness demonstrations are conducted, or may be updated consistent with safety experience, additional Category I or Category II credit or constraints may apply to Operators or aircraft as necessary for safe operations. In general, criteria related to operational approval is contained in the main body of this AC and criteria related primarily to the airworthiness demonstration of systems or equipment is included in the appendices to this AC.
*NOTE: Operations Specifications are unique Federal Aviation Regulations applicable to a particular operator. OpSpecs are based on the regulations. However, they are specifically applicable to and tailored to a particular operator’s aircraft, routes, and operating circumstances. Standard Operations Specifications are developed by FAA and provided to FAA field offices to aid in development and issuance of the particular and unique OpSpecs issued to each operator.
3.3. Applicable Criteria. Except as described below, new airworthiness demonstrations or operational authorizations should use the criteria of AC 120-29A. Airworthiness demonstrations may use equivalent JAA criteria where agreed by FAA through the FAA/JAA criteria harmonization process. Operators electing to comply with these revised criteria may receive additional credit when using the revised criteria. Aircraft manufacturers or modifiers may elect to demonstrate their aircraft using the revised criteria to seek credit for additional operations. Aircraft demonstrated using earlier criteria may continue to be approved for Category I or Category II operations in accordance with (IAW) that earlier criteria. Operators seeking additional credit provided for in this AC must, however, use the criteria of this AC for that credit.
3.4. Category I, II, and III Terminology.
a. Since 1985, the FAA has referred to all approaches other than Category II or Category III as Category I, for purposes of regulatory authorization for part 121, 125, 135, and 129 operators (e.g., Operations Specifications). Thus for consistency and continuity, all Category I approach procedures and operational authorizations are now addressed in this AC. In addition to typical Category I Instrument Landing System (ILS), Microwave Landing System (MLS) and Global Navigation Satellite System (GNSS) Landing System (GLS) procedures (e.g., procedures historically considered as precision approach), information about approaches other than ILS, MLS, and GLS are now included (e.g., procedures historically considered as non-precision approach). The use of the term “non-precision” has been dropped within this AC to reduce confusion which exists with use of this term with current and future
systems and authorizations, particularly with Vertical Navigation (VNAV) and Area Navigation (RNAV), and with other approaches that may incorporate the use of barometric VNAV to provide a stabilized descent path to a runway.
b. Accordingly, Category I, II, and III terminology used in this AC is based on and is consistent with current U.S. Standard Operations Specifications for part 121, 125, 135, and 129 Operators. Definition usage is also consistent with other ACs (e.g., AC120-28D). Definitions of instrument approach Categories in current use in the U.S. are listed in Appendix 1 of this AC (i.e., Category I, Category II, Category IIIa, IIIb, and IIIc). While there are slight variations of these definitions as used within ICAO and various countries internationally, the broad objectives and practical operational applications are similar. It is significant to note that for U.S. applications to part 121, 125, 135, and 129 operators, Category I is considered to include any instrument approach procedure having minima not less than 200 ft. Height Above Touchdown (HAT) and RVR not less than 1800ft. Accordingly, approaches such as Localizer (LOC); LOC BCRS; Localizer-Type Directional Aid (LDA); Simplified Directional Facility (SDF); Very High Frequency (VHF) Omni-directional Radio Range (VOR); Non-Directional Beacon (NDB); and RNAV are each considered to be Category I approaches. In other states, Category I may only apply to straight-in ILS or MLS instrument procedures. Also, in certain states, lowest authorized minima may be slightly different than as promulgated by the U.S. or ICAO criteria. In a few states, these approach categories relate more closely to aircraft configuration or ILS facilities used, rather than directly landing minima (e.g., Decision Altitude (Height) (DA(H)) and visibility or RVR).
3.5. Requirement for Evaluation Prior to Operations. Instrument approach procedures in the United States and its territories must be validated by an authorized FAA process. Special procedure requests should be made through the CMO to AFS-400.
4. OPERATIONAL CONCEPTS.
4.1. Classification and Applicability of Minima. Landing minima are generally classified by Category I, Category II, and Category III. Definitions for Category I, II, and III are as specified by ICAO and individual states. For the U.S. these definitions are as included in Appendix 1. Certificate Holding District Offices (CHDO) and Operators should be aware that slight differences exist in definition and use of Category I, II, and III terminology in international operations. Operators should ensure that any differences in definitions do not adversely affect intended operations (see Paragraph 3.4 above).
a. This AC addresses criteria for Category I and Category II instrument approach operations. AC 120-28 addresses takeoff in low visibility conditions and Category III landing operations.
b. Landing minima are generally addressed by parts 91.175, 121.649, 121.651, 121.652 and standard or special OpSpecs Part C. Application of these definitions of Category I, II, and III to landing is discussed in paragraph 4.3.1 below.
c. Although a wide variety of normal and non-normal situations are considered in the design and approval of systems and procedures for Category I and Category II, landing weather minima are primarily intended to apply to normal operations. For non-normal operations, flightcrews are expected to take the safest course of action appropriate for the situation, notwithstanding landing weather minima. When aircraft systems have been demonstrated to account for certain non-normal configurations and a procedure is specified (e.g., an approach with an engine inoperative non-normal procedure), the flightcrew may take account of this information in assessing the safest course of action. In addition, when inoperative aircraft systems have been accounted for in the Airplane Flight Manual (AFM) as an alternate configuration using criteria of this AC (e.g., an approach with an engine inoperative is specified as a demonstrated configuration) operational credit for that configuration (alternate minima credit) may be authorized.
d. Takeoff minimums are generally addressed by parts 91, 121, 135, and standard or special OpSpecs. Application of takeoff minima is discussed in paragraph 4.2 below.
4.2. Takeoff.
a. Takeoff Minima.
(1) Takeoff minima are addressed by sections 91.175(f), 121.649, 121.651, 135.225, and standard or special OpSpecs Part C. The authority for lower than standard takeoff minima is contained in sections 135.225(h)(3) and 121.651(a)(1).
(2) OpSpecs are applicable to part 121 and 135 Operators and certain other Operators (e.g., part 125 and part 129). Where minima lower than that provided in standard OpSpecs are necessary, applicable criteria for use of those minima are specified in AC 120-28D. When appropriate, principal operations inspectors (POI(s)) issue OpSpecs specifying the lower minima through paragraph C056 for part 121 Operators and OpSpecs paragraph C057 for part 135 Operators. OpSpecs contain specific guidance regarding pilots, aircraft, and airports when lower than standard takeoff minimums are used.
b. Takeoff RVR Equivalence and Assessment (See also 8.6.3). For takeoff procedures where minima are published only in terms of RVR, but visibility is being reported as a meteorological visibility, tables referenced in Standard OpSpecs may be used to establish equivalent RVR (see Appendix 7, OpSpec Paragraph). This table does not apply to minima published as meteorological visibility being reported as RVR
c. Pilot Assessment of equivalent RVR. For takeoff circumstances where Touchdown Zone RVR is inoperative or is determined by the pilot to be significantly in error (e.g., patchy fog obscuring a transmissometer but not the runway, snow on transmissometer causing erroneous readings), a pilot assessment may be made in lieu of RVR (see Appendix 7, OpSpec Paragraph C078).
(1) To be eligible to use this provision the operator must ensure that each pilot authorized to make this determination has completed approved training addressing pilot procedures to be used for visibility assessment in lieu of RVR, and the pilot can determine the necessary runway markings or runway lighting that must be available to provide an equivalent RVR to that specified to ensure adequate visual reference for the takeoff.
(2) When any pilot assessment of equivalent RVR is made, the pilot must be able to positively determine position on the airport and correct runway, and positively establish that the aircraft is at the correct position for initiation of takeoff. Typically this equivalent RVR assessment is applicable only at a runway threshold where runway identifying markings and number(s) are visible from the takeoff position (e.g., not applicable to intersection takeoffs).
(3) When such a pilot RVR assessment is made, the result of the assessment should typically be provided to any pertinent air traffic facility when practical, and may also be provided to the operator (e.g., dispatch) to facilitate other operations.
4.3. Landing.
4.3.1. Approach and Landing Concepts and Objectives. Landing minima are classified as Category I, Category II, and Category III. Definitions of these categories are provided in Standard OpSpecs Part A paragraph A002, and in Appendix 1. While generally consistent with ICAO definitions, the definitions used in Standard OpSpecs, where different from ICAO, apply and take precedence for U.S. operators, or for international operators conducting operations within the United States, or at U.S. facilities.
a. For U.S. Operators, any instrument approach with a DA(H) or Minimum Descent Altitude (Height) (MDA(H)) and visibility above that specified in OpSpecs for Category I, (see Appendix 7) is considered to be a Category I operation (e.g., an approach with either a DA(H) or an MDA(H) which is not lower than 200 ft. HAT and visibility not less than 1800 RVR is considered to be Category I, even though it may be based on a Navigational Aid (NAVAID) other than ILS).
b. Any instrument approach with a DA(H) or visibility less than that specified for Category I, but above that specified for Category II, is considered to be a Category II operation.
c. Any instrument approach with a DA(H) less than that specified for Category II (or with no DA(H) or with an Alert Height), or with a visibility less than that specified for Category II, IAW applicable OpSpecs is considered to be a Category III operation.
d. Category I operations may be conducted manually using raw data information, by reference to flight guidance displays (flight directors), or automatically using approved autopilot or autoland systems. However, air carrier operations, particularly with turbine powered aircraft, typically have minima restricted by OpSpecs if a flight director or autopilot is not used.
e. For Category I, basic airworthiness certification for IFR under provisions of 14 CFR part 25 typically is considered an acceptable means of demonstration of capability for operational acceptance of an aircraft and its associated systems. Specific criteria for airworthiness demonstration of certain specific systems or capabilities for Category I are included in Appendix 2 (e.g., FMS or RNP).
f. For Category I minima, it is expected that for non-normal operations (e.g., engine(s) inoperative, hydraulic or electrical system(s) failure) the pilot or operator should consider any necessary adjustment of operating minima, wind limit constraints, or other factors to ensure safe operation with the non-normal condition.
g. Category II operations may be conducted manually using flight guidance (e.g., flight director) displays. However, most Category II operations are conducted using an autopilot or autoland system, or with combinations of systems using both automatic and flight guidance (e.g., flight director) elements. Additional demonstration or operational assessment beyond that required for basic IFR flight under provisions of basic aircraft 14 CFR part 25 type certification typically is necessary for operational authorization of an aircraft for Category II (see Paragraph 5 and Appendix 3). Specific criteria for airworthiness demonstration of systems or capabilities for Category II are included in Appendix 3 (e.g., for flight director(s), autopilot(s), or HUD) for cases where an applicant seeks prior credit for such a prior airworthiness demonstration documented in the AFM).
h. For Category II minima, certain non-normal conditions are typically considered in the assessment and authorization process. Response to those non-normal conditions may be explicitly defined in the Category II authorization (e.g., engine failure, electrical component failure, or engine inoperative Category II). For failures other than those addressed by the Category II authorization, the pilot or operator may need to adjust the operating minima used, introduce wind limit constraints, or address other factors to ensure safe operation for the particular non-normal condition.
4.3.1.1. Operational Safety Evaluation. For any instrument approach using either Category I or Category II minima, the operator must adequately consider and provide for safe operations considering at least the following:
a. The possibility of a failure of any one of the pertinent navigation systems, flight guidance system, flight instrument system, or annunciation system elements used for the approach or missed approach (e.g., ILS receiver failure, Autopilot disconnect, etc.).
b. The possibility of a failure of a key aircraft component or related supporting system during the approach or missed approach (e.g., engine failure, electrical generator failure, single hydraulic component failure). Even though a particular failure may in itself be considered too remote based on exposure time (e.g., engine failure), it is nonetheless important to address these considerations since, in practical circumstances, a “go-around” may be due to a factor which relates to or leads to the failure, and thus is not an independent event (e.g., flocking bird ingestion). This is consistent with the long standing principle of safety of operation of multi-engine aircraft in air carrier operations which notes that after passing V1 on takeoff, until touchdown, the aircraft should typically be able to sustain a failure such as engine failure and still safely be able to continue flight and land.
c. The possibility of a balked landing or rejected landing at or below DA(H), or MDA(H), as applicable.
d. The possibility of loss or significant reduction of visual reference, that may result in or require a go-around.
e. Suitable obstacle clearance following a missed approach, considering applicable aircraft configuration during approach and any configuration changes associated with a go-around (e.g., engine failure, flap retraction).
f. For special airports identified IAW section 121.445 (e.g., mountainous terrain), or other airports with critical obstacles that have not otherwise been accounted for, the ability to ensure suitable obstacle clearance following a rejected landing; applicable aircraft configuration(s) during approach and any configuration changes associated with a go-around and missed approach should be considered.
g. Unusual atmospheric or environmental conditions that could adversely affect the safety of the operation (e.g., extreme cold temperatures, known local atmospheric or weather phenomena that introduce undue risk, etc.).
When conducting a safety assessment of issues listed above, and uncertainty exists as to aircraft failure condition effects, procedural design intent or margins, aircraft characteristics or capabilities following failure, or other such issues, the operator should consult with an appropriate organization source able to provide reliable and comprehensive information. Typically this includes consultation with one or more of the following as applicable, and as necessary:
• Aircraft manufacturer, • Avionics manufacturer; • Procedure designer; • Air Traffic Service provider, or regulatory authority.
NOTE: For definitions and discussion of differences among the terms “balked landing,” “rejected landing,” “go-around,” and “missed approach,” see Appendix 1.
4.3.1.2. Primary and Supplementary Means of Navigation and Required Navigation Performance (RNP). For the purpose of this AC, “Primary” and “Supplementary” means of navigation and Required Navigation Performance (RNP) are defined in Appendix 1. Application of these terms to instrument approach or takeoff is described below. In addition, it should be noted that the term “Primary Means of Navigation” may apply to either instrument approach initial, intermediate final approach, or missed approach courses of procedures flown to Category I or Category II minima. The term Supplemental Means of Navigation can typically apply to initial or intermediate segments or Missed approach segments, but typically does not apply to flying a final approach course of an instrument procedure. For definitions of Category I or Category II as used by the U.S. and ICAO, see Appendix 1.
a. Primary Means of Navigation. A “Primary Means” of navigation is a means of navigation that satisfies each of the necessary levels of accuracy and integrity for a particular area, route, procedure or operation. The failure of a “Primary Means” of navigation may result in, or require reversion to a “non-normal” means of navigation or alternate level of RNP.
(1) “Availability” as relates to a primary means of navigation is typically addressed in conjunction with the applicable operating rules for use of the system, in the context of the area, airspace, route, procedures, or operations for which system use is intended (e.g., use of multiple versus single sensors or systems, or NAVAID signal access, reliability, or continuity of service as might apply to a particular approach path).
(2) As applicable to instrument approach operations for an air carrier, particularly for a final approach segment or a missed approach segment, the following may be considered to satisfy requirements for a primary means of navigation.
(3) For sensor specific approaches (e.g., VOR, or NDB, or ILS) each particular airborne system using its respective associated NAVAID (e.g., ILS) may be considered as the “primary means of navigation” for completion of that respective specified approach procedure (e.g., ILS RWY 16R).
(4) When multiple components are required (e.g., ILS, with use of an NDB for the missed approach), the collective set of specified navigation components are considered to be the primary means of navigation for that procedure. Failure of any one of the required components may preclude use of the procedure, or may require reversion to a non-normal means of navigation for completion of the procedure (e.g., failure of the NDB missed approach NAVAID associated with an ILS approach).
(5) For RNAV based procedures where the only method of flying the procedure is by an RNAV or RNAV/RNP system (e.g., FMS), RNAV is considered to be the primary means of navigation for that approach procedure. Any associated NAVAID, or combinations of NAVAIDs, or airborne sensors necessary to achieve the necessary level of FMS performance may be considered as an input sensor(s) to the FMS, but the sensors or NAVAIDs taken alone are not necessarily considered to be the primary means of navigation.
(6) Where RNAV systems are used to overfly other types of instrument approach procedures (e.g., FMS RNAV systems over-flying VOR or NDB procedures), the RNAV system may be considered as a supplemental system if the aircraft can revert to use of the underlying procedure flown with “raw data,” in the event of failure of the RNAV system (see b. below).
b. Supplementary Means of Navigation. A “Supplementary Means” of navigation is a means of navigation which satisfies one or more, but not necessarily all of the necessary levels of accuracy, integrity, and availability for a particular area, route, procedure, or operation. The failure of a “Supplementary Means” of navigation may result in, or require reversion to another alternate “normal” means of navigation for the intended route, procedure, or operation.
(1) As applicable to instrument approach operations for an air carrier, particularly for a final approach segment or a missed approach segment, the following may be considered to satisfy requirements as a supplementary means of navigation.
(2) When procedures have multiple methods to achieve compliance (e.g., a multi-sensor FMS over-flying a VOR approach, or an ILS approach with the choice of either an NDB or a VOR-based missed approach), those airborne systems which have another alternate normal means to accomplish the procedure, or a portion of the procedure, for one or more applicable segments, may be considered as supplementary for those applicable segments (e.g., if the FMS should fail, and the crew is monitoring the underlying VOR information, and the crew can transition to use of VOR-based navigation) the FMS may be considered as supplementary.
(3) Or, if, after an ILS approach, FMS RNAV capability is used to overfly a VOR/DME-based missed approach (with VOR/ DME NAVAID facilities operating), the FMS RNAV capability may be considered supplementary. Note, however, that if the specified approach/missed approach VOR/DME NAVAIDs are not operative, and the FMS RNAV operation is based on use of multi-sensor NAVAID capability, then the FMS use for that approach/missed approach would typically be considered a primary means of navigation.
c. Required Navigation Performance (RNP). Required Navigation Performance is a statement of the navigation performance necessary for operation within a defined airspace (Adapted from ICAO - IS&RP Annex 6). Required Navigation Performance is specified in terms of accuracy, integrity, and availability of navigation signals and equipment for a particular airspace, route, procedure, or operation.
4.3.1.3. Use of ICAO Standard NAVAIDs. U.S. Category I or Category II Operations are based on use of ICAO standard NAVAIDs, equivalent NAVAIDs, or other NAVAIDs acceptable to FAA and approved in OpSpecs. Authorization for use of NAVAIDs other than ICAO Standard NAVAIDs must be coordinated with AFS-400.
In the context of this AC, a Standard Landing Aid (SLA) is considered to be any navigation service or navigation aid provided by a State which meets internationally accepted performance standards (e.g., ICAO Standards and Recommended Practices (SARPs), or equivalent U.S. or other State standards - see Appendix 1).
4.3.1.4. Standard Instrument Approach Procedures (SIAPS).
a. Acceptable Instrument Approach Procedure Basis. Instrument approach procedures used by Operators IAW with this AC should be based on:
(1) U.S. Standard Instrument Approach Procedures;
(2) For non-U.S. airports, foreign instrument approach procedures acceptable to FAA promulgated by the state of the airport of landing (i.e., ICAO - State of the Aerodrome). The operator may propose use of such procedures for Principal Operations Inspector (POI), Aircrew Program Manager (APM), or Certificate Management Office (CMO) acceptance;
(3) Military instrument procedures acceptable to FAA for operations at military facilities. The operator may propose use of such procedures for POI, APM, or CMO acceptance;
(4) Special instrument approach procedures approved by the FAA;
(5) Special instrument approach procedures developed by the operator which are acceptable to FAA, or procedures developed by the operator using methods acceptable to FAA; or
(6) Special instrument approach procedures, acceptable to FAA, developed by other U.S. or non-U.S. Operators, or by the State of the Aerodrome (for foreign airports).
b. Considerations for use of procedures other than U.S. Standard procedures. For procedures other than those developed IAW FAA Order 8260.3, United States Standards for Terminal Instrument Procedures (TERPS), the operator must ensure consideration of at least the following factors related to use of those instrument procedures:
(1) Availability of suitable weather reporting and forecasts;
(2) Identification of any necessary alternate airports or alternate minima;
(3) Ability to discontinue an approach, if necessary, from any point to touchdown;
(4) Suitability of the airborne equipment to use the procedure (e.g., compatibility of the airborne equipment with the type/characteristics of the ILS, VOR, DME, NDB ground facilities used);
(5) Suitability of Ground Systems/Equipment (e.g., lighting, transmissometers, pilot control of lighting);
(6) Suitability of NAVAIDs (e.g., maintenance, monitoring);
(7) Suitability of Airport/Runway (e.g., obstructions, clear zones, markings);
(8) Availability of Aeronautical Information (e.g., timely NOTAM availability);
(9) Identification of any special Training or qualification related to the procedure; and
(10) Resolution of any issues identified from adverse “service experience” with the procedure.
c. Special Instrument Approach Procedures. Special instrument approach procedures should be coordinated with the Flight Standards Division of the FAA region having responsibility for the airport of the procedure. Special procedures should address any provisions associated with application of section 121.445 for special airport qualification. Special procedures are approved by AFS-400 and issued by the POI after coordination with pertinent FAA organizations.
d. Use of FAA/JAA Harmonized Instrument Approach Minima Tables. Information from FAA/JAA harmonized instrument approach minima tables are provided in Appendix 8. Unless otherwise authorized by AFS-400, procedures incorporating these minima are issued as special instrument procedures through OpSpecs, or through a Letter of Authorization (LOA). Minima based on values provided in Appendix 8 should not be below the lowest minima authorized through a Category I Standard OpSpec authorization, or below any applicable published foreign aerodrome minima when operating outside the United States (see Paragraph 6.2.18 and Appendix 8).
4.3.1.5. “Steep Approaches” and Approach Path Descent Angle Constraints. Approach path angles between 2.75 degrees and 3.77 degrees are considered standard for air carrier operations. Approach angles above 3.77 degrees are considered “steep angle” and, if authorized, may require additional assessment. Air carrier use of approach angles over 3.77 degrees requires coordination with AFS-400. Use of approach angles over 4.5 degrees should normally be based on an associated aircraft type AFM provision for “steep angle approaches,” IAW AC 25-7A, Flight Test Guide for Certification of Transport Category Airplanes, or equivalent, and paragraph 6.8 of Appendix 2.
4.3.1.6. “Normal Maneuvering” Considerations. Part 91, section 91.175 requires that approach procedures should be based on use of “normal maneuvers” before and after passing DA(H) or MDA(H). Normal maneuvers typically do not involve use of bank angles greater than 30 degrees, pitch attitudes in excess of 25 degrees nose up or 10 degrees nose down, or sink rates in excess of 1100 ft. per minute below 500 ft. HAT while maneuvering to land within the touchdown zone, during go-around, or during a rejected landing. During a missed approach, pitch attitudes in excess of +30 degrees or bank angles greater than 30 degrees would typically be considered excessive.
4.3.1.7. Non-Normal Events or Configurations. Takeoff and landing weather minimums are intended for normal operations. When non-normal events occur, flightcrews are expected to take the safest course of action to ensure safe completion of the flight. Using emergency authority, crews may deviate from rules or polices, to the extent necessary for the circumstances, to minimize risk during landing.
Paragraph 6.1.8 addresses guidelines and procedures to be considered in conducting an instrument approach during a non-normal event.
4.3.1.8. Go-Around Safety.
a. General. A multiengine aircraft conducting a Category I or Category II instrument approach should be capable of safely executing a “one-engine-inoperative” go-around from any point in an approach prior to touchdown with the aircraft in a normal configuration, or specified non-normal configurations (e.g., engine out, if applicable). This is necessary to provide for go-around safety due to missed approaches or rejected landings due to a variety of circumstances such as:
• Unexpected environmental conditions (e.g., cross winds, turbulence) • Aircraft related failures (e.g., gear unsafe) • Air Traffic Service contingencies (e.g., RTO on a crossing runway) • Loss of visual reference • When a pilot finds the runway surface unsuitable (e.g., clutter, flocking birds) • When the runway is blocked (airport vehicles or exiting aircraft ahead not clear), or due to a go-around or missed approach due to any other reason
(1) This objective may be achieved by the operator providing information to flightcrews on an appropriate lateral flight path to follow to enable the aircraft to safely operate to the runway, and out from the runway following a rejected landing. In the rare event that operation out of a runway may not be possible following a rejected landing, then provision of suitable information on a “commit point,” or equivalent condition (e.g., limit weight, minimum speed, or suitable configuration) may instead be provided. The intent of providing information on safe go-around capability is to identify the best option or options for a safe lateral ground track and flight path to follow in the event that a missed approach, balked landing, rejected landing or go-around is necessary. It is not the intention of this provision to require or indicate the need for an analysis of each flight, or a dispatch assessment, or an individual
flight landing weight assessment or limitation. Operators may make the judgment as to whether a review on a “perflight” or specific condition basis may or may not be needed.
(2) While coping with the go-around contingency situation is appropriate for any operation, it is particularly important for low visibility operations in which the pilot has minimum time to respond, and may have limited visual reference available to safely cope with the adverse condition (e.g., night and poor visibility). Further, “go-around” safety should be addressed regardless of when an engine failure may occur prior to landing. However, operators may elect to distinguish between procedures or expected crew response for engine failures occurring at various times during a flight as follows:
(a) Engine failure occurring enroute or prior to passing a final approach fix or point,
(b) Engine failure during a final approach segment, or
(c) Engine failure after passing DA(H) or after descending below MDA(H) but prior to touchdown, or during a go-around or missed approach.
(3) For an engine failure occurring prior to final approach, flight diversion planning should allow for the potential need for a missed approach or balked landing, and for the need to maintain subsequent suitable obstacle clearance (e.g., when making suitable diversion choices - sections 121.161, 121.191, or 121.193. The pilot should consider any adjustment to minima, procedures or missed approach path that may be appropriate to facilitate safe obstacle clearance (e.g., following a suitable operator-developed takeoff procedure, published takeoff procedure, or IFR Departure Procedure (DP)). This is particularly appropriate if U.S. TERPS or ICAO PANS-Ops-specified instrument procedural gradients cannot be met during any portion of a go-around or missed approach, or if following a suitable lateral path cannot be ensured (e.g., crosswinds with no course guidance available, cannot maintain VMC, or at night).
(4) For engine failure during approach, if there is any doubt of the ability to safely complete the landing or ensure a safe balked landing and missed approach capability, the pilot should consider the advisability of discontinuing the approach and diverting to a different airport or runway, to better ensure safe missed approach or balked landing obstacle clearance.
(5) For engine failure after passing DA(H) or descending below MDA(H), the pilot should be prepared to expeditiously follow or join any pre-established and applicable “T-procedure” or “IFR Departure Procedure,” or equivalent, until becoming established on a published segment of the missed approach procedure, at or above a safe altitude.
(6) Accordingly, an operator should have reviewed the missed approach and rejected landing flight path to ensure that in the event of a go-around the aircraft is able to ensure safe obstacle clearance following a missed approach or go-around. This can be particularly important in mountainous areas where the landing runway may be in a direction not typically used for takeoff (e.g., an airport that is one way in, and the opposite direction out).
b. Go-Around Assessment Considerations.
(1) Operators may accomplish such assessments generically for a particular runway, procedure, aircraft type, and expected performance, and need not perform this assessment for each specific flight. Operators may use simplifying assumptions to account for the transition, reconfiguration, and acceleration distances following goaround (e.g., use expected landing weights, assume anticipated landing flap settings).
(2) The operational considerations should include:
(a) Go-around configuration transitions from approach to missed approach configuration including expected flap settings and flap retraction procedures.
(b) Expected speed changes.
(c) Appropriate engine failure and shutdown (feathering if applicable) provisions, if the approach was assumed to be initiated with all engines operative.
(d) Any lateral differences of the missed approach flight path from the corresponding takeoff flight path, and
(e) Suitable balked landing obstacle clearance, until reaching instrument approach missed approach or enroute procedurally protected airspace.
(f) Any performance or gradient loss during turning flight, if necessary to follow a flight path that is not over the runway or is not aligned with the runway after the balked landing transition.
(g) Any relevant related situations such as if the aircraft cannot dump fuel and may need to make an emergency return landing above maximum landing weight immediately after takeoff.
(h) Methods used for takeoff analysis, such as “Overspeed V2”, “engine-out maximum angle climb,” or other such techniques may be used if determined to be appropriate by the operator or aircraft manufacturer.
(i) Applicable flight guidance system operational procedures used. Information about any techniques required to achieve the specified performance should be available to the flightcrew (e.g., appropriate mode selection).
(j) Operators may make obstacle clearance assumptions similar to those applied to corresponding takeoff flight paths (e.g., Section 121.189) in the determination of net vertical flight path clearance or lateral track definition or lateral track obstacle clearance within an airport boundary or beyond an airport boundary, until the point at which cruise or other obstacle clearance requirements apply.
c. Go-Around Assessment Conditions.
(1) Assessments may assume the following initial conditions:
(a) A “balked landing” starts at the end of the Touchdown Zone (TDZ).
(b) An engine failure occurs at the initiation of the balked landing, from an all-engine configuration.
(c) Balked landing initiation speed > VREF or VGA (as applicable).
(d) Balked Landing initiation height is equal to the specified elevation of the TDZ.
(e) Balked landing initiation configuration is normal landing flaps, gear down.
(f) At the initiation of the maneuver, all engines are at least in a spooled configuration.
(2) A TDZ typically is considered to be the first 3000 ft. of a designated landing runway. When appropriate for the purposes of this provision, Operators may propose to use a different designation for a touchdown zone. For example, alternate consideration of a TDZ may be appropriate for runways that:
(a) Are less than 6000 ft. in length and which do not have standard TDZ markings;
(b) Short runways requiring special aircraft performance information or procedures for landing;
(c) Runways for STOL aircraft; or
(d) Runway where markings or lighting dictate that a different TDZ designation would be more appropriate.
d. “One Way” Airports, “Commit Point,” or Other Special Situations.
(1) Where obstacle clearance is determined by the operator to be critical such as for:
(a) “One-way in,” “opposite way out” airports in mountainous terrain, or
(b) Runways at which a landing is to be planned or attempted, but at a weight which is significantly greater than that which would otherwise be allowed for a takeoff, or
(c) Where rejected landing obstacle clearance may not be readily ensured, a review should be completed by the operator to determine whether a contingency go-around path can be appropriately defined or whether a “commit point” or equivalent condition is necessary (e.g., limit weight, speed, or configuration).
(2) A “commit point” or equivalent condition however, should only be used where it is not otherwise possible to identify a safe go-around path. For a “commit point,” the operator should either provide a representative weight, configuration or condition at which obstacle clearance can be ensured after initiation of a balked landing at the TDZ, or identify a path related waypoint, location, altitude, height, or fix, beyond which a go-around should not be attempted. For such determinations, the operator should consider at least the runway elevation, temperature, and appropriate aircraft configurations or configuration changes. If a “commit point” is used, the operator should provide any necessary advisory information to flightcrews to address any events which, while unlikely, could nonetheless occur beyond the designated “commit” point or condition (e.g., unforeseen significant wind shear, unacceptable winds, turbulence, or runway clutter, loss of visual reference, flare extending beyond the touchdown zone, or an obstruction on the runway).
e. TERPS/ICAO PANS-Ops Criteria Not Applicable to “Non-Normal” Operations. TERPS or ICAO PANS-Ops- based criteria do not typically address “special” instrument approach procedures, and they do not and are not intended to address non-normal operations (engine inoperative) or operations below published segments of instrument procedures (e.g., operations below DA(H) or MDA(H)). TERPS or ICAO PANS-Ops based criteria are intended only to address “standard procedures”, normal operations (e.g., all-engine), and published segments of the resulting procedures. Thus, operator assessments of missed approach safety related to operations below published segments of instrument procedures, or operations with non-normal configurations or situations, need not apply provisions of TERPS or ICAO PANS-Ops. Compliance with TERPS or ICAO PANS-Ops based instrument procedure requirements alone may not necessarily ensure missed approach or rejected landing go-around safety. For example, it is recognized that certain types of aircraft (e.g., two-engine aircraft) may operate at weights that achieve gradients with an engine inoperative that may be less than TERPS or PANS-Ops gradients. Go-around from below DA(H) or MDA(H) (e.g., following loss of visual reference, or runway not suitable or available) does not necessarily provide for and does not need to apply TERPS or PANS-Ops criteria or provide for TERPS or PANS-Ops specified levels of obstacle clearance vertically or laterally. Methods related to TERPS or PANS-Ops criteria such as “Collision risk model (CRM)” also are not applicable to assessments other than for TERPS and PANS-Ops related procedure elements.
f. Flight Guidance System (FGS) Use. If not already assessed for the aircraft type during basic type certification, or STC, flight guidance systems (FGS) suitability for the intended procedure(s) should be considered. The operator may need to assess FGS mode use to ensure compatibility with intended flight path, mode transitions, and gradient determinations. This may be achieved by demonstrating (in simulation or flight) a safe go-around from 100 ft. above the TDZ (HAT) operationally for the specific procedure or, if applicable, for the most critical runway for that operator. For aircraft that have airworthiness demonstrations conducted IAW Appendix 2 or 3 or with AC 120-28D this provision is considered to be addressed.
g. Performance and Obstacle Data Availability and Use.
(1) Information or methods used by the operator for this assessment may be the best available information or methods from applicable aircraft manuals, terrain or obstruction charts, or supplementary information from aircraft or engine manufacturers. In the event that performance, obstacle, or flight path data are not otherwise available to support the necessary analysis from the above sources, the operator may develop, compute, demonstrate,
or determine such information to the extent necessary to provide for safe obstacle clearance during an engine-out missed approach or an engine-failure following a rejected landing. Data or methods used need not necessarily be from the applicable AFM or from the original aircraft manufacturer. Data or methods may be developed by the operator based on equivalence to other data or methods (e.g., takeoff data) or may be derived by using standard practices applicable to aircraft performance assessment or procedure construction, or may be derived by appropriate aircraft performance or engineering analysis, techniques, or methods.
(2) Information on terrain or obstructions for these assessments may be based on the best available information to the operator or to the agency or entity supporting the operator at the time the information is supplied (e.g., data available to a performance information contractor, or chart supplier). Best available information may be used, notwithstanding that certain information or data may not necessarily be “approved” by an authority, or may be data that is not necessarily recent (e.g., certain types of charting or obstruction information is not frequently updated). FAA Order 8260.19, paragraph 271 describes how the accuracy of the source data should be considered when constructing the procedure.
h. Related Information. Other paragraphs of this AC contain information related to this paragraph. Paragraph 5.14 describes typical factors to be considered when assessing go-around capability for a particular aircraft and flight guidance system. Paragraph 6 addresses procedures including those used for go-around or rejected landing, and Paragraph 7 addresses Training and Crew Qualification including relevant aspects of missed approach, go-around, or rejected landing.
4.3.2. ILS, GLS, or MLS (xLS) Instrument Approach Operations. ILS, GLS, or MLS (i.e., xLS) operations may be authorized to the lowest applicable DA(H) for the procedure used, and to the lowest visibility minima specified in the OpSpecs for the NAVAID, facilities, and lighting systems used (see Appendix 7, Standard OpSpecs Part C Paragraph C053 for Category I, and Standard OpSpecs Part C paragraph C059 for Category II).
a. ILS, GLS, or MLS (e.g., xLS) operations are typically authorized based on use of two or more navigation receivers or multi-mode receivers (MMRs) of a pertinent type (see 14 CFR, part 121, section 121.349, and part 125 section 125.203), each providing independent information to the appropriate flight guidance system elements and pilot displays.
b. Provisions of sections 121.349, and 125.203 applicable to ILS may also be considered as applicable to GLS or MLS.
c. Provisions of section 121.349 for use of a single navigation (e.g., ILS) receiver are typically limited to operations using minima at or above RVR4000, or for Minimum Equipment List (MEL) authorization for dispatch with a NAVAID receiver inoperative.
d. Precision Approach Radar (PAR) procedures are not considered xLS procedures( see paragraph 4.3.3).
4.3.3. Instrument Approaches other than ILS, GLS, or MLS (xLS). Instrument approach procedures other than ILS, GLS, or MLS (xLS) that may be authorized for air carriers include the procedure types shown in the following paragraphs.
a. Standard Instrument Procedures Other Than xLS. The following NAVAID specific instrument procedures are considered to be standard procedures for the purpose of air carrier operation specification approval. Typically these procedures do not inherently specify use of vertical guidance (i.e., most were traditionally considered as non-precision approaches).
(1) Some of these approach types may provide vertical guidance (e.g., a glideslope), however, the procedure may be offset from the runway, may not otherwise permit a straight in landing in the touchdown zone when flying the specified path, or may not have flight deck display of path information. Hence the approach is not considered to be an xLS approach.
(2) Approvable standard approach types other than xLS are considered to include:
• Localizer (LOC)
• Localizer Back Course (BC)
• SDF
• LDA
• VOR
• VOR/DME
• NDB
• Dual NDB
• NDB/DME
• TACAN, and
• RNAV (2D)* based on a procedurally specified NAVAID (e.g., typically when a particular VOR/DME is specified as a “Procedure tuned” facility to serve as a basis for a particular RNAV procedure - These RNAV procedures usually are those which meet U.S. TERPS Chapter 15 criteria for RNAV).
b. Standard Procedures Flown Using Vertical Navigation Path Guidance (VNAV). The procedures specified in paragraph a. above may also be flown in conjunction with use of FMS derived vertical guidance (e.g., FMS VNAV capability). In this instance, VNAV capability is considered to be based on a pre-specified and defined vertical path.
c. Standard Procedures Flown Using “Constant Vertical Descent Rate” Techniques. NAVAID specific procedures other than xLS may be flown using “Constant Vertical Descent Rate” Techniques as a “pilot procedural technique” to maintain a pre-determined vertical speed to achieve a corresponding assumed descent path (e.g., “open-loop” vertical speed descent profile). Operators may use these techniques, particularly when xLS or VNAV path guidance is not available or cannot otherwise be used. However, such “Constant Vertical Descent Rate” techniques are not considered to be “VNAV vertical guidance”. This is true regardless of whether such a procedure or technique is based on an altitude/distance cross check or not. While use of such techniques may be desirable for aircraft that are not using xLS or VNAV, they are not considered to be eligible for DA(H) use or credit.
d. “RNAV” Procedures (3D or 2D)* Based On RNP. Operators may use RNAV procedures based on RNP criteria that are found to be acceptable to FAA. Those RNAV procedures may use minima based on RNP criteria, or may use RNP for definition of some or all procedure segments (e.g., initial, intermediate, final, or missed approach segments).
e. Other “RNAV” Procedures (3D or 2D)*.
(1) When determined acceptable to FAA, Operators may also use RNAV Procedures (3D or 2D)* other than those based on criteria specified in U.S. TERPS Chapter 15 for RNAV (e.g., RNAV procedures as listed in paragraph a. above), or other than procedures based on RNP (RNAV procedures as listed in paragraph d. above), as follows:
• RNAV procedures identified as “GPS” instrument approach procedures, if those procedures are determined to be suitable for the aircraft and navigation system to be used (e.g., use of FMS with GNSS sensor inputs).
• International RNAV procedures, when appropriate for use at non-U.S. airports.
• RNAV procedures based on multi-sensor FMS using inertial systems and NAVAIDs other than specific “procedure-tuned” VOR or DME facilities. For example, RNAV Procedures (3D or 2D)* may be based on multi-sensor FMS systems which use DME-DME updating, or scanning DME updating, or VOR/DME updating, or VOR/VOR updating, from suitable and available NAVAIDs.
• RNAV procedures based on multi-sensor FMS using inertial systems and GNSS, or GNSS with Ground Based Augmentation System (GBAS), or Space Based Augmentation System (SBAS)).
(2) RNAV procedures may also be based on combinations of sensors if equivalent performance, availability, and integrity are established compared with any of the above methods.
*NOTE: For the purpose of this AC a “3D” approach procedure (3D) is considered to be one having both lateral and vertical path guidance (e.g., three dimensions - with x, y, and z path coordinates). These procedures may be identified as LNAV/VNAV. A “2D” procedure (2D) is considered to be one having only lateral path guidance (two dimensions - x and y path coordinates). These procedures may be identified as LNAV.
f. Airport Surveillance Radar (ASR) Procedures. ASR or international equivalent procedures may be used.
g. Precision Approach Radar (PAR) Procedures. PAR or international equivalent procedures may be used.
h. Other Limited Use Special Procedures. Other special instrument approach procedures (e.g., LORAN, Transponder Landing System (TLS), airborne radar approach, Eastern European KRM). Special procedures include use of LORAN C, airborne radar, or any other landing system or non-ICAO NAVAID. Special procedures typically require unique approval of an operator’s operational procedures, flightcrew qualification, and maintenance programs as well as proof of concept demonstration prior to operational authorization. Special Category I operations, by definition, require the use of airborne and/or ground based or satellite-based equipment over and above the minimum equipment necessary to operate in the U.S. national airspace. Special Category I operations usually also require special knowledge, skills, proficiency, and procedures. As a result, changes and amendments to the operator’s overall Category I operations program are usually necessary to ensure safe conduct of these operations. There is additional criteria which must be incorporated into an operator’s program for special Category I operations.
4.3.4. Applicability of a DA(H), MDA(H), or RA. Instrument approach and landing operations have limitations related to the minimum altitude (height) to which descent can be made without establishing visual reference (e.g., 14 CFR part 91, section 91.175). Minimum altitude or height to which descent can be made is typically related to assurance of clearance over terrain or obstacles, airborne instrumentation and equipment, NAVAIDs, and visual aids. Such a minimum altitude or height is usually specified as a DA(H), or MDA(H). A DA(H) may be intended for use as either a Decision Altitude (DA), or as a Decision Height (DH). A DH may be used directly, or it may be specified as a corresponding radio altitude (RA) value above underlying approach terrain. The type of instrument approach procedure determines whether a DA or DH is used, and whether a DH is specified directly, or is defined in terms of a corresponding radio altitude (RA) value above terrain. For a Category I procedure, a DA is typically used. For a Category II procedure, a DH with a corresponding radio altimeter (RA) height above approach terrain is usually used. When a RA value above approach terrain is specified, it typically corresponds to a particular desired DH value for the intended height above the TDZ (HAT).
Uses of DA(H), MDA(H), and RA are further described in paragraphs 4.3.4.1 through
a. DA, DH, RA, OCA, OCH, OCL. For xLS approaches (e.g., precision approaches), and certain RNAV approaches with VNAV, the minimum altitude or height for flight without having established the necessary visual reference during an approach is specified as a DA(H). For Category I within the U.S., the DA element of a DA(H) usually defines the applicable minima. For Category II, applicable minima are usually based on a DH, expressed in the published procedure as an RA value. In other countries, for Category I, either a DA or a DH may be used. For Category II outside the U.S., minima may be based either on a direct specification of DH, or on a corresponding RA value, as is done within the U.S. Other expressions of minima equivalent to a decision altitude (DA) or decision
height (DH) may also be encountered outside of the U.S., such as when an obstacle clearance altitude (OCA), obstacle clearance height (OCH), or obstacle clearance limit (OCL) is specified, and is to be treated as a corresponding DA or DH.
(1) In the United States and other countries that use U.S. TERPS criteria, the minimum instrument flight altitude for xLS approaches is considered to be the DA element of the DA(H) if minima are based on a barometric altimeter, or the (H) value of the DA(H) expressed as an RA minima, if minima are based on use of a radio altimeter. When a DH applies, it is usually specified as an RA value above the pertinent underlying approach terrain, considering a nominal approach vertical path. When a barometric altimeter specified DA is used to establish minima, the associated height value (H) is typically considered to be advisory. When a DH specified in terms of a radio altitude (RA) value is used, the corresponding published RA value is considered to be controlling, and any associated barometric altitude value shown in a procedure is typically considered to be advisory.
(2) For procedures with minima based on a DA, the DA is specified as a decision altitude referenced to mean sea level (MSL) using QNH altimeter settings. While the (H) element of the DA(H) is typically advisory for such procedures, in certain circumstances the (H) value may be the basis for minima, such as when a QFE referenced barometric altimeter setting is used.
(3) Obstacle Clearance Height (OCH) and Obstacle Clearance Limit (OCL) are used in some countries IAW various versions or revision levels of ICAO PANS-OPS. OCA, where used, is referenced to a barometric altitude (MSL). OCH and OCL are referenced to height above either the elevation of the airport, the elevation of the touchdown zone, or the elevation of the landing threshold.
b. Minimum Descent Altitude (MDA), Minimum Descent Height (MDH), HAT, Height Above Airport (HAA), Obstacle Clearance Altitude (OCA), OCH, OCL.
(1) For approaches other than xLS, the minimum height or altitude may be specified as a decision altitude DA or a DA(H) if suitable vertical guidance is authorized and provided (e.g., VNAV path), or specified as a minimum descent altitude MDA of an MDA(H) if vertical guidance is not provided. Minima may also be specified height above touchdown (HAT), height above airport (HAA), minimum descent height (MDH), obstacle clearance altitude (OCA), obstacle clearance height (OCH), or obstacle clearance limit (OCL). MDA, HAT, and HAA are typically used by certain countries that use various earlier versions of U.S. TERPS criteria. OCA, OCH, and OCL are used in countries having procedures established IAW ICAO PANS-OPS. Although ICAO PANS-OPS now does not use OCL, some procedures still use OCL criteria from previous versions of PANS-OPS. Some countries, in addition to OCA and OCH, provide MDA and MDH. MDA and OCA are barometric flight altitudes referenced to mean sea level (MSL). HAT, HAA, MDH, OCH, and OCL are radio or radar altitudes referenced to either the elevation of the airport, the elevation of the touchdown zone, or the elevation of the landing threshold.
(2) Accordingly, for international operations, the following equivalent minima formulations should be used by U.S. Operators:
(a) Use the altitude value of the MDA(H) where OCA may be specified for procedures other than xLS.
(b) Use the equivalent altitude value of the MDA(H) where HAT, OCH, or OCL are specified for “straight-in” approach procedures.
(c) Use the equivalent altitude value of the MDA(H) where HAA, OCH, or OCL may be specified circling approach maneuvers.
c. Lowest Permissible DA(H) or MDA(H). The lowest permissible DA(H) or MDA(H) for instrument flight (IMC) for any approach should not be lower than the most restrictive of the following, as applicable:
• Minimum height or altitude published or otherwise established for the instrument approach
• Minimum height or altitude authorized in OpSpecs for the approach
• Minimum height or altitude authorized for the flightcrew
• Minimum height or altitude authorized for the operator, aircraft, and airborne equipment
• Minimum height or altitude permitted by operative airborne equipment and NAVAIDs
• Minimum height or altitude for which required NAVAIDs can be relied upon*
• Minimum height or altitude which provides adequate obstacle clearance*, and
• Minimum altitude which provides compensation for extremely cold temperatures, if applicable**
* Note: Item normally addressed by the published instrument approach procedure.
** Note: Applicable only when an operator has a procedure to correct altimeter errors for extremely cold temperatures (Typically T less than -22F/-30C).
4.3.4.1. Application of a DA(H) for Category I. Procedures established based on use of NAVAID electronic vertical guidance (e.g., ILS, MLS, or GLS) use the barometrically based DA (of the specified DA(H)) for minima determination. Radio altitude above the approach terrain or touchdown zone, if provided, is advisory.
Procedures established based on use of other acceptable electronic vertical guidance (e.g., Baro VNAV meeting provisions of this AC, GNSS based geometric path VNAV) may use a barometrically based DA (of the specified DA(H)) for minima determination if an appropriate obstacle assessment has been completed for the region between the earliest point along the approach path at which the DA may be reached, to the runway threshold. Radio altitude, if provided, is advisory.
For Category I a decision height (DH) is not used.
DA(H) is applied to Category I instrument approach procedures as follows:
a. Category I ILS, MLS, or GLS (xLS) Approaches.
(1) For Category I approaches based on ILS, MLS, or GLS (e.g., xLS, or precision approaches), a DA(H) is typically specified. The DA(H) represents the minimum altitude in an approach to which descent may continue, or by which a missed approach must be initiated, if the required visual reference to continue the approach has not been established. The DA(H) “altitude” value is typically measured by a barometric altimeter, and is the determining factor for descent minima for an xLS approach procedure. The “height” value specified in parenthesis is typically a radio or radar altitude equivalent height above the TDZ (HAT) used only for advisory reference, and does not necessarily reflect actual height above underlying terrain. Where a Middle Marker (MM) beacon is installed, it may be used as advisory information, confirming a barometrically determined DA(H) that is coincident with the glide slope altitude at that point.
(2) For approaches which normally provide vertical guidance (e.g., xLS), but when vertical guidance capability cannot be used, such as due to an airborne system failure, see paragraph 4.3.4.2 below.
b. Category I Approaches with VNAV. For Category I approaches other than ILS, MLS, or GLS which use a published VNAV descent path to the runway threshold, a DA(H) may be specified instead of an MDA(H). See (a) above for DA(H) applicability.
c. Precision Approach Radar (PAR) procedures. For Category I minima, a DA(H) may be specified for PAR. See paragraph a. above for DA(H) applicability. Category II is not typically applicable to civil aircraft use of PAR (see 4.3.8.g).
4.3.4.2. Application of an MDA(H) for Category I. Procedures that are not based on use of vertical guidance (e.g., VOR, NDB, Back Course ILS) use the barometrically based MDA (of the specified MDA(H)) for minima determination. Radio altitude, if provided, is advisory.
a. Category I Approaches other than ILS, MLS, or GLS. For Category I approach other than ILS, MLS, or GLS (e.g., non-precision approaches), an MDA(H) is typically specified. The MDA(H) represents the minimum altitude in an approach to which descent may continue, until either the required visual reference is established and the aircraft is in a position to continue the descent to land using normal maneuvering, or until reaching the specified missed approach point. The MDA(H) “Altitude” value is typically measured by a barometric altimeter, and is the determining factor for descent minima for approaches other than ILS, MLS, or GLS (other than xLS) Category I instrument approach procedures. The “Height” value specified in parenthesis is typically a radio or radar altitude equivalent height above the touchdown zone (HAT), and is used only for advisory reference. This height value does not necessarily reflect actual height above underlying terrain. Where a VHF marker beacon (e.g., FM) is used, it may indicate a longitudinal position for a step-down fix, if identified in the procedure.
b. Circling Approaches. Many instrument procedures provide for circling approach minima. U.S. criteria require SIAP publication of circling maneuver minima if the inbound course does not meet straight-in alignment criteria, or when a specified descent gradient for a straight-in approach is steeper than a maximum value allowed by instrument procedure design criteria. Sufficient visual references for manually maneuvering the aircraft to a landing must be maintained throughout a circling maneuver. The pilot must keep the aircraft’s position within the established maneuvering area while performing the circling maneuver. The circling MDA(H) or equivalent must be maintained until an aircraft is in a position from which a normal descent can be made to touchdown within the touchdown zone, using normal maneuvers and a safe descent path.
4.3.4.3. Application of a DA(H), or equivalent (i.e., Inner Marker), for Category II. Procedures using Category II minima typically use a radio altimeter and the associated DH (of the specified DA(H)) for minima determination. Barometric altitude is advisory.
a. Procedures that have “Radio Altitude Not Authorized (RA NA)” (for example, due to irregular underlying terrain) typically use the first indication of arrival at the “inner marker” as a means to establish DA(H). However, an operator may elect to use first indication of arrival at either the “inner marker” or the barometric altitude DA, which ever comes first, as the means for minima determination. In the first instance, both radio altitude and barometric altitude are advisory. In the second instance barometric altitude may be an acceptable means to establish DA(H), but only if it occurs before arriving at the “inner marker.” When a procedure specifies “RA NA,” a DA(H) greater than 100 ft. HAT is typically not used, since a marker beacon is not located in a position along the approach path corresponding to that minima.
b. While for Category II the use of barometric decision altitude (DA) is advisory, this does not preclude an operator or flightcrew from initiating a missed approach if the altitude equivalent to the barometric altitude minima (DA) is reached prior to arrival at the specified DH. A barometrically specified “DA” is not currently used for air carrier Category II minima. This applies regardless of whether radio altimeter or inner marker determines the DH.
c. For Category II a Decision Height of a published DA(H) (or an equivalent Inner Marker (IM) for irregular pre-threshold terrain) is used as the applicable descent minima. Any “altitude” value specified is considered to be advisory. The altitude value is available for cross-reference and backup. Use of the barometrically referenced DA element of a published DA(H) is not currently authorized for parts 121, 129, or 135 operations at U.S. facilities. If an operator elects to base discontinuance of an approach on the DA, if the DA is reached prior to the applicable DH, the DA element of a DA(H) may be considered applicable to Category II in other than an advisory capacity.
4.3.4.4. “Specified Visual Reference” Requirements for Category I or Category II.
a. Section 91.175 and Standard OpSpecs specify that for operation below the DA(H) or MDA(H) on an instrument approach, the required visual reference to continue the approach must be established. Unless otherwise
authorized by the CMO (e.g., POI or APM for a particular type) the required visual reference may be considered to be those provisions as listed in section 91.175 items (c) and (d).
b. Circumstances in which the operator may request and the CMO may authorize use of alternative visual reference provisions might be situations such as certain Category I and II minima are based on use of autoland or HUD (see paragraph 10.5.3). In this instance provisions such as those shown in section 91.175 (c) (3) (i) for “red terminating bars” or “red side row bars” may not be necessary or appropriate. This is because these particular approach lighting visual references or configurations may not always be needed when operations are predicated on HUD or autoland use. They may not even be installed or applicable as a part of the approach lighting system for the runway or runways to be specially authorized. Conversely, for operations such as the ones noted above for autoland or HUD, it may be determined by the operator and CMO that continued descent below the DA(H) based solely on visual contact with a VGSI (which may in instances be otherwise permitted by 14 CFR), but without having sight of either the runway, runway lights, touchdown zone lights, centerline lights, or runway markings would not be appropriate. In this instance, the CMO may authorize the operator to define and use alternate visual references or visual reference combinations for Category I and II operations, rather than relying solely on the sighting of a VGSI as a basis for continued descent below a DA(H).
c. Refer to FAA Order 8400.13 for lower Category I operations. Changing the required visual reference requires the use of a Special Procedure and additional authorization.
4.3.5. Visibility and RVR Minima. Visibility minima are as specified in Standard or Special Instrument Approach Procedures approved for use by the operator, or as otherwise listed in standard OpSpecs applicable to that operator for Category I or II landing. Operating minimums may be expressed as meteorological visibility (VIS), runway visual range (RVR), or runway visibility values (RVV).
a. Meteorological Visibility (VIS). Meteorological visibility may be used as reported by the NWS, a source approved by the NWS, by FAA, or a source approved by the FAA.
(1) Outside of the U.S., the FAA may accept meteorological reporting sources for use by a particular operator. Outside the U.S. meteorological visibility determination may vary, and the operator should ensure that the meaning, definition, and significance of any meteorological visibility reported for use in determining minima is understood by that operator’s pilots.
(2) For approval of use of weather sources other than the NWS (e.g., international), Operators should consult their respective CMO, CMU, or POI. FAA FSDOs, CMOs, or CMUs that need assistance in responding to operator inquiries regarding approval of weather sources that are not otherwise already addressed by current directives (e.g., FAA Order 8400.10) should consult AFS-400.
b. Runway Visual Range (RVR). RVR is considered to be an instrumentally derived value measured by transmissometers. RVR is calibrated by reference to runway lights and/or the contrast of objects.
(1) Controlling RVR means the reported values of one or more RVR reporting locations (TDZ, Mid, Rollout, or equivalent international locations) used to determine whether operating minima are or are not met, for the purpose of approach initiation, or in some cases, approach continuation.
(2) All U.S. Category I operating minimums below 1/2 statute mile (RVR2400) and all Category II and III operating minimums are based on RVR.
(3) Where RVR is used, the controlling RVR for Category I minima is touchdown RVR. All other readings are advisory.
(4) For Category II minima, controlling RVR is as specified by OpSpecs.
(5) RVR use has practical limitations that should be familiar to both the operator and pilot. For example, RVR is a value which typically only has meaning for the portions of the runway associated with the RVR report (TDZ, MID, or Rollout). RVR is a value that may vary with runway light step settings (1 through 5). Operators should ensure that pilots are familiar with runway light setting effects on reported RVR. RVR may not be representative of actual visibility along portions of the runway due to the location of the transmissometer baseline and limited length of the baseline, or due to variable conditions of fog, blowing snow, or other obscurations along the runway, or due to obscurations varying rapidly in time (e.g., patchy fog). Additionally, newer RVR systems may have localized performance sensitivity since they do not use a baseline along the runway (e.g., a scatter array may be used for visibility assessment). Thus, pilots and Operators should note that RVR is an instrumentally derived value that has operationally significant limitations and can be greater than or less than the actual visibility available to a pilot at typical flight deck eye height (ground level) at the runway. This is particularly true at night, if runway lights are not at settings standard for the prevailing conditions, or if unusual daylight conditions are experienced such as when a runway is aligned with a sunrise or sunset condition, in shallow or patchy fog.
(6) Outside of the U.S. some RVR reports may not necessarily be instrumentally derived by transmissometers or scatter meters, and may alternately be made by pilots or other weather observers. Accordingly, Operators should ensure that the meaning, definition, significance, and variability of any non-instrumentally derived value of RVR reported to the pilot for use in determining minima is understood by that operator, and that operator’s pilots.
c. Runway Visibility Values (RVV). RVV minima are now used infrequently, are being phased out, and should be used only where minima cannot otherwise be specified as a meteorological visibility (VIS) or runway visual range (RVR).
4.3.6. Visibility Assessment and RVR Equivalence for Landing.
a. For instrument procedures where minima are expressed in terms of meteorological visibility, but reported visibility available to the flightcrew is specified as an RVR, the tables referenced in standard OpSpecs may be used to establish equivalent meteorological visibility minima. (see Appendix 7, OpSpecs paragraph C051).
b. Conversely, for instrument procedures outside of the United States where minima available to the flightcrew on instrument procedures are expressed only in terms of RVR, but reported visibility available to the flightcrew by ATS or other approved source is specified only as a meteorological visibility and RVR is not reported, the “Visibility-RVR Equivalence” table referenced in standard OpSpecs may be used to establish an equivalent RVR value (see Appendix 7, OpSpec paragraph C051). Use of this provision, however, specifically requires FAA authorization in addition to issuance of paragraph C051, and should be limited by the POI or CMO to only those Operators and locations outside of the U.S. that have a need to use the “visibility-RVR” equivalence table for this type of determination.
4.3.7. General Requirements for Category I Operations and Minima.
4.3.7.1. Category I Definition, Background, Classification, and General Criteria.
a. Category I Definition. Within the United States, a Category I instrument approach is considered to be any instrument approach or approach and landing with a decision altitude (height) not lower than 60m (200 ft) and with either a visibility not less than 1/2 statute mile (800m), or a runway visual range not less than 550m (1800 ft).
b. Background. Originally the term Category I applied only to the difference between basic turbojet ILS minima and use of a 200 foot DH with a commensurate low RVR. Subsequently, the definition and common use of the Category I classification evolved several additional times, and variations in its use developed internationally. For U.S. air carriers, the current Category I definition has been in use since FAA’s standard OpSpecs were revised in the 1980s. Air carriers since that time have been issued these revised OpSpecs, in both domestic and international operations.
(1) This latest adjusted U.S. Category I definition was necessary because previous criteria for instrument approaches relating to “precision” and “non-precision” approach classification was inadequate to address modern air carrier operations. Provisions were not made for numerous levels of navigation system performance capability that are possible and needed by operators. Systems or methods such as FMS, RNAV, VNAV, electronic map displays, multi-sensor filtering, GPS, inertial systems, RNP, and various GPS augmentation schemes such as GBAS or SBAS now make possible significant improvements in instrument approach capability and cannot be suitably addressed by former criteria or classifications. Combinations of the above approach capability also cannot be adequately classified, represented, or used. Former classifications and criteria failed to appropriately consider the linear nature of modern RNAV systems, certain rare-normal and non-normal conditions, and often did not properly relate to necessary supporting airport systems (e.g., lighting, markings) or meteorological reporting capabilities (e.g., RVR). Previous criteria did not recognize that some procedures or systems formerly considered as “non-precision” (RNAV) may actually have superior performance to systems considered as “precision” systems (e.g., FMS can have better performance than ILS at and beyond distances several miles from the runway). With former criteria and classifications, it was not easy to appropriately classify these systems or derive appropriate benefits.
(2) An important consequence of the U.S. definition for Category I is that, for an air carrier, any instrument approach with minima not less than a DA(H) or MDA(H) of 200 HAT, and visibility not less than RVR 1800, is considered to be Category I. This means that VOR, NDB, RNAV, LOC, Back Course LOC and other such approaches, other than ILS or MLS, are also treated as Category I. This is true even though those approach types may have been considered “non-precision.”
(3) This use of Category I is important to consistently apply to certification and authorization criteria for modern systems and procedures. It is also necessary to ensure that Operators or authorities can implement safety and efficiency advances in a timely and effective way, provide effective and uniform training, and provide necessary facilities, meteorological services, and air traffic services.
c. Instrument Approach Classification.
(1) Accordingly, this AC is based on and uses the definition of Category I as provided in 4.3.7.1. a. The AC treats classification of instrument approach procedures as being grouped into any one of three broad classes:
(a) “xLS,”
(b) “RNAV,” and
(c) “Instrument procedures other that xLS, or RNAV” (e.g., traditional or classic procedures such as VOR, NDB, LOC, and ASR).
(2) Procedures identified as “xLS” may apply to ILS, MLS or GLS.
(3) Procedures identified as RNAV include procedures based on use of
• FMS
• RNAV systems using traditional VOR/DME sensors systems, or
• GNSS (GPS) or augmented GNSS systems (e.g., includes SBAS/WAAS)
Continue reading ↓ 120 of 899 passages shown