FocusFlight

There is a category of commercial flight that is genuinely strange. It is long enough that two of them, end to end, would beat the average person's working week. Long enough that the cabin crew rotates twice. Long enough that you cross the international date line, climb into a new climate band, and watch the sun pass overhead more than once before the wheels touch down. These are the ultra-long-haul routes — Sydney to London, Singapore to New York, Paris to Sydney — and they sit at the outer edge of what aviation, and human endurance, currently allow.

This hub uses eleven of those routes as the basis for the longest deep-work containers FocusFlight offers. The shortest route on the list is New York (JFK) → Singapore (SIN) at 18h 10m / 15,339 km. The longest is Sydney (SYD) → London (LHR) at 21h 32m / 17,020 km — currently among the most ambitious non-stop legs flown by any commercial carrier. If you press start on the SYD–LHR timer in the morning, the timer outlasts the working day, the evening, and most of the night before it expires. That is the point. It is a container designed to hold something that genuinely needs more than a day of attention.

These routes are not for the kind of work most people do most of the time. They are for the work you have been delaying because no normal window is large enough to fit it. The whole dissertation chapter, written from outline to first draft in one sitting. The all-day code refactor that touches twelve files and cannot be left half-done. The legal brief that has to be argued from premise to conclusion in a single, continuous read.

What this kind of timer is good for

There are three legitimate uses for an 18-to-21-hour focus container. Outside those three uses, picking a route from this hub is almost certainly the wrong choice — and we'll get to the failure modes shortly.

The first is the project you have been delaying for months because every shorter session is honestly too small to hold it. A doctoral candidate writing a chapter. A novelist writing the climactic three chapters that have to be drafted as a single arc or they won't sit right. A senior engineer doing an architectural rewrite that touches the database layer, the API contracts, and the front-end calls — and where pausing mid-stream means rebuilding context for an hour the next morning. The reason ordinary deep-work blocks don't help these projects is not lack of effort. It is that the cost of putting the work down and picking it back up is, for some projects, genuinely larger than the cost of just sitting with it for another six hours.

The second is the symbolic session. The "I am clearing my calendar and attempting this one thing as a personal experiment" session. People run marathons for symbolic reasons that are not strictly logical, and they run all-day focus sessions for similar reasons. The narrative matters. The fact that you booked a Sydney–London-shaped block on your calendar and made it through tells you something about yourself that a stack of forty-five-minute Pomodoros, however productive, cannot.

The third is paired work across time zones. If you and a collaborator on the other side of the world both run a Sydney–Paris-shaped timer on the same calendar day, you are both in deep work for most of each other's waking hours. The synchronisation is not magical, but it is unusually useful for projects that benefit from continuous coverage without continuous interruption — code reviews that get answered the same business day, manuscripts that move forward overnight.

The hub is not for switchy work, meeting-heavy days, anything requiring real-time collaboration with people you haven't pre-coordinated with, or any task that decomposes cleanly into four-hour chunks. If your work can be done in four hours, a 20-hour timer is a 16-hour drift session attached to a 4-hour deep block. Use a shorter route.

The route gallery

The eleven routes below are ordered from shortest to longest. The shorter end of the band starts at just over eighteen hours; the longest crosses twenty-one and a half.

New York (JFK) → Singapore (SIN) — 18h 10m

The 15,339 km eastbound leg from JFK across the polar region into Southeast Asia, with a +13 hour clock jump on arrival. This is the shortest route in the hub but still longer than any other timer on the site by a wide margin. Use it for a project where the unit of completion is a single deliverable that has to feel finished by the end — a research paper draft from outline to last paragraph, an investor deck built and rehearsed in one sitting, a long-form essay that is supposed to come out as one continuous voice rather than a stitched-together draft. The 18-hour window lets you split the work into three big blocks of four to five hours, with two real breaks and one shorter mid-block reset.

Toronto (YYZ) → Singapore (SIN) — 19h 10m

The 14,994 km variant from Toronto's Pearson, crossing high latitudes and arriving in Singapore +13 hours later on the calendar. At nineteen hours and ten minutes, the timer adds a full extra hour of cruise to the JFK shape — enough to fit one additional medium-sized block at the end of the session, the kind of "wrap-up phase" where the testing, documentation, and final email get written rather than left for the next morning. Pearson is one of the busiest airports in North America and the home hub of Air Canada; the cabin ambience here works well for the technical-work variant of this session, since you have already committed to a longer container than the work strictly requires.

Singapore (SIN) → New York (JFK) — 19h 36m

The westbound counterpart to JFK–SIN, slightly longer at 19h 36m because of headwinds across the polar route, with a −13 hour clock jump (you arrive in New York on the same calendar day you left Singapore, which is mathematically true and emotionally bizarre). Singapore Changi is famous for the Jewel complex centred on the world's tallest indoor waterfall — a useful aesthetic anchor for a session that is going to last most of a day. Use this timer when the work has a strong "land it before they wake up" component: a feature that needs to be merged before the New York team starts their morning, a manuscript that has to be in the editor's inbox by US business hours, a financial close that has to be done before the markets open.

Amsterdam (AMS) → Sydney (SYD) — 19h 48m

