FocusFlight

The westbound transpacific flight has a different feeling from its eastbound mirror. You leave San Francisco or Los Angeles in the late morning or early afternoon. You climb out into the Pacific. You spend the next thirteen to eighteen hours in the air with a steady headwind nudging the cruise speed just below the eastbound number. And when you finally descend into Singapore or Seoul, the calendar has skipped a date. You did not gain a day; you lost one. The session ends, and the world on the other side has already moved into tomorrow.

That asymmetry is a real aerodynamic fact, and it is also a useful metaphor for a particular kind of focus session — the one where the goal is not to make something new, but to finish something that has been sitting too long. The work has accumulated. The list of half-done tasks has grown. The backlog has acquired its own gravity, and the only honest way through it is to clear an entire working day, sit down, and close out everything that has been kicked from one week to the next.

This hub uses ten real US West Coast to Asia routes as the basis for ten different ways of structuring a long close-out session. The shortest is Los Angeles to Seoul at 12h 27m over 9,627 km. The longest is Los Angeles to Singapore at 17h 56m over 14,101 km. Each route on this page is also available as a one-click timer inside FocusFlight: pick the route, press start, and the app times you to the wheels-down of the real-world flight while cabin ambience plays in the background.

Why westbound feels longer

The headwind on a westbound transpacific flight is not folklore. The mid-latitude jet stream runs roughly west-to-east at altitudes commercial aircraft cruise through, and the consequence is that the same great-circle distance flown westbound generally takes thirty to ninety minutes longer than the eastbound mirror. Singapore to Los Angeles is 16h 55m eastbound; Los Angeles to Singapore is 17h 56m westbound, a difference of an hour and a minute for the identical 14,101 km route. Seoul to LAX is 11h 52m eastbound; LAX to Seoul is 12h 27m westbound, a difference of thirty-five minutes.

The session timers in FocusFlight honour that asymmetry deliberately, because the asymmetry is a feature of the metaphor, not a flaw in the data. Eastbound sessions feel like starting — you leave in the morning, you work, you land before the day is technically over. Westbound sessions feel like finishing — you leave in the afternoon, you work, and somewhere in the cruise the date quietly rolls over and you arrive in tomorrow. Same airport pair, same distance, different psychological shape.

The headwind also matters operationally. A longer container means a session has slightly more room for the wrap-up phase — the testing, the documentation, the careful re-read before the work goes out the door. If the eastbound timer is just enough for the build, the westbound timer is just enough for the build plus the close-out.

What this kind of timer is good for

Westbound transpacific routes work especially well for three categories of work.

The first is close-out. Project close-out is its own discipline — going back through six weeks of half-done sub-tasks and finishing them properly rather than declaring them done and moving on. The reason it gets put off is that close-out work is not exciting; the rewards are quiet rather than visible. A long, single-sitting container helps because it removes the temptation to switch to something more interesting. The plane is in the air. The timer is running. The only honest move is to keep closing.

The second is long-form writing where the structure already exists. The kind of writing where the outline is done, the notes are organised, and what remains is the patient work of writing each section in turn. A research paper revision. A book manuscript that needs the final pass. A long technical specification that has to be made internally consistent. Cal Newport's framing of deep work as a protected condition translates directly: the long westbound timer is the protection, and the writing-from-an-outline task is the shape that best fits twelve to eighteen hours of continuous attention.

The third is archival cleanup. Reorganising the code repository. Tagging six months of email. Auditing the bug tracker. Migrating notes from one system to another. These tasks are not glamorous, but they accumulate, and they pay off compoundingly. The westbound container is a clean way to do an entire round of archival work in a single sitting without the start-and-stop tax that normally makes the work feel worse than it is.

The hub is not well-suited to discovery work — the kind of session where you do not yet know what you are trying to accomplish and need to explore. The westbound metaphor is about closing, not opening. If you are trying to start a new project, pick a route from the sibling transpacific eastbound hub instead; the eastbound psychology is better for blank-page work.

The route gallery

Ten routes, ordered from shortest to longest. Pick the one whose flight time matches the size of the close-out work in front of you.

Los Angeles (LAX) → Seoul (ICN) — 12h 27m

The 9,627 km westbound mirror of the ICN–LAX eastbound route, with a +17 hour clock jump (you land in Seoul the next day, technically, on the calendar). At twelve and a half hours, this is the shortest container in the hub — a long working day with a wrap-up phase included. Use this timer for the close-out work that fits an ordinary deep-work day plus a clean ending: finishing a small project's documentation, tagging and archiving the last quarter's notes, reviewing and merging six accumulated pull requests in one sitting. The Seoul Incheon arrival anchor is useful aesthetically — Incheon's reputation for orderliness and quiet design makes the metaphor land naturally on the kind of work where the deliverable is "everything is tidy now."

San Francisco (SFO) → Shanghai (PVG) — 12h 45m

The 9,877 km westbound shape, +16 hours on the clock. Eighteen minutes longer than LAX–ICN. The minutes matter mostly in the wrap-up phase — eighteen minutes is one extra Pomodoro plus a short break, which is often exactly the difference between "I closed everything except the last email" and "the email is sent." Pick this route when the close-out you are doing has a known small extra step that the LAX–ICN timer would clip.

