the instruction, taken apart
What Leaves Your Browser When You Press the Fare Button
Every trip in this catalog opens with the odds against it, on the principle that a number you can read settles what a paragraph only argues about. This page applies the same principle to the fare box: it takes the instruction the button sends and reads it back, character by character, and then says who receives it.
Why a seat carries no odds
Nineteen trips sit in this catalog and each one leads with a percentage: how often the weather has beaten that trip in those months. It leads with it because a percentage is checkable and a reassurance is not.
A scheduled flight cannot be given that number, and the reason is not shyness. Aircraft go in weather that closes a mountain pass, cancels a sailing and shuts a trailhead. On the uncommon day one does not go, an airline moves you onto another under rules written long before you booked, and this office has no standing in that decision whatsoever.
A thing with no odds against it and no negotiation behind it does not need a desk in the middle. It needs a field, a button, and an honest account of who answers.
The instruction, taken apart
Choose two airports and a departure date and the button has everything it needs. What it sends is one parameter.
Suppose it reads `CLE1509LIS2409c200`.
- `CLE`
- The airport you leave from
- `1509`
- The fifteenth of September, going out
- `LIS`
- The airport you land at
- `2409`
- The twenty fourth, coming back
- `c`
- Cabin. Blank means economy, `w` premium economy, `c` business, `f` first
- `2`
- Adults occupying seats
- `0`
- Children aged two to eleven
- `0`
- Infants traveling on a lap
Thirteen characters for a one way seat, eighteen for that one. Nothing else rides along, because the parameter has no room for anything else.
Why the day of the week is printed
Fill in a date and the day it falls on appears underneath, spelled out.
A date control shows `09/15/2026` and stops. The two commonest ways to get a flight wrong are a day out and a month out, and neither looks wrong in digits. Tuesday looks wrong immediately if you meant the weekend.
It is worked out in your own browser from the numbers already in the field, it is shown to you and to nobody else, and it forms no part of what the button sends.
Whose systems answer
Not this office's. The list reads the same way all the way down.
- Producing the prices
- A booking company, live, from its own systems
- Holding your seat
- That company
- Taking the card
- That company, on its own pages. Nothing in this catalog carries a field that could accept one
- Setting the conditions on the ticket
- That company. Those are the terms that govern, and this page is not one of them
- Altering the booking afterwards
- Beyond anything this office can do, and it will not suggest otherwise
- What comes back here
- Part of a margin that company had already built into its figure, and only where a sale happens
- What that costs you
- Nothing. The figure was fixed before anyone knew which website you came through
What stays on this machine
Airport codes arrive once, as a single file, when the page loads. Everything after that happens where you are sitting: the matching against what you type, the ordering of the suggestions, the day of the week, and the assembling of that one parameter.
- A name
- Not asked for by this box, therefore not in the instruction
- Somewhere to write back to
- Not asked for
- A telephone number
- Not asked for
- Anything typed into the question form elsewhere on this site
- Stays with that form; the two share a website and nothing else
- The first thing to leave your browser
- The press of the button. Everything before it is silent
A city you started typing and thought better of reaches no machine but this one.
What the box turns down
Nothing at all happens before the script arrives, and the button says so by staying gray. An instruction the far end cannot parse does not fail loudly; it comes back as a blank page, which is worse.
Seven refusals, each printed against the field responsible rather than gathered under the button. A city typed but never taken from the suggestions, since only a real code may travel. The same airport at both ends. A departure already past. A return dated before its own departure, and that field empties itself if the departure is moved past it. Ten or more in the seats, nine being what one instruction holds. A lap infant with no adult seated beside it. And anything beyond eleven months.
The eleven months, and why not twelve
Look again at `1509` and `2409`: a day and a month, four digits, and no year in either.
That is what the far end expects, and it works until the question runs past twelve months. Ask for something sixteen months out and four digits cannot record which September you meant. The far end assumes the nearer one and comes back with genuine prices for dates nobody asked about, saying nothing about the substitution. Eleven months is the last month those four digits still mean one thing, so eleven months is where the box stops.
Two things this is not
It is not a quotation, and neither are the flight numbers on the trip pages. Those are a year of watching what a route asks, set down so a whole week can be costed at one sitting. Like the odds beside every trip here, they describe a pattern and promise nothing about any single day. The figure to act on is the live one, and it appears on their page rather than on this one.
Neither is it a route into a trip that somebody operates. As soon as a departure hangs on a minimum number aboard, or on a clause about wind and ice, or on a date past which it is on or off, a search field has nothing useful to say about it. That is the point at which the desk starts earning its keep.