COR → BRCCordoba to San Carlos de Bariloche

live

Direct flights from Cordoba (COR) to San Carlos de Bariloche (BRC): 4 nonstop departures observed each week across 1 airline. The median arrival is 13 minutes late. No cancellations were recorded across the 4 tracked flights. The nonstop covers 1,257 km, an estimated 2 hours 7 minutes in the air. Measured by Pro Flight Search from live flight boards at Cordoba and San Carlos de Bariloche. Updated 18 October 2026 at 15:22 UTC.

Today, COR → BRC

Sun 18 Oct · local times
AR1554AEROLINEAS ARGENTINAS60 min late

The COR board at 12:22 shows departure at 14:20 instead of 13:20, gate 05 (TC).

Landing
16:30BRC board estimate · sched 15:35
Later cancelled
0.6%of 1,577 past AEROLINEAS ARGENTINAS flights whose board showed 40 to 70 min late
Still to leave today
No other nonstoplast COR to BRC departure of the day
Track AR1554 →
  1. 13:20 AR1554AEROLINEAS ARGENTINAS Est. 14:20 +60Gate 05 · TC BRC est. 16:30 +55sched 15:35

Checked COR board 12:22 · BRC board 12:22

COR Cordoba smooth · +0
BRC San Carlos de Bariloche smooth · +0
1,257 km · ~2h 07m est.
departs 13:254x weekly
Running clean · 1 airline · 4x weekly · nonstop
73 / 100

route health from live COR and BRC delay boards

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

Median arrival+13 minacross the last 4 operated legs
Flight time~2h 07mestimated from route distance
Weekly departures4x1 direct airline on the leg

Who flies it

observed on the boards · 7 days
AEROLINEAS ARGENTINASAR

Flights AR1554 varies Mo We Fr Su

History

operated legs · board outcomes
10-16AR1554dep +38 → arr+13
10-14AR1554dep +65 → arr+36
10-12AR1554dep +31 → arr−2
10-11AR1554dep +14 → arr−15

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
CORCordoba +0 min smooth 🌤 mostly cloudy · ENE 6 kt Full COR delay board →
BRCSan Carlos de Bariloche +0 min smooth ⛅ mostly cloudy · ENE 4 kt Full BRC delay board →

Weather lens

Current conditions put the pressure at BRC: 45% odds of a 15+ minute delay and around +15 min expected when it bites, measured from this route's own weather-matched delay history. See live delays → · Weather risk by airport →

How the Cordoba to San Carlos de Bariloche route actually runs

Pro Flight Search records official board updates for nonstop COR to BRC 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 — Cordoba (COR) to San Carlos de Bariloche (BRC) route reliability, measured from operated flights on official airport boards.

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

COR to BRC questions

Is COR–BRC running on time right now?

Mostly on schedule. Both endpoints currently score the same, route health score 73/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from COR to BRC?

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

How often does COR–BRC fly?

AEROLINEAS ARGENTINAS runs the route with about 4 flights a week (sun, mon, wed, fri). Since one carrier owns the route, a single disruption tends to ripple through the day.

What does the route health score measure?

A blend of departure-side delay at COR and arrival-side delay at BRC, 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.