Radar Vectors
Handbook Current Issued 2017 92 pages Copy saved Nov 20, 2026

FAA-H-8083-16B Ch. 4 Approaches

Official source ↗ Open PDF

Text read by OCR from a scanned file (4 of 92 pages). Check the original, as some words may be misread.

Chapter 4

Chapter 4

Introduction

This chapter discusses general planning and conduct of instrument approaches by pilots operating under Title 14 of the Code of Federal Regulations (14 CFR) Parts 91,121, 125, and 135. The operations specifications (OpSpecs), standard operating procedures (SOPs), and any other FAA- approved documents for each commercial operator are the final authorities for individual authorizations and limitations as they relate to instrument approaches. While coverage of the various authorizations and approach limitations for all operators is beyond the scope of this chapter, an attempt is made to give examples from generic manuals where it is appropriate.

Approaches

Approach Planning

Depending on speed of the aircraft, availability of weather information, and the complexity of the approach procedure or special terrain avoidance procedures for the airport of intended landing, the in-flight planning phase of an instrument approach can begin as far as 100-200 NM from the destination. Some of the approach planning should be accomplished during preflight. In general, there are five steps that most operators incorporate into their flight standards manuals for the in-flight planning phase of an instrument approach:

• Gathering weather information, field conditions, and Notices to Airmen (NOTAMs) for the airport of intended landing.

• Calculation of performance data, approach speeds, and thrust/power settings.

• Flight deck navigation/communication and automation setup.

• Instrument approach procedure (IAP) review and, for flight crews, IAP briefing.

• Operational review and, for flight crews, operational briefing.

Although often modified to suit each individual operator, these five steps form the basic framework for the in-flight planning phase of an instrument approach. The extent of detail that a given operator includes in their SOPs varies from one operator to another; some may designate which pilot performs each of the above actions, the sequence, and the manner in which each action is performed. Others may leave much of the detail up to individual flight crews and only designate which tasks should be performed prior to commencing an approach. Flight crews of all levels, from single-pilot to multi-crewmember Part 91 operators, can benefit from the experience of commercial operators in developing techniques to fly standard instrument approach procedures (SIAPs).

Determining the suitability of a specific IAP can be a very complex task, since there are many factors that can limit the usability of a particular approach. There are several questions that pilots need to answer during preflight planning and prior to commencing an approach. Is the approach procedure authorized for the company, if Part 91, subpart K, 121, 125, or 135? Is the weather appropriate for the approach? Is the aircraft currently at a weight that will allow it the necessary performance for the approach and landing or go around/ missed approach? Is the aircraft properly equipped for the approach? Is the flight crew qualified and current for the approach? Many of these types of issues must be considered during preflight planning and

within the framework of each specific air carrier’s OpSpecs, or Part 91.

Weather Considerations

Weather conditions at the field of intended landing dictate whether flight crews need to plan for an instrument approach and, in many cases, determine which approaches can be used, or if an approach can even be attempted. The gathering of weather information should be one of the first steps taken during the approach-planning phase. Although there are many possible types of weather information, the primary concerns for approach decision-making are windspeed, wind direction, ceiling, visibility, altimeter setting, temperature, and field conditions. It is also a good idea to check NOTAMs at this time, in case there were any changes since preflight planning.

Windspeed and direction are factors because they often limit the type of approach that can be flown at a specific location. This typically is not a factor at airports with multiple precision approaches, but at airports with only a few or one approach procedure, the wrong combination of wind and visibility can make all instrument approaches at an airport unavailable. Pilots must be prepared to execute other available approaches, not just the one that they may have planned for. As an example, consider the available approaches at the Chippewa Valley Regional Airport (KEAU) in Eau Claire, Wisconsin. [Figure 4-1] In the event that the visibility is reported as less than one mile, the only useable approaches for Category C aircraft is the Instrument Landing System (ILS) and Lateral navigation (LNAV)/vertical navigation (VNAV) to Runway 22. This leaves very few options for flight crews if the wind does not favor Runway 22; and, in cases where the wind restricts a landing on that runway altogether, even a circling approach cannot be flown because of the visibility.

Weather Sources

Figure 4-1: picture of page 3Figure 4-1 · page 3
Picture of the page from the copy saved here

Most of the weather information that flight crews receive is issued to them prior to the start of each flight segment, but the weather used for in-flight planning and execution of an instrument approach is normally obtained en route via government sources, company frequency, or Aircraft Communications Addressing and Reporting System (ACARS).

Air carriers and operators certificated under the provisions of Part 119 (Certification: Air Carriers and Commercial Operators) are required to use the aeronautical weather information systems defined in the OpSpecs issued to that certificate holder by the FAA. These systems may use basic FAA/National Weather Service (NWS) weather services, contractor or operator-proprietary weather services, and/

Figure 4-1. Chippewa Regional Airport (KEAU), Eau Claire, Wisconsin.

or Enhanced Weather Information System (EWINS) when approved in the OpSpecs. As an integral part of EWINS approval, the procedures for collecting, producing, and disseminating aeronautical weather information, as well as the crewmember and dispatcher training to support the use of system weather products, must be accepted or approved.

Operators not certificated under the provisions of 14 CFR Part 119 are encouraged to use FAA/NWS products through the Flight Service Stations (FSS). FSS provide pilot weather briefings, en route weather, receive and process instrument flight rule (IFR) and visual flight rule (VFR) flight plans, relay air traffic control (ATC) clearances, and issue NOTAMs. They also provide assistance to lost aircraft and aircraft in emergency situations and conduct VFR search and rescue services.

Direct User Access Terminal System (DUATS), funded by the FAA, allows any pilot to access weather information and file a flight plan via computer. Two contract vendors currently provide information services within the DUATS system, and can be accessed via the Internet at www.duats.com or www.1800wxbrief.com. The current vendors of DUATS II service and the associated phone numbers are listed in Chapter 7 of the Aeronautical Information Manual (AIM).

Flight Information Service—Broadcast (FIS-B) provides certain aviation weather and other aeronautical information to aircraft equipped with an appropriate flight deck display. Reception of FIS-B services can be expected within a ground station coverage volume when line-of-sight geometry is maintained between the aircraft and ground station. National Airspace System (NAS) wide service availability was targeted for 2013 and is currently available within certain regions. FIS-B provides the following textual and graphical aviation weather and aeronautical products free-of-charge. A detailed description of these products can be found in the AIM.

• Aviation Digital Data Services (ADDS) provides the aviation community with text, digital and graphical forecasts, analyses, and observations of aviation related weather variables. ADDS is a joint effort of National Oceanic and Atmospheric Administration’s (NOAA) Earth System Research Laboratory, National Center for Atmospheric Research (NCAR) Research Applications Laboratory (RAL), and the Aviation Weather Center (AWC).

• Hazardous In-flight Weather Advisory Service (HIWAS) is a national program for broadcasting hazardous weather information continuously over selected navigation aids (NAVAIDs). The broadcasts

include advisories such as Airman’s Meteorological Information (AIRMETs), Significant Meteorological Information (SIGMETs), convective SIGMETs, and urgent pilot weather reports (PIREPs/UUA). These broadcasts are only a summary of the information, and pilots should contact an FSS for detailed information.

• Telephone Information Briefing Service (TIBS) is a service prepared and disseminated by Flight Service. It provides continuous telephone recordings of meteorological and aeronautical information. Specifically, TIBS provides area and route briefings, as well as airspace procedures and special announcements, if applicable. It is designed to be a preliminary briefing tool and is not intended to replace a standard briefing from a flight service specialist. The TIBS service is available 24 hours a day and is updated when conditions change, but it can only be accessed by a touch tone phone. The phone numbers for the TIBS service are listed in the Chart Supplement, formerly the Airport/Facility Directory (A/FD). TIBS should also contain, but is not limited to: surface observations, terminal aerodrome forecast (TAFs), and winds/temperatures aloft forecasts.

The suite of available aviation weather product types is expanding with the development of new sensor systems, algorithms, and forecast models. The FAA and NWS, supported by the NCAR and the NOAA Forecast Systems Laboratory (FSL), develop and implement new aviation weather product types through a comprehensive process known as the Aviation Weather Technology Transfer process. This process ensures that user needs and technical and operational readiness requirements are met as experimental product types mature to operational application.

The development of enhanced communications capabilities, most notably the internet, has allowed pilots access to an increasing range of weather service providers and proprietary products. It is not the intent of the FAA to limit operator use of this weather information. However, pilots and operators should be aware that weather services provided by entities other than the FAA, NWS, or their contractors (such as the DUATS and flight information services data link (FISDL) providers) may not meet FAA/ NWS quality control standards.

Broadcast Weather

The most common method used by flight crews to obtain specific in-flight weather information is to use a source that broadcasts weather for the specific airport. Information about ceilings, visibility, wind, temperature, barometric

pressure, and field conditions can be obtained from most types of broadcast weather services. Broadcast weather can be transmitted to the aircraft in radio voice format or digital format, if it is available, via an ACARS system.

Automated Terminal Information Service (ATIS)

Automatic terminal information service (ATIS) is the continuous broadcast of recorded non-control information in selected high activity terminal areas. Its purpose is to improve controller effectiveness and to relieve frequency congestion by automating the repetitive transmission of essential but routine information. The information is continuously broadcast over a discrete very high frequency (VHF) radio frequency or the voice portion of a local NAVAID. ATIS transmissions on a discrete VHF radio frequency are engineered to be receivable to a maximum of 60 NM from the ATIS site and a maximum altitude of 25,000 feet above ground level (AGL). At most locations, ATIS signals may be received on the surface of the airport, but local conditions may limit the maximum ATIS reception distance and/or altitude. Pilots are urged to cooperate in the ATIS program as it relieves frequency congestion on approach control, ground control, and local control frequencies. The CS indicates airports for which ATIS is provided.

ATIS information includes the time of the latest weather sequence, ceiling, visibility, obstructions to visibility, temperature, dew point (if available), wind direction (magnetic), velocity, altimeter, other pertinent remarks, instrument approach and runway in use. The ceiling/sky condition, visibility, and obstructions to vision may be omitted from the ATIS broadcast if the ceiling is above 5,000 feet and the visibility is more than five miles. The departure runway will only be given if different from the landing runway except at locations having a separate ATIS for departure. The broadcast may include the appropriate frequency and instructions for VFR arrivals to make initial contact with approach control. Pilots of aircraft arriving or departing the terminal area can receive the continuous ATIS broadcast at times when flight deck duties are least pressing and listen to as many repeats as desired. ATIS broadcast will be updated upon the receipt of any official hourly and special weather. A new recording will also be made when there is a change in other pertinent data, such as runway change and instrument approach in use.

Automated Weather Observing Programs

Automated weather reporting systems are increasingly being installed at airports. These systems consist of various sensors, a processor, a computer-generated voice subsystem, and a transmitter to broadcast local, minuteby-minute weather data directly to the pilot.

Automated Weather Observing System

