Route profile

Montevideo (MVD) → Asuncion (ASU)

A reference for the Carrasco International /General C L Berisso Airport to Silvio Pettirossi International Airport route. You'll find the operators on file, the great-circle geometry, the connecting options if no nonstop fits your dates, and a short profile of each endpoint airport.

1,077 kmGreat-circle distance
669 miIn miles
2hApprox. block time
1Operators on file

The flight from Montevideo (MVD) to Asuncion (ASU) covers a great-circle distance of roughly 1,077 km (669 miles). Aircraft leave Carrasco International /General C L Berisso Airport on an initial north heading. As international sectors go, this one sits in the medium-haul bracket: long enough that most carriers run it as its own dedicated rotation, but short enough to fit inside a single crew duty period.

BQB Lineas Aereas is the only carrier filing a scheduled MVD to ASU service in the dataset. Single-operator routes like this usually reflect a focus-city or hub-spoke relationship, or a market that's big enough to support one dedicated daily but not big enough to attract a second entrant yet.

Operators on the MVD → ASU direction

Carriers with at least one scheduled rotation on this sector in the OpenFlights dataset, ranked by the number of code-shared filings.

IATAAirlineCountryCallsign
5Q BQB Lineas Aereas Uruguay

A medium-haul sector of this length is an operational sweet spot. Block time lands near 2h, well inside a single crew duty for most carriers, and modern narrow-bodies (A320neo, 737 MAX, A321) can fly it without payload restrictions. Premium-cabin product on this kind of sector is usually a recliner seat rather than a fully flat bed.

If a nonstop doesn't match your dates, Miami (MIA), Sao Paulo (GRU), and Lima (LIM) show up on both ends of the network and make the most natural connecting points. The connecting-hubs grid below extends that list to the eight strongest options, ranked by each airport's overall departure activity. That ranking is a fast proxy for how many onward flights a single stop is likely to feed.

Connecting hubs

Airports that already appear on both ends of this network. They're the natural one-stop options when no nonstop matches your dates, ranked by overall departure activity.

This is an international sector between Uruguay and Paraguay. Build in time for passport validity, possible visa requirements, and the time-zone gap between Montevideo and Asuncion. International itineraries are quoted in local time at each end, so a "midnight" departure in Montevideo typically lands the next morning in Asuncion. Customs clearance happens on first arrival in the destination country.

On the day of operation, the MVD to ASU direction lifts off heading north, then the great-circle track curves to compensate for the Earth's rotation. The return ASU to MVD sector heads south out of the gate, with 1 operators on file for the inbound side. Combine the two operator lists for a full picture of the city pair's competitive landscape.

Endpoints

Other routes from Montevideo (MVD)

Other destinations served from the same origin. Handy for combining trips or for finding an alternate first leg.

Other routes into Asuncion (ASU)

Other origins that already file scheduled service into the destination airport.

Reading this route page

The operator list reflects scheduled-route filings in the OpenFlights dataset, not real-time availability. A carrier appearing here publishes a scheduled service on this sector. It isn't a live timetable, and the actual flight numbers, frequencies, and aircraft types shift season to season. For booking and current schedules, cross-reference the airline page above with the carrier's own website.

Distance here is the great-circle arc between the two airports' published coordinates. Real flight tracks wander off that line because of wind, ATC routings, oceanic crossings, and political airspace constraints. Block time is an estimate covering ground taxi, climb, cruise at typical jet speeds, and descent. Real block times shift with aircraft type, weather, and traffic, so treat the stat-strip number as a planning indicator rather than a published flight time.