Skip to content

SBFI - Foz do Iguaçu

General Information

Information
Aerodrome name Foz do Iguaçu - Cataratas
Type of Operation International and Public
Transition altitude 4000 ft5
Elevation 787 ft (240 m)
Largest aircraft Code 4C (A321, B737)1
Airspace Cataratas CTR, class C, GND/FL0655
Accepts A380?

Useful Information

Select one of the tools in the tabs above (Charts, Weather or Traffic) to access the aerodrome information.

Loading METAR...
Loading TAF...

Traffic

Runways

Runway system

SBFI has one runway, 15/33 (2705 × 45 m, asphalt), with no parallel taxiway. All links between the runway and the aprons are on the southeast half: D, A, B and C lead to aprons 1 and 2, and F leads to apron 3, next to threshold 33. E runs along the front of aprons 1 and 2, from D to C.

  • Runway 15

    ILS CAT I. Takeoff from the threshold, with a backtrack of ~1340 m from D.

  • Runway 33

    RNP. Takeoff from the threshold, with a backtrack of ~670 m from C (or ~135 m from F).

Runway selection

The AIP sets no preferential runway: the runway in use follows the wind.

Runway data

Runway Dimensions TORA LDA Approach Pattern
15 2705 × 45 m 2705 m 2705 m ILS CAT I Left (standard)
33 2705 × 45 m 2705 m 2705 m Non-precision (RNP) Right (non-standard)
  • The AD accepts aircraft up to code 4C1.
  • 180° turns for aircraft with a wingspan of 20 m or more only on the turnaround areas; aircraft with an MTOW above 40 t turn only at the thresholds2.
  • The SBFI traffic pattern is a racetrack NNE of the runway centerline: left-hand on 15 and right-hand on 336.

ATC Units

Code Abbr. Callsign Frequency Remarks
SBFI_ATIS AFI ATIS 136.975
SBFI_TWR TFI Cataratas Tower 118.800 DCL (code SBFI)
  • The VATSIM package only has Tower: there is no Ground or Clearance Delivery. The voice ATIS exists only on the network; in the real world it is D-ATIS only3.
  • Above Tower, top-down: SBWI_APP (Foz Control, 120.300), which controls the Foz TMA and the Foz 1 and 2 CTRs.
  • The Cataratas CTR is class C, from the ground to FL0655.

DCL

The ROTAER lists DCL on Cataratas Tower3. On the network, the station code is SBFI. There is no Clearance Delivery (DEL) position: Tower issues the clearances.
Station code SBFI
Who operates it SBFI_TWR. Without TWR, the position covering clearance top-down (APP or ACC)
Controller tool DCL window, with your personal Hoppie ACARS code
Pilot tool Aircraft ACARS or a Hoppie-compatible client, sending the clearance request to SBFI

How it works:

  1. The pilot sends the request (RCD) to SBFI, with the parking stand and the ATIS letter, if any.
  2. The controller checks the flight plan and replies with the clearance: limit, runway, SID, transponder code and next frequency.
  3. The pilot accepts (WILCO/ACCEPT). The clearance is then issued and there is no voice readback.
  4. With the clearance accepted, the pilot calls Tower for start-up or pushback.

Controller setup

  • Log in to the DCL with the code SBFI before opening the position.
  • Announce it in the controller information: DCL AVBL LOGON SBFI.
  • A faulty request (invalid plan, wrong SID) goes back as REVERT TO VOICE: the pilot calls Tower on frequency.
  • If the pilot does not accept within a reasonable time, consider the clearance not delivered and call them by voice.

Areas of responsibility

Since there is only a Tower position, SBFI_TWR controls everything: aprons, taxiways and runway 15/33. Neither the AIP nor the package has a Ground or Apron position.

  • Departure: Tower issues the clearance (DCL or voice), approves pushback and taxi, clears the aircraft to enter and backtrack the runway, and clears the takeoff, all on the same frequency.
  • Arrival: Tower clears the landing and, once the aircraft has vacated, the taxi to the apron.
  • Pushback is mandatory for aircraft the size of an E-145 or larger leaving the stand4.
  • With no parallel taxiway, the runway is the taxi route to the thresholds: while an aircraft backtracks, the runway is occupied. Plan the landing and takeoff sequence with that time in mind.

Ground flow

