Brazil Division
| ICAO | Name | ATC Facilities | SSR | Type of Operation |
|---|---|---|---|---|
| SBSP | Congonhas | TWR / GND / DEL | 0201-0210 | VFR / IFR |
Purpose
This document describes the procedures that must be followed by the Air Traffic Service (ATS) at Congonhas Airport. The procedures described here are supplementary to the DECEA procedures.
Scope
Those procedures must be followed and applied by all members that are operating at SBSP. Especially the ATC, but not exclusive.
Procedural deviations
Exceptional situations, or unusual ones, can necessitate procedural deviations, or complementary procedures, to be added to the following procedures described in this document.
| Facility | Callsign | Frequência | ID |
| Tower | São Paulo Tower | 118.050 | SP1 |
| Helicopter Control | 118.350 | SP11 | |
| Ground | São Paulo Ground | 121.900 | SP2 |
| Clearance Delivery | São Paulo Clearance | 120.600 | SP3 |
| ATIS | ATIS | 127.650 | ATIS |
| Facility | Callsign | Frequency | ID |
| Approach Control |
São Paulo Control |
129.000 | XP1 |
| VFR Control | 129.500 | XP2 |
| Facility | Callsign | Frequency | ID |
| Center | Curitiba Center | 124.4¹ / 128.400² | CW1 |
| Brasília Center | 126.750 | BS1 |
¹ - primary frequency
² - secondary frequency
| WAYPOINT | SID | ID |
| ASETA | UGTIX 2A | UGT2A.AS |
| EGEVA | UGT2A.EG | |
| GERTU | UGT2A.GE | |
| MADNI | UTKOM 1A | UTK1A.MA |
| NIBGA | UTK1A.NI | |
| NIBRU | BAIAN 1A | BAI1A.NI |
| SOVSI | UTKOM 1A | UTK1A.SO |
| UBRIR | BAIAN 1A | BAI1A.UB |
| UBSOD | UTKOM 1A | UTK1A.UB |
| UREMI | BAIAN 1A | BAI1A.UR |
| VUMEV | BAI1A.VU | |
| VURDU | UGTIX 2A | UGT2A.VU |
| WAYPOINT | SID | ID |
| ASETA | UGTIX 1B | UGT1B.AS |
| EGEVA | UGT1B.EG | |
| GERTU | UGT1B.GE | |
| MADNI | SEDLO 1A | SED1A.MA |
| NIBGA | SED1A.NI | |
| NIBRU | BAIAN 1B | BAI1B.NI |
| SOVSI | SEDLO 1A | SED1A.SO |
| UBRIR | BAIAN 1B | BAI1B.UB |
| UBSOD | SEDLO 1A | SED1A.UB |
| UREMI | BAIAN 1B | BAI1B.UR |
| VUMEV | BAI1B.VU | |
| VURDU | UGTIX 1B | UGT1B.VU |
| AEROVIA | SID | TRANSIÇÃO | ID |
|---|---|---|---|
| UL301 | UGTIX 2A | ASETA | UGT2A.AS |
| UL304 | GERTU | UGT2A.GE | |
| UL310 | ASETA | UGT2A.AS | |
| UM415 | |||
| UM417 | GERTU | UGT2A.GE | |
| UM423 | |||
| UM775 | |||
| UZ14 | BAIAN 1A | VUMEV | BAI1A.VU |
| UZ152 | UGTIX 2A | ASETA | UGT2A.AS |
| UZ171 | BAIAN 1A | NIBRU | BAI1A.NI |
| UZ21 | UGTIX 2A | GERTU | UGT2A.GE |
| UZ22 | BAIAN 1A | UBRIR | BAI1A.UB |
| UZ23 | |||
| UZ25 | UGTIX 2A | GERTU | UGT2A.GE |
| UZ38 | UTKOM 1A | UBSOD | UTK1A.UB |
| UZ42 | BAIAN 1A | UREMI | BAI1A.UB |
| UZ45 | UTKOM 1A | UBSOD | UTK1A.UB |
| UZ58 | UGTIX 2A | EGEVA | UGT2A.EG |
| UZ85 | UTKOM 1A | SOVSI | UTK1A.SO |
| UZ92 | MADNI | UTK1A.MA | |
| Z11 | BAIAN 1A | NIBRU | BAI1A.NI |
| Z41 | UGTIX 2A | GERTU | UGT2A.GE |
| Z47 | BAIAN 1A | UBRIR | BAI1A.UB |
| Z5 | UGTIX 2A | ASETA | UGT2A.AS |
| Z59 | |||
| Z85 | EGEVA | UGT2A.EG | |
| Z91 | UTKOM 1A | SOVSI | UTK1A.SO |
| AEROVIA | SID | TRANSIÇÃO | ID |
|---|---|---|---|
| UL301 | UGTIX 1B | ASETA | UGT1B.AS |
| UL304 | GERTU | UGT1B.GE | |
| UL310 | ASETA | UGT1B.AS | |
| UM415 | ASETA | UGT1B.AS | |
| UM417 | GERTU | UGT1B.GE | |
| UM423 | |||
| UM775 | |||
| UZ14 | BAIAN 1B | VUMEV | BAI1B.VU |
| UZ152 | UGTIX 1B | ASETA | UGT1B.AS |
| UZ171 | BAIAN 1B | NIBRU | BAI1B.NI |
| UZ21 | UGTIX 1B | GERTU | UGT1B.GE |
| UZ22 | BAIAN 1B | UBRIR | BAI1B.UB |
| UZ23 | |||
| UZ25 | UGTIX 1B | GERTU | UGT1B.GE |
| UZ38 | SEDLO 1A | UBSOD | SED1A.UB |
| UZ42 | BAIAN 1B | UREMI | BAI1B.UB |
| UZ45 | SEDLO 1A | UBSOD | SED1A.UB |
| UZ58 | UGTIX 1B | EGEVA | UGT1B.EG |
| UZ85 | SEDLO 1A | SOVSI | SED1A.SO |
| UZ92 | MADNI | SED1A.MA | |
| Z11 | BAIAN 1B | NIBRU | BAI1B.NI |
| Z41 | UGTIX 1B | GERTU | UGT1B.GE |
| Z47 | BAIAN 1B | UBRIR | BAI1B.UB |
| Z5 | UGTIX 1B | ASETA | UGT1B.AS |
| Z59 | |||
| Z85 | EGEVA | UGT1B.EG | |
| Z91 | SEDLO 1A | SOVSI | SED1A.SO |
SBSP has only one NON-RNAV SID, the OMNI. It can be used for all runway. How the OMNI SID has no lateral restrictions, authorizing a direct route after passing 3900ft (starting from RWY17), or 3600ft (starting from RWY35), can bring a number of problems to the ATC.
If the Sao Paulo APP (XP1) is online, the SP Tower must coordinate with APP what will be done after SID OMNI, before issuing the ATC clearance to the pilot.
If the Sao Paulo APP is offline, the following information must be used, according to the RWY in use, taking into account the ideal RADIAL between the VOR Congonhas (CGO 116.9) and the first waypoint of the route. To discover such information, you have two options:
-
Ask the pilot:
- [WAYPOINT] "PTOMX, confirm the ideal CGO VOR radial to LUVLA";
- [DESTINATION] "PRSMT, confirm the ideal CGO VOR radial to Ribeirao Preto". Ou
-
Get this information from Skyvector:
- When you tap "CGO [space] WAYPOINT/DESTINATION" on Skyvector Flight Plan ROUTE, it will show a magenta line with the ideal CGO VOR RADIAL. In the case shown on the right side image, is the CGO RADIAL 011.
- This is a slightly more laborious, but more reliable and quick way way to get the information.
Knowing the ideal CGO VOR Radial to the first waypoint, or destination, the following table must be given to the pilot as departure instruction:
| RADIAL | INITIAL CLIMB | DEPARTURE INSTRUCTION | WHEN TO CLIMB? |
|---|---|---|---|
| 007 a 039 | 6000FT | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly DCT SCP, when at 10NM to SCP, fly to the first waypoint route | After flying to the first waypoint route |
| 040 a 094 | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly DCT SCP. After SCP VOR, fly to the first waypoint route. | After SCP VOR | |
| 095 a 119 | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly to the first waypoint route. | At 15NM from CGO VOR | |
| 120 a 249 | After 3600ft, fly to the first waypoint route. | ||
| 250 a 279 | After 3600ft, intercept 250 CGO VOR RADIAL until 12NM then fly to the first waypoint route. | At 20NM from CGO VOR | |
| 280 a 006 | After 3600ft, intercept 250 CGO VOR RADIAL, until 12NM then fly to SCB VOR. After SCB fly to the first waypoint route. |
NOTE: every pilot's intention, including flight level changes, must be previously coordinated on air-to-air frequency to avoid any possible conflict.
Knowing the ideal CGO VOR Radial to the first waypoint, or destination, the following table must be given to the pilot as departure instruction:
| RADIAL | INITIAL CLIMB | DEPARTURE INSTRUCTION | WHEN TO CLIMB? |
|---|---|---|---|
| 007 a 039 | 6000FT | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly DCT SCP, when at 10NM to SCP, fly to the first waypoint route | After flying to the first waypoint route |
| 040 a 094 | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly DCT SCP. After SCP VOR, fly to the first waypoint route. | After SCP VOR | |
| 095 a 119 | After 3600ft, intercept 110 CGO VOR RADIAL, until 30NM, then fly to the first waypoint route. | At 15NM from CGO VOR | |
| 120 a 169 | |||
| 170 a 249 | At 20NM from CGO VOR | ||
| 250 a 279 | After 3600ft, intercept 250 CGO VOR RADIAL until 12NM then fly to the first waypoint route. | ||
| 280 a 006 | After 3600ft, intercept 250 CGO VOR RADIAL, until 12NM then fly to SCB VOR. After SCB fly to the first waypoint route. |
NOTE: every pilot's intention, including flight level changes, must be previously coordinated on air-to-air frequency to avoid any possible conflict.
The frequency to call after departure given to the pilot must follow this priority, depending on which ATC is online at that moment:
| # | Position | Frequency | ID |
|---|---|---|---|
| 1 | SBXP_APP | 129.000 | XP1 |
| 2 | SBCW_ACC | 124.400¹ / 128.400² | CW1 |
| 3 | Air-to-Air frequency | 123.450 | - |
NOTE: To standardize the airflow in the TMA SP in case of APP XP offline, in no case an SP TMA TWR will transfer an aircraft to Brasilia ACC (BS1) after the departure.
According to DECEA, PREFERENTIAL ROUTES is a "Mandatory route, previously established in a collaborative way and published by the CGNA, related to the flight between origin and destination locations or just a segment of the route" (DECEA, ICA 100-22, 2018).
In this way, the ATC must EVER consult the preferential routes BEFORE connecting to the desired position. For this, go to the AISWEB website.
Independently if APP SP or ACC CW is online, the SID given in the ATC Clearance must follow the SID table on this category. This procedure aims to reduce coordination between ATC positions and consequently the workload.
Following the AIP Brazil, the operation of Fixed Wings ACFT VFR flights to or from SBSP is PROHIBITED, except for BRAZILIAN MILITARY
AIRCRAFT. For these cases, you should observe what you are willing to follow.
The departures from RWY17, the VFR fixed wings must, after the departure, fly to INTERLIGACAO position (purple line) to join the visual corridors; to the departures from RWY35, the VFR fixed wings must fly to REGIS position (blue line) to join visual corridors ( as pictured on the right side).
The HELI CONTROL facility ("subdivision" of Sao Paulo Tower responsible for helicopters control of North Sector from SAO PAULO CTR) isn't implemented yet on POSCON Brazil. So, the SP TWR (SP1) will control those aircraft there. To standardize the airflow and the ATC, the departure standard below must be informed to the aircraft, if the SP TWR is offline. In case the SP TWR is online, ALL helicopter departures must be previously coordinated with the TWR.
| RWY IN USE | INITIAL CORRIDOR | INSTUCTION AFTER DEPARTURE |
|---|---|---|
| RWY17 | TANCREDO | Left turn after departure to MARIA MALUF posicion |
| CONGONHAS | Left turn after departure to CEBOLINHA position | |
| ACLIMAÇÃO | Left turn after departure to ANA ROSA position | |
| ESPRAIADA | Right turn after departure to WASHINGTON LUÍS position | |
| ANCHIETA | Right turn after departure to MERCEDES position | |
| FÁBRICA | After departure, fly direct to KENTINHA position | |
| IMIGRANTES |
| RWY IN USE | INITIAL CORRIDOR | INSTRUCTION AFTER DEPARTURE |
|---|---|---|
| RWY35 | TANCREDO | Right turn after departure to position CLUBE SIRIO, then fly to MARIA MALUF position |
| CONGONHAS | Right turn after departure to CLUBE SIRIO position | |
| ACLIMAÇÃO | Right turn after departure to CLUBE SIRIO position to join CONGONHAS corridor. After passing CEBOLINHA position fly to ANA ROSA position | |
| ESPRAIADA | Left turn after departure to PONTE ESTAIADA position | |
| PINHEIROS | ||
| ANCHIETA | Right turn after departure to CLUBE SIRIO position, then fly to MERCEDES position | |
| FÁBRICA | ||
| IMIGRANTES | Right turn after departure to CLUBE SIRIO position, then fly to MERCEDES position to join FABRICA corridor. After passing KENTINHA position, join IMIGRANTES corridor. |
Its PROHIBITED IFR training within Congonhas CTR, Guarulhos CTR, and Sao Paulo TMA. As a result of such restriction, this type of flight may be made:
- under TMA-SP 1, in VMC, within a non-conflitant area with others IFR TFC, and that isn't necessary to maintain the bilateral communication with Sao Paulo APP; or
- within the other CTR on SP TMA, once have been made prior coordination with the respective ATS, to determine the time for execution of the FLT that least interferes with the IFR TFC.
Hangars
You can find the hangar's name of SBSP on the picture on the right side. Their names can be used during the radiocommunications to facilitate the parking position indication of a specific aircraft.
Parking positions
The APRON 3 positions of SBSP (gate 1 to 16) are destinated to the narrow-body commercial aircraft (A320, B737, E190...). As well as the 17 to 29 position on APRON "A300".
The commercial aircraft that not use the gate (ATR, C208, E145, CRJ...), they must use the position 13 to 29.
The GA aircraft that don't have a parking position in a HANGAR, the APRON 1 and 2 must be used. How there isn't number definided to that position, the expression "position at your discretion" must be used, like the following example:
TWR -> PSEYA, on the ground at 03', vacate the runway to the left and taxi via Q and S. Contact São Paulo Ground at 121.9.
Pilot -> São Paulo Ground, PSEYA, taxiing via Q and S to apron 1.
GND -> PSEYA, continue taxi via Q and S, apron 1, position at your discretion.
Pushback on APRON 3
The M TWY, on MAIN APRON, must be used as an auxiliary taxi line to give agility to the airflow.
Usually, the parked aircraft on positions 1 to 15 must be instructed to perform the pushback to the "N TWY", as the following example:
Pilot -> GLO9923, stand 5, ready to pushback and start up.
GND -> GLO9923, pushback, and startup approved, limited to the N taxiway, report to taxi.
The procedure above only can be done when involving two aircraft with a wingspan equal to or less than 36 meters (A320, B737, E190, C25C, LJ45, PA34, or smaller).
The A300 Apron has 3 taxi lines (W, Y, and X) that can be used to the pushback. However, USUALLY, the aircraft parked on positions 17 to 23 will perform pushback to the W TWY; and the aircraft parked on positions 24 to 29 will perform to X TWY.
This procedure, on A300 apron, must be used with aircraft with a wingspan equal to or less than 36 meters, as well as on the main apron.
Helicopters parking
Usually, the helicopters will park on hangars, however, the airport administration has some parking positions for rotative wings. The first one is on the "military" apron (officially known as "patio do pavilhão"), on side of position 1, on the main apron. Those positions are used by military helicopters. The other one, which doesn't have a position on a designated hangar, must park on the helicopter's parking, on the east side of the airport, in front of Q TWY.
Helicopter's departure and landing
Is PROHIBITED the landing/departure operation of helicopters in a place that isn't the runway.
"S" TWY
The ATC must observe the following limitations of S TWY (east side of the airport):
- MAX wingspan allowed 24 meters (MAX SPAN 24M); and
- MAX speed of 15kt on TWY.
"O" TWY
The ATC must observe the following limitations on O TWY (east side of the airport):
- MAX wingspan allowed 24 meters (MAX SPAN 24M).
Instruction after landing
When the ACFT is on final, the TWR must ask what will be the parking local of the aircraft. So, the TWR will inform this position to the GND.
The TWR will transmit the following information at the landing momento, in this sequence:
- callsign;
- landing time;
- taxiway to be used to vacate the runway;
- taxi instruction after vacating, to avoind desnecessary occupation in a exit taxiway;
- GND frequency to contact after vacating.
TWR -> PROMX, on ground at 28', vacate to the left, cleared taxi via Q and S, after vacating, contact São Paulo Ground, frequency 121.9.
When the aircraft calls the GND SP, the taxi instruction will be informed again by the GND, and the parking HANGAR (or parking box) will be informed.
GND -> PROMX, cleared taxi via Q and S to VOAR 1 hangar.
The TWY informed by the TWR on landing time must follow those criteria:
| RWY USED | PARKING HANGAR | TAXI INSTRUCTION AFTER VACATING |
|---|---|---|
| RWY 17L | EAST SIDE | Vacating TWY [TWR choice, coordinated with GND] + S TWY |
| WEST SIDE | Vacating TWY | |
| RWY 17R | EAST SIDE | Vacating TWY [TWR choice, coordinated with GND] + M TWY (if the traffic vacate on H, or F TWY), or L TWY (if vacated on I, J or K TWY) |
| WEST SIDE | Vacating TWY | |
| RWY 35R | EAST SIDE | Vacating TWY [TWR choice, coordinated with GND] + S TWY |
| WEST SIDE | Vacating TWY | |
| RWY 35L | EAST SIDE | Vacating TWY |
| WEST SIDE | Vacating TWY [TWR choice, coordinated with GND] + M TWY (if the traffic vacate on H, or F TWY), or L TWY (if vacated on I, J or K TWY) |
Examples:
-
Traffic landing on RWY35L, going to VOAR 3 HANGAR
- "PTOMX, ground at 50', vacate to the right, cleared taxi via B TWY to hold point RWY35R";
-
Traffic landing on RWY17R, going to box 3
- "GLO1829, ground at 51', vacate to the right, taxi via I and M, after vacating, contact SP GND freq 121.9".
NOTE: due to the taxi duration of the traffic vacating the RWY on TWY Q (to the HEL PRKG), or vacating on TWY S (to APRON 1, or to the TAM EXECUTIVA 1), or vacating on TWY E or F (to the "PATIO DO PAVILHAO"), the TWR will instruct the traffic to MONITOR the GND SP on 121.9, following the example:
TWR -> FAB2501, on ground at 28', vacate to the left, cleared taxi via F and M to box 2A, after vacating, monitor São Paulo Ground, frequency 121.9.
Clearance to depart from an intermediate position of RWY
Following a DECEA instruction, always that a clearance/suggestion to depart from an intermediate position is given, the ATC must inform the remaining runway length from that position. To this, observe the image below:

