GRU → MDZSão Paulo to Mendoza

live

Direct flights from São Paulo (GRU) to Mendoza (MDZ): 18 nonstop departures observed each week across 3 airlines. 60% of the last 10 tracked flights arrived within 15 minutes of schedule. The median arrival is 10 minutes late. No cancellations were recorded across the 10 tracked flights. The nonstop covers 2,419 km, an estimated 3 hours 36 minutes in the air. Measured by Pro Flight Search from live flight boards at São Paulo and Mendoza. Updated 30 October 2026 at 03:08 UTC.

Today, GRU → MDZ

Fri 30 Oct · local times
  1. · G37486GOL LINHAS AÉREAS On schedule MDZ 12:55scheduled
  2. · JJ8168LATAM BRASIL On schedule MDZ 16:05scheduled

Checked GRU board 22:03 · MDZ board 00:08

GRU São Paulo busy · +18
MDZ Mendoza heavy · +50
2,419 km · ~3h 36m est.
dep bank 08:15–12:2718x weekly
Runs mixed · 3 airlines · 18x weekly · nonstop
60% on time

of the last 10 tracked GRU → MDZ flights arrived within 15 minutes

Median arrival delay is +10 min. 0 of 10 tracked legs cancelled in the sample. Will a delayed flight be cancelled? →

Median arrival+10 minacross the last 10 arrivals
Flight time~3h 36mestimated from route distance
Weekly departures18x3 direct airlines on the leg
Cancelled0.0%recent route rate · 0 of 10

Who flies it

observed on the boards · 7 days
GOL LINHAS AÉREASG3

Flights G37486 varies Tu Th Fr Su

LATAM AirlinesLA

Flights LA8019 varies Mo Tu Th Sa Su

LATAM BrasilJJ43% on time

Flights JJ8019 varies Mo Tu Th Sa Su · JJ8168 varies Mo We Fr Su

History

operated legs · board outcomes
10-29G37486dep +29 → arr−10
10-29JJ8019dep +0 → arr+10
10-28JJ8168arrived+0
10-27G37486dep +11 → arr−10
10-27JJ8019dep +0 → arr+47
10-26JJ8019dep +0 → arr+63
10-25G37486dep +17 → arr+9
10-25JJ8168arrived+24
10-24JJ8019dep +0 → arr+31
10-23JJ8168dep +0 → arr+6

Actual board outcomes rather than schedules, paired departure and arrival per flight and day.

Full board history, day by day →

Airports right now

live boards
GRUSão Paulo +18 min busy 🌫 overcast · SSW 2 kt Full GRU delay board →
MDZMendoza +50 min heavy 🌤 few clouds · SW 3 kt Full MDZ delay board →

Weather lens

Conditions are tightest at MDZ: a 38% chance of a 15+ minute delay. In this weather, the more delayed of the two airports is typically about +12 min. Both figures come from the two airports' delay records in similar weather. See live delays → · Weather risk by airport →

How the São Paulo to Mendoza route actually runs

Pro Flight Search records official board updates for nonstop GRU to MDZ flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: São Paulo (GRU) to Mendoza (MDZ) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/GRU-MDZ
How we measure this →

GRU to MDZ questions

Is GRU–MDZ running on time right now?

Some delays possible. The arrival side at MDZ is the weaker end, route health score 55/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from GRU to MDZ?

Great-circle distance is 2,419 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 201–237 min gate-to-gate on this route.

How often does GRU–MDZ fly?

3 carriers operate this route, around 18 flights a week between them. Compare carrier days and times in the airline list above.

What does the route health score measure?

A blend of departure-side delay at GRU and arrival-side delay at MDZ, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.