The automated weather observing system (AWOS) observations include the prefix “AUTO” to indicate that the data are derived from an automated system. Some AWOS locations are augmented by certified observers who provide weather and obstruction to vision information in the remarks of the report when the reported visibility is less than seven miles. These sites, along with the hours of augmentation, are published in the CS. Augmentation is identified in the observation as “OBSERVER WEATHER.” The AWOS wind speed, direction and gusts, temperature, dew point, and altimeter setting are exactly the same as for manual observations. The AWOS also reports density altitude when it exceeds the field elevation by more than 1,000 feet. The reported visibility is derived from a sensor near the touchdown of the primary instrument runway. The visibility sensor output is converted to a visibility value using a 10-minute harmonic average. The reported sky condition/ ceiling is derived from the ceilometer located next to the visibility sensor. The AWOS algorithm integrates the last 30 minutes of ceilometer data to derive cloud layers and heights. This output may also differ from the observer sky condition in that the AWOS is totally dependent upon the cloud advection over the sensor site.

Automated Surface Observing System (ASOS)/ Automated Weather Sensor System (AWSS)

The automated surface observing system (ASOS)/ automated weather sensor system (AWSS) is the primary surface weather observing system of the United States. The program to install and operate these systems throughout the United States is a joint effort of the NWS, the FAA, and the Department of Defense (DOD). AWSS is a follow-on program that provides identical data as ASOS. ASOS/AWSS is designed to support aviation operations and weather forecast activities. The ASOS/ AWSS provides continuous minute-by-minute observations and performs the basic observing functions necessary to generate a aviation routine weather report (METAR) and other aviation weather information. The information may be transmitted over a discrete VHF radio frequency or the voice portion of a local NAVAID. ASOS/AWSS transmissions on a discrete VHF radio frequency are engineered to be receivable to a maximum of 25 NM from the ASOS/AWSS site and a maximum altitude of 10,000 feet AGL.

At many locations, ASOS/AWSS signals may be received on the surface of the airport, but local conditions may limit the maximum reception distance and/or altitude. While the automated system and the human may differ in their methods of data collection and interpretation, both produce an observation quite similar in form and

content. For the objective elements, such as pressure, ambient temperature, dew point temperature, wind, and precipitation accumulation, both the automated system and the observer use a fixed location and time-averaging technique. The quantitative differences between the observer and the automated observation of these elements are negligible. For the subjective elements; however, observers use a fixed time (spatial averaging technique) to describe the visual elements (sky condition, visibility, and present weather, etc.), while the automated systems use a fixed location and time averaging technique. Although this is a fundamental change, the manual and automated techniques yield remarkably similar results within the limits of their respective capabilities.

The use of the aforementioned visibility reports and weather services are not limited for Part 91 operators. Part 121 and 135 operators are bound by their individual OpSpecs documents and are required to use weather reports that come from the NWS or other approved sources. While all OpSpecs are individually tailored, most operators are required to use ATIS information, runway visual range (RVR) reports, and selected reports from automated weather stations. All reports coming from an AWOS-3 station are usable for Part 121 and 135 operators. Each type of automated station has different levels of approval as outlined in individual OpSpecs. Ceiling and visibility reports given by the tower with the departure information are always considered official weather, and RVR reports are typically the controlling visibility reference. Refer to Chapter 1, Departures, of this manual, as well as the AIM section 7-1-12 for further description of automated weather systems.

Center Weather Advisories (CWA)

Center weather advisories (CWAs) are unscheduled inflight, flow control, air traffic, and aircrew advisories. By nature of its short lead time, the CWA is not a flight planning product. It is generally a nowcast for conditions beginning in the next two hours. CWAs will be issued:

1. As a supplement to an existing SIGMET, convective SIGMET, or AIRMET.

2. When an in-flight advisory has not been issued but observed or expected weather conditions meet SIGMET/AIRMET criteria based on current pilot reports and reinforced by other sources of information about existing meteorological conditions.

3. When observed or developing weather conditions do not meet SIGMET, convective SIGMET, or AIRMET criteria (e.g., in terms of intensity or area coverage), but current pilot reports or other

weather information sources indicate that existing or anticipated meteorological phenomena will adversely affect the safe and efficient flow of air traffic within the ARTCC area of responsibility.

Weather Regulatory Requirements

There are many practical reasons for reviewing weather information prior to initiating an instrument approach. Pilots must familiarize themselves with the condition of individual airports and runways so that they may make informed decisions regarding fuel management, diversions, and alternate planning. Because this information is critical, 14 CFR requires pilots to comply with specific weather minimums for planning and execution of instrument flights and approaches..

Weather Requirements and Part 91 Operators

According to 14 CFR Part 91, § 91.103, the pilot in command (PIC) must become familiar with all available information concerning a flight prior to departure. Included in this directive is the fundamental basis for pilots to review NOTAMs and pertinent weather reports and forecasts for the intended route of flight. This review should include current weather reports and terminal forecasts for all intended points of landing and alternate airports. In addition, a thorough review of an airport’s current weather conditions should always be conducted prior to initiating an instrument approach. Pilots should also consider weather information as a planning tool for fuel management.

For flight planning purposes, weather information must be reviewed in order to determine the necessity and suitability of alternate airports. For Part 91 operations, the 600-2 and 800-2 rule applies to airports with precision and nonprecision approaches, respectively. Approaches with vertical guidance (APV) are non-precision approaches because they do not meet the International Civil Aviation Organization (ICAO) Annex 10 standards for a precision approach. (See Final Approach Segment section later in this chapter for more information regarding APV approaches.) Exceptions to the 600-2 and 800-2 alternate minimums are listed in the front of the Aeronautical Information Services in the Terminal Procedures Publication (TPP) and are indicated by a symbol A on the approach charts for the airport. This does not preclude flight crews from initiating instrument approaches at alternate airports when the weather conditions are below these minimums. The 600­ 2 and 800-2 rules, or any exceptions, only apply to flight planning purposes, while published landing minimums apply to the actual approach at the alternate.

Weather Requirements and Part 135 Operators

Unlike Part 91 operators, Part 135 operators may not depart for a destination unless the forecast weather there will allow an instrument approach and landing. According to 14 CFR Part 135, § 135.219, flight crews and dispatchers may only designate an airport as a destination if the latest weather reports or forecasts, or any combination of them, indicate that the weather conditions will be at or above IFR landing minimums at the estimated time of arrival (ETA). This ensures that Part 135 flight crews consider weather forecasts when determining the suitability of destinations. Departures for airports can be made when the forecast weather shows the airport will be at or above IFR minimums at the ETA, even if current conditions indicate the airport to be below minimums. Conversely, 14 CFR Part 135, § 135.219 prevents departures when the first airport of intended landing is currently above IFR landing minimums, but the forecast weather is below those minimums at the ETA.

Another very important difference between Part 91 and Part 135 operations is the Part 135 requirement for airports of intended landing to meet specific weather criteria once the flight has been initiated. For Part 135, not only is the weather required to be forecast at or above instrument flight rules (IFR) landing minimums for planning a departure, but it also must be above minimums for initiation of an instrument approach and, once the approach is initiated, to begin the final approach segment of an approach. 14 CFR Part 135, § 135.225 states that pilots may not begin an instrument approach unless the latest weather report indicates that the weather conditions are at or above the authorized IFR landing minimums for that procedure. 14 CFR Part 135, § 135.225 provides relief from this rule if the aircraft has already passed the final approach fix (FAF) when the weather report is received. It should be noted that the controlling factor for determining whether or not the aircraft can proceed is reported visibility. RVR, if available, is the controlling visibility report for determining that the requirements of this section are met. The runway visibility value (RVV), reported in statute miles (SM), takes precedent over prevailing visibility. There is no required timeframe for receiving current weather prior to initiating the approach.

Weather Requirements and Part 121 Operators

Like Part 135 operators, flight crews and dispatchers operating under Part 121 must ensure that the appropriate weather reports or forecasts, or any combination thereof, indicate that the weather will be at or above the authorized minimums at the ETA at the airport to which the flight is dispatched (14 CFR Part 121, § 121.613). This regulation attempts to ensure that flight crews will always be able to

execute an instrument approach at the destination airport. Of course, weather forecasts are occasionally inaccurate; therefore, a thorough review of current weather is required prior to conducting an approach. Like Part 135 operators, Part 121 operators are restricted from proceeding past the FAF of an instrument approach unless the appropriate IFR landing minimums exist for the procedure. In addition, descent below the minimum descent altitude (MDA), decision altitude (DA), or decision height (DH) is governed, with one exception, by the same rules that apply to Part 91 operators. The exception is that during Part 121 and 135 operations, the airplane is also required to land within the touchdown zone (TDZ). Refer to the section titled Minimum Descent Altitude, Decision Altitude, and Decision Height later in this chapter for more information regarding MDA, DA, and DH.

Aircraft Performance Considerations

All operators are required to comply with specific airplane performance limitations that govern approach and landing. Many of these requirements must be considered prior to the origination of flight. The primary goal of these performance considerations is to ensure that the aircraft can remain clear of obstructions throughout the approach, landing, and goaround phase of flight, as well as land within the distance required by the FAA. Although the majority of in-depth performance planning for an instrument flight is normally done prior to the aircraft’s departure, a general review of performance considerations is usually conducted prior to commencing an instrument approach.

Aircraft Performance Operating Limitations Generally speaking, air carriers must have in place an approved method of complying with Subpart I of 14 CFR Parts 121 and 135 (Airplane Performance Operating Limitations), thereby proving the airplane’s performance capability for every flight that it intends to make. Flight crews must have an approved method of complying with the approach and landing performance criteria in the applicable regulations prior to departing for their intended destination. The primary source of information for performance calculations for all operators, including Part 91, is the approved Aircraft Flight Manual (AFM) or Pilot’s Operating Handbook (POH) for the make and model of aircraft that is being operated. It is required to contain the manufacturer determined performance capabilities of the aircraft at each weight, altitude, and ambient temperature that are within the airplane’s listed limitations. Typically, the AFM for a large turbine powered aircraft should contain information that allows flight crews to determine that the aircraft will be capable of performing the following actions, considering the landing weight and other pertinent environmental factor:

• Land within the distance required by the regulations.

• Climb from the missed approach point (MAP) and maintain a specified climb gradient with one engine inoperative.

• Perform a go-around from the final stage of landing and maintain a specified climb gradient with all engines operating and the aircraft in the landing configuration.

Many airplanes have more than one allowable flap configuration for normal landing. Often, a reduced flap setting for landing allows the airplane to operate at a higher landing weight into a field that has restrictive obstacles in the missed approach or rejected landing climb path. On these occasions, the full-flap landing speed may not allow the airplane enough energy to successfully complete a go-around and avoid any high terrain and/or obstacles that might exist on the climb out. Therefore, all-engine and engine-out missed approaches, as well as rejected landings, must be taken into consideration in compliance with the regulations.

Aircraft Approach Categories

