Brazil Division
ICAO | Name | ATC Facilities | SSR | Type of Operation |
SBBR | Presidente Juscelino Kubitschek | TWR / GND / DEL | 0111-0130 | VFR / IFR |
Purpose
This document describes the procedures that must be followed by the Air Traffic Service (ATS) at Brasília 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 SBBR. 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.
AIRWAY | SID | TRANSITION |
---|---|---|
UL452 | ESBUX 4A | DOLVI |
UM403 | PAPID 1A | SIREM |
UM532 | ROMIK | |
UM668 | GNV | |
UZ18 | PANOK 3C | USESO |
UZ19 | SELDI 1A | - |
UZ2 [NORTH] | ESBUX 4A | DOMLI |
UZ2 [SOUTH] | SEMDU 1A | MAVNI |
UZ24 | ESBUX 4A | DOLVI |
UZ25 | DOTKA | |
UZ26 | KOGLI | |
UZ27 | PANOK 3C | SAPRU |
UZ32 | KOMGI | - |
UZ33 | ESBUX 4A | PAPES |
UZ35 | SEMDU 1A | MUGIS |
UZ40 | ESBUX 4A | PAPES |
UZ5 [NORTH] | OPSAM | |
UZ5 [SOUTH] | SEMDU 1A | EDMIN |
UZ51 | PANOK 3C | USESO |
UZ59 | ARPON | |
UZ6 | SEMDU 1A | NIMKI |
UZ76 | ESBUX 4A | KOGDI |
AIRWAY | SID | TRANSITION |
---|---|---|
UL452 | KOTVU 3B | DOLVI |
UM403 | MOXOB 3B | SIREM |
UM532 | ROMIK | |
UM668 | GNV | |
UZ18 | KOTVU 3C | USESO |
UZ19 | SIGER 1A | SELDI |
UZ2 [NORTH] | KOTVU 3B | DOMLI |
UZ2 [SOUTH] | LIVEV 1B | MAVNI |
UZ24 | KOTVU 3B | DOLVI |
UZ25 | DOTKA | |
UZ26 | KOGLI | |
UZ27 | KOTVU 3C | SAPRU |
UZ32 | SIGER 1A | KOMGI |
UZ33 | KOTVU 3B | PAPES |
UZ35 | LIVEV 1B | MUGIS |
UZ40 | KOTVU 3B | PAPES |
UZ5 [NORTH] | OPSAM | |
UZ5 [SOUTH] | LIVEV 1B | EDMIN |
UZ51 | KOTVU 3C | USESO |
UZ59 | ARPON | |
UZ6 | LIVEV 1B | NIMKI |
UZ76 | KOTVU 3B | KOGDI |
AIRWAY | SID | TRANSITION |
---|---|---|
UL452 | TINSI 3A | DOLVI |
UM403 | GAXON 1A | SIREM |
UM532 | ROMIK | |
UM668 | - | - |
UZ18 | UBRUR 2A | USESO |
UZ19 | NEDES 1A | SELDI |
UZ2 [NORTH] | TINSI 3A | DOMLI |
UZ2 [SOUTH] | GAXON 1A | MAVNI |
UZ24 | TINSI 3A | DOLVI |
UZ25 | DOTKA | |
UZ26 | KOGLI | |
UZ27 | UBRUR 2A | SAPRU |
UZ32 | NEDES 1A | SIGER |
UZ33 | TINSI 3A | PAPES |
UZ35 | GAXON 1A | MUGIS |
UZ40 | TINSI 3A | PAPES |
UZ5 [NORTH] | OPSAM | |
UZ5 [SOUTH] | GAXON 1A | EDMIN |
UZ51 | UBRUR 2A | USESO |
UZ59 | ARPON | |
UZ6 | GAXON 1A | NIMKI |
UZ76 | TINSI 3A | KOGDI |
AEROVIA | SID | TRANSIÇÃO |
---|---|---|
UL452 | UTPAS 3B | DOLVI |
UM403 | BOBEM 1A | SIREM |
UM532 | ROMIK | |
UM668 | - | - |
UZ18 | PANOK 2B | USESO |
UZ19 | KIACA 1A | SELDI |
UZ2 [NORTH] | UTPAS 3B | DOMLI |
UZ2 [SOUTH] | BOBEM 1A | MAVNI |
UZ24 | UTPAS 3B | DOLVI |
UZ25 | DOTKA | |
UZ26 | KOGLI | |
UZ27 | PANOK 2B | SAPRU |
UZ32 | KIACA 1A | SIGER |
UZ33 | UTPAS 3B | PAPES |
UZ35 | BOBEM 1A | MUGIS |
UZ40 | UTPAS 3B | PAPES |
UZ5 [NORTH] | OPSAM | |
UZ5 [SOUTH] | BOBEM 1A | EDMIN |
UZ51 | PANOK 2B | USESO |
UZ59 | ARPON | |
UZ6 | BOBEM 1A | NIMKI |
UZ76 | UTPAS 3B | KOGDI |
DIRECTION TO | SID | TRANSITION |
Northeast | PANOK3C | ARPON |
SAPRU | ||
USESO | ||
South | SEMDU1A | MUGIS |
NIMKI | ||
MAVNI | ||
EDMIN | ||
Southwest | PAPID1A | TIPTU |
SIREM | ||
GNV | ||
ROMIK | ||
North | ESBUX4A | OPSAM |
DOMLI | ||
DOTKA | ||
KOGLI | ||
DOLVI | ||
GIGTI | ||
KOGDI | ||
PAPES | ||
Northeast |
ARPON1A ARPON1B |
ARPON |
ARPON | ||
Southeast | KOMGI1A | KOMGI |
Northeast | SELDI1A | SELDI |
DIRECTION TO | SID | TRANSITION |
South | LIVEV1B | MUGIS |
NIMKI | ||
MAVNI | ||
EDMIN | ||
Southwest | MOXOB3B | TIPTU |
SIREM | ||
GNV | ||
ROMIK | ||
North | KOTVU3B | OPSAM |
ILSUL | ||
DOMLI | ||
DOTKA | ||
KOGLI | ||
DOLVI | ||
GIGTI | ||
KOGDI | ||
PAPES | ||
Northeast | KOTVU2D | ARPON |
KOTVU2E |
FSA ARPON |
|
Southeast | SIGER1A | SELDI |
KOMGI |
DIRECTION TO | SID | TRANSITION |
South | GAXON1A | MUGIS |
NIMKI | ||
MAVNI | ||
EDMIN | ||
SIREM | ||
ROMIK | ||
Northeast | NEDES1A | FSA |
KOLDA | ||
SIGER | ||
SELDI | ||
North | TINSI3A | OPSAM |
ILSUL | ||
DOMLI | ||
DOTKA | ||
KOGLI | ||
DOLVI | ||
GIGTI | ||
PAPES | ||
KOGDI | ||
Northeast | UBRUR2A | USESO |
SAPRU | ||
ARPON |
DIRECTION TO | SID | TRANSITION |
South | BOBEM1A | MUGIS |
NIMKI | ||
MAVNI | ||
EDMIN | ||
SIREM | ||
ROMIK | ||
Northeast | KIACA1A | KOLDA |
SELDI | ||
SIGER | ||
Northeast | PANOK2B | USESO |
SAPRU | ||
ARPON | ||
North | UTPAS3B | OPSAM |
ILSUL | ||
DOMLI | ||
DOTKA | ||
KOGLI | ||
DOLVI | ||
GIGTI | ||
KOGDI | ||
PAPES |
RUNWAY | DIRECTION TO | SID | TRANSITION |
29L | NORTH | ANPAX2A | PANOK |
FSA | |||
KOLDA | |||
ARPON | |||
NORTH | KOGLI2A | KOGLI | |
SOUTH | LUZ1A | ISOPI | |
OPRAX | |||
29R | NORTH | KOGLI1B | KOGLI |
NORTHEAST | UKENA2A | PANOK | |
FSA | |||
KOLDA | |||
ARPON | |||
11L | NORTHEAST | FSA3A | KOLDA |
ARPON | |||
EAST | OTAFO1A | OTAFO | |
SOUTH | IRITU1A | ISOPI | |
OPRAX | |||
NORTH | NIRDI1A | PANOK | |
KOGLI | |||
11R | EAST | KOTVU1A | OTAFO |
FSA | |||
ARPON | |||
SOUTH | LUZ2D | ISOPI | |
OPRAX | |||
NORTH | MIBIS1A | PANOK | |
KOGLI |
The frequency to call after departure gave to the pilot must follow this priority, depending which ATC is online at that moment:
# | Facility | Frequency | ID |
---|---|---|---|
1 | SBWR_APP | 129.150 | WR1 |
2 | SBBS_ACC | 126.750 | BS1 |
3 | Air-to-Air Frequency | 123.450 | - |
The ATC must inform the departure frequency at the ATC clearance.
NOTE: In case the aircraft remains the traffic pattern, or stays near the airfield, after the departure; the pilot must be instructed to maintain the Brasília Tower frequency 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.
Steps to determine the SID of an aircraft:
- APP Brasília (WR1) is online, ALL SID must be provided by the APP before giving the ATC Clearance;
- Use the charts available on AISWEB to determine the correct SID based on aircraft type and route.
All VFR departures must be coordinated with the Brasília APP before departure. For this, is necessary to inform to APP:
- First visual corridor after the departure.
With that information, the Brasília APP will be capable to provide how will be the departure maneuver to the aircraft (if it will be directed to the corridor; or if it will follow some specific instructions, like flying through "Barragem Santa Maria position" after departure...)
Is important for the Brasilia TWR to know the visual corridors (REA) since they can be used for departing aircraft.
It isn't common traffic. Before giving the ATC Clearance, the Brasília TWR must ask the crew's intentions. Having that information, ask the Brasília APP (WR1), or the Brasilia ACC (BS1), in case the Brasília APP is offline, the correct SID for the traffic. Then, give the ATC Clearance for the IFR training traffic.
Usually, the airplanes going to SBBR must follow those rules about the Parking position:
Flight Type | Position |
Azul | 17 - 20 |
Gol | 5 - 16 |
Latam | 24 - 41 |
International | 1 - 2 (M) | 3 - 4 (M e H) |
Cargo | 52 - 60 (L e M) | 47 - 49 (H) |
Executive | 67 - 70 |
ATR | 49A - 51 |
General apron (Apron 2) | 42 - 46 | 61 - 66 |
Military aircrafts | Military Apron |
TGL at SBBR
Despite being Brasília TWR responsibility area, the TWR must maintain the Brasília APP informed about the aircraft performing TGL (touch and go landing) at SBBR; just like, when the aircraft goes to perform a 360º maneuvering on downwind leg or extending the downwind leg.
Traffic Pattern Restrictions
-
RWY 11L/29R
- ACFT from W, NW, N, NE, and E sector, must enter on traffic pattern from N sector;
- ACFT from SE, S, SW sector, must request clearance from BR TWR to cross the aerodrome to enter on traffic pattern;
- departure RWY 11L: LEFT TURN MANDATORY, except when cleared by BR TWR;
- departure RWY 29R: RIGHT TURN MANDATORY, except when cleared by BR TWR;
- departure from RWY 11L/29R: START TURN after 4000'.
-
RWY 11R/29L
- ACFT from W, SW, S, and SE, must enter on traffic pattern from S sector;
- ACFT from NW, N, NE, and E, must request clearance from BR TWR to cross the aerodrome to enter on traffic pattern;
- departure RWY 11R: RIGHT TURN MANDATORY, except when cleared by BR TWR;
- departure RWY 29L: LEFT TURN MANDATORY, except when cleared by BR TWR;
- departure from RWY 11R/29L: START TURN after 4000'.
The IFR traffic will be, normally, handoff by the Brasília APP, or by the Brasilia ACC (when the Brasília 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 Brasília APP, or the Brasilia ACC, is offline, the Brasília TWR must contact the aircraft, by the GUARD frequency (121.5), when the IFR Arriving Traffic is starting the IFR procedure.
During the departure clearance, the BR TWR will instruct the aircraft to contact WR APP, or BS ACC (when the WR APP is offline), conform the following example:
PSGUV, runway 1-1 right, cleared to lineup and takeoff, wind 1-7-0 degrees, 8kt. After airborne, first turn to the right and contact Brasilia Control, frequency 129.15.
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 WR APP, or BS ACC, is offline, the TWR must give the instruction to change frequency during the departure clearance too, as following example:
PRMOM, runway 1-1 right, cleared to lineup and takeoff, wind 2-0-0 degrees, 2kt. The next controller is offline. After airborne, first turn to the right and frequency change approved.
The VFR traffic will be handoff, normally, by the Brasilia APP, or by the Brasilia ACC (when the Brasília APP is offline), at 1 minute to leave the visual corridor.0NM (10 nautical miles) to SBBR.
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 Brasília APP, or the Brasilia ACC, is offline, the Brasília TWR must contact the aircraft, by the GUARD frequency (121.5), when the VFR Arriving Traffic is passing the last position of the visual corridor, or at 15NM (15 nautical miles) to SBBR if the aircraft isn't following a visual corridor.
The VFR departing traffic, that won't remain at the traffic pattern, must be handoff to Brasília APP, or Brasilia ACC (when Brasília APP is offline), when airborne.
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 Brasília APP, or Brasilia ACC, is offline, the Brasília TWR must authorize the aircraft to change the frequency when airborne using the following phraseology:
PTOMX, airborne at 06', next controller is offline, frequency change approved.
As Brasília Airport has two parallel runways, it operates by the Simultaneous Independent Parallel Operations procedure, which consists of approach and takeoffs where the ATS separation minima aren't applied. For this operation to occur, the ILS procedures of both runways in use must beILS procedures of both runways in use are in full working order.
During the operation of this procedure, the No Transgression Zone (NTZ) is active due to the non-application of the separation minima. The NTZ is an 800 meters corridor of airspace of defined dimensions located centrally between the two extended runway centerlines, where penetration by an aircraft requires the intervention of a monitoring radar controller to maneuver any threatened aircraft on the adjacent approach. In case of an NTZ violation, the ATCO must interfere IMMEDIATELY to establish a separation between those aircraft.
To the Simultaneous Independent Parallel Operations execution, the ATCO of APP-BR must inform, as soon as possible, the runway in use and the ILS procedure designated to both aircraft. The pilot in command must readback immediately. The ATCO must provide a separation of 1000FT or 3NM, according to the capabilities of the ATS surveillance system, until both aircraft are stable in the respective LOC course and inside the Normal operating zone.
In case of a Resolution Advisory (RA) TCAS warning, both flight crews must follow the instructions immediately at any time this warning occurs.
If the aircraft is already listening to the TWR-BR, the breakout will be commanded by the ATCO that is monitoring the NTZ, through the overmodulation of the TWR-BR frequency
Aircraft category following ahead of the aircraft category | Category of aircraft following behind | Minimum |
SUPER | Heavy | 6 NM |
Medium | 7 NM | |
Light | 8 NM | |
HEAVY | Heavy | 4 NM |
Medium | 5 NM | |
Light | 6 NM | |
MEDIUM | Light | 5 NM |
Brasília Airport may also operate the Independent Simultaneous Parallel Departure procedure which consists of independent IFR takeoffs, the only requirement for conducting independent IFR departures will be the existence of satisfactory bilateral radio communications for any other specialized form of control or specification.
-
Brasília Tower must inform all aircrafts involved in Parallel Departures the way of the first turn after airborne. This information will be transmitted by voice, data link, on ATC clearance and reinforced in takeoff clearance.
-
When flight crew receive the initial information, they must verify the FMS programming and verify the SID selection. Special attention to the runway in use informed by Brasília Tower.
-
The pilot in command must readback the first turn information given by the TWR and due to the particularity of the Parallel Departures, the pilot must call the APP immediately after airborne (when leaving the ground, or at most, when crossing the opposite threshold). The delay in changing the frequency can reduce the time for the APP-BR to resolve traffic situations that occur shortly after take-off.
- If, after the initial ATC clearance, for any reason, the aircraft is authorized to proceed for take-off on a different runway to the one initially authorized, the TWR must reiterate the information of modification of the exit procedure and on the side of the first turn.
During Parallel Departure operations, the crew is expected to be especially alert to the trajectory of the SID procedure and the direction of the first turn after takeoff. If the aircraft's autopilot executes a different trajectory from the authorized one, the crew must react immediately, returning to the expected profile of the authorized procedure and informing the APP as soon as possible.
Cases of suspension or cancellation of the Parallel Departure operations:
- Adverse weather conditions in the TMA, especially when they affect the SBBR approach and departure paths;
- Takeoff or approach of aircraft in emergency, carrying Head of State or in aeromedical evacuation;
NOTE: Such suspension will be coordinated between APP and TWR, and will be informed to pilots by voice.
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 SBBR is less or equal at 5kt, the 11 system must be used as PREFERENTIAL. Except in the cases that operational gains can be provided, and be previously coordinated with WR APP, the 29 system can be used.
Follow those rules when an IFR aircraft starts the missed approach procedure:
- coordinate IMMEDIATELY with the Brasília APP, or Brasilia ACC (when the Brasília APP is offline), when the Brasília 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 Brasília APP, or to Brasilia 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 Brasilia 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.
- Brasilia Tower won't inform the departure time of the aircraft. The instruction referent the departure frequency and complementary instructions will be given on ATC clearance;
- On landing operations, the pilots won't report the landing gear situation to the tower, except in emergencies.