Coordination with APP XP
Ever that the traffic is flying on SBSP traffic pattern, and the XP APP is online, the 360º maneuvering on downwind leg or extending the downwind leg must be coordinated with APP.
Restrictions on Traffic Pattern
Normally, the ARRIVALS to the traffic pattern will obey the entrance contained in the VAC, by the positions:
- Washington Luís;
- Maria Maluf;
- Clube Sírio.
The DEPARTURES will obey what is contained in this chapter, in VFR DEPARTURES.
The IFR traffic will be, normally, handoff by the Sao Paulo APP, or by the Curitiba ACC (when the Sao Paulo APP is offline), when on IFR procedure final.
NOTE: the handoff can occur at another point, as long as previously coordinated between the TWR and APP (or ACC, when APP is offline).
Next Controller offline
In case the Sao Paulo APP, or the Curitiba ACC, is offline, the Sao Paulo TWR must contact the aircraft, by the GUARD frequency (121.5), when the IFR Arriving Traffic is starting the IFR procedure.
Next controller online
During the takeoff clearance, the SP TWR will instruct the departing aircraft to contact APP XP, or ACC CW (when APP XP is offline), as the following example:
PSJOV, runway 1-7 right, cleared to lineup and takeoff, wind 1-7-0 degrees, 8kt. After airborne, contact São Paulo Control, frequency 129.0.
NOTE: the handoff can occur at another point, as long as previously coordinated between the TWR and APP (or ACC, when APP is offline).
Next controller offline
If the APP XP is offline, and the ACC CW too, the SP TWR will give the following instruction during the takeoff clearance:
PRMOM, runway 1-7 right, cleared to lineup and takeoff, wind 2-0-0 degrees, 2kt. The next controller is offline. After airborne, frequency change approved.
Next controller online
The VFR traffic will, normally, handoff to SP TWR when at 1 minute to join on SAO PAULO CTR.
NOTE: the handoff can occur at another point, as long as previously coordinated between the TWR and APP (or ACC, when APP is offline).
Next controller offline
In case the Sao Paulo APP, or the Curitiba ACC, is offline, the SP TWR must contact the aircraft, by the GUARD frequency (121.5), when the VFR Arriving Traffic is at 2 minutes to join SAO PAULO CTR.
Next controller online
The departing VFR aircraft will instructed to contact SP APP, or CW ACC, when leaving the SAO PAULO CTR.
NOTE: the handoff can occur at another point, as long as previously coordinated between the TWR and APP (or ACC, when APP is offline).
Next controller offline
If the SP APP, or CW ACC, is offline, the TWR must authorize the frequency change, after the traffic leaving the SAO PAULO CTR, following this example:
Pilot -> Sao Paulo Tower, PTOZZ, passing AVENIDA MORUMBI position.
Tower -> PTOZZ, the next controller is offline, frequency change approved.
The Helicopter Control Area is located within SAO PAULO CTR (Class D, from GND to 3600FT; and controlled by SP TWR). In real life, this
airspace portion is controlled by "HELI CONTROL" (a subdivision of SP TWR), on frequency 118.35. However, due to POSCON's actual traffic characteristics, the HELI CONTROL is deactivated and grouped to SP TWR (this doesn't mean that future activations and/or temporary ones are prohibited).
This area is a rectangle that begins on THR RWY17 and ends at 6NM on the final. And it has 2,5NM for each side.
In this region, the SP TWR will give clearances and restrictions to avoid the helicopters conflict with the landing traffic of RWY17 or departing of RWY35.
The composite separation can be applied, on the final approach RWY17 and/or on the departure sector of RWY35 of SBSP, between the IFR ACFT and VFR HEL flying in the Helicopter Control Area. The composite separation minimum to be applied is 2,5 NM x 500 FT.
There are a lot of heliports located in this area. To facilitate situational awareness were created numbered sectors of A1 to A6 (left side), and B1 to B6 (right side). So, those quadrants can be used for communication to help the controllers and pilots to localize yourselves. See the following example:
TWR SP -> PTOMS, confirm your destination quadrant.
Pilot -> It's on Birmann 21 building, on the A4 quadrant. Near the Pinheiro marginal.
Another example that we can use the quadrants to traffic information:
TWR SP -> PPMMZ, maintain position on A3 quadrant. I inform an AS50, on the A2 quadrant to B2 inbound.
Each Helicopter Control Area quadrant has 1NM of height and 2,5NM of length.
EVERY HELICOPTER THAT WILL FLY WITHIN HELICOPTER CONTROL AREA must contact the SP TWR. Exceptional cases can occur after PREVIOUS COORDINATION between the involved parts.
Use ever the AISWEB to check the active NOTAM.
NOTE: What must prevail ever is common sense. If the pilot asks not to simulate a NOTAM, and this won't disturb other simmers, this request MUST BE attended! Punctual issues must be reported to our staff team.
Ever the wind intensity at SBSP is less or equal at 5kt, the 17 system must be used as PREFERENTIAL. Except in the cases that operational gains can be provided, and be previously coordinated with XP APP, the 35 system can be used in this case.
Follow those rules when an IFR aircraft starts the missed approach procedure:
- coordinate IMMEDIATELY with the Sao Paulo APP, or Curitiba ACC (when the Sao Paulo APP is offline), when the Sao Paulo TWR notes an aircraft is starting the missed approach;
- don't change, UNDER ANY CIRCUMSTANCES, the missed approach procedure; unless the pilot declares intentions to join in the traffic pattern;
- handoff the traffic to Sao Paulo APP, or to Curitiba ACC (when APP is offline), or authorize "frequency change approved" (when Next Controller is offline), ASAP;
- understand the crew workload during this procedure can be increased; causing delayed answers by the pilots.
The Sao Paulo Tower only can receive a flight plan via radio to the SAR operation aircraft, and others one provided for in official DECEA regulation.
NOTE: It equates to Operation SAR, the aircraft on a radio patrol mission.
Due to POSCON limitation, SBSP doesn't have ATIS; so, the TWR must give meteorological information to all departing aircraft, with the following information, and in this sort:
- runway in use;
- wind direction and intensity;
- QNH
- temperature
- visibility, or runway in use RVR; and
- time check
Example:
GLO1817, runway in use 1-7 right, wind 1-4-0º, 8KT, altimeter setting 1-0-1-2, temperature 2-8º, visibility 8km, time check 5-6'.
| # | Date | Description | Author |
|---|---|---|---|
| - | 20MAR22 | Criação do documento | Juvenal Gomes (1025243) |

