Skip to content

SBWJ - Rio de Janeiro

General data

TMA Rio de Janeiro TMA
Position SBWJ_APP
Callsign Rio Control
Frequency 119.000 MHz1
Real-world frequencies 119.000 / 119.350 / 120.550 / 120.750 / 124.950 / 125.950 / 133.700; VFR 133.300 / 126.200 MHz
Real-world hours H24
ATS surveillance Radar (listed in AIP ENR 1.6)
Aerodromes in the TMA SBGL, SBRJ, SBJR, SBSC, SBAF, SBMI

Useful Information

Use the tabs above: Aeronautical Charts shows the TMA charts, Weather shows a weather map of the area and VATSIM Traffic opens the traffic at the main aerodrome (SBGL).

Map

Click a volume to see its limits and class. Use the layer control to change the base map and toggle the volumes.

Volumes

Volume Limits Class
Rio 3 1000 FT – 3500 FT C
Rio 2 3500 FT – 6500 FT C
Rio 1 6500 FT – FL245 A C
Galeão CTR GND – 2000 FT D
Rio CTR (SBRJ) GND – 2000 FT D
Santa Cruz CTR GND – 2500 FT C
Afonsos CTR GND – 1500 FT D
Jacarepaguá ATZ GND – 2000 FT —

APP Sectorization

The APP is split into sectors, each with its own position and frequency in the package. Turn on the APP sectors layer on the map to see them. When a sector position is offline, the sector passes to the position listed under Coverage.

Position Frequency Limits Coverage
SBWJ_S_APP 126.200 6500 FT – FL245 SBWJ_APP
SBWJ_RJ_APP 120.750 1500 FT – FL120 SBWJ_N_APP / SBWJ_S_APP
SBWJ_N_APP 125.950 6500 FT – FL245 SBWJ_NE_APP
SBWJ_E_APP 133.300 6500 FT – FL245 SBWJ_NE_APP
SBWJ_GL_APP 128.900 1500 FT – FL120 SBWJ_N_APP

Combined positions

Position Frequency Takes over
SBWJ_APP 119.000 SBWJ_S_APP, SBWJ_NE_APP
SBWJ_NE_APP 120.550 SBWJ_N_APP, SBWJ_E_APP

Delegated and subordinate airspace

Tubulão (delegated by Curitiba ACC)

The Tubulão is the Curitiba FIR corridor between the São Paulo and Rio de Janeiro TMAs, used by the Rio–São Paulo shuttle. In the package, Curitiba ACC (SBCW_CTR) delegates this airspace to Rio APP, split into two halves. Turn on the Tubulão layer on the map to see them.

Sector Limits Position Coverage
Tubulão North (CTA T8N) FL105 – FL245 SBWJ_N_APP SBWJ_NE_APP → SBWJ_APP
Tubulão South (CTA T8S) FL105 – FL245 SBWJ_S_APP SBWJ_APP
Tubulão North (UTA T8N) FL245 – FL600 SBWJ_N_APP SBWJ_NE_APP → SBWJ_APP
Tubulão South (UTA T8S) FL245 – FL600 SBWJ_S_APP SBWJ_APP

Above FL245, the UTA T8N and T8S sectors also cover the projection of the Rio de Janeiro TMA. With every Rio APP position offline, the Tubulão returns to Curitiba ACC, starting at SBCW_E_CTR.

Aldeia Control (SBES_APP)

São Pedro da Aldeia APP (SBES_APP, Controle Aldeia, 119.450) controls CTR Aldeia 1 (2000 FT – 6500 FT), inside the Macaé TMA. In the package it is subordinate to Rio APP, not to Macaé APP: when it is offline, CTR Aldeia 1 passes to SBWJ_E_APP, then SBWJ_NE_APP and SBWJ_APP. CTR Aldeia 2 (GND – 2000 FT) belongs to Aldeia Tower (SBES_TWR) and, without it, goes up to SBES_APP.

ATC Units

Code Abbr. Callsign Frequency Remarks
SBWJ_APP WJ Controle Rio 119.000
SBGL_TWR TGL Torre Galeão 118.200
SBRJ_TWR TRJ Torre Rio 118.700
SBSC_TWR TSC Torre Santa Cruz 118.800
SBAF_R_TWR RAF Rádio Afonsos 118.900
SBJR_TWR TJR Torre Jacarepaguá 118.400
SBES_APP XES Controle Aldeia 119.450 Subordinate to Rio APP

