Where can you fly nonstop? Direct-flight discovery, explained

The most useful map for a short trip isn't "where is cheap" - it's "where can I get to without a connection". This guide covers how nonstop discovery works, why direct-both-ways is the constraint that matters, and how to read the results honestly.

Why nonstop dominates short trips

A connection costs you, on average, 2-4 hours each way - plus the tail risk of a missed connection that eats a whole day. On a two-week holiday that's noise. On a 3-day trip it's 10-25% of your time away, spent in the wrong airport. That's why the practical question for weekend-scale travel is not "where should I go?" but "of the places I can reach nonstop, which do I want at this price?" Inverting the search this way - destination last, not first - is what discovery modes are for.

Direct out is not enough: the return leg

Route networks aren't symmetric in practice. Seasonal and low-cost routes may fly out on days that don't line up with when you want back; a leisure route might operate Monday/Thursday/Saturday only. A destination you can reach nonstop but can't leave nonstop on your dates quietly turns your short trip into a connection after all - in the direction where you're tired and out of buffer.

WRVR's Anywhere · direct mode enforces this both ways for round trips: it discovers every destination with a nonstop outbound from your airport(s) in your date window, then keeps only those that also have a nonstop return. What's left is the honest list of places a nonstop weekend actually works, ranked cheapest first.

Same city back, or a radius around it

By default a round trip returns from the city you flew into - any airport of that city (land Gatwick, leave Heathrow; the engine knows FCO and CIA are both Rome). If you're up for a little overland travel, a return-city radius loosens this: set 300 km and the return may depart any discovered city within that distance of where you landed - land in Milan, come home from Venice, with the train ride in between as part of the holiday. That's an open-jaw trip assembled from nonstop legs; the result card shows the ground gap distance so you can judge it. (Why open-jaw pricing works is its own guide.)

Reading discovery results honestly

Route discovery is only as good as its data, and it's worth knowing what the data is:

• Fare-based discovery shows where fares were seen, not the full route map. WRVR's data source is recently-observed fares. If a route exists but no fare for your window has been cached recently, it can be missing from the list. Absence of a city means "no recent cheap fare found", not "no flight exists". For a definitive route map, the airport's own destination list is the source of truth.
• Prices are indicative. Each result carries a freshness note ("seen 2d ago"); you confirm the live price at booking. The prices guide explains this pipeline.
• Seasonality is real. The nonstop list from your airport in July and in November are different lists. Discovery for "next month" reflects next month, not the annual network.

Ways to use it

• The classic: free weekend, no destination in mind. Anywhere · direct, round trip, 2-4 nights, whole month, weekend days pinned - scan twenty options in one screen.
• Deciding where to take visitors: parents in town for a week? The nonstop list is the realistic day-trip-by-air menu.
• New home airport: just moved? Run discovery once with a wide window - it's the fastest way to learn what your airport is actually good for.
• One-way drifting: in one-way mode, discovery lists every nonstop escape, cheapest first - useful for the "leave Friday, figure the rest out later" school of travel.

Try Anywhere · direct on WRVR →