Aircraft approach category means a grouping of aircraft based on a reference landing speed (VREF), if specified, or if VREF is not specified, 1.3 VSO at the maximum certified landing weight. VREF, VSO, and the maximum certified landing weight are those values as established for the aircraft by the certification authority of the country of registry. A pilot must use the minima corresponding to the category determined during certification or higher. Helicopters may use Category A minima. If it is necessary to operate at a speed in excess of the upper limit of the speed range for an aircraft’s category, the minimums for the higher category must be used. For example, an airplane that fits into Category B, but is circling to land at a speed of 145 knots, must use the approach Category D minimums. As an additional example, a Category A aircraft that is operating at 130 knots on a straight-in approach must use the approach Category C minimums. See the following category limits noting that the airspeeds depicted are indicated airspeeds (IAS):

• Category A: Speed less than 91 knots.

• Category B: Speed 91 knots or more but less than 121 knots.

• Category C: Speed 121 knots or more but less than 141 knots.

• Category D: Speed 141 knots or more but less than 166 knots.

• Category E: Speed 166 knots or more.

Note: Helicopter pilots may use the Category A line of minimums provided the helicopter is operated at Category A airspeeds.

An airplane is certified in only one approach category, and although a faster approach may require higher category minimums to be used, an airplane cannot be flown to the minimums of a slower approach category. The certified approach category is permanent and independent of the changing conditions of day-to-day operations. From a TERPS viewpoint, the importance of a pilot not operating an aircraft at a category line of minimums lower than the aircraft is certified for is primarily the margin of protection provided for containment of the aircraft within the procedure design for a slower aircraft. This includes height loss at the decision altitude, missed approach climb surface, and turn containment in the missed approach at the higher category speeds.

Pilots are responsible for determining if a higher approach category applies. If a faster approach speed is used that places the aircraft in a higher approach category, the minimums for the appropriate higher category must be used. Emergency returns at weights in excess of maximum certificated landing weight, approaches made with inoperative flaps, and approaches made in icing conditions for some airplanes are examples of situations that can necessitate the use of higher approach category minima.

Circling approaches are one of the most challenging flight maneuvers conducted in the NAS, especially for pilots of CAT C and CAT D turbine-powered, transport category airplanes. These maneuvers are conducted at low altitude, day and night, and often with precipitation present affecting visibility, depth perception, and the ability to adequately assess the descent profile to the landing runway. Most often, circling approaches are conducted to runways without the benefit of electronic navigation aids to support the descent from the Circling Minimums Decision Altitude (CMDA) to the runway.

Circling approaches conducted at faster-than-normal, straight-in approach speeds also require a pilot to consider the larger circling approach area, since published circling minimums provide obstacle clearance only within the appropriate area of protection and is based on the approach category speed. [Figure 4-2] The circling approach area is the obstacle clearance area for aircraft maneuvering to land on a runway that does not meet the criteria for a straight- in approach. The size of the circling area varies with the approach category of the aircraft, as shown in Figure 4-2.

A

B

C

D

E

1.3

1.5

1.7

2.3

4.5

Approach category Radius (miles)

RADII (r) defining size of areas, vary

with the approach category

Circling approach area

r

r r

r

r

Figure 4-2. Construction of circling approach area.

Figure 4-2: picture of page 9Figure 4-2 · page 9
Picture of the page from the copy saved here

A minimum of 300 feet of obstacle clearance is provided in the circling segment. Pilots should remain at or above the circling altitude until the aircraft is continuously in a position from which a descent to a landing on the intended runway can be made at a normal rate of descent and using normal maneuvers. Since an approach category can make a difference in the approach and weather minimums and, in some cases, prohibit flight crews from initiating an approach, the approach speed should be calculated and the effects on the approach determined and briefed in the preflight planning phase, as well as reviewed prior to commencing an approach.

Prior to FAA Order 8260.3 Change 21, pilots were often faced with the challenge of descending using a stabilized approach concept if the CMDA height above airport (HAA) exceeded 1,200 feet. Once the HAA approached 1,200 feet, pilots were often forced to increase their rates of descent in order to arrive at the appropriate “in-slot” position. “In-slot” being defined as at a minimum, a CAT C or CAT D turbine-powered airplane should be wings level on a three degree - 318 ft/NM descent path not less than 1 NM from the touchdown point (1,000 feet beyond runway threshold). This was due to the small size of the circling protected airspace that the aircrews must remain within to ensure obstacle clearance.

The FAA Order 8260.3 Change 21 to the circling protected airspace afforded much greater obstacle protection.

However, it also afforded the pilot the opportunity to use the extra protected airspace to mitigate the need to conduct a high descent rate, unstabilized approach that was often necessary as a result of the previous criteria for the Circling Approach Radius (CAR). For example, under FAA Order 8260.3 Change 21, a sea level airport with a 1,500 ft HAA will have CAT C CAR of 2.86 NM, a 1.16 NM (68.5%) increase over pre-Change 21 CAR for CAT C. This extra protected airspace can be used by the pilot to maneuver the aircraft instead of being forced to use high descent rates which are often necessary for high HAA circling approaches.

Most commercial operators dictate standard procedures for conducting instrument approaches in their FAA-approved manuals. These standards designate company callouts, flight profiles, configurations, and other specific duties for each flight deck crewmember during the conduct of an instrument approach.

Instrument Approach Charts

Beginning in February 2000, the FAA began issuing the current format for instrument approach charts. This chart was developed by the Department of Transportation (DOT), Volpe National Transportation Systems Center and is commonly referred to as the Pilot Briefing Information format. The FAA chart format is presented in a logical order, facilitating pilot briefing of the procedures. [Figure 4-3]

Approach Chart Naming Conventions

Individual FAA charts are identified on both the top and bottom of the page by their procedure name (based on the NAVAIDs required for the final approach), runway served, and airport location. The identifier for the airport is also listed immediately after the airport name. [Figure 4-4]

There are several types of approach procedures that may cause some confusion for flight crews unfamiliar with the naming conventions. Although specific information about each type of approach is covered later in this chapter, listed below are a few procedure names that can cause confusion.

Straight-In Procedures

Figure 4-3: picture of page 10Figure 4-3 · page 10
Picture of the page from the copy saved here

When two or more straight-in approaches with the same type of guidance exist for a runway, a letter suffix is added to the title of the approach so that it can be more easily identified. These approach charts start with the letter Z and continue in reverse alphabetical order. For example, consider the (RNAV) (GPS) Z RWY 13C and RNAV (RNP) Y RWY 13C approaches at Chicago Midway International Airport. [Figure 4-5] Although these two approaches can be flown with a global positioning system (GPS) to the

City and state Issue # (issue authority) TOP MARGIN IDENTIFICATION Approach lighting (this is U.S. PITTSFIELD, MASSACHUSETTS AL-975 (FAA) configuration sequenced 10322

LOC/DME I-EIF Chan 20 108.3 APP CRS 2590 Rwy ldg TDZE Apt Elev 5001 1176 1194 flashing, see FIH) PITTSFIELD MUNI (PSF) VY26

Figure 4-5: picture of page 12Figure 4-5 · page 12
Picture of the page from the copy saved here

V Circling to Rwy 14/32 NA at night. Inoperative table does not apply. MALSF MISSED APPROACH: Climb to 4000 on INFATION A Visibility reduction by helicopters NA. Circling NA south of Runways 8 and 32. 135.375 ASOS 132.825 307.2 ALBANY APP CON CLNC DEL 128.6 4 to HIDAL INT/PWL 30 DME and hold. heading 259° and PWL VOR/DME R-021 122.7 (CTAF) UNICOM

115.0 CAM CAMBRIDGE Chan 97 (32.2) b 5700 A 3688 Missed approach verbiage Procedure Entry. DME Required fcr 090- MSA CTR 25 NM 4700] -270°

2989 MISSED APCH FIX 115.1 CTR A ELEPE INT (IAF) 3900 Chan 98 2460 ± I-EIF 7.4

117.6 IGN Chan 123 PWL 30 HIDAL R-0324 -R-0211 -114.3 PWL Chan 90 -R-279 2339 A 1330 1477 A A HEKIR INT 1-EIF 4.1 1285 R-179 CAM32.2 -079° 259° min A2407 079° 2290 PLAM IIEW

A1872± A2554

NE-1, 10 MAR 2011 to 07 APR 2011 Cha 90 R-021 2273 A LOCALIZER 108.3 A 1968 I-EIF Chan 20 I-EIF 1.2 WARKA 2256 10 NM 2243 A R-322 2234 115.1 CTR CHESTER Chan 98

ELEV 1194 Missed approach icons

4000 HIDAL ELEPE One Minute PWL I-EIF7.4 Holding Pattern R-021 dg 2590 HEKIR

AIRR DRROAM 188A 5006×100 1261 A A1178 3496×100 1250 -1.0%UP 0.8%UP OA 1190 3 1208 TDZE 1176 CATEGORY S-26 I-EIF 1.2 WARKA 0.3 2300-11/4 1124 (1200-1/4) A 2.9NM I-EIF 4.1 2300 B -259°- 3.3 NM TCH 54 3.48° 2300-3 1124 (1200-3) 259° C 079° D 3600 PRO VIEW

MIRL Rwys 8-26 and 14-32 0 FAF to MAP 6.2 NM S-26 CIRCLING HEKIR FIX MINIMUMS (DUAL VOR RECEIVERS OR DME REQUIRED) 1106 (1200-1/4) 2300-11/4 1880-1 704 (700-1) 1106(1200-1/2) 2300-11/2 704 (700-2) 1880-2 2300-3 1106 (1200-3) 704 (700-2 14) 1880-2 LANDING MIIINUMS

Min:Sed 6:12 Knots 60 4:08 90 3:06 120 2:29 150 2:04 180 CIRCLING 1880-1 686 (700-1) 686 (700-2) 1880-2 1006(1100-3) 2200-3

PITTSFIELD, MASSACHUSETTS PITTSFIELD MUNI (PSF) Amdt 8 29JUL10 42°26'N-73°18'W LOC RWY 26

PITTSFIELD, MASSACHUSETTS PITTSFIELD MUNI (PSF) Amdt 8 29JUL10 42°26'N-73°18'W LOC RWY 26

Amendments Latitude/longitude coordinates Airport identifier

Time and speed table BOTTOM MARGIN IDENTIFICATION

Figure 4-3. Instrument approach chart.

NOT FOR NAVIGATION

Figure 4-4. Procedure identification.

Figure 4-4: picture of page 11Figure 4-4 · page 11
Picture of the page from the copy saved here

NOT FOR NAVIGATION

same runway, they are significantly different (e.g., one is a Required Navigation Performance (RNP) Authorization Required (AR) formally known as SPECIAL AIRCRAFT & AIRCREW AUTHORIZATION REQUIRED (SAAAR);” one has circling minimums and the other does not; the minimums are different; and the missed approaches are not the same). The approach procedure labeled Z has lower landing minimums than Y (some older charts may not reflect this).

In this example, the LNAV MDA for the RNAV (GPS) Z RWY 13C has the lowest minimums of either approach due to the differences in the final approach required obstacle clearance (ROC) evaluation. This convention also eliminates any confusion with approach procedures labeled A and B, where only circling minimums are published. The designation of two area navigation (RNAV) procedures to the same runway can occur when it is desirable to accommodate panel mounted GPS receivers and flight management systems (FMSs), both with and without vertical navigation (VNAV). It is also important to note that only one of each type of approach for a runway, including ILS, VHF omnidirectional range (VOR), and non-directional beacon (NDB) can be coded into a database.