The 16,658 km eastbound Kangaroo Route from Schiphol, +9 hours on the clock at arrival. At nineteen hours and forty-eight minutes, this is where the routes start to feel like genuine endurance containers rather than long workdays. The shape that fits this duration best is three blocks of approximately five hours each, with two real meal-and-walk breaks of forty-five to sixty minutes between them, and a strict commitment that the last block is reserved for closing — testing, documentation, sending the final email, archiving the working files. Without that closing block, a twenty-hour session ends in a tired drift rather than a clean ship.

Frankfurt (FRA) → Sydney (SYD) — 19h 38m

The 16,496 km Kangaroo Route from Lufthansa's main hub, also +9 hours. Functionally very close to the AMS–SYD timer above, with about ten minutes of extra cruise. Pick this one when you want a slightly tighter container — for example, if the goal is to write a complete legal brief from premise through argument structure to citations, and you have a precise sense that the work fits in just under twenty hours rather than just over.

Paris (CDG) → Sydney (SYD) — 20h 07m

The 16,944 km Charles de Gaulle to Kingsford Smith leg, +9 hours. Crossing the twenty-hour threshold meaningfully changes the session. Anything past about twelve hours of effective focus is past the point where additional time produces additional output for most people — the empirical literature on sustained attention is consistent that performance plateaus and then degrades after roughly that point. The reason a twenty-hour timer is still useful is that the container is twenty hours, but the work inside it is meant to include real recovery breaks, eating, walking around, and the natural rhythm of a day rather than continuous grinding. If you treat this as twenty hours of unbroken concentration, you will fail. If you treat it as a day-and-a-half-shaped envelope for one big project, you will succeed.

London (LHR) → Sydney (SYD) — 20h 11m

The Kangaroo Route's most famous incarnation: Heathrow to Sydney non-stop, 17,020 km, +10 hours on arrival. Currently one of the longest scheduled commercial flights in the world. The LHR–SYD pairing has historical weight — for decades it was flown only with a stopover, and the non-stop is a relatively recent engineering achievement. Use this timer when the symbolic weight matters as much as the duration. The "Kangaroo" of the Kangaroo Route is the original symbolic gesture, and pressing start on a twenty-hour LHR–SYD timer is the focus-work equivalent of choosing to read Ulysses in one sitting because the gesture is itself part of the work.

Sydney (SYD) → Frankfurt (FRA) — 20h 51m

The westbound 16,496 km return into central Europe, −9 hours. The westbound asymmetry is a real aerodynamic effect — the mid-latitude jet stream gives eastbound flights a tailwind that westbound flights pay for with headwinds, generally adding thirty to ninety minutes to the same great-circle distance flown the other way. The timers in this hub reflect that asymmetry honestly, so westbound routes run noticeably longer than their eastbound mirrors. Use SYD–FRA for the second half of a paired session, or as a stand-alone container for a project where the additional thirty-five minutes over the FRA–SYD route make the difference between "almost done" and "actually done" at wheels down.

Sydney (SYD) → Amsterdam (AMS) — 21h 04m

The 16,658 km westbound mirror to AMS–SYD, also −9 hours, just past the twenty-one-hour mark. At this duration, the session must be planned around two genuine rest periods of forty-five to ninety minutes each, plus a strict "do not start" rule for any block in the last two hours of the timer. The last hour of a twenty-one-hour session is for closing the work cleanly, not for starting new sub-tasks; everything you start in that last hour will have to be carried over to a future session, which defeats the point of using the long container in the first place.

Sydney (SYD) → Paris (CDG) — 21h 26m

The 16,944 km westbound leg from Sydney to Charles de Gaulle, −9 hours. The shape of this session almost demands that you treat it as a "split-day" — open the timer, work three or four hours on the most cognitively expensive task, take a full break with food and a walk, work another three or four hours on the next-hardest task, take another full break, and continue. Anyone who tries to power through a twenty-one-hour container without scheduled breaks will be doing low-quality work by hour fourteen and net-negative work by hour eighteen.

Sydney (SYD) → London (LHR) — 21h 32m

The longest non-stop route in commercial aviation that we model: 17,020 km from Kingsford Smith to Heathrow, with a −10 hour clock change. At twenty-one and a half hours, this is the outermost container FocusFlight offers. Reserve it for the kind of project that is genuinely once-in-a-quarter: the all-day creative push, the manuscript submitted by the deadline, the architectural rewrite that has to be finished before Monday. Press start, and the timer does not expire until well after most people you know will have gone to sleep, woken up, and started their next working day.

How to structure an 18-hour-plus session

A session this long is not a long Pomodoro. The technique that works at twenty-five minutes — sustained, unbroken concentration — is exactly the technique that fails at twenty hours. The session has to be designed as a day, not a block.

Three-block versus two-block: pick by task shape. A useful default for routes in the 18–20h band is three blocks of approximately five hours each, separated by two real breaks of forty-five to sixty minutes, with a buffer of about an hour at the front for opening rituals and an hour at the back for closing. For the 20–21h+ routes, the same shape still works but the breaks lengthen — a session that lasts twenty-one hours needs at least one ninety-minute pause, ideally including some kind of meal that is not eaten at the desk.

