• FAA Order 8400.33 (RNP-4): Paragraph 9 (Operational Requirements) and paragraph 10 (Operating Practices and Procedures, Training Programs).
• ICAO PBN Manual, Volume II, Part B, Chapter 1 (RNP-10): Paragraphs 1.3.4,
1.3.5 and 1.3.6.
• ICAO PBN Manual, Volume II, Part C, Chapter 1 (RNP-4): Paragraphs 1.3.4, 1.3.5 and 1.3.6.
c. LRNS Failure or Malfunction after Entry onto WATRS Plus Oceanic Routes or Areas. The following is WATRS Plus CTA policy for LRNS failure or malfunction en route:
• To conduct operations as an RNP-10 or RNP-4 operator/aircraft, at least two RNP-10 or RNP-4 authorized LRNSs will be operational at entry on to oceanic route segments or areas in the WATRS Plus CTAs.
• After entry on to an oceanic route segment or area within the WATRS Plus CTAs if an LRNS fails or malfunctions and only one LRNS remains operational, the pilot will inform ATC. ATC will acknowledge and monitor the situation. The aircraft may continue on the cleared route provided that, in the pilot’s judgment, the remaining LRNS will enable the aircraft that is navigated within approximately 10 NM of the cleared route centerline (CL). If that is not the case, then the paragraph below applies.
• If the pilot cannot, in their judgment, navigate the aircraft within approximately 10 NM of the cleared route CL:
• The pilot will advise ATC of the situation and coordinate a course of action.
• The pilot will consider the best option to maintain the safety of the operation
(e.g., continuing on route or turning back).
• Obtain, whenever possible, an ATC clearance before deviating from cleared route or FL and keep ATC advised.
• ATC will establish an alternative separation standard as soon as practicable, coordinate the safest course of action with the pilot and monitor the situation.
• If the pilot cannot accomplish coordination with ATC within a reasonable period of time, the pilot should consider climbing or descending 500 feet, broadcasting action on 121.5 and advising ATC as soon as possible.
d. In-flight Contingency Procedures (e.g., Rapid Descent, Turn-Back, Diversion).
Pilot training/knowledge programs must emphasize in-flight contingency procedures for oceanic airspace now published in FAA notices, posted on the WATRS Plus Web site and published in ICAO Document 4444. The published procedures are applicable to the WATRS Plus CTA Par 7-3 Page 71
reduction of lateral separation from 90 NM to 50 NM. The full text of in-flight contingency procedures is on the WATRS Plus Web page under “Operating Policy” in section 2.
e. Special Emphasis: Maneuvering to Avoid Convective Weather in a 50 NM Separation Environment. WATRS Plus operations require pilots to maneuver (deviate) around convective weather on a regular basis. Therefore, emphasize weather deviation procedures in accordance with the following:
• Pilot training/knowledge programs and operations manuals or comparable operations documents must emphasize weather deviation procedures as published in FAA notices and ICAO Document 4444 and posted under “Operating Policy” in section 2 of the WATRS Plus Web site. RNP-10 and RNP-4 job aids address weather deviation procedures.
• It is imperative that pilots keep ATC advised of their intentions during the initial weather avoidance maneuver and any subsequent maneuvers to avoid convective weather.
• Pilots must be aware of the provision to climb or descend 300 feet (depending on the direction of flight and direction of deviation from track) to mitigate the chance of conflict with other aircraft when forced to deviate without a clearance.
• The FAA recommends that, if equipped, the Airborne Collision Avoidance System (ACAS) (Traffic Alert and Collision Avoidance Systems (TCAS)) be operational.
ACAS provides a valuable tool to alert the pilot to the presence and proximity of nearby aircraft in weather deviation situations.
f. Strategic Lateral Offset Procedure (SLOP). Pilots should use SLOP procedures in the course of regular oceanic operations. FAA notices and ICAO Document 4444, posted under “Operating Policy” in section 2 of the WATRS Plus Web site, contain published SLOP procedures. The RNP-10 and RNP-4 job aids address SLOP.
g. Pilot Report of Non-RNP 10 Status. The pilot will report the lack of RNP-10 or RNP-4 status in accordance with subparagraph c above:
• When the operator/aircraft does not have RNP-10 or RNP-4 authorization; and
• When an operator/aircraft previously granted RNP-10 or RNP-4 authorization is operating with only one operational LRNS.
h. Flight of Aircraft Previously Authorized RNP-10 or RNP-4 with One LRNS Operational.
(1) WATRS Oceanic Routes. To the maximum extent possible, operators that are authorized RNP-10 or RNP-4 should operate on WATRS Plus oceanic routes in compliance with those standards. If the situation warrants, however, operators may fly an aircraft on WATRS Plus oceanic routes with one LRNS operational. The intent of this policy is to allow operators to fly aircraft to a maintenance facility for repair. For U.S. operators conducting operations under Page 72 Par 7-3
Title 14 of the Code of Federal Regulations (14 CFR) part 121, 125, or 135, OpSpecs paragraph B054 (Class II Navigation Using Single Long-Range Navigation System (S-LRNS), applies.
(2) Follow ICAO Flight Plan Item 18. In this situation, operators will follow the practices detailed in subparagraph c (i.e., ICAO flight plan Item 18 annotation and pilot report to ATC of aircraft Non-RNP 10 status). The aircraft will receive treatment as a Non-RNP 10 aircraft and have the appropriate lateral separation applied to them.
i. Provisions for Accommodation of Non-RNP 10 Aircraft (Aircraft Not Authorized RNP-10 or RNP-4).
(1) ICAO Flight Plan Item 18 Annotations for Non-RNP 10 Operators. Operators of Non-RNP 10 aircraft must annotate ICAO flight plan Item 18 as follows:
• “STS/NONRNP10” (no space between letters and numbers).
• Pilots of Non-RNP 10 aircraft flight planned to operate or operating on WATRS Plus “L” and “M” routes in the Atlantic portion of the Miami Oceanic CTA and the San Juan CTA/FIR must report the lack of authorization by stating “Negative RNP 10.” (New York Oceanic airspace does not require these reports). The following require reports when:
• In the Atlantic portion of the Miami Oceanic CTA and the San Juan CTA/FIR;
• On initial call to ATC; and
• In read back of clearance to descend from FL 410 and above.
(See subparagraph (5) below).
(2) RNP-10 or RNP-4 Authorization. Operators of Non-RNP 10 aircraft will not annotate ICAO flight plan Item 18 (Other Information) with “NAV/RNP10” or “NAV/RNP4,” as shown in paragraph h, if they have not obtained RNP-10 or RNP-4 authorization.
(3) Non-RNP 10 Operators/Aircraft in WATRS Plus Airspace. Non-RNP 10 operators/aircraft will be able to file any route at any altitude in WATRS Plus airspace. They will receive clearance to operate on their preferred routes and altitudes as traffic permits. Aircraft that are authorized RNP-10 or RNP-4, however, will have a better opportunity of obtaining their preferred altitude and route because of the 50 NM lateral separation standard applied to those aircraft. Non-RNP 10 aircraft do not receive 50 NM lateral separation.
(4) Climbing or Descending for Non-RNP 10 Aircraft. Non-RNP 10 aircraft will retain the option of climbing to operate at altitudes above those where traffic is most dense
(i.e., at/above FL 410). To minimize the chance of conflict with aircraft on adjacent routes, Non-RNP 10 aircraft should plan on completing their climb to or descent from higher FLs within radar coverage.
Par 7-3 Page 73
(5) Aircraft Clearance. All aircraft can enhance their opportunity to receive a clearance on their preferred route and altitude if they operate at non-peak hours, approximately 0100 to 1100 UTC.
j. RNP-10 or RNP-4 Authorization: Policy and Procedures for Aircraft and Operators. In accordance with ICAO guidance, RNP-10 and RNP-4 are the only Nav Specs applicable to oceanic and remote area operations (see note below). Other RNAV and RNP Nav Specs are applicable to continental en route, terminal area, and approach operations.
NOTE: “RNP navigation specification” (e.g., RNP-10) is the term adopted in the new ICAO PBN Manual (Doc 9613). It replaces the term “RNP type.”
k. Responsible State Authority (ICAO Guidance). The following is ICAO guidance on the state authority responsible for authorizations such as RNP-10, RNP-4, and RVSM.
(1) International Commercial Operators. The State of Registry makes the determination that the aircraft meets the applicable RNP requirements. The State of Operator issues operating authority (e.g., OpSpecs).
(2) IGA Operators. The State of Registry makes the determination that aircraft meets the applicable RNP requirements and issues operating authority (e.g., LOA).
l. FAA Guidance. The guidance and direction of FAA Order 8400.12, RNP-10 Operational Approval, current edition, is used to grant RNP-10 authorization to operators and aircraft for which the FAA is responsible. FAA Order 8400.33, Procedures For Obtaining Authorization For RNP 4 Oceanic/Remote Area Operations, current edition, is used to authorize RNP-4. The FAA RNP-10 and RNP-4 orders are consistent with the ICAO PBN Manual guidance discussed below. The WATRS Plus Web page contains posted FAA and ICAO documents.
m. ICAO PBN Manual (New Doc 9613). In a letter to states dated April 27, 2007, ICAO urged states to use the ICAO PBN Manual to establish approval policies and processes for RNP and RNAV operations. Volume II, part B, chapter 1 provides RNP-10 guidance. RNP-4 guidance is in volume II, part C; chapter 1. The ICAO State Letter with volume II attached is on the WATRS Plus Web page.
n. RNP-10 and RNP-4 Job Aids. Operators and authorities should use the RNP-10 or RNP-4 job aids posted on the WATRS Plus Web page. These job aids address the operational and airworthiness elements of aircraft and operator authorization and provide references to appropriate documents. One set of RNP-10 and RNP-4 job aids provides references to FAA documents and another set provides references to ICAO documents. The job aids provide a method for operators to develop and authorities to track the operator/aircraft program elements required for RNP-10 or RNP-4 authorization.
o. RNP-10 Time Limit for INS or IRU Only Equipped Aircraft. Operators should review their AFM, AFMS, or other appropriate documents and/or contact the airplane or avionics manufacturer to determine the RNP-10 time limit applicable to their aircraft. They will then need to determine its effect, if any, on their operation. Unless otherwise approved, the basic Page 74 Par 7-3
RNP-10 time limit is 6.2 hours between position updates for aircraft on which INSs or IRUs provide the only source of long-range navigation. Extended RNP-10 time limits of 10 hours and greater is already approved for many IRU systems.
p. Flight Planning Requirements.
(1) ICAO Flight Plan Requirement. File ICAO flight plans for operations on oceanic routes and areas in the WATRS Plus CTAs.
(2) ICAO Flight Plan AFTN Addressing for Operations in the New York Oceanic CTA/FIR (Including WATRS). All flights entering the New York Oceanic CTA/FIR will address flight plans to KZWYZOZX. Flights entering the New York Oceanic CTA/FIR from domestic U.S. airspace or Bermuda must address flight plans to both KZWYZOZX and KZNYZQZX. If operators do not address flight plans to KZWYZOZX, they may not have 50 NM lateral separation applied to them.
(3) Informing ATC and Keying Ocean21 Automation of RNP-10 or RNP-4 Authorization. To inform ATC and to key Ocean21 automation that they have obtained RNP-10 or RNP-4 authorization and are eligible for 50 NM lateral separation, operators will:
• Annotate ICAO flight plan Item 10 (Equipment) with the letters “R” and “Z” and;
• Annotate Item 18 (Other Information) with, as appropriate, “NAV/RNP10” or “NAV/RNP4” (no space between letters and numbers).
(4) Application of 50 NM Lateral Separation to Operators/Aircraft.
Operators/aircraft that annotate the ICAO flight plan in accordance with this policy have separation of 50 NM lateral applied only to them. Operators that have not obtained RNP-10 or RNP-4 authorization will not annotate ICAO flight plan Item 18 (Other information) with “NAV/RNP10” or “NAV/RNP4.”
NOTE: On the ICAO flight plan, the letter “R” indicates that the aircraft will maintain the appropriate RNP navigation specification for the entire flight through airspace where ICAO prescribes RNP. The letter “Z” indicates that information explaining aircraft navigation and/or communication capability is in Item 18.
Par 7-3 Page 75
Page 76 Par 7-3 FIGURE 5. WEST ATLANTIC ROUTE SYSTEM PLUS OCEANIC AIRSPACE
CHAPTER 8. SOUTH AMERICA AND THE CARIBBEAN
8-1. INTRODUCTION. International Civil Aviation Organization (ICAO) standards and phraseology are the official agreed-upon standards used by all countries on international flights.
With that in mind, the South America region consists of those states in the South American continent. This regional guide follows the ICAO standards and phraseology.
8-2. NAVIGATION. Operators use Class I navigation (very high frequency (VHF) Omnidirectional Range (VOR)/automatic direction finder (ADF)) procedures on some of the South American routes. A few routes operate outside the 200 mile range of standard airways radio navigation facilities. They require the use of Class II (global positioning system (GPS)/inertial reference systems (IRS)) navigation procedures. Between JFK, MIA, and South American destinations, the flight plan should specify Class II route segments for Area Navigation (RNAV)-equipped aircraft. The flight plan should identify that portion of the route where you need to accomplish Class II procedures. You should also provide a West Atlantic/Caribbean plotting chart. This would normally be on routes from JFK to South America or the Caribbean. (Minimum required equipment for operation in Class II airspace is in Chapter 10.) En route Navigational Aid (NAVAID) outages, however, have the potential for turning almost any long-range international flight into one requiring Class II navigation procedures. The FAA considers all long-range flights (those with stage lengths longer than 1,000 nautical miles (NM) outside the United States) Class II operations. As a result, all flights exceeding 1,000 NM outside North America should receive basic Class II navigation checks.
These navigation checks would include the following:
• Magnetic compass deviation check.
• Air data inertial reference unit (ADIRU)/flight management computer (FMC) gross error check.
• Navigation source validation.
• High frequency (HF) radio check.
NOTE: NAVAIDs in the Caribbean and South America, both VORs and non-directional radio beacons (NDB), may not operate continuously. An asterisk (*) preceding the frequency indicates this. Operators may turn them off when they do not expect traffic. Thus, if a NAVAID appears to be off the air, operators may make a request to the controller to reinstate operation.
NDBs shown on the en route chart with an underlined alpha identifier
(e.g., ABC) requires adding a B (for beat frequency oscillator (BFO)) to the frequency (e.g., 321B) for proper tuning on the NAV/RAD page.
8-3. COMMUNICATIONS. Operators use standard ICAO terminology throughout the Caribbean and South America regions. In both regions, they monitor an air-to-air frequency of
123.45 on very high frequency (VHF), while 121.5 is monitored on the other VHF when not in VHF contact. Flights in this area can often exchange route information ahead. Flights should do this even though air traffic control (ATC) has approved an altitude change. Altitude changes are the most dangerous maneuvers in South America. Listen closely to other aircraft position reports.
Acknowledge the pilot making those reports. Several close calls have occurred with flights Par 8-1 Page 77
scheduled to be at the same fix at the same time and altitude. You must help provide your own traffic separation on these routes.
a. Communication with Dispatcher. Maintaining a flight watch or operational control capability with dispatch is mandatory. In addition to re-dispatch messages, the dispatcher must be able to contact you at any time for weather or security issues. If Aircraft Communications Addressing and Reporting System (ACARS) is operative on either VHF or satellite communication (SATCOM) Voice, it will fulfill this requirement. However, to ensure coverage, the FAA strongly recommends the flight establish and maintain contact with a high frequency (HF) Long Distance Operational Control (LDOC) facility. Remember that the HF center frequencies used in South America are not general purpose (GP) facilities and the flight cannot use them for company communication. The facilities used throughout South America are New York Aeronautical Radio, Inc. (ARINC), Houston Radio, Lima Flight Support, and the very powerful Cedar Rapids Radio. Cedar Rapids Radio should be the primary LDOC facility in South America and the Caribbean. In South America, Lima Flight Support is secondary and in the Caribbean, New York ARINC is secondary.
b. HF LDOC Frequencies and Reception. Cedar Rapids Radio (6637, 8933, 10075, 13348) has enough power to have an LDOC link all the way into deep South America. Try to raise them first for HF and Selective Call (SELCAL) check. If that fails, call ARINC on VHF
129.35 for working HF frequency. If that fails, time WWV on 5000, 10000 or 15000 and listen for time signal to confirm HF reception. Work on SELCAL check after airborne. Both HFs should be operational for dispatch (14 CFR part 91, § 91.511). Same HF frequencies coming out of EZE (try all 4 before giving up).
c. Company Flight Watch Communication. When contacting the LDOC GP operator to establish company flight watch communications, ask for primary and secondary frequencies and also obtain a SELCAL check. We assume that the flight will be monitoring the primary facility via SELCAL. If you must use a secondary facility, ask the GP operator to send a message to company to indicate the monitored facility (e.g., “Please relay to company that we will be monitoring Lima Flight Support.”).
d. Communicating Between Florida and San Juan. In the Caribbean, between Florida and San Juan, normal VHF ARINC communications are available on 130.7. An automatic dial-up feature is available on 130.7 in certain remote areas by keying the mike three times in 5 seconds. The ARINC operator should respond on the frequency.
e. Position Reports. Most airline dispatch offices would like to have position reports for flights to and from South America every 2 hours following departure from the U.S. or the South American departure station. These informal reports should include time over your chosen fix, altitude, fuel and weather conditions. You may use the MFD (multifunction display) “POSITION REPORT” or “MESSAGE TO COMPANY” format. Both reports go directly to the dispatcher. If SATCOM Voice ACARS is unavailable, use HF LDOC. In-flight blind broadcasts on frequency
123.45 are still in use in parts of South America.
Page 78 Par 8-3
f. Language.
(1) Communications with ATC. Controllers and radio operators speak English in the Caribbean and South America, and the equipment they use may have excessive static. Those who deliver airway clearances and taxi clearances seem to be the most difficult to understand. Use the following suggestions to avoid problems:
• Use standard phraseology and speak slowly and clearly. Politeness and patience are imperative.
• Make a special effort to have all crewmembers listen to ATC when able.
• Review en route charts and put names to the abbreviated identifiers on the Flight Plan Forecast to be able to recognize them in a verbal clearance.
• Reading back the phonetic alphabet for NAVAID identifiers, however, is often better than trying to pronounce the NAVAID name.
• Do not rely on ATC to correct clearance read-back errors. Continue to query the controller when in doubt.
(2) Requesting and Receiving Clearances. A radio call to station operations with a request to call the tower and clarify an airways clearance is an option. After reviewing the routing, with the Standard Instrument Departures (SID) and runway in use, write down the anticipated clearance before calling delivery. Then check off the items as the controller reads them. The sequence may be different than what you expect. Ask the controller to repeat any misunderstood items.
FIGURE 6. IN-FLIGHT BROADCAST PROCEDURES OVER INTERTROPICAL
CONVERENCE ZONE 19
INTER-TROPICAL
CONVERGENCE ZONE
INTER-TROPICAL
CONVERGENCE ZONE UL304UL304INFLIGHT BROADCASTPROCEDURESINFLIGHT BROADCASTPROCEDURES 19
Par 8-3 Page 79
g. ATC. There are significant differences in ATC facilities, procedures, and controller capability between countries. Controllers in the Caribbean and South America assume that pilots are masters of their fate and know what to do. Keep in mind that the clearance you ask for is the one you will receive. It is almost always prudent to stay on your route of flight, rather than asking for a reroute or direct. Also, never accept a clearance that you cannot complete
(e.g., “request 250 knots to the outer marker”). Let them know what you will accept, and almost always, they will grant you a clearance.
(1) Caribbean Flight Information Regions (FIR). In the Caribbean, you will cross multiple FIRs within a relatively short distance and you must use the associated FIR procedures for crossing. As a technique, locate all the communications boxes on the Jeppesen, LIDO, or Department of Transportation (DOT) charts, which give FIR guidance. They may not be anywhere near your route of flight. Jeppesen has recently begun using heavier marking around the sector frequency boxes, using a small telephone symbol as the line.
(2) Position Reports. To reduce the possibility of a communication error, remember that the controllers use a very precise order in receiving your position report. You must report your position in the proper format:
• Call sign.
• Position.
• Time.
• Altitude.
• Estimate for next fix.
• Name of succeeding fix.
(3) Controller Response. The controller’s most common response to your report is, “Aircraft 985, roger report ISANI.” Listen closely since the controllers may have you omit a report over intervening fixes. Some controllers and other foreign carriers may insert the word “position” before the name of a fix (e.g., “Aircraft 985, roger, report position ISANI” or “Aircraft 985, say estimate position TESAL.”).
(4) Phrasing Responses. Avoid taking shortcuts in communications or the inclusion of non-essential phrases or American colloquialisms (e.g., “Aircraft 984 getting moderate chop at three five oh and we’d like to go up to three nine oh”). The controller will probably respond to this request with silence or, even worse, a clearance for something totally unrelated to your request. Keep it simple: “Aircraft 984 requesting flight level three niner zero.” Expect a response such as “Aircraft 984, standby for FL 390.” Be careful not to interpret that as a clearance to climb to flight level (FL) 390. It is quite common for the controller to respond to your first request for an altitude change with “Standby FL 390.” They may have to check down line, maybe by antiquated teletype, to see if they can grant your request. Read back all clearances and report leaving any assigned altitude.
(5) Communication Difficulties. In South America, when out of reach of VHF, it may be possible to contact other aircraft on 123.45 and ask if they are talking to anyone on VHF. You can try that frequency, or ask them to relay a request or position report for you. Please volunteer to do the same for others having communication difficulty. It is also wise to get the flight Page 80 Par 8-3
numbers of the flight passing in the opposite direction to you. All flights that pass over each other between north and mid South America are great resources for weather and flight conditions along your route of flight.
(6) VHF and HF Communications. Most ATC communications is on VHF. From Los Angeles to San Salvador, expect VHF communications throughout the flight with radar coverage for most of Mexico. However, areas where VHF communication with ATC is not available require HF radios. There is a small area of central Brazil that may require the use of HF to contact Belem or Manaus centers. Do not give up on VHF too soon; the controllers may take 30 to 60 seconds to answer as they may be handling another flight on a different frequency. If the use of HF is necessary, a center that is nowhere near your location may answer. After making several calls to either Belem or Manaus, Maiquetia may take your call. They will be able to relay your position report to the proper center. Cedar Rapids Radio has very good reception throughout Central and South America.
h. ACARS. There are two VHFs in use in the Caribbean: 131.55 (ARINC/ACARS) and
131.72 (Societe International de Télécommunications Aeronautiques (SITA)/Air/ground Communications (AIRCOM)). In South America, operators use 131.55. In addition, ACARS will use SATCOM Voice if you cannot find an active VHF frequency. With these choices, ACARS can downlink messages to the company without any problem. Problems may arise, however, when dispatch tries to uplink messages to the aircraft via one of the three VHF networks.
Messages may be lost as the aircraft transitions from one VHF network to another with the message then returned to the originator as “unable to deliver.”
(1) HF LDOC Link. Until SATCOM Voice is proven reliable in South America, it is imperative to establish an HF LDOC link with the company to maintain the required operational control and ensure timely receipt of important messages. In the Caribbean, there is good ACARS coverage throughout.
(2) ACARS Gap and Approaching Top of Descent (TOD). An ACARS gap crops up occasionally about 200 to 400 miles north of Buenos Aires (EZE). Neither VHF nor SATCOM Voice will work and it is a good reason to keep confirming an LDOC link with Cedar Rapids Radio. Downlink any messages to the station prior to reaching this area. As the TOD approaches, ACARS should return. If all else fails, a call to station operations will work at TOD.
Par 8-3 Page 81
Page 82 Par 8-3 FIGURE 7. AIRCRAFT COMMUNICATIONS ADDRESSING AND REPORTING
SYSTEM GAP 16 UL304UL304
COMMUNICATIONS GAP
COMMUNICATIONS GAP
CLASS II FOR
INS AIRCRAFT
CLASS II FOR
INS AIRCRAFT 16
8-4. COLLISION AVOIDANCE. Do not assume ATC is providing aircraft separation. Listen to the ATC position reports of other aircraft. Monitor the Traffic Alert and Collision Avoidance Systems (TCAS) display on the navigation display (ND) and listen to the blind broadcast frequency. When possible, pull up the “HOWGOZIT” for other company flights and compare estimates at common fixes. Turn on a landing light when changing altitudes or when passing opposite direction traffic. Keep the lights in the cockpit at a level that does not impair distant vision. The most important glass component in any aircraft is the windshield. If an effort to avoid collision requires immediate action, respond to the TCAS RA. Consider setting one transponder TCAS to “ABV” and one to “BLW” for greatest traffic coverage. Finally, never accept a wrong way altitude. (Normal levels are 290, 330: 370, 410 southbound, 310, 350, 390, 430 northbound but some exceptions occur at eastbound/westbound magnetic course changeovers indicated with < E.)
8-5. DISPATCH. When comparing South American operations to other international remote areas, the following factors must enter into your planning:
• Weather reporting and forecasting are not as accurate as other parts of the world.
• Weather forecasts for en route airports may be 5 to 6 hours old.
• Alternate airports are unfamiliar to flightcrews as well as the language spoken.
• Weather deviations, to some extent, occur on nearly every flight.