General rule

  • There is no parallel taxiway: every departure enters the runway and backtracks to the threshold.
  • E links aprons 1 and 2 to exits D, A, B and C. Apron 3 only connects to the runway, via F.
  • Turnaround areas: at the thresholds, one north of the runway ~670 m from threshold 15, and one south of it ~465 m from threshold 33.

Ground flow on runway 15: departures via E to D and backtrack to threshold 15; landings vacating via C; apron 3 via F
Green: departures. Blue: landings. Orange dashed: landing for apron 3.

  • Departures (15): E to D, enter the runway and backtrack ~1340 m to threshold 15. From apron 3, F and a backtrack of the whole runway.
  • Landings (15): vacate via C (~2030 m) or B (~1790 m) for aprons 1 and 2. For apron 3, vacate via F (~2565 m).

Example: AZU4321, taxi via E and D, enter and backtrack runway 15, report ready.

Ground flow on runway 33: departures via E to C and backtrack to threshold 33; landings vacating via A; aircraft rolling past D turn on the turnaround area and come back
Green: departures. Blue: landings. Orange dashed: landing rolling past D.

  • Departures (33): E to C, enter the runway and backtrack ~670 m to threshold 33. From apron 3, F and a ~135 m backtrack.
  • Landings (33): vacate via A (~1190 m) or B (~910 m, smaller aircraft) and continue on E. An aircraft that rolls past D (~1360 m) has no further exit: it turns on the turnaround area (or at threshold 15 if above 40 t) and backtracks to D.

Example: GLO1234, taxi via E and C, enter and backtrack runway 33, report ready.

Runway exits

Runway Exits
15 D (~1340 m), A (~1505 m), B (~1790 m), C (~2030 m) or F (~2565 m, apron 3)
33 F (~135 m, apron 3), C (~670 m), B (~910 m), A (~1190 m) or D (~1360 m)

Approximate distance from the threshold to the exit, measured on the diagram. The SBFI AIP does not publish exits.

Takeoff points

SBFI overview with aprons, turnaround areas and the takeoff points at the thresholds
Takeoff points (purple) with the available TORA. Circles: aprons.
Runway Point TORA Used by
15 Threshold 15 (backtrack) 2705 m All
33 Threshold 33 (backtrack) 2705 m All
  • The SBFI AIP does not publish intersection takeoffs.

Aprons and airlines

Reference for simulation. Stands follow the PDC charts; airlines follow the airport's airline list on Wikipedia. The split between stands is a simplification, not the airport's official allocation. VAs use the stands of the real airline they represent.

Apron2Passenger terminalDomestic and international, via B or CStands 7 to 11
Azul
AZU
GOL
GLO
LATAM
TAM
JetSMART
JAT
Apron1Hangars and cargo terminalVia D or AStands 1 to 6

Cargo and general and business aviation.

Apron3Next to threshold 33Only via F, from the runwayStands 12 to 15

General aviation and helicopters (stands 12H to 15H).

Logos from GRU Airport. Trademarks belong to their respective airlines.

Other procedures

  • Follow the VAC to enter and leave the traffic pattern6.
  • The Foz TMA aerodromes have their patterns on different sides of the runway centerline, all racetracks6:
    • Foz do Iguaçu (SBFI): NNE;
    • Cataratas del Iguazú (SARI, Argentina): SSW;
    • Ciudad del Este / Guarani (SGES, Paraguay): WNW;
    • Hernandarias / Itaipu (Paraguay): WNW.
  • Flights over the Iguaçu Falls need prior coordination and authorization from Cataratas Tower and follow the VAC pattern6.
  • On the approach to threshold 33, watch for helicopter traffic over the Falls at 1650 ft (ROTAER).
  • Every IFR flight in the Foz TMA or the Cataratas, Foz and Guarani CTRs needs two-way communication with the ATS units6.

Diagrams drawn by VATSIM Brasil over OpenStreetMap geometry (ODbL), checked against the SBFI ADC and PDC charts. Not for real-world navigation. Normative source: AIP Brasil, AD 2 SBFI, AMDT 2610A1.

  1. AIP Brasil, AD 2 SBFI 2.20, item 1. ↩↩

  2. AIP Brasil, AD 2 SBFI 2.20, item 6. ↩

  3. AIP Brasil, AD 2 SBFI 2.18 and ROTAER. ↩↩

  4. AIP Brasil, AD 2 SBFI 2.8, item 6. ↩

  5. AIP Brasil, AD 2 SBFI 2.17 and IAC charts. ↩↩↩

  6. AIP Brasil, AD 2 SBFI 2.22. ↩↩↩↩↩