Circling-Only Procedures

Approaches that do not have straight-in landing minimums are identified by the type of approach followed by a letter. Examples in Figure 4-6 show four procedure titles at the

same airport that have only circling minimums.

Figure 4-6: picture of page 13Figure 4-6 · page 13
Picture of the page from the copy saved here

As can be seen from the example, the first approach of this type created at the airport is labeled with the letter A, and the lettering continues in alphabetical order. Typically, circling only approaches are designed for one of the following reasons:

• The final approach course alignment with the runway centerline exceeds 30°.

• The descent gradient is greater than 400 ft/NM from the FAF to the threshold crossing height (TCH). When this maximum gradient is exceeded, the circling only approach procedure may be designed to meet the gradient criteria limits. This does not preclude a straight-in landing if a normal descent and landing can be made in accordance with the applicable CFRs.

• A runway is not clearly defined on the airfield.

Communications

The communication strip provided near the top of FAA approach charts gives flight crews the frequencies that they can expect to be assigned during the approach. The frequencies are listed in the logical order of use from arrival to touchdown. Having this information immediately available during the approach reduces the chances of a loss of contact between ATC and flight crews during this critical phase of flight.

It is important for flight crews to understand their responsibilities with regard to communications in the various approach environments. There are numerous differences in communication responsibilities when operating into and out of airports without ATC towers as compared to airports with control towers. Today’s pilots face an increasing range of ATC environments and conflicting traffic dangers, making approach briefing and preplanning more critical. Individual company operating manuals and SOPs dictate the duties for each crewmember.

FAA AC 120-71, Standard Operating Procedures for Flight Deck Crewmembers, contains the following concerning ATC communications: SOPs should state who (Pilot Flying (PF), Pilot Monitoring (PM), Flight Engineer (FE/SO)) handles the radios for each phase of flight, as follows:

• PF makes input to aircraft/autopilot and/or verbally states clearances while PM confirms input is what he or she read back to ATC.

• Any confusion in the flight deck is immediately cleared up by requesting ATC confirmation.

• If any crewmember is off the flight deck, all ATC instructions are briefed upon his or her return. Or,

NOT FOR NAVIGATION

EC-3, 18 NOV 2010 to 16 DEC 2010

EC-3, 18 NOV 2010 to 16 DEC 2010

EC-3, 18 NOV 2010 to 16 DEC 2010

EC-3, 18 NOV 2010 to 16 DEC 2010

Figure 4-5. Multiple approaches.

NOT FOR NAVIGATION

NW-1,

NW-1, 18 NOV 2010 to 16

V 2010 to 16 DEC 2010

2010

Figure 4-6. Procedures with circling landing minima.

if any crewmember is off the flight deck, all ATC instructions are written down until his or her return and then passed to that crewmember upon return. Similarly, if a crewmember is off ATC frequency when making a precision approach (PA) announcement or when talking on company frequency, all ATC instructions are briefed upon his or her return.

• Company policy should address use of speakers, headsets, boom microphone, and/or hand-held microphone.

• SOPs should state the altitude awareness company policy on confirming assigned altitude.

Example: The PM acknowledges ATC altitude clearance. If the aircraft is on the autopilot, then the PF makes input into the autopilot/altitude alerter. PF points to the input while stating the assigned altitude as he or she understands it. The PM then points to the input stating aloud what he or she understands the ATC clearance to be confirming that the input and clearance match. If the aircraft is being handflown, then the PM makes the input into the altitude alerter/ autopilot, then points to the input and states clearance. PF then points to the alerter stating aloud what he or she understands the ATC clearance to be confirming that the alerter and clearance match.

Example: If there is no altitude alerter in the aircraft, then both pilots write down the clearance, confirm that they have the same altitude, and then cross off the previously assigned altitude.

Approach Control

Approach control is responsible for controlling all instrument flights operating within its area of responsibility. Approach control may serve one or more airports. Control is exercised primarily through direct pilot and controller communication and airport surveillance radar (ASR). Prior to arriving at the initial approach fix (IAF), instructions will

be received from the air route traffic control center (ARTCC) to contact approach control on a specified frequency. Where radar is approved for approach control service, it is used not only for radar approaches, but also for vectors in conjunction with published non-radar approaches using conventional NAVAIDs or RNAV/GPS.

When radar handoffs are initiated between the ARTCC and approach control, or between two approach control facilities, aircraft are cleared (with vertical separation) to an outer fix most appropriate to the route being flown and, if required, given holding instructions. Or, aircraft are cleared to the airport or to a fix so located that the handoff is completed prior to the time the aircraft reaches the fix. When radar handoffs are used, successive arriving flights may be handed off to approach control with radar separation in lieu of vertical separation.

After release to approach control, aircraft are vectored to the final approach course. ATC occasionally vectors the aircraft across the final approach course for spacing requirements. The pilot is not expected to turn inbound on the final approach course unless an approach clearance has been issued. This clearance is normally issued with the final vector for interception of the final approach course, and the vector enables the pilot to establish the aircraft on the final approach course prior to reaching the FAF.

Air Route Traffic Control Center (ARTCC)

ARTCCs are approved for and may provide approach control services to specific airports. The radar systems used by these centers do not provide the same precision as an ASR or precision approach radar (PAR) used by approach control facilities and control towers, and the update rate is not as fast. Therefore, pilots may be requested to report established on the final approach course. Whether aircraft are vectored to the appropriate final approach course or provide their own navigation on published routes to it, radar service is automatically terminated when the landing is completed; or when instructed to change to advisory frequency at airports without an operating ATC tower, whichever occurs first. When arriving on an IFR flight plan at an airport with an operating control tower, the flight plan is closed automatically upon landing.

The extent of services provided by approach control varies greatly from location to location. The majority of Part 121 operations in the NAS use airports that have radar service and approach control facilities to assist in the safe arrival and departure of large numbers of aircraft. Many airports do not have approach control facilities. It is important for pilots to understand the differences between approaches with and without an approach control facility. For example,

Figure 4-7. Durango approach and low altitude en route excerpt.

consider the Durango, Colorado, ILS DME RWY 2 and low altitude en route chart excerpt shown in Figure 4-7.

High or Lack of Minimum Vectoring Altitudes (MVAs)

Considering the fact that most modern commercial and corporate aircraft are capable of direct, point-to-point flight, it is increasingly important for pilots to understand the limitations of ARTCC capabilities with regard to minimum altitudes. There are many airports that are below the

Figure 4-7: picture of page 14Figure 4-7 · page 14
Picture of the page from the copy saved here

coverage area of Center radar, and; therefore, off-route transitions into the approach environment may require that the aircraft be flown at a higher altitude than would be required for an on-route transition. In the Durango example, an airplane approaching from the northeast on a direct route to the Durango VOR may be restricted to a minimum IFR altitude (MIA) of 17,000 feet MSL due to unavailability of Center radar coverage in that area at lower altitudes. An arrival on V95 from the northeast would be able to descend to a minimum en route altitude (MEA) of 12,000 feet, allowing a shallower transition to the approach

environment. An off-route arrival may necessitate a descent into holding in order to avoid an unstable approach to Durango.

Lack of Approach Control Terrain Advisories

Flight crews must understand that terrain clearance cannot be assured by ATC when aircraft are operating at altitudes that are not served by Center or approach radar. Recent National Transportation Safety Board (NTSB) investigations have identified several accidents that involved controlled flight into terrain (CFIT) by IFR rated and VFR pilots operating under visual flight conditions at night in remote areas. In many of these cases, the pilots were in contact with ATC at the time of the accident and receiving radar service. The pilots and controllers involved all appear to have been unaware that the aircraft were in danger. Increased altitude awareness and better preflight planning would likely have prevented all of these accidents. How can pilots avoid becoming involved in a CFIT accident?

CFIT accidents are best avoided through proper preflight planning.

• Terrain familiarization is critical to safe visual operations at night. Use sectional charts or other topographic references to ensure that your altitude safely clears terrain and obstructions all along your route.

• In remote areas, especially in overcast or moonless conditions, be aware that darkness may render visual avoidance of high terrain nearly impossible and that the absence of ground lights may result in loss of horizon reference.

• When planning a nighttime VFR flight, follow IFR practices, such as climbing on a known safe course, until well above surrounding terrain. Choose a cruising altitude that provides terrain separation similar to IFR flights (2,000 feet AGL in mountainous areas and 1,000 feet above the ground in other areas.)

• When receiving radar services, do not depend on ATC to warn you of terrain hazards. Although controllers try to warn pilots if they notice a hazardous situation, they may not always be able to recognize that a particular VFR aircraft is dangerously close to terrain.

• When issued a heading along with an instruction to “maintain VFR,” be aware that the heading may not provide adequate terrain clearance. If you have any doubt about your ability to visually avoid terrain and obstacles, advise ATC immediately and take action to reach a safe altitude if necessary.

• ATC radar software can provide limited prediction and warning of terrain hazards, but the warning system

is configured to protect IFR flights and is normally suppressed for VFR aircraft. Controllers can activate the warning system for VFR flights upon pilot request, but it may produce numerous false alarms for aircraft operating below the MIA, especially in en route center airspace.

• If you fly at night, especially in remote or unlit areas, consider whether a GPS-based terrain awareness unit would improve your safety of flight.

• Lack of approach control traffic advisories—if radar service is not available for the approach, the ability of ATC to give flight crews accurate traffic advisories is greatly diminished. In some cases, the common traffic advisory frequency (CTAF) may be the only tool available to enhance an IFR flight’s awareness of traffic at the destination airport. Additionally, ATC will not clear an IFR flight for an approach until the preceding aircraft on the approach has cancelled IFR, either on the ground, or airborne once in visual meteorological conditions (VMC).

Airports With an ATC Tower

Control towers are responsible for the safe, orderly, and expeditious flow of all traffic that is landing, taking off, operating on and in the vicinity of an airport and, when the responsibility has been delegated, towers also provide for the separation of IFR aircraft in terminal areas. Aircraft that are departing IFR are integrated into the departure sequence by the tower. Prior to takeoff, the tower controller coordinates with departure control to assure adequate aircraft spacing.

Airports Without A Control Tower

From a communications standpoint, executing an instrument approach to an airport that is not served by an ATC tower requires more attention and care than making a visual approach to that airport. Pilots are expected to self-announce their arrival into the vicinity of the airport no later than 10 NM from the field. Depending on the weather, as well as the amount and type of conflicting traffic that exists in the area, an approach to an airport without an operating ATC tower increases the difficulty of the transition to visual flight.

In many cases, a flight arriving via an instrument approach needs to mix in with VFR traffic operating in the vicinity of the field. For this reason, many companies require that flight crews make contact with the arrival airport CTAF or company operations personnel via a secondary radio over 25 NM from the field in order to receive traffic advisories. In addition, pilots should attempt to listen to the CTAF well in advance of their arrival in order to determine the VFR traffic situation.

NOT FOR NAVIGATION