Los Angeles (LAX) → Beijing (PEK) — 13h 00m

The 10,062 km westbound leg, +16 hours. At exactly thirteen hours, this is the cleanest "long working day plus an hour" container in the hub. The shape that fits best is two large blocks of approximately five hours each, separated by a real break of forty-five minutes, with the last hour reserved for the close-out itself — finishing the file, sending the email, archiving the working notes. Beijing Capital's three-runway hub layout is the destination anchor; the metaphor for the session is the careful, completed handoff.

Los Angeles (LAX) → Shanghai (PVG) — 13h 25m

The 10,415 km westbound mirror, +16 hours. Twenty-five minutes longer than LAX–PEK. The extra time mostly serves a slightly more ambitious close-out: not just finishing the file but also writing the wrap-up message to the team that explains what got done, what is deferred, and what the next steps are. The single most underrated discipline in close-out work is the explanatory message at the end — without it, the work you closed gets reopened a week later by someone who didn't know it was done.

San Francisco (SFO) → Guangzhou (CAN) — 14h 14m

The 11,080 km westbound leg, +16 hours. Guangzhou Baiyun operates twenty-four-hour-a-day on its three parallel runways, and the destination anchor matters here — the metaphor is "the work site is open continuously, and so is the session." At fourteen hours and fourteen minutes, this is the right container for a close-out that includes one substantial creative task in addition to the cleanup work. Write the longer wrap-up document, not just the message. Record the explainer video. Do the part of the close-out that benefits from a fresh perspective rather than mechanical execution.

Los Angeles (LAX) → Guangzhou (CAN) — 14h 54m

The 11,618 km variant, +16 hours. Forty minutes longer than SFO–CAN. The extra time is useful specifically for close-out work that has two creative components — for example, both the explanatory document and the screencast, or both the post-mortem write-up and the slide deck for the team meeting that will discuss it. At fifteen hours minus six minutes, the timer is past the "long working day" tier and into the genuinely committed session category.

San Francisco (SFO) → Bangkok (BKK) — 16h 17m

The 12,749 km westbound leg into Suvarnabhumi, +15 hours. Sixteen hours and seventeen minutes is no longer a working day; it is an intentional commitment with the next day's calendar cleared. The session shape that works here is three blocks of approximately four hours each, separated by two real breaks of forty-five minutes, with a meal break in the middle that includes actually leaving the desk. Use this timer when the close-out has expanded into a project of its own — for example, a quarterly archival pass where you are not just finishing the open items but also reorganising how the system stores them so that the next quarter's accumulation works better.

Los Angeles (LAX) → Bangkok (BKK) — 16h 58m

The 13,291 km variant, +15 hours. Forty-one minutes longer than the SFO–BKK shape. At seventeen hours minus two minutes, the timer is right at the threshold where the next-day calendar absolutely has to be clear. Use this route when the close-out work has the additional component of a serious, considered piece of writing at the end — the post-mortem essay, the year-in-review document, the technical retrospective that the whole team will read.

San Francisco (SFO) → Singapore (SIN) — 17h 17m

The 13,580 km westbound mirror of SIN–SFO, +16 hours. Seventeen hours and seventeen minutes is a session length that genuinely tests the limits of useful work in a single sitting. The recommended shape is three blocks of approximately four to five hours each, separated by genuine breaks of forty-five to ninety minutes where you stand up, walk around, eat something real, and look at something far away. If the close-out you are doing cannot survive that kind of break — if you feel you would lose the thread by walking away — the work is probably not actually close-out work; it is mid-project work that has not yet been broken into closable units.

Los Angeles (LAX) → Singapore (SIN) — 17h 56m

The longest route in this hub. 14,101 km, +16 hours on the clock, and just shy of the eighteen-hour threshold where the ultra-long-haul hub takes over. At seventeen hours and fifty-six minutes, this is the timer for the once-in-a-quarter close-out — the kind of session you schedule deliberately, clear the calendar around, and treat as the formal close of one phase of work before the next phase begins. The shape: open with a written, one-sentence statement of what "fully closed" looks like at the end. Plan three blocks. Schedule the breaks. Reserve the last sixty minutes for closing rituals — sending the wrap-up message, archiving the working files, recording the brief note about what was deferred and why.

Session design when the timer "skips a day"

A long westbound session is not just a long Pomodoro. The technique that works at twenty-five minutes — sustained, unbroken concentration — does not scale linearly to twelve hours, much less to eighteen. The session has to be designed as a closing day, not as a block.

Open the session like a flight, but with an inventory. Spend the first fifteen to twenty minutes deliberately quieting the room. Close every tab you do not need. Put the phone in another room. Make the coffee. Then — and this is the part specific to close-out work — write down the inventory of items you are closing. The list should be honest. If there are sixteen things, write sixteen. If there are forty, write forty. The list is not aspirational; it is the manifest of what this session will dispatch.