Top-down coverage

Read from bottom to top: when a position is offline, the airspace falls to the next online position above.

Show coverage diagram
flowchart BT
    p0["SBCW_CTR"]:::ctr
    p1["SBCW_CSE_CTR"]:::ctr
    p2["SBCW_CWE_CTR"]:::ctr
    p3["SBCW_SE_CTR"]:::ctr
    p4["SBCW_CE_CTR"]:::ctr
    p5["SBCW_E_CTR"]:::ctr
    p6["SBWJ_APP"]:::app
    p7["SBWJ_NE_APP"]:::app
    p8["SBWJ_N_APP"]:::app
    p9["SBWJ_GL_APP"]:::app
    p10["SBGL_TWR"]:::twr
    p11["SBWJ_S_APP"]:::app
    p12["SBWJ_RJ_APP"]:::app
    p13["SBRJ_TWR"]:::twr
    p14["SBSC_TWR"]:::twr
    p15["SBAF_R_TWR"]:::twr
    p16["SBJR_TWR"]:::twr
    p17["SBWJ_E_APP"]:::app
    p18["SBES_APP"]:::app
    a0(["Rio de Janeiro TMA"]):::esp --> p6
    a1(["Galeão CTR"]):::esp --> p10
    a2(["Rio CTR (SBRJ)"]):::esp --> p13
    a3(["Santa Cruz CTR"]):::esp --> p14
    a4(["Afonsos CTR"]):::esp --> p15
    a5(["Jacarepaguá ATZ"]):::esp --> p16
    a6(["CTR Aldeia 1"]):::esp --> p18
    a7(["Tubulão North"]):::esp --> p8
    a8(["Tubulão South"]):::esp --> p11
    p1 --> p0
    p2 --> p1
    p3 --> p2
    p4 --> p3
    p5 --> p4
    p6 --> p5
    p7 --> p6
    p8 --> p7
    p9 --> p8
    p10 --> p9
    p11 --> p6
    p12 --> p11
    p13 --> p12
    p14 --> p12
    p15 --> p9
    p16 --> p12
    p17 --> p7
    p18 --> p17
    classDef esp stroke-dasharray:4 3
    classDef twr stroke:#2e9e5b,stroke-width:2px
    classDef app stroke:#2f7fd1,stroke-width:2px
    classDef ctr stroke:#8a56c9,stroke-width:2px

VFR circulation

  • Flights from outside controlled airspace entering the TMA via the REA or REH corridors are exempt from filing a flight plan, but must first report registration, position, persons on board, endurance, origin and destination.
  • Rio 2 and Rio 3 use VFR frequencies in the real world: 133.300 (primary) and 126.200 (secondary).
  • SBRJ: with IFR approaches to RWY 02R, VFR departures to REA FOXTROT route via Icaraí, Piratininga Lagoon and the Itaipu gate.
  • Helicopter routes chart: CCV REH WJ2-Rio de Janeiro
  • Helicopter routes chart: CCV REH WJ3-Rio de Janeiro
  • Helicopter routes chart: REH Bacia de Santos
  • Ultralight routes chart: CCV REUL WJ3-Rio de Janeiro
  • VFR routes chart: CCV REA WJ1-Rio de Janeiro

Remarks

  • Rio 1 is class A between FL145 and FL245 and class C between 6500 FT and FL145.
  • The package does not split the Rio 1, 2 and 3 volumes: the map shows the TMA lateral outline, formed by the union of the APP sectors.
  • SBSC (Santa Cruz) and SBAF (Afonsos) are Air Force bases: civil aircraft require authorization from the base command. SBMI (Maricá) lies in a class G FIZ.

Sources: VATSIM Brasil SBCW sector package (lateral limits, positions, frequencies, top-down coverage, Tubulão delegation and Aldeia Control subordination) and AIP Brasil, AIRAC A 17/2026 (classes, vertical limits, ATS surveillance and VFR rules).

Back to the Curitiba FIR terminals overview.


  1. Frequency in the VATSIM Brasil sector package. ↩