A training block assumes continuity. Long-haul travel is the opposite of continuity. For years I tried to solve that contradiction by being disciplined enough, which is another way of saying I ignored it and paid for it later. The version that works now starts from an unflattering admission: the flight wins. Plan around it rather than through it.
Jet lag and training load compound
The thing I got wrong for a long time was treating travel fatigue and training fatigue as separate accounts. They are not. They draw on the same recovery capacity, and they compound rather than add. A hard session that I would absorb comfortably at home takes noticeably longer to clear in the days after crossing eight or more time zones, and the effect is largest in exactly the window where motivation is highest, because arriving somewhere new makes you want to go out and run.
The practical consequence is that the first days after a long-haul arrival are not a place to put quality work. Not because the session will feel bad in the moment — it often feels fine — but because the recovery cost is mispriced, and the bill shows up as a flat week afterward that I then have to explain to myself.
The days either side
My rough template now looks like this, and it is a template rather than a rule because the direction of travel matters.
The day before a long flight gets an easy aerobic session, done early, with no intensity. The instinct is to bank a hard session because you assume the next few days will be lost. That instinct is wrong. Boarding an eleven-hour flight with sore legs makes the flight worse, the arrival worse, and the first two days on the ground worse. Easy, early, then travel.
The flight itself is not a training opportunity, but it is a recovery opportunity that most people waste. Water, less alcohol than the cabin encourages, and getting up to walk every couple of hours are unglamorous and they are most of what determines how the first day on the ground goes.
The arrival day gets movement, not training. Twenty to forty minutes easy, outdoors, in daylight, at whatever time of day the destination says it is. The point is not the aerobic stimulus. It is the light exposure and the signal to the body clock, and it does more for the next three days than any session could.
Days two and three stay aerobic and unstructured. I hold intensity back until sleep has looked normal for two consecutive nights. Eastward travel typically costs me longer than westward, which matches most of what is known about circadian adjustment and matches my own logs closely enough that I plan on it.
What survives, and what does not
Strength work survives travel best. It is short, it is indoors, it does not depend on weather or on finding a safe route, and a hotel gym is usually adequate for maintenance even when it is not adequate for progression. On a trip week, strength is often the only structured thing I keep.
Easy aerobic volume survives well. It is portable, it does not need a facility, and it tolerates being done at odd hours.
Threshold and interval work does not survive. Not because it is impossible, but because doing it badly is worse than not doing it. A key session executed at eighty percent quality on legs that have not recovered from a flight gives me the fatigue of the session and very little of the adaptation. That is the worst trade in the sport.
Long endurance sessions are the awkward middle case. They are portable in principle and brutal in practice on a disrupted sleep schedule. I will move a long run to the end of a trip rather than the start, or accept it will be slower than the plan says and stop treating that as a failure.
What I have stopped pretending works
Training on arrival day to "beat" jet lag. It does not beat anything. It front-loads fatigue onto the exact days when the recovery system is least able to deal with it. Light exposure and an easy walk do the job the hard session was supposed to do, at a fraction of the cost.
Hotel-gym cardio as a substitute for the session I planned. A treadmill session in a windowless room at the wrong time of day, done to preserve a number in a training log, is compliance rather than training. If the block calls for something the trip cannot support, the honest move is to change the block, not to fake the session.
Assuming a race a few days after a long-haul arrival will go to plan. It might. It also might be the day the sleep debt presents its invoice, and no amount of taper discipline compensates for that. I now plan arrival buffers around anything that matters, and I would rather lose two training days to an earlier flight than lose the event.
And the biggest one: pretending the travel is free. Every trip has a training cost. Naming it in advance turns it into a planned deload instead of an unexplained bad week, and a planned deload is a perfectly good part of a block. That is really the whole method. The flight is going to take something. Decide what it takes.
The same logic applies to the working week, which pays its own version of this bill: What a Time Zone Actually Costs. And the reason facilities feature so heavily in how I pick a base city is that a base which supports the training makes the travel around it survivable.
← Back to Travel
Ready to Train Smarter?
Get personalized training zones, race predictions, and performance insights with our free calculators.