Since separation cannot be provided by ATC between IFR and VFR traffic when operating in areas where there is no radar coverage, pilots are expected to make radio announcements on the CTAF. These announcements allow other aircraft operating in the vicinity to plan their departures and arrivals with a minimum of conflicts. In addition, it is very important for crews to maintain a listening watch on the CTAF to increase their awareness of the current traffic situation. Flights inbound on an instrument approach to a field without a control tower should make several self-announced radio calls during the approach:

• Initial call within 4-10 minutes of the aircraft’s arrival at the IAF. This call should give the aircraft’s location as well as the crew’s approach intentions.

• Departing the IAF, stating the approach that is being initiated.

• Procedure turn (or equivalent) inbound.

• FAF inbound, stating intended landing runway and maneuvering direction if circling.

• Short final, giving traffic on the surface notification of imminent landing.

When operating on an IFR flight plan at an airport without a functioning control tower, pilots must initiate cancellation of the IFR flight plan with ATC or an AFSS. Remote communications outlets (RCOs) or ground communications outlets (GCOs), if available, can be used to contact an ARTCC or an AFSS after landing. If a frequency is not available on

NW-1, 18 NOV 2010 to 16 DEC 2010

NW-1, 18 NOV 2010 to 16 DEC 2010

Figure 4-8. Cheyenne Regional (KCYS), Cheyenne, Wyoming, ILS or LOC RWY 27.

the ground, the pilot has the option to cancel IFR while in flight if VFR conditions can be maintained while in contact with ARTCC, as long as those conditions can be maintained until landing. Additionally, pilots can relay a message through another aircraft or contact flight service via telephone.

Primary NAVAID

Figure 4-8: picture of page 16Figure 4-8 · page 16
Picture of the page from the copy saved here

Most conventional approach procedures are built around a primary final approach NAVAID; others, such as RNAV (GPS) approaches, are not. If a primary NAVAID exists for an approach, it should be included in the IAP briefing, set into the appropriate backup or active navigation radio, and positively identified at some point prior to being used for course guidance. Adequate thought should be given to the appropriate transition point for changing from FMS or other en route navigation over to the conventional navigation to be used on the approach. Specific company standards and procedures normally dictate when this changeover occurs; some carriers are authorized to use FMS course guidance throughout the approach, provided that an indication of the conventional navigation guidance is available and displayed. Many carriers, or specific carrier fleets, are required to change over from RNAV to conventional navigation prior to the FAF of an instrument approach.

Depending on the complexity of the approach procedure, pilots may have to brief the transition from an initial NAVAID to the primary and missed approach NAVAIDs. Figure 4-8 shows the Cheyenne, Wyoming, ILS Runway 27 approach procedure, which requires additional consideration during an IAP briefing.

If the 15 DME arc of the CYS VOR is to be used as the transition to this ILS approach procedure, caution must be paid to the transition from en route navigation to the initial NAVAID and then to the primary NAVAID for the ILS approach. Planning when the transition to each of these NAVAIDs occurs may prevent the use of the incorrect NAVAID for course guidance during approaches where high pilot workloads already exist.

Equipment Requirements

The navigation equipment that is required to join and fly an IAP is indicated by the title of the procedure and notes on the chart. Straight-in IAPs are identified by the navigation system by providing the final approach guidance and the runway with which the approach is aligned (for example, VOR RWY 13). Circling-only approaches are identified by the navigation system by providing final approach guidance and a letter (for example, VOR A). More than one navigation system separated by a slant indicates that more than one type of equipment must be used to execute the

final approach (for example, VOR/DME RWY 31). More than one navigation system separated by the word“or”indicates either type of equipment can be used to execute the final approach (for example, VOR or GPS RWY 15).

In some cases, other types of navigation systems, including radar, are required to execute other portions of the approach or to navigate to the IAF (for example, an NDB procedure turn to an ILS, or an NDB in the missed approach, or radar required to join the procedure or identify a fix). When ATC radar or other equipment is required for procedure entry from the en route environment, a note is charted in the plan view of the approach procedure chart (for example, RADAR REQUIRED or AUTOMATIC DIRECTION FINDER (ADF) REQUIRED). When radar or other equipment is required on portions of the procedure outside the final approach segment, including the missed approach, a note is charted in the notes box of the pilot briefing portion of the approach chart (for example, RADAR REQUIRED or DISTANCE MEASURING EQUIPMENT (DME) REQUIRED). Notes are not charted when VOR is required outside the final approach segment. Pilots should ensure that the aircraft is equipped with the required NAVAIDs to execute the approach, including the missed approach. Refer to the AIM paragraph 5-4-5 for additional options with regards to equipment requirements for IAPs.

RNAV systems may be used as a Substitute Means of Navigation when a very high frequency (VHF) Omnidirectional Range (VOR), Distance Measuring Equipment (DME), Tactical Air Navigation (TACAN), VOR/TACAN (VORTAC), VOR/DME, non-directional radio beacon (NDB), or compass locator facility including locator outer marker and locator middle marker is out-of-service, i.e., the Navigation Aid (NAVAID) information is not available; an aircraft is not equipped with an automatic direction finder (ADF) or DME; or the installed ADF or DME on an aircraft is not operational. For example, if equipped with a suitable RNAV system, a pilot may hold over an out-of-service NDB. Refer to Advisory Circular 90-108, Use of Suitable RNAV System on Conventional Routes and Procedures, dated March 3, 2011 for additional guidance on the proper times and procedures for substituting a RNAV system for means of navigation.

Courses

Traditional Courses

An aircraft that has been cleared to a holding fix and subsequently “cleared…approach,” normally does not receive new routing. Even though clearance for the approach may have been issued prior to the aircraft reaching the holding fix, ATC would expect the pilot to

proceed via the holding fix that was the last assigned route, and the feeder route associated with that fix, if a feeder route is published on the approach chart, to the IAF to commence the approach. When cleared for the approach, the published off-airway (feeder) routes that lead from the en route structure to the IAF are part of the approach clearance.

If a feeder route to an IAF begins at a fix located along the route of flight prior to reaching the holding fix, and clearance for an approach is issued, a pilot should commence the approach via the published feeder route. For example, the aircraft would not be expected to overfly the feeder route and return to it. The pilot is expected to commence the approach in a similar manner at the IAF, if the IAF for the procedure is located along the route of flight to the holding fix.

If a route of flight directly to the IAF is desired, it should be so stated by the controller with phraseology to include the words “direct,” “proceed direct,” or a similar phrase that the pilot can interpret without question. When a pilot is uncertain of the clearance, ATC should be queried immediately as to what route of flight is preferred.

The name of an instrument approach, as published, is used to identify the approach, even if a component of the approach aid is inoperative or unreliable. The controller will use the name of the approach as published, but must advise the aircraft at the time an approach clearance is issued that the inoperative or unreliable approach aid component is unusable. (Example: “Cleared ILS RWY 4, glideslope unusable.”)

Area Navigation Courses

RNAV (GPS) approach procedures introduce their own tracking issues because they are flown using an onboard navigation database. They may be flown as coupled approaches or flown manually. In either case, navigation system coding is based on procedure design, including waypoint (WP) sequencing for an approach and missed approach. The procedure design indicates whether the WP is a fly-over (FO) or fly-by (FB), and provides appropriate guidance for each. A FB WP requires the use of turn anticipation to avoid overshooting the next flight segment. A FO WP precludes any turn until the WP is over flown and is followed by either an intercept maneuver of the next flight segment or direct flight to the next WP.

Figure 4-9. Fly-by and fly-over waypoints.

Figure 4-9: picture of page 18Figure 4-9 · page 18
Picture of the page from the copy saved here

Approach waypoints, except for the missed approach waypoint (MAWP) and the missed approach holding waypoint (MAHWP), are normally FB WPs. Notice that in the plan view in Figure 4-9, there are four FB WPs, but only the circled WP symbol at PRINO is a FO WP. If flying manually to a selected RNAV WP, pilots should anticipate the turn at a FB WP to ensure a smooth transition and avoid overshooting the next flight segment. Alternatively, for a FO WP, no turn is accomplished until the aircraft passes the WP.

There are circumstances when a WP may be coded into the database as both a FB WP and a FO WP, depending on how the WPs are sequenced during the approach procedure. For example, a WP that serves as an IAF may be coded as a FB WP for the approach and as a FO WP when it also serves as the MAWP for the missed approach procedure (MAP). This is just one reason why instrument approaches should be loaded in their entirety from the FMS and not manually built or modified.

Altitudes

Prescribed altitudes may be depicted in four different configurations: minimum, maximum, recommended, and mandatory. The U.S. Government distributes approach charts produced by the FAA. Altitudes are depicted on these charts in the profile view with an underscore or overscore, or both to identify them as minimum, maximum, or mandatory, respectively.

• Minimum altitudes are depicted with the altitude value underscored. Aircraft are required to maintain altitude at or above the depicted value (e.g., 3000).

• Maximum altitudes are depicted with the altitude value overscored. Aircraft are required to maintain altitude at or below the depicted value (e.g., 4800).

• Mandatory altitudes are depicted with the altitude value both underscored and overscored. Aircraft are required to maintain altitude at the depicted value (e.g., 5500).

• Recommended altitudes are depicted without an underscore or overscore.

Note: Pilots are cautioned to adhere to altitudes as prescribed because, in certain instances, they may be used as the basis for vertical separation of aircraft by ATC. If a depicted altitude is specified in the ATC clearance, that altitude becomes mandatory as defined above.

Minimum Safe/Sector Altitude

Minimum Safe Altitudes are published for emergency use on IAP charts. MSAs provide 1,000 feet of clearance over all obstacles but do not necessarily assure acceptable navigation signal coverage. The MSA depiction on the plan view of an approach chart contains the identifier of the

center point of the MSA, the applicable radius of the MSA, a depiction of the sector(s), and the minimum altitudes above mean sea level which provide obstacle clearance. For conventional navigation systems, the MSA is normally based on the primary omnidirectional facility on which the IAP is predicated, but may be based on the airport reference point (ARP) if no suitable facility is available. For RNAV approaches, the MSA is based on an RNAV waypoint. MSAs normally have a 25 NM radius; however, for conventional navigation systems, this radius may be expanded to 30 NM if necessary to encompass the airport landing surfaces.

Depicted on the Plan View of approach charts, a single sector altitude is normally established. However when it is necessary to obtain obstacle clearance, an MSA area may be further divided with up to four sectors.

Final Approach Fix Altitude

Another important altitude that should be briefed during an IAP briefing is the FAF altitude, designated by the cross on a non-precision approach, and the lightning bolt symbol designating the glideslope/glidepath intercept altitude on a precision approach. Adherence and cross-check of this altitude can have a direct effect on the success and safety of an approach.

Proper airspeed, altitude, and configuration, when crossing the FAF of a non-precision approach, are extremely important no matter what type of aircraft is being flown. The stabilized approach concept, implemented by the FAA within the SOPs of each air carrier, suggests that crossing the FAF at the published altitude is often a critical component of a successful non-precision approach, especially in a large turbojet aircraft.

