FocusFlight

There is a particular kind of long-haul flight that feels designed for focus work. You leave Seoul, Shanghai, or Singapore in the late morning. You spend the next twelve to seventeen hours in the air. And then you land in San Francisco or Los Angeles earlier in the same calendar day than when you took off. The clock says you have done the impossible — gained the day back.

That is the geometry of the transpacific eastbound flight, and it is also a useful container for a long deep-work session. The duration is the whole point. A real Asia-to-US-West-Coast leg is long enough to do one big thing — to ship a feature, finish a chapter, fix a long-standing bug, write the whole report. The timezone arithmetic is a bonus: the idea of arriving on the same date you departed is exactly the kind of small ritual that makes a long focus block feel meaningful instead of grueling.

This hub uses ten real transpacific eastbound routes as the basis for ten different ways of sizing an all-day focus session. The shortest is Seoul to Los Angeles at 11h 52m over a great-circle distance of 9,627 km. The longest is Singapore to Los Angeles at 16h 55m 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.

What this kind of timer is good for

Transpacific eastbound routes work especially well for three types of work.

The first is shipping. By "shipping" we mean the kind of work where the goal is to finish one specific thing and have it out the door by the end of the session. Ship a feature. Send a report. Submit an application. Close the dissertation chapter. The reason the long-haul format helps is that the end is non-negotiable. The plane lands. The timer ends. If you have built the session around a single deliverable, the natural anxiety of "will I finish before we descend?" becomes useful pressure instead of background dread.

The second is deep technical work. Coding, mathematical proofs, legal drafting, scientific analysis — anything where context is expensive to load and easy to lose. The shortest route in this hub still gives you eleven full hours of cruise. That is far more than the two-Pomodoro window of most office days, and it is roughly the length of an aggressive deep-work day described in the classic deep-work literature. Cal Newport's framing of deep work as a protected condition rather than a wishful state translates directly into the transpacific timer: the cabin is the protected condition, and the timer enforces it.

The third is single-project archival or research dives. The kind of work where you cannot break it into a single Pomodoro because the cost of putting it down and picking it back up is higher than the cost of just sitting with it for a few extra hours. Reading a long primary source. Auditing a six-month log. Writing the literature review. Building the dataset.

The hub is not for short, switchy work or for tasks that depend on collaboration with others. If you need three different people to unblock you, a fifteen-hour timer is not what you want — pick a shorter route, or use a Pomodoro stack instead.

The route gallery

These are the ten routes, ordered from shortest to longest. Pick the one whose flight time matches the size of the task in front of you.

Seoul (ICN) → Los Angeles (LAX) — 11h 52m

The shortest transpacific eastbound route in the hub, at 9,627 km and a 17-hour clock jump backward (you arrive in LAX 17 hours "earlier" than the local time you left in Seoul, which feels like cheating). Incheon is built on reclaimed land between two islands and has won the ACI World "best airport" award for passenger experience repeatedly — a good aesthetic anchor for the start of a focus session. Use this route when you have one big thing to do but want the timer to end before you completely run out of energy. Eleven and a half hours is plenty for two big work blocks plus a real break, and you'll land mentally lit rather than mentally burned.

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

Shanghai Pudong sits on reclaimed land east of the city and was the world's first commercial airport to host a maglev train link. The 9,877 km route is the geometric heart of the China–Bay-Area corridor. Use this timer for the work session you'd plan if you knew, today, that tomorrow's standup was the deadline — the night-before-the-thing focus block. The 12-hour window is enough for a full coding session plus testing plus the careful re-read before you commit.

Beijing (PEK) → Los Angeles (LAX) — 12h 20m

Beijing Capital is one of the busiest airports in Asia, with three runways and a Norman Foster–designed Terminal 3 that opened for the 2008 Olympics. The 10,062 km great-circle puts you over the Pacific for the entire cruise. The session feels best paired with one heavy creative task that has an obvious unit of completion — a long-form article from blank page to draft, a problem set from question one to finished, a presentation outlined and slide-built in the same sitting.

Shanghai (PVG) → San Francisco (SFO) versus Shanghai (PVG) → Los Angeles (LAX)

Worth noting: the difference between landing in SFO (12h 09m) and LAX (12h 46m) from PVG is roughly thirty-seven minutes. That is one extra Pomodoro plus a stretch break. If you are choosing between the two for a session, pick LAX when the work is genuinely bigger than the SFO timer allows, not because the longer number feels more impressive. A timer that is twenty minutes too long is a session that ends in a sigh; a timer that is the right size ends in completion.

Shanghai (PVG) → Los Angeles (LAX) — 12h 46m

The 10,415 km route. The minute difference matters in practice mostly because it lets you fit a slightly more ambitious task than the SFO version — a feature implementation plus the integration tests, rather than the feature alone.

Guangzhou (CAN) → San Francisco (SFO) — 13h 31m

Guangzhou Baiyun is the main southern China hub for China Southern Airlines and operates around the clock thanks to its three parallel runways. The 11,080 km route is the cleanest "one full working day plus four extra hours" timer in the hub. Use it when you want a session that mimics the rhythm of an eight-hour workday and then keeps going into the evening. Three deep blocks of three to four hours each, with two short breaks and one real meal-and-walk break, fits cleanly inside this duration.

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

The 11,618 km variant. Same shape as the SFO route above, but with an extra thirty-six minutes — useful for a project where the wrap-up phase (testing, documentation, sending the final email) is itself a significant chunk of the work.

Bangkok (BKK) → San Francisco (SFO) — 15h 23m