Block length should not exceed about four to five hours of sustained concentration even for people who can go longer. The cognitive cost of the next block rises sharply after that, and the diminishing-returns curve gets ugly past hour twelve of effective focus. Cal Newport's framing of deep work as a protected condition rather than a wishful state translates directly: the ultra-long-haul container is the protection, but the blocks inside it still have to respect the underlying human limits on attention.

Schedule the breaks by the clock, not by tiredness. This matters more for long sessions than short ones, because tiredness in a twenty-hour session is not a reliable signal. You will feel tired at hour six and recover by hour seven; you will feel sharp at hour fifteen and crash hard at hour seventeen. If you wait for tiredness to declare breaks, the timing is wrong. The schedule is the prosthesis.

Decide the closing ritual before you start. A twenty-hour timer that ends in "well, I almost finished" is a worse outcome than a twelve-hour timer that ends in a clean ship. Before you press start, write down what "done" looks like in one sentence. Then write down what the closing block contains — the pull request opened, the chapter committed, the email sent, the file exported, the working notes archived. When the timer expires, you stop. Discipline lives in the ending, not the beginning.

Eat and walk on real schedules. A session that lasts longer than a normal working day has to include real food and real movement. Treat the longer break in the middle as a meal break: leave the desk, prepare or order food, eat it somewhere other than where you are working, walk for ten or fifteen minutes after. The temptation in a long session is to "stay in the zone" by eating at the desk and pushing through. This works for an hour. It does not work for twenty.

Sound environment for very long sessions

The default sound layer inside FocusFlight is steady cabin ambience: low engine hum, faint air-conditioning, the occasional muted announcement. For ultra-long-haul sessions, the sound matters more than for shorter ones, because anything that fatigues the ear at hour two will be unbearable at hour fifteen.

The cabin layer is loud enough to mask irregular ambient noise — HVAC kicking on, a neighbour's car door, a distant siren — without being interesting enough to demand attention. Predictable sound is what makes a room feel less likely to interrupt you; the interruptions that hurt focus the most are the irregular ones, because they force the brain to evaluate whether something needs a response. The cabin layer keeps the irregular ones from registering.

For sessions past the twenty-hour mark, err quieter than you would for a short session. The hearing-safety guidance from the CDC NIOSH overview is the relevant reference: a sound that is comfortable at twenty minutes can be wearing at fifteen hours. The right volume for an ultra-long-haul session is the volume at which, ten minutes in, you stop noticing the sound is there. If you can hear the sound consciously, it is too loud. Lower it until it sits behind the work like wallpaper.

A useful operational rule: if you are pausing the audio mid-session to rest your ears, the audio is too loud for the container. Lower it once for the rest of the session rather than toggling. The pause-and-resume cycle is its own micro-interruption.

When not to use this hub

The diminishing-returns case is real, and it is worth being explicit about. There is consistent evidence that effective focused work plateaus at about eight to twelve hours per day for most people, even very practiced ones, and that pushing past that produces output that is measurably worse rather than just marginally less. An ultra-long-haul timer is not a magical extension of that ceiling.

So: pick a route from this hub only when (a) the work genuinely does not decompose into shorter sessions without losing context, (b) you have cleared the next day's calendar to recover, and (c) the symbolic weight of running a full ultra-long-haul block is itself useful to the project. If any of those three are missing, pick a shorter timer from one of the sibling hubs — the transpacific eastbound routes (Asia to US West Coast) or the transpacific westbound routes (US West Coast to Asia) cover the 11h 52m to 16h 55m band, and the heartland routes (Asia to North American interior) cover 12h 20m to 17h 47m. Any of those will hold most real projects without overshooting the container.

The honest framing is that the routes in this hub are for the occasional big push, not the regular working day. A practitioner who runs an ultra-long-haul session every week is probably hurting themselves; a practitioner who runs one every quarter, deliberately and with the next day cleared, is using the format the way it is designed to be used.

Related hubs

If you want to think about the shape of focus sessions rather than the route, the blog post on the best focus timer schedule for real deep work is the natural companion. It covers how to design a working day around different block sizes, which becomes especially relevant when one of those blocks is a twenty-hour Kangaroo Route.

How to start

  1. Pick the route above whose duration honestly matches the size of your task — and the size of the calendar you have cleared around it.
  2. Write down, on paper or in a sticky note, the single sentence describing what "done" looks like at the end of the session, plus the closing ritual that ends the work cleanly.
  3. Press start. The timer counts down to the real wheels-down of that flight. Cabin ambience begins.
  4. Schedule your breaks by the clock, eat real food, walk during the long pause, and reserve the last hour for closing.
  5. When the timer ends, stop — even if you are tempted to push another twenty minutes. Then sleep.

Ultra-long-haul focus is a once-in-a-while practice, not a daily habit. The eleven routes in this hub are containers for the rare project that genuinely needs the entire day-and-then-some, and they work best when chosen deliberately, used sparingly, and respected for what they actually are: the outermost edge of how long a person can usefully sit with a single piece of work.

Start a Focus Flight