Block by category, not by item. A common mistake is to work through the list item by item, in the order it happens to appear. The cognitive cost of switching between unrelated close-out items is high, and a long session that hops between categories will feel exhausting by hour eight. Instead, group the items by kind — all the writing items together, all the documentation items together, all the code-review items together — and work through the categories rather than the individuals.

Plan the cruise in four-to-five-hour blocks. Inside the long window, identify two to four blocks of four to five hours each, with shorter breaks between them and one longer break in the middle. The shorter the route, the more aggressively you can compress the breaks; the longer the route (LAX–SIN, SFO–SIN, LAX–BKK), the more you need a true mid-session pause. Block length should not exceed about four to five hours of sustained concentration even for people who can technically go longer, because the cognitive cost of the next block rises sharply past that point.

Use breaks the way airlines use cabin service. On a real flight, the meal carts come at scheduled times because they shape the experience. In the focus session, schedule the breaks at defined clock times, not when you happen to feel tired. If you wait for tiredness to declare a break, you will either break too late or break too often, depending on the day. The schedule is the prosthesis for self-control.

Reserve the last hour for the explanatory message. This is the single most underrated discipline in close-out work. When the timer hits sixty minutes remaining, stop adding new items to the close-out queue and start writing the wrap-up message — the short summary of what got closed, what is deferred, and what the next steps are. Send it before the timer ends. Without that message, the work you closed gets reopened a week later by someone who did not know it was done.

Decide the closing ritual before you start. Long sessions need an ending that means something. Decide before the timer starts what "wheels down" looks like for the session: the pull requests are merged, the inbox is at zero, the documentation is published, the wrap-up message is sent. When the timer hits zero, you stop, regardless of whether you "still have a few more items." The discipline is in the ending.

Best for: writing, project closeout, archival cleanup

Three categories of work fit the westbound timer especially well, and they share a structural feature: in each one, the goal is to finish rather than to create.

Long-form writing where the outline exists. A research paper revision after the structure has been argued through. A book chapter where the notes are organised and the section headings already written. A long technical specification that needs internal consistency rather than new ideas. The reason westbound timers fit this work so well is that the work is mostly patient execution against a known plan, and patience is exactly what a long single-sitting container provides.

Project close-out. Going through six weeks of half-done sub-tasks and finishing them properly. The reason close-out gets postponed is that the rewards are quiet rather than visible — but the long-term cost of not closing is high, because half-done work accumulates background guilt, and background guilt corrodes the next project's focus. A westbound session, run quarterly, is an unusually effective antidote.

Archival cleanup. Reorganising the repository. Tagging six months of email. Auditing the bug tracker. Migrating notes from one system to another. These are not glamorous tasks, but they pay off compoundingly. A westbound container is a clean way to do an entire round of archival work without the start-and-stop tax.

If the work in front of you is not one of these three things — if it is discovery, exploration, blank-page creative work, or anything that requires real-time collaboration with others — pick a different hub. The westbound metaphor is about closing, and forcing open-ended work into a closing-shaped container produces a session that ends in frustration.

Cabin ambience for the long close-out

The default sound layer inside FocusFlight is steady cabin ambience: low engine hum, faint air-conditioning, the occasional muted announcement. The reason this works well for westbound sessions specifically is that the sound is predictable, and predictable sound is what makes a room feel less likely to interrupt you.

The irregular interruptions are the ones that hurt focus most — a door slam, a notification ping, the dog barking once — because they force the brain to check whether something needs attention. The cabin layer is loud enough to mask irregular ambient noise (HVAC kicking on, a neighbour's car door) without being interesting enough to demand attention itself.

For sessions in the upper end of the westbound band — the LAX–SIN, SFO–SIN, and LAX–BKK routes — err quieter than feels natural at the start. 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 a long westbound 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: do not pause the audio mid-session to rest your ears. If you find yourself wanting to, the audio was too loud — lower it once and continue, rather than toggling. The pause-and-resume cycle is its own micro-interruption, and a long session does not need extra ones.

When to choose a shorter or longer route

A useful question to ask before picking a westbound route: what does "fully closed" look like for this session, and roughly how many items are on the close-out list?

The biggest single mistake people make is picking a timer that is larger than the actual work. A small close-out inside an eighteen-hour container is a session that ends with twelve hours of unfocused drift, not twelve hours of bonus close-out. If in doubt, size down by one route and book a second session for the next month.

Related hubs

If you want to think about the shape of close-out 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 seventeen-hour westbound flight.

How to start

  1. Pick the route above whose duration matches the size of the close-out work in front of you.
  2. Write down, on paper or in a sticky note, the inventory of items being closed and the single sentence describing what "fully closed" looks like at the end.
  3. Press start. The timer counts down to the real wheels-down of that flight. Cabin ambience begins.
  4. Work by category, schedule the breaks by the clock, and reserve the last hour for the explanatory message.
  5. When the timer ends, stop. Send the wrap-up. The next day belongs to the next project.

Long-haul close-out is a quietly important discipline, and the westbound transpacific routes in this hub are an unusually well-shaped container for it: long enough to hold the entire backlog of a phase, short enough to finish in a single day, and grounded in the rhythm of an actual flight whose date-line geometry is the metaphor for the work itself.

Start a Focus Flight