Sao Paulo Airport (GRU) — Direct Flights, Airlines, USD Fares | Brazil

Guarulhos International (GRU, ICAO SBGR) serves Sao Paulo, Brazil and is a destination reached by travellers flying from across Africa. It is the based hub of LATAM Airlines, G3. Our catalogue links 0 direct destinations out of GRU and 2 African origins into it, served by 3 carriers.

At a glance

2 catalogued corridors touch Sao Paulo (GRU / SBGR) in Brazil: 0 outbound and 2 inbound, flown by 3 carriers, with LATAM Airlines and G3 based here. 0 of those corridors carry a cached USD quote in our fare file; the rest are catalogued on schedule evidence alone.

The route mix at GRU splits into 0 short sectors under four hours, 0 medium sectors of four to seven hours and 2 long-haul sectors beyond seven — a profile that tells you what the terminal is actually built around. 1 of the corridors here is flagged in our data as labour-migration or diaspora routes, where checked-baggage terms drive booking decisions more than schedule does.

Two codes, two uses. GRU is the IATA code you will see on a ticket, a baggage tag and a departure board, while SBGR is the ICAO code used in flight plans, NOTAMs and air-traffic filing. They are not interchangeable: IATA codes are reused across the world’s smaller fields and are the ones that cause mis-booking, which is why every corridor on this site is keyed on the pair of codes rather than a city name.

Airlines serving GRU

3 carriers appear on the GRU corridors catalogued here, 3 of them with a row in our carrier file, recording checked-baggage baselines of 23 kg, and 1 of those rows sits inside a global alliance (Star Alliance 1). That list is built from the 2 corridors this site catalogues through GRU, so it is our coverage rather than the airport’s full published schedule.

These carriers operate the GRU corridors catalogued on this site. Guarulhos International is the based hub of LATAM Airlines, G3, which anchors most of its schedule and connecting bank.

Alliance spread decides how easily a disruption at GRU gets fixed. With 1 Star Alliance carrier on these corridors, a passenger stuck here can sometimes be reflowed onto a partner without a new ticket — but only within the same alliance, and only when the original ticket permits it. Between alliances, re-accommodation is a commercial favour rather than an entitlement.

Top routes into GRU

7/10 is the highest demand score on any GRU corridor in our catalogue — Luanda to Sao Paulo (LAD–GRU), about 5 flights a week on DT and LA. Demand score is this catalogue’s own 1-10 editorial rating across 2 corridors at GRU, not a passenger count from a civil-aviation authority.

Sorted by demand; the USD market-low column is the cheapest fare our cache has seen on the corridor across all carriers.

About 100% of the roughly 12 weekly departures catalogued at GRU sit on just three corridors. That concentration is why the airport’s overall size tells you nothing useful about your own flight: on the trunk routes a cancellation costs hours, while on the tail of the distribution the next departure can be several days out. Read the frequency column, not the terminal.

Block times across these corridors run from about 8.5 h to 10.5 h. That range is the practical reason a single connecting-time rule does not work at GRU: a short regional inbound and a long-haul outbound have very different delay profiles, and a tight self-built connection between them is where most missed onward flights on this site’s corridors happen. On separate tickets there is no protection at all.

Corridors and typical fares from GRU

0 of the 2 GRU corridors carry a cached USD quote, so most pricing here is planning-band rather than observed. Fares are quoted in USD across the whole site so corridors from different African markets stay comparable. Sector length drives the shape: 0 run under four hours, 0 four to seven and 2 beyond seven.

Most GRU corridors here serve diaspora and long-haul family travellers. The mix is 2 long-haul routes (over 7 h). 1 are labour-migration or diaspora corridors where extra-baggage allowances matter. USD fares vary by corridor — intra-Africa typically $400–900, Gulf hubs $500–1,200, long-haul $800–2,200; each per-route guide below carries live cached fares.

