How long does a flight deal last?

Someone sees a fare drop and asks the same question every time: is this here tomorrow, or do I need to decide right now? The honest answer is that “flight deal” describes three different events with three different clocks, and the site showing you the fare will not tell you which one you are looking at.

The question hides three questions

A fare a few dollars under yesterday’s number, a fare 40% under the route’s normal range, and a fare that has quietly stayed low for three weeks are not the same phenomenon wearing different sizes. They come from different causes, and the cause is what sets the clock.

Sorting a fare into the right one of the three below takes less time than reading a countdown banner, and it is the difference between booking calmly and booking scared. It is also the sorting Flydar does before a fare ever reaches your inbox, so the rest of this piece works whether you run it by hand or let the product run it for you.

Mistake fares: hours, sometimes minutes

A mistake fare is a price the airline never intended to publish: a fare-basis error, a currency conversion fault, a missing fuel surcharge. The window is short because the error is spotted from the inside, not because demand exhausts it. Once someone in revenue management notices, the fare is pulled, usually within hours and sometimes within minutes of going live.

That short window is also the reason mistake fares favour whoever was already watching a route closely enough to recognise an absurd number as absurd. The mechanics, the booking rules, and what US regulation promises you if one gets cancelled are covered in full in mistake fares explained. This piece will not repeat that ground, because the two lifespans have nothing else in common with what follows.

Where Flydar sits on this one: squarely in it. A fare that far below a route’s normal price clears the bar instantly, and Flydar notifies you the moment it does, mistake fare or not, on any route you have named. The product does not need to know which of the three lifespans it is looking at to act correctly. It only needs the fare to be clearly low, and this category is the least ambiguous kind of low there is.

Ordinary drops: days, sometimes a couple of weeks

Most fares that look like deals are not errors at all. They are a cheap fare bucket that reopened because bookings on that flight are running behind the airline’s forecast, exactly as why flight prices change describes. Nobody made a mistake. The pricing software made a routine adjustment, and the routine adjustment happens to be good for you.

This kind of drop tends to last as long as the bucket stays open, which in practice runs from a few days to a couple of weeks before demand catches up or the airline tightens the forecast again. Picture a route that normally runs $650 to $950 round trip. A bucket reopens, the fare drops to $580, and it sits there for eleven days before selling through and stepping back up to $710. Nothing about the eleven days is announced anywhere. You either caught it or you did not.

That is also why an ordinary drop is not a single irreplaceable moment. Because the cause is a forecast running behind, not a one-off event, the same route often dips again within a few weeks if you miss this one. The clock resets rather than closing.

This is the lifespan Flydar is built around. Days to a couple of weeks is exactly long enough that a person checking manually will most often miss it, and exactly short enough that nobody sustains a personal checking habit that would reliably catch it either. You name the route once, Flydar keeps comparing every fare against what that route normally costs, and you hear about it the moment one clears the bar, not the day you happen to remember to look. Missing the eleven days above costs you nothing you were paying attention to lose; it costs the thing that was watching for you.

Seasonal soft patches: weeks, sometimes a month or more

The slowest of the three, and the easiest to mistake for something more urgent than it is. A whole route, not one flight, sells below its usual band for an extended stretch, because demand for that period is genuinely soft: a shoulder-season week, a destination between festival dates, a route still recovering from a schedule change. This is not one bucket reopening on one departure. It is the forecast for a whole slice of the calendar sitting lower than usual, and it can hold for a month or longer before demand or capacity catches up.

A soft patch rewards patience the mistake fare punishes. There is no single flight to grab before someone else does. There is a window of weeks in which most departures inside it price lower than the route’s ordinary season, and it usually recurs at roughly the same point on the calendar the following year, which is a different, calmer kind of “it’ll be back.”

This is also where a route watcher without fixed dates earns its keep. A soft patch does not care which day you meant to fly, only that the whole window is cheap, and a per-search alert bolted to one date pair cannot see a window at all. Flydar’s default is a departure range rather than a single date, so a month-long dip shows up as what it is: several weeks of qualifying fares, not one lucky day. Tracking a route with no fixed dates is a longer treatment of exactly this gap.

Telling which one you are looking at

Two questions, and they sort almost every case correctly.

How far below the normal range does it sit? A drop of 40% or more, especially on a route where that has never happened before, is a mistake-fare candidate. A drop of 15-25% that still lands inside or near the route’s known low end is an ordinary bucket reopening. Establishing the normal range in the first place is the whole method in how to tell if a flight price is good, and it is the one piece of homework that makes every question on this page answerable.

Is it one flight or a whole stretch of dates? Pull the flexible-date calendar. If only your exact departure date is cheap and the days either side are not, you are looking at one bucket on one flight, the ordinary case. If a run of two or three weeks is uniformly low, you are looking at a soft patch, and there is no reason to fixate on today’s date over next Tuesday’s.

Both questions take about ten minutes by hand, using the same calendar-grid method as judging any fare. Flydar runs the same two comparisons against the routes you have named before it ever emails you, which is why a Flydar alert already tells you a fare is worth acting on rather than handing you a number and leaving the sorting to you.

The decision rule for each

Mistake fare: move within the hour. Book direct, do not call to confirm, and read the fuller rules before you do either.

Ordinary drop: there is no reason to panic, but there is a reason not to sit on it for a month. The bucket that opened will close, typically inside two weeks. Book when it clears your threshold, using the 24-hour reservation requirement if you want a short pause to check anything else (US carriers must let you cancel for a full refund within 24 hours on tickets bought at least seven days before departure, though not on bookings made through a third-party agent), and stop pretending the decision is more urgent than it is. If a Flydar alert is what told you about it, the threshold check already happened, so the only decision left is whether the trip itself is a yes.

Seasonal soft patch: the least urgent of the three. If your dates are flexible inside the window, there is little cost to waiting a few more days to see whether it drops further, and if it does not come back next year at the same time, nothing was lost by treating it calmly. This is also the safest lifespan to leave entirely to a route watcher, since nothing about a multi-week window rewards checking it more than once.

The question that matters more than “how long”

Most people never get to ask any of this, because they never see the fare drop in the first place. They are not checking a calendar grid on a Tuesday afternoon in March for a trip they have not committed to. Nobody does that indefinitely, for every route, forever, which is the real reason the countdown banner works: it is selling urgency to someone who has no other way of knowing if this is rare or routine.

The lifespans above only matter to a person who was already looking. That is the entire product: you name the routes you would actually take, and Flydar keeps comparing every fare against what that route normally costs, for as long as you want it watched. When one clears the bar, mistake fare, ordinary drop, or soft patch, whichever it turns out to be, that is the only time you hear anything. Nothing when it rises, nothing when a sale banner sits over an ordinary price, and no guessing about which of the three clocks is running, because the clock has already been checked before the email exists.

You can still run the method above by hand, for every route, on a schedule, indefinitely. Or you can name the routes once and let something else carry the part of this that never ends.

Either way, the sorting comes down to three lines:

• 40% or more below the route’s normal range, on one departure nobody else is matching: hours, sometimes minutes. Move now, or accept you have missed it.
• 15-25% below, on one flight, with the days either side unchanged: days to a couple of weeks, and the same route tends to dip again within a few weeks if you miss it.
• A run of two or three weeks all sitting low together: a month or more, no single moment to catch, and usually the same stretch of calendar again next year.