Suvarnabhumi (literally "golden land") opened in 2006 and was at the time the largest single-building airport terminal on Earth. The 12,749 km route crosses the equator and most of the Pacific. At fifteen and a half hours, this is no longer a normal working day — it is a committed session, the kind you schedule when you have intentionally cleared the calendar and want to attempt something you'd normally consider too ambitious. Two five-hour deep blocks plus a serious break between them is one shape that works. Three blocks of four to five hours, decreasing in cognitive intensity (write the hard new code first, then test, then document), is another.

Bangkok (BKK) → Los Angeles (LAX) — 15h 59m

The 13,291 km variant adds another 36 minutes to the BKK–SFO shape. Use it specifically when the LA-style work pattern (creative drafting, screenwriting, design iteration) is what you have in mind, and the additional half-hour gets you to a natural breakpoint that the SFO version would clip.

Singapore (SIN) → San Francisco (SFO) — 16h 20m

Singapore Changi's Jewel complex centres on the world's tallest indoor waterfall and was designed by Moshe Safdie. The 13,580 km route is among the longer practical transpacific eastbound options in commercial service. At sixteen hours and twenty minutes, this is the timer for a project you have been delaying for weeks because every shorter session was, honestly, too small to fit it. Read the entire stack of accumulated papers. Write the long-form essay that has been in your head for a month. Refactor the entire module from one architectural pattern to another.

Singapore (SIN) → Los Angeles (LAX) — 16h 55m

The longest route in this hub. 14,101 km, a 17-hour clock jump backward, and a session length that genuinely tests the limits of sustainable focus in a single sitting. The recommended shape: three large blocks of approximately three to four hours, separated by genuine breaks of forty minutes (not five) where you stand up, walk around, eat something real, and look at something far away. If the work cannot survive that kind of break, the work was probably the wrong size for the timer.

How to structure a transpacific session

A 12-to-17-hour focus session is not just a long Pomodoro. The same techniques that work at 25 minutes break down at 12 hours. Use the following frame as a starting point.

Open the session like a flight. Spend the first ten to fifteen minutes deliberately quieting the room before the timer goes. Close every tab you do not need. Put the phone in another room or in a drawer. Make the coffee. Set a single, written goal for the session — one sentence, on paper or in the project README, naming what "shipping" looks like at the end. This is the cabin door closing. After that, the rule for the rest of the session is that incoming interrupts wait until the next break.

Plan the cruise in two- to four-hour blocks. Inside the long window, identify two or three "blocks" of two to four 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 (Singapore to LA, Bangkok to SFO), the more you need a true mid-session pause. A useful rule of thumb is that block length should not exceed about four hours of sustained concentration, even for people who can go longer, because the cognitive cost of the next block rises sharply after that.

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 the same way: at a defined clock time, 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.

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 task: the pull request is open, the chapter is committed, the email is sent, the file is exported. When the timer hits zero, you stop, regardless of whether you "still have a little more to do." The discipline is in the ending.

Why eastbound feels different from westbound

The eastbound transpacific direction has a unique psychological quality. You leave Asia in the morning. You spend most of the flight in daylight. You arrive in California earlier in the same calendar day than you left, even though you have been working for many hours. The phenomenology is roughly: I have done a day's work and the day has not actually started yet.

That is the opposite of a normal workday, and it is also why the eastbound transpacific timer pairs so well with certain kinds of projects. Anything that benefits from "stealth completion" — work you'd rather be done before everyone else's working day begins — fits the metaphor naturally. The reverse direction (US West Coast back to Asia) feels different and is covered in a sister hub on westbound transpacific routes. If you are doing a paired session with a colleague on the other side of the Pacific, one of you on each direction is a slightly absurd but actually useful symmetry.

The eastbound asymmetry is also a real aerodynamic fact, not just a story. Tailwinds along the mid-latitude jet stream typically shave thirty to ninety minutes off the eastbound flight versus its westbound mirror. That is why the same 9,627 km between Seoul and Los Angeles is 11h 52m eastbound but 12h 27m westbound. The session timer in FocusFlight mirrors that real asymmetry — eastbound routes get a small tailwind credit; westbound routes pay a corresponding headwind cost — so the timers are not symmetric, and that's intentional.

Cabin ambience for daytime focus

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 transpacific sessions specifically is that the sound is predictable. Predictable sound is what makes a room feel less likely to interrupt you. The interruptions that hurt focus the most are the irregular ones — 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. If you find the default too quiet, the app lets you raise the volume; if you find it too loud, lower it until it sits behind the work like wallpaper. The hearing-safety guidance from sources like the CDC NIOSH overview applies here in the obvious way: a sound that fatigues you after twenty minutes is too loud for a session that lasts fifteen hours. Err quieter.

When to choose a shorter or longer route

A useful question to ask before picking a route: what does "done" look like for this session, and roughly how big is that work?

The biggest single mistake people make is picking a timer that is larger than the actual task. A two-hour task inside a sixteen-hour container is a session that ends with eleven hours of unfocused drift, not eleven hours of bonus focus. If in doubt, size down by one route and book a second session for the next week.

Pair this hub with

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 your day around different block types, which becomes especially relevant when one of those blocks is a fifteen-hour transpacific flight.

How to start

  1. Pick the route above whose duration matches the size of your task.
  2. Write down, on paper or in a sticky note, the single sentence describing what "done" looks like at the end of the session.
  3. Press start. The timer counts down to the real wheels-down of that flight. Cabin ambience begins.
  4. When the timer ends, stop. If "done" was honest, you'll be there. If you finished early, the next break belongs to you — go for a walk.

Long-haul focus is a craft you build over many sessions, not a trick you find once. The transpacific eastbound routes in this hub are an unusually well-shaped container for that practice: long enough to fit something real, short enough to finish in a single day, and grounded in the rhythm of an actual flight that thousands of people are crossing the Pacific in right now.

Start a Focus Flight