The shape of the fare curve follows the sector length. The 0 short corridors under four hours from GRU price like regional traffic and move mostly with the day of the week; the 2 long-haul corridors beyond seven hours move with season and school holidays, and can double between the cheapest and dearest month in our own cache. Mixing the two on one average would be meaningless, which is why every corridor page carries its own floor.

Direct flights to GRU — 2 routes

2 catalogued routes are listed below for GRU, reaching 2 countries, led by Angola and South Africa. Our catalogue records 0 departure and 2 arrival corridors at GRU, each linking to a corridor guide with carriers, frequency, block time and any cached fare. The list is this site’s catalogue, not the airport’s timetable.

• JNB -> GRU
• LAD -> GRU

Every entry leads to a corridor page with the same skeleton of facts: who flies it, how often, how long the nonstop sector is scheduled to take, how far apart the two airports actually are, and what our fare cache has recorded. Routing and carrier decide the trip; the fare only decides between equivalents.

Treat the list as a catalogue rather than a timetable. Routes are included where African outbound demand justifies a guide, so charter and marginal regional services at Sao Paulo may be flying without being listed. Where a corridor is here, the carriers shown are the ones our route file records and a dash in the fare column means unqueried, not unavailable.

Hub airlines based at GRU

2 carriers base an operation at Sao Paulo (GRU): LATAM Airlines (LA), on 2 catalogued corridors and G3 (G3), on 0 catalogued corridors. A based carrier is where the airport’s recovery capacity lives. Across the 2 corridors catalogued at GRU, a based operation is what makes a same-day recovery realistic; an outstation carrier usually has one rotation and no local engineering.

LATAM Airlines, G3

Hub status is operational, not marketing. A carrier that bases aircraft and crew at GRU builds connecting banks around it, holds spare capacity there, and can usually re-crew or swap metal the same day. The same airline at an outstation typically has one rotation and no local engineering, so an identical technical fault produces a two-hour delay at the hub and an overnight at the outstation.

It also shapes price. The based carrier usually sets the fare level on corridors out of Sao Paulo and competitors price against it, which is why a hub airport is rarely the cheapest place to originate on its own home routes. Where our cache shows an unusually low floor at GRU, it is normally a competing carrier buying share rather than the hub carrier discounting.

FAQ

5 questions below answer what travellers ask most often about this page’s subject, drawn from the same route, carrier, airport and fare files as everything above. Where a figure is missing from our data, the answer says so rather than estimating.

How is GRU airport connected? GRU (Sao Paulo) is reachable on 2 direct routes in our catalogue — see the full route list above.

What are the IATA and ICAO codes for GRU airport? The IATA code is GRU and the ICAO code is SBGR. The airport serves Sao Paulo, Brazil.

Which airlines are based at GRU? Hub carriers at GRU: LA, G3.

How can I check fares and schedules for routes through GRU? Each route in the list above links to a guide with live USD fares, weekly frequency and the airlines that operate it.

Which airlines fly from GRU? Carriers on GRU corridors catalogued here: TAAG Angola Airlines, LATAM Airlines, South African Airways. See the airlines table above for alliance and baggage.

Related

1 related page follow. Each is linked because it shares an endpoint, a carrier, a country or an audience cluster with this one — the annotations say what each adds, so the ones that do not apply to your trip can be skipped.

• Flights to Brazil — country landing page: 6 catalogued corridors from African airports, carriers, visa row and the USD fare floor we have on file.

Internal links on this site are placed from the data, not from a keyword list: a corridor is linked when it shares an origin, a destination, a carrier or an audience cluster with the page you are on. If a link above looks unrelated to your trip, it probably shares a carrier or a hub rather than a destination.

Corridor pages carry the per-route detail — carriers, weekly frequency, scheduled block time, great-circle distance and whatever the fare cache holds. Airport pages carry the full catalogued route list at that field, the based hub carriers and the compensation regime of the country it sits in. Carrier pages carry the baggage baseline, alliance and the network as this catalogue records it.