The glideslope intercept altitude of a precision approach should also be included in the IAP briefing. Awareness of this altitude when intercepting the glideslope can ensure the flight crew that a “false glideslope” or other erroneous indication is not inadvertently followed. Many air carriers include a standard callout when the aircraft passes over the FAF of the non-precision approach underlying the ILS. The PM states the name of the fix and the charted glideslope altitude, thus allowing both pilots to cross-check their respective altimeters and verify the correct indications.

Minimum Descent Altitude (MDA), Decision Altitude (DA), And Decision Height (DH)

MDA—the lowest altitude, expressed in feet MSL, to which descent is authorized on final approach or during circle-toland maneuvering in execution of a standard instrument approach procedure (SIAP) where no electronic glideslope is provided.

DA—a specified altitude in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established.

DH—with respect to the operation of aircraft, means the height at which a decision must be made during an ILS, MLS, or PAR IAP to either continue the approach or to execute a missed approach.

CAT II and III approach DHs are referenced to AGL and measured with a radio altimeter.

The height above touchdown (HAT) for a CAT I precision approach is normally 200 feet above touchdown zone elevation (TDZE). When a HAT of 250 feet or higher is published, it may be the result of the signal-in-space coverage, or there may be penetrations of either the final or missed approach obstacle clearance surfaces (OCSs). If there are OCS penetrations, the pilot has no indication on the approach chart where the obstacles are located. It is important for pilots to brief the MDA, DA, or DH so that there is no ambiguity as to what minimums are being used. These altitudes can be restricted by many factors. Approach category, inoperative equipment in the aircraft or on the ground, crew qualifications, and company authorizations are all examples of issues that may limit or change the height of a published MDA, DA, or DH.

For many air carriers, OpSpecs may be the limiting factor for some types of approaches. NDB and circling approaches are two common examples where the OpSpecs minimum listed altitudes may be more restrictive than the published minimums. Many Part 121 and 135 operators are restricted from conducting circling approaches below 1,000 feet MDA and 3 SM visibility by Part C of their OpSpecs, and many have specific visibility criteria listed for NDB approaches that exceed visibilities published for the approach (commonly 2 SM). In these cases, flight crews must determine which is the more restrictive of the two and comply with those minimums.

In some cases, flight crew qualifications can be the limiting factor for the MDA, DA, or DH for an instrument approach. There are many CAT II and III approach procedures authorized at airports throughout the United States, but RNP AR restricts their use to pilots who have received specific training, and aircraft that are equipped and authorized to conduct those approaches. Other rules pertaining to flight crew qualifications can also determine the lowest usable MDA, DA, or DH for a specific approach. 14 CFR Part 121, § 121.652, 14 CFR Part 125, § 125.379, and 14 CFR Part 135, § 135.225 require that some PICs,

with limited experience in the aircraft they are operating, increase the approach minimums and visibility by 100 feet and one-half mile respectively. Rules for these “highminimums” pilots are usually derived from a combination of federal regulations and the company’s OpSpecs. There are many factors that can determine the actual minimums that can be used for a specific approach. All of them must be considered by pilots during the preflight and approach planning phases, discussed, and briefed appropriately.

Pilots are cautioned to fully understand and abide by the guidelines set forth in 14 CFR § 91.175(c) regarding proper identification of the runway and runway environment when electing to continue any approach beyond the published DA/DH or MDA.

It is imperative to recognize that any delay in making a decision to execute the Missed Approach Procedure at the DA/DH or MDA/Missed Approach Point will put the aircrew at risk of impacting any obstructions that may be penetrating the visual obstacle clearance surface

The visual segment of an IAP begins at DA or MDA and continues to the runway. There are two means of operating in the visual segment, one is by using natural vision under 14 CFR Part 91, § 91.175 (c) and the other is by using an Enhanced Flight Vision System under 14 CFR Part 91, § 91.176.

Figure 4-10A. View during an approach with EFVS (left) and without EFVS (right). (Images courtesy of NASA Langley Research Center)

Enhanced Flight Vision Systems (EFVS) and Instrument Approaches [Figure 4-10A]

An Enhanced Flight Vision System (EFVS) is an installed aircraft system which uses a head up display (HUD), or an equivalent display that is a head up presentation, to combine aircraft flight information and flight symbology, navigation guidance, and a real-time image of the external scene to the pilot on a single display. Imaging sensors, which may be based on forward-looking infrared (FLIR), millimeter wave radiometry, millimeter wave radar, low-level light intensification, or other real-time imaging technologies, produce a real-time image of the outside scene. Combining

Figure 4-10A: picture of page 20Figure 4-10A · page 20
Picture of the page from the copy saved here

the flight information, navigation guidance, and sensor imagery on a HUD or equivalent display allows the pilot to continue looking forward along the flightpath throughout the entire approach, landing, and rollout.

Sections 91.175(c) and 91.176 specify two means of operating visually below DA/DH or MDA in the visual segment of an IAP. One means is by using natural vision under § 91.175(c), and the other is by using enhanced vision provided by an EFVS under § 91.176. When the runway environment cannot be visually acquired using natural vision, a pilot may use an EFVS to continue descending below DA/DH or MDA under § 91.176. An EFVS operation is an operation in which visibility conditions require an EFVS to be used in lieu of natural vision to perform an approach or landing, determine enhanced flight visibility, identify required visual references, or conduct a rollout. There are two types of EFVS operations – EFVS operations to touchdown and rollout and EFVS operations to 100 feet above the touchdown zone elevation (TDZE). An EFVS operation to touchdown and rollout is an operation in which a pilot uses the enhanced vision imagery provided by an EFVS in lieu of natural vision to descend below DA or DH to touchdown and rollout [Figure 4-10B]. These operations may be conducted on standard instrument approach procedures (SIAPs) or special instrument approach procedures (IAPs) that have a DA or DH (e.g., Precision or APV approach).

Figure 4-10B: picture of page 21Figure 4-10B · page 21
Picture of the page from the copy saved here

Figure 4-10B. EFVS Operation to Touchdown and Rollout.

An EFVS operation to 100 feet above the TDZE is an operation in which the pilot uses the EFVS in lieu of natural vision to descend below DA/DH or MDA down to 100 feet above the TDZE [Figure 4-10C]. To descend below 100 feet above the TDZE, however, natural vision must be used. EFVS operations to 100 feet above the TDZE may be conducted on SIAPs or special IAPs that have a DA/DH or MDA.

While the regulations do not prohibit EFVS from being used during any phase of flight for situational awareness, EFVS displays are not designed, installed, certified, or intended as a sufficient visual system to conduct circling maneuvers. EFVS may only be used during a circle-to-land maneuver provided the visual references required throughout the circling maneuver are distinctly visible to the pilot using natural vision throughout the circling maneuver. Therefore,

Figure 4-10C: picture of page 21Figure 4-10C · page 21
Picture of the page from the copy saved here

an EFVS cannot be used to satisfy the requirement that an identifiable part of the airport be distinctly visible to the pilot during a circling maneuver at or above MDA or while descending below MDA from a circling maneuver.

The visual information provided by an EFVS serves as independent verification of the position information provided by the aircraft’s displays and systems. An EFVS also enables a pilot to assess the enhanced flight visibility and identify required visual references, helps a pilot align the aircraft with the runway, and provides position, roll, rate of closure, and distance remaining information. Sections 91.176(a) and 91.176(b) permit a pilot to use an EFVS to identify the required visual references and to determine that the enhanced flight visibility provided by the EFVS is not less than the visibility prescribed in the IAP to be flown. Both the visual reference and enhanced flight visibility requirements of the regulations must be met before the pilot can descend below DA/DH during an EFVS operation to touchdown and rollout or below DA/DH or MDA during an EFVS operation to 100 feet above the TDZE. The aircraft also must continuously be in a position from which a descent to landing can be made on the intended runway at a normal rate of descent using normal maneuvers. For EFVS operations to touchdown, § 91.176(a)(2)(vi) requires that the descent rate must allow touchdown to occur within the touchdown zone of the runway of intended landing for all operations. Section 91.176(b)(2)(v), operations conducted to 100 feet above the TDZE, requires the descent rate to allow touchdown to occur within the touchdown zone of the runway of intended landing for operations conducted under 14 CFR Parts 121 and 135.

Figure 4-10C. EFVS Operations to 100 Feet Above the TDZE.

It is important to understand that using an EFVS does not result in obtaining lower minima with respect to the visibility or the DA/DH or MDA specified in the IAP. For example, a pilot who is using an EFVS on a Category I ILS approach that specifies a DA of 200 feet and a required visibility of RVR 2400 feet must comply with a 200-foot DA and an enhanced flight visibility of 2400 feet, even though the pilot may not have 2400 feet of flight visibility using natural vision or a reported

EC 2010

visibility of RVR 2400 feet. The decision altitude is specified by the IAP the pilot is flying, and it does not change whether EFVS is used or not. Accordingly, the visibility specified in the IAP does not change. The difference is whether the pilot assesses the RVR 2400 feet visibility prescribed by the IAP using natural vision or whether he or she assesses it using an EFVS. An EFVS simply provides another means of operating in the visual segment of an IAP. That is, it gives the pilot another means to see the required visual references when they might not be visible using natural vision, and it gives the pilot a means to see forward along the flightpath the distance required by the enhanced flight visibility – when he or she might not be able to do so using natural vision.

During an EFVS operation, a pilot must initiate a go-around at or below DA/DH or MDA whenever the requirements of § 91.176 are not met. The published missed approach procedure provides obstacle clearance only when the missed approach is initiated from or above the DA/DH, or at the MAP. It assumes a climb rate of 200 fT/NM unless a higher climb gradient is identified on the procedure. If a pilot initiates a go-around at a point below DA/DH or after the MAP, obstacle clearance is not necessarily provided by following the published missed approach procedure. Prior

planning is recommended and should include contingencies between the published MAP and touchdown with reference to obstacle clearance, aircraft performance, and alternate escape plans. Additionally, pilots should be especially knowledgeable of the approach conditions and approach course alignment when considering whether to rely on EFVS during an instrument approach with an offset final approach course. Depending upon the combination of crosswind correction, approach course offset, and the lateral field of view provided by a particular EFVS, the required visual references may or may not be within the pilot’s view looking through the EFVS upon reaching the MAP. AC 90-106 (current version) contains additional information about visual segment obstacle clearance, missed approach obstacle clearance, and considerations associated with offset approaches.

Operators that have a specific approval from the FAA to conduct special IAPs should evaluate those instrument procedures to determine their compatibility with EFVS operations. Special IAPs are frequently dependent on the ability of the operator to meet certain requirements that may include aircraft performance, equipage, airport facility equipment, crew training, or other requirements. These

EC-2, 18 N

NOT FOR NAVIGATION

Figure 4-11A. VNAV information.

procedures also may have nonstandard features such as nonstandard final approach course alignment, nonstandard descent gradients, or other features that may or may not be compatible with the conduct of EFVS operations.

Under § 91.176(a), operators who have been issued OpSpec C073, MSpec MC073, or LOA C073, may conduct EFVS operations to touchdown and rollout on certain vertical navigation (VNAV) IAPs that use an MDA as a DA/DH in accordance with C073. Additionally, §§ 91.176 and 91.189 permit an authorized EFVS operation to be conducted during an authorized Category II or Category III operation.

