Log a flight that crosses a time zone
Flying from Palo Alto (Pacific time, UTC−7 in October) to Boise (Mountain time, UTC−6)? Type each clock as it showed at that airport: OUT and OFF in Palo Alto time, ON and IN in Boise time. Log Flight works out UTC and the block time for you.
1. Each clock in its own airport’s time
Section titled “1. Each clock in its own airport’s time”- Log Flight → New Flight → Flight step: Pick the date (for example 3 October), the Departure (KPAO) and the aircraft.
- Total step, OOOI: tap each box and type the time (for example OUT 08:00, OFF 08:10, ON 13:05, IN 13:15). Tap each box rather than the keyboard’s Next, which can jump into Block or Air.
- The small line under each clock shows it in UTC.
OUT and OFF are read in the departure airport’s time, ON and IN in the arrival’s.
2. Until the arrival is set, it’s an hour off
Section titled “2. Until the arrival is set, it’s an hour off”With no arrival yet, all four clocks are read in Palo Alto time, so ON and IN can come out an hour off, and Block an hour too long.
Go back to Flight, tap Arrival, type the code and pick Boise (KBOI / BOI). A line on the Flight step says which times moved (it ends local times kept), with Undo. Back on Total:
- The clocks still read as you typed them (13:05, 13:15), but ON and IN now count as Boise time: 19:05 and 19:15 UTC.
- Block 4:15, Air 3:55.
- The route strip shows each airport’s offset: −7 at Palo Alto, −6 at Boise.
So you can pick the arrival before or after typing the clocks: the app keeps what you typed and re-reads it in the new airport’s time.
3. Check in UTC
Section titled “3. Check in UTC”Tap the route strip (Times shown in airport local time. Tap to switch to UTC.): every clock switches to UTC (15:00 → 19:15). Tap it again for local time.
4. Save it
Section titled “4. Save it”Tap Complete. The flight’s page opens (Sat, Oct 3, 2026 · KPAO → KBOI · 4:15). Tap Total Flight: the clocks are kept as you typed them, each in its own airport’s time, with UTC underneath: OUT 08:00 (15:00 UTC) at Palo Alto, IN 13:15 (19:15 UTC) at Boise, Block 4:15, Air 3:55.
Good to know
Section titled “Good to know”- If the strip is on UTC when you change an airport, the clocks keep their UTC times and only the local line under them moves. If you typed in UTC, keep the strip on UTC until both airports are set. Switch back to local first and the app re-reads them as that airport’s local times, which moves the UTC you typed.
- Most Arizona airports stay on UTC−7 all year, so a Pacific → Arizona flight in summer usually shows no change. Airports on the Navajo Nation (Window Rock, Kayenta, Tuba City) keep daylight time.
- Picking Boise from the search list doesn’t add it to My Airports by itself; saving the flight does (Account → Database → Airports went from six to seven).