GRU → MCZSão Paulo to Maceió

live

Direct flights from São Paulo (GRU) to Maceió (MCZ): 14 nonstop departures observed each week across 2 airlines. 85% of the last 20 operated flights arrived within 15 minutes of schedule. The median arrival is on schedule. No cancellations were recorded across the 20 tracked flights. The nonstop covers 1,919 km, an estimated 2 hours 58 minutes in the air. Measured by Pro Flight Search from live flight boards at São Paulo and Maceió. Updated 11 September 2026 at 01:03 UTC.

GRU São Paulo busy · +17
MCZ Maceió tracking
1,919 km · ~2h 58m est.
dep bank 07:58–23:5214x weekly
Runs reliable · 2 airlines · 14x weekly · nonstop
85% on time

of the last 20 operated GRU → MCZ flights arrived within 15 minutes

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

Median arrival+0 minacross the last 20 operated legs
Flight time~2h 58mestimated from route distance
Weekly departures14x2 direct airlines on the leg
Cancelled0.0%recent route rate · 0 of 20

The week

scheduled departures · origin local time
06121824
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Gol Transportes AéreosLATAM Brasil

Each mark is a scheduled departure at its origin-local time, observed operating in the last 7 days. Today is highlighted.

Who flies it

observed on the boards · 7 days
Gol Transportes AéreosG340% on time

Flights G31668 varies daily · G31670 14:00 daily · G31672 varies daily

LATAM BrasilJJ100% on time

Flights JJ3446 varies daily · JJ3450 varies Mo Tu We Th Fr Sa · JJ3448 varies Mo Th Fr Sa Su · JJ3452 varies Mo Tu We Th Fr Su

History

operated legs · board outcomes
09-10G31670departed+35
09-10JJ3448departed+0
09-10JJ3450departed+0
09-09JJ3198departed+0
09-09JJ3446departed+0
09-09JJ3450departed+0
09-09JJ3452departed+0
09-08G31670departed+43
09-08JJ3198departed+0
09-08JJ3450departed+0
09-07G31672departed+147
09-07JJ3198departed+0
09-07JJ3448departed+0
09-07JJ3450departed+0
09-07JJ3452departed+0
09-06G31670departed+13
09-06G31672departed+14
09-06JJ3198departed+0
09-06JJ3446departed+0
09-06JJ3452departed+0

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 +17 min busy 🌫 mostly cloudy · N 0 kt Full GRU delay board →
MCZMaceió tracking Full MCZ delay board →

How the São Paulo to Maceió route actually runs

Pro Flight Search records official board updates for nonstop GRU to MCZ 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 Maceió (MCZ) route reliability, measured from operated flights on official airport boards.

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

GRU to MCZ questions

Is GRU–MCZ running on time right now?

Mostly on schedule. The departure side at GRU is the weaker end, route health score 78/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from GRU to MCZ?

Great-circle distance is 1,919 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 165–194 min gate-to-gate on this route.

How often does GRU–MCZ fly?

2 carriers operate this route, around 52 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 MCZ, 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.