Figure 4-11A: picture of page 22Figure 4-11A · page 22
Picture of the page from the copy saved here

Currently, EFVS operations in rotorcraft can be conducted only on IAPs that are flown to a runway. Instrument approach criteria, procedures, and appropriate visual references have not yet been developed for straight-in landing operations below DA/DH or MDA under IFR to heliports or platforms. EFVS cannot be used in lieu of natural vision to descend below published minimums on copter approaches to a point-in-space (PinS) followed by a “proceed visual flight rules (VFR)” visual segment, or on approaches designed to a specific landing site using a “proceed visually” visual segment.

Vertical Navigation

One of the advantages of some GPS and multi-sensor FMS RNAV avionics is the advisory VNAV capability. Traditionally, the only way to get vertical path information during an approach was to use a ground-based precision NAVAID. Modern RNAV avionics can display an electronic vertical path that provides a constant-rate descent to minimums.

Since these systems are advisory and not primary guidance, the pilot must continuously ensure the aircraft remains at or above any published altitude constraint, including stepdown fix altitudes, using the primary barometric altimeter. The pilots, aircraft, and operator must be approved to use advisory VNAV inside the FAF on an instrument approach.

VNAV information appears on selected conventional nonprecision, GPS, and RNAV approaches (see “Types of Approaches” later in this chapter). It normally consists of two fixes (the FAF and the landing runway threshold), a FAF crossing altitude, a vertical descent angle (VDA), and may provide a visual descent point (VDP) [Figure 4-11A].

The VDA provides the pilot with advisory information not previously available on nonprecision approaches. It provides a means for the pilot to establish a stabilized descent from the FAF or step-down fix to the MDA. Stabilized descent is a key factor in the reduction of

controlled flight into terrain (CFIT) incidents. However, pilots should be aware that the published angle is for information only − it is strictly advisory in nature. There is no implicit additional obstacle protection below the MDA. Pilots must still respect any published stepdown fixes and the published MDA unless the visual cues stated 14 CFR § 91.175 are present, and they can visually acquire and avoid both lit and unlit obstacles once below the MDA. The presence of a VDA does not guarantee obstacle protection in the visual segment and does not change any of the requirements for flying a nonprecision approach.

Pilots may use the published angle and estimated/actual groundspeed to find a target rate of descent from the rate of descent table published in the back of the U.S. Terminal Procedures Publication. This rate of descent can be flown with the Vertical Velocity Indicator (VVI) in order to use the VDA as an aid to flying a stabilized descent. No special equipment is required.

In rare cases, the LNAV minima may have a lower HAT than minima with a glide path, due to the location of the obstacles and the nonprecision MAP. This should serve as a clear indication to the pilot that obstacles exist below the MDA, which must be seen in order to ensure adequate clearance. In those cases, the glide path may be treated as a VDA and used to descend to the LNAV MDA, as long as all of the rules for a nonprecision approach are applied at the MDA.

When there are obstacles in the visual area that could cause an aircraft to destabilize the approach between the MDA and touchdown, the IAP will not show a vertical descent angle in the profile view. The charts currently include the following statement: “Descent Angle NA” or “Descent Angle NA-Obstacles” [Figure 4-11B ].

Figure 4-11B. Descent Angle N/A..

Figure 4-11B: picture of page 23Figure 4-11B · page 23
Picture of the page from the copy saved here

OKLAHOMA CITY, OKLAHOMA AL-301 (FAA)

OKLAHOMA CITY, OKLAHOMA AL-301 (FAA)

CH 56202 W35A WAAS APP CRS 353° Rwy Idg TDZE Apt Elev 9800 1295 1277 OKLAHOMA CITY/ WILL ROGERS WORLD (OKC) RNAV (GPS) RWY 35L

V Baro-VNAV NA below -17°C (2°F). MALSR MISSED APPROACH: Climb to ASR DME/DME RNP - 0.3 NA. 3800 direct FILUM and hold. ATIS OKE CITY APP CON ROGERS TOWER GND CON CLNC DEL 125.85 124.6 266.8 119.35 269.45 121.9 348.6 124.35 MISSED APCH FIX 2164± 4NM

353% 1376 A 1845 FILUM A 1490 A 1881 A A RW35L A 1953 1631 1320±

30 NM to AKUYI 3200 3300 173° IMZUY (FAF) 1357± 3800 3200 16 NM o FiXIB 30 NM to FIXIB

30 NM to AKUYI 3200 3300 173° IMZUY (FAF) 1357± 3800 3200 16 NM o FiXIB 30 NM to FIXIB

AKUYI FIXIB -083° 353° 2800 263°

3200 NoPT 3200 NoPT 083° 263° SC-1, 10 MAR 2011 to 07 APR 2011 AKUYI (IAF) (5) (IF/IAF) CUBTU 353° 173° 4NM (5) 083° (IAF) FIXIB CUBTU 263°

[3200 ELEV 1295 D TDZE 1277

[3200 ELEV 1295 D TDZE 1277

1325

7800×150 1436 1364 3800 FILUM CUBTU Holding Pattern 4NM

3078 X75 81 361 ☆3 1340 9802 X 150 *LNAV only RW35L 0.8NM to RW35L IMZUY 2800 -353°- ←353° 173° GS 3.00° TCH 55 3200

1317 0.8 3.8NM 6NM A5 CATEGORY A B C D -35L 35R LPV DA 1530/50 253 (300-1) VNAV LNAV/ DA 1580/50 303 (300-1)

353° to RW35L REIL Rwys 13 and 31 TDZ/CL Rwy 35R LNAV MDA 1580/50 303 (300-1)

HIRL Rwys 17L-35R ond 17R-35L MIRL Rwy 13-31 CIRCLING 445 (500-1) 1740-1 465 (500-1) 1760-1 465 (500-1/2) 1760-1/2 565 (600-2) 1860-2 OKLAHOMA CITY, OKLAHOMA OKLAHOMA CITY/ WILL ROGERS WORLD (OKC) Amdt 2 11069 35° 24'N-97° 36'W RNAV (GPS) RWY 35L

Figure 4-12. RNAV GPS approach minima.

Figure 4-12: picture of page 24Figure 4-12 · page 24
Picture of the page from the copy saved here

Like flying any other IAP, the pilot must see and avoid any obstacles in the visual segment during transition to landing. A constant-rate descent has many safety advantages over non-precision approaches that require multiple level-offs at stepdown fixes or manually calculating rates of descent. A stabilized approach can be maintained from the FAF to the landing when a constant-rate descent is used. Additionally, the use of an electronic vertical path produced by onboard avionics can serve to reduce CFIT, and minimize the effects of visual illusions on approach and landing. Some countries even mandate the use of continuous descent final approaches (CDFAs) on non-precision approaches.

Wide Area Augmentation System

The Wide Area Augmentation System (WAAS) offers an opportunity for airports to gain ILS like approach capability without the purchase or installation of any ground-based navigation equipment at the airport. Today, WAAS is already being used at more than 900 runways across the United States to achieve minimums as low as 200 feet height above HAT/one-half mile visibility.

Benefits Of WAAS In The Airport Environment

WAAS is a navigation service using a combination of GPS satellites and the WAAS geostationary satellites to improve the navigational service provided by GPS. WAAS achieved initial operating capability (IOC) in 2003. The system is

owned and operated by the FAA and provided free of direct user charges to users across the United States and most of Canada and Mexico.

WAAS improves the navigational system accuracy for en route, terminal, and approach operations over all the continental United States and significant portions of Alaska, Canada, and Mexico. This new navigational technology supports vertically-guided instrument approaches to all qualifying runways in the United States. Vertically-guided approaches reduce pilot workload and provide safety benefits compared to non-precision approaches. The WAAS enabled vertically guided approach procedures are called LPV, which stands for “localizer performance with vertical guidance,”and provide ILS equivalent approach minimums as low as 200 feet at qualifying airports. Actual minimums are based on an airport’s current infrastructure, as well as an evaluation of any existing obstructions. The FAA plans to publish 300 WAAS approach procedures per year to provide service to all qualifying instrument runways within the NAS.

Advantages Of WAAS Enabled LPV Approaches

The advantages of WAAS enabled LPV approaches include:

• LPV procedures have no requirement for groundbased transmitters at the airport.

• No consideration needs to be given to the placement of navigation facility, maintenance of clear zones

Ranging sources

Status information

GBAS reference receivers

GBAS ground facility

Omnidirectional VHF data broadcast (VDB) signal

GPS satellites

Differential corrections, integrity data and path definition

Figure 4-13. GBAS architecture.

around the facility, or access to the facility for maintenance.

• LPV approaches eliminate the need for critical area limitations associated with an ILS.

• From a pilot’s viewpoint, an LPV approach looks and flies like an ILS, but the WAAS approach is more stable than that of an ILS.

• WAAS equipped users can fly RNAV and basic required navigation performance (RNP) procedures, as well as LPV procedures, and the avionics costs are relatively inexpensive considering the total navigation solution provided.

Figure 4-13: picture of page 25Figure 4-13 · page 25
Picture of the page from the copy saved here

RNAV (GPS) approach charts normally have four lines of approach minimums: LPV, LNAV/VNAV, LNAV, and Circling. Figure 4-12 shows how these minimums might be presented on an approach chart, with the exception of Ground Based Augmentation System (GBAS) Landing System (GLS). This enables as many GPS equipped aircraft to use the procedure as possible and provides operational flexibility if WAAS becomes unavailable. Some aircraft may only be equipped with GPS receivers so they can fly to the LNAV MDA. Some aircraft equipped with GPS and FMS (with approach-certified barometric vertical navigation, or Baro-VNAV) can fly to the LNAV/VNAV MDA. Flying a WAAS LPV approach requires an aircraft with WAAS-LPV avionics. If for some reason the WAAS service becomes unavailable, all GPS or WAAS equipped aircraft can revert to the LNAV MDA and land safely using GPS only, which is available nearly 100 percent of the time. Some locations will have an LP line of minima on an RNAV (GPS) approach chart; but the use of LP is being phased out. At locations with obstacle penetrations in the missed approach segment, there might be two lines of minima for the same type of navigation- one line with higher approach minima without a specified climb gradient and another line with lower approach minima with a specified climb gradient in the event of missed approach.

LPV identifies WAAS approach with vertical guidance (APV) approach minimums with electronic lateral and vertical guidance capability. LPV is used for approaches constructed with WAAS criteria where the value for the vertical alarm limit is more than 12 meters and less than 50 meters. WAAS avionics equipment approved for LPV approaches is required for this type of approach. The lateral guidance is equivalent to localizer accuracy, and the protected area is considerably smaller than the protected area for the present LNAV and LNAV/VNAV lateral protection. Aircraft can fly this minima line with a statement in the AFM that the installed equipment supports LPV approaches. In Figure 4-12, notice the WAAS information shown in the top left corner of the pilot briefing information on the chart depicted. Below the term WAAS is the WAAS channel number (CH 56202), and

the WAAS approach identifier (W35A), indicating Runway 35L in this case, and then a letter to designate the first in a series of procedures to that runway [Figure 4-12].

LNAV/VNAV identifies APV minimums developed to accommodate an RNAV IAP with vertical guidance, usually provided by approach certified Baro-VNAV, but with vertical and lateral integrity limits larger than a precision approach or LPV. Many RNAV systems that have RNP 0.3 or less approach capability are specifically approved in the AFM. Airplanes that are commonly approved in these types of operations include Boeing 737NG, 767, and 777, as well as the Airbus A300 series. Landing minimums are shown as DAs because the approaches are flown using an electronic glide path. Other RNAV systems require special approval. In some cases, the visibility minimums for LNAV/VNAV might be greater than those for LNAV only. This situation occurs because DA on the LNAV/VNAV vertical descent path is farther away from the runway threshold than the LNAV MDA missed approach point.

Also shown in Figure 4-12, is the LNAV minimums line. This minimum is for lateral navigation only, and the approach minimum altitude is published as a MDA. LNAV provides the same level of service as the present GPS stand alone approaches. LNAV supports the following systems: WAAS, when the navigation solution will not support vertical navigation; and GPS navigation systems which are presently authorized to conduct GPS approaches.

Circling minimums that may be used with any type of approach approved RNAV equipment when publication of straight-in approach minimums is not possible.

Ground-Based Augmentation System (GBAS)

The United States version of the Ground-Based Augmentation System (GBAS) has traditionally been referred to as the Local Area Augmentation System (LAAS). The worldwide community has adopted GBAS as the official term for this type of navigation system. To coincide with international terminology, the FAA is also adopting the term GBAS to be consistent with the international community. GBAS is a ground-based augmentation to GPS that focuses its service on the airport area (approximately a 20–30 mile radius) for precision approach, DPs, and terminal area operations. It broadcasts its correction message via a very high frequency (VHF) radio data link from a ground-based transmitter. GBAS yields the extremely high accuracy, availability, and integrity necessary for Category I, II, and III precision approachesand provides the ability for flexible, curved approach paths. GBAS demonstrated accuracy is less than one meter in both the horizontal and vertical axis. [Figure 4-13]

Figure 4-14. GLS approach at Newark, New Jersey.

Figure 4-15. RNAV RNP approach procedure with curved flight tracks.

Figure 4-14: picture of page 27Figure 4-14 · page 27
Picture of the page from the copy saved here

Figure 4-16. North Platte Regional (KLBF), North Platte, Nebraska, RNAV (GPS) RWY 30.

The GBAS augments the GPS to improve aircraft safety during airport approaches and landings. It is expected that the end state configuration will pinpoint the aircraft’s position to within one meter or less with a significant improvement in service flexibility and user operating costs.

GBAS is comprised of ground equipment and avionics. The ground equipment includes four reference receivers, a GBAS ground facility, and a VHF data broadcast transmitter. This ground equipment is complemented by GBAS avionics installed on the aircraft. Signals from GPS satellites are received by the GBAS GPS reference receivers (four receivers for each GBAS) at the GBAS equipped airport. The reference receivers calculate their position using GPS. The GPS reference receivers and GBAS ground facility work together to measure errors in GPS provided position.

Figure 4-16: picture of page 29Figure 4-16 · page 29
Picture of the page from the copy saved here

The GBAS ground facility produces a GBAS correction message based on the difference between actual and GPS calculated position. Included in this message is suitable integrity parameters and approach path information. This GBAS correction message is then sent to a VHF data broadcast (VDB) transmitter. The VDB broadcasts the GBAS signal throughout the GBAS coverage area to avionics in GBAS equipped aircraft. GBAS provides its service to a local area (approximately a 20–30 mile radius). The signal coverage is designed support the aircraft’s transition from en route airspace into and throughout the terminal area airspace.

The GBAS equipment in the aircraft uses the corrections provided on position, velocity, and time to guide the aircraft safely to the runway. This signal provides ILS look alike guidance as low as 200 feet above touchdown. GBAS will eventually support landings all the way to the runway surface. Figure 4-14 is an example of a GBAS (LAAS) approach into Newark, New Jersey.

Required Navigation Performance (RNP)

The operational advantages of RNP include accuracy, onboard performance monitoring and alerting which provide increased navigation precision and lower minimums than conventional RNAV. RNP DAs can be as low as 250 feet with visibilities as low as 3/4 SM. Besides lower minimums, the benefits of RNP include improved obstacle clearance limits, as well as reduced pilot workload. When RNP capable aircraft fly an accurate, repeatable path, ATC can be confident that these aircraft are at a specific position, thus maximizing safety and increasing capacity.

To attain the benefits of RNP approach procedures, a key component is curved flight tracks. Constant radius turns

around a fix are called “radius-to-fix legs (RF legs).”These turns, which are encoded into the navigation database, allow the aircraft to avoid critical areas of terrain or conflicting airspace while preserving positional accuracy by maintaining precise, positive course guidance along the curved track. The introduction of RF legs into the design of terminal RNAV procedures results in improved use of airspace and allows procedures to be developed to and from runways that are otherwise limited to traditional linear flight paths or, in some cases, not served by an IFR procedure at all. Navigation systems with RF capability are a prerequisite to flying a procedure that includes an RF leg. Refer to the notes box of the pilot briefing portion of the approach chart in Figure 4-15.

In the United States, operators who seek to take advantage of RNP approach procedures must meet the special RNP requirements outlined in FAA AC 90-101, Approval Guidance for RNP Procedures with Authorization Required (AR). Currently, most new transport category airplanes receive an airworthiness approval for RNP operations. However, differences can exist in the level of precision that each system is qualified to meet. Each individual operator is responsible for obtaining the necessary approval and authorization to use these instrument flight procedures with navigation databases.

RNAV Approach Authorization

Like any other authorization given to air carriers and Part 91 operators, the authorization to use VNAV on a conventional non-precision approach, RNAV approaches, or LNAV/VNAV approaches is found in that operator’s OpSpecs, AFM, or other FAA-approved documents. There are many different levels of authorizations when it comes to the use of RNAV approach systems. The type of equipment installed in the aircraft, the redundancy of that equipment, its operational status, the level of flight crew training, and the level of the operator’s FAA authorization are all factors that can affect a pilot’s ability to use VNAV information on an approach.

Because most Part 121, 125, 135, and 91 flight departments include RNAV approach information in their pilot training programs, a flight crew considering an approach to North Platte, Nebraska, using the RNAV (GPS) RWY 30 approach shown in Figure 4-16, would already know which minimums they were authorized to use. The company’s OpSpecs, FOM, and the AFM for the pilot’s aircraft would dictate the specific operational conditions and procedures by which this type of approach could be flown.

There are several items of note that are specific to this type of approach that should be considered and briefed. One is the terminal arrival area (TAA) that is displayed in the

approach planview. TAAs, discussed later in this chapter, depict the boundaries of specific arrival areas, and the MIA for those areas. The TAAs should be included in an IAP briefing in the same manner as any other IFR transition altitude. It is also important to note that the altitudes listed in the TAAs should be referenced in place of the MSAs on the approach chart for use in emergency situations.

In addition to the obvious differences contained in the planview of Figure 4-16, RNAV (GPS) approach procedure example, pilots should be aware of the issues related to Baro-VNAV and RNP . The notes section of the procedure in the example contains restrictions relating to these topics.

RNP values for each individual leg of the procedure, defined by the procedure design criteria for containment purposes, are encoded into the aircraft’s navigation database. Applicable landing minimums are shown in a normal manner along with the associated RNP value in the landing minimums section.

RNP required sensors, FMS capabilities, and relevant procedure notes are included in the Pilot Briefing Information procedure notes section. [Figure 4-15] RNP AR requirements are highlighted in large, bold print. RNP procedures are sequenced in the same manner as RNAV (GPS) procedures. Procedure title “RNAV” includes parenthetical “(RNP)” terminology. RF legs can be used in any segment of the procedure (transition, intermediate, final, or missed approach). RF leg turn directions (left or right) are not noted in the planview because the graphic depiction of the flight tracks is intuitive. Likewise, the arc center points, arc radius, and associated RF leg performance limits, such as bank angles and speeds are not depicted because these aircraft performance characteristics are encoded in the navigation database. RNP values for each individual leg of the procedure, defined by the procedure design criteria for containment purposes, are encoded into the aircraft's navigation database. Applicable landing minimums are shown in a normal manner along with the associated RNP value in the landing minimums section.

When more than one set of RNP landing minimums is available and an aircrew is able to achieve lower RNP through approved means, the available (multiple) sets of RNP minimums are listed with the lowest set shown first; remaining sets shown in ascending order, based on the RNP value. On this particular procedure, lateral and vertical course guidance from the DA to the Runway Waypoint (LTP) is provided by the aircraft’s FMS and onboard navigation database; however, any continued flight below the DA to the landing threshold is to be conducted under VMC. [Figure 4-15]

Baro-VNAV Baro-VNAV is an RNAV system function that uses barometric altitude information from the aircraft’s altimeter to compute and present a vertical guidance path to the pilot. The specified vertical path is computed as a geometric path, typically computed between two waypoints or an angle based computation from a single waypoint. Operational approval must also be obtained for Baro− VNAV systems to operate to the LNAV/VNAV minimums. Baro−VNAV may not be authorized on some approaches due to other factors, such as no local altimeter source being available. Baro−VNAV is not authorized on LPV procedures.

For the RNAV (GPS) RWY 30 approach, the note “DME/ DME RNP-0.3 NA” prohibits aircraft that use only DME/ DME sensors for RNAV from conducting the approach. [Figure 4-16]

Because these procedures can be flown with an approach approved RNP system and “RNP” is not sensor specific, it was necessary to add this note to make it clear that those aircraft deriving RNP 0.3 using DME/DME only are not authorized to conduct the procedure.

The least accurate sensor authorized for RNP navigation

Figure 4-17. Example of LNAV and Circling Minima lower than LNAV/VNAV DA. Harrisburg International RNAV (GPS) Runway 13.

Figure 4-18. Explanation of Minima.

Figure 4-17: picture of page 31Figure 4-17 · page 31
Picture of the page from the copy saved here

NOT FOR NAVIGATION

NOT FOR NAVIGATION

NOT FOR NAVIGATION

C

EC-3, 18 NOV 2010 to 16 DEC 2010

Airport sketch

EC-3, 18 NOV 2010 to 16 DEC 2010

E

Figure 4-19. Airport sketch and diagram for Chicago O'Hare International.

is DME/DME. The necessary DME NAVAID ground infrastructure may or may not be available at the airport of intended landing. The procedure designer has a computer program for determining the usability of DME based on geometry and coverage. Where FAA flight inspection successfully determines that the coverage and accuracy of DME facilities support RNP, and that the DME signal meets inspection tolerances, although there are none currently published, the note “DME/DME RNP 0.3 Authorized” would be charted. Where DME facility availability is a factor, the note would read, “DME/DME RNP 0.3 Authorized; ABC and XYZ required,”meaning that ABC and XYZ DME facilities are required to assure RNP 0.3.

Hot and Cold Temperature Limitations

Figure 4-19: picture of page 32Figure 4-19 · page 32
Picture of the page from the copy saved here

Continue reading ↓ 120 of 265 passages shown