How to convert local time to UTC for logbook entries

Most logbook errors are not dramatic. They are quiet, one-line mistakes that sit unnoticed in a record for months until someone reads the times back carefully. UTC conversion is one of the most common sources of these errors, and it tends to show up at the worst moment: during a licence application, a type rating check, or an audit, when the times finally get scrutinised line by line.

The rules for converting local time to UTC are simple. The failure points are specific and predictable, which is good news, because predictable problems are easy to design out. This post covers the conversion rule, the places pilots actually get tripped up, a quick-reference table for the regions where Wingman has active cohorts, and how the app removes the conversion step entirely.

Why UTC exists in aviation

UTC stands for Coordinated Universal Time. It is the single time reference used across global aviation: air traffic control, NOTAMs, METARs, and flight plans all run on it. The reason is straightforward. A flight from Dubai to London crosses several civil time zones, and a flight from Los Angeles to Tokyo crosses the date line. If every party used local time, every clearance and every filed time would need a translation step, and translation steps are where errors live.

UTC removes the ambiguity. A departure logged at 0900Z means the same instant whether the reader is in Chennai, Frankfurt, or Seattle. That is also why your logbook is expected to be in UTC. ICAO Annex 1 and the national licensing regulations built on it require logbook entries to be recorded in UTC, so that an entry can be read and verified against any other aviation record without conversion.

The conversion rule

The core rule is one line:

UTC = local time + offset (for regions east of UTC), or UTC = local time − offset (for regions west of UTC).

The signs follow the time zone offset, not always your intuition about geography. A region east of the Greenwich meridian carries a positive offset, so its local clock is ahead of UTC and you subtract to get back to UTC. A region west carries a negative offset, so its local clock is behind UTC and you add. Two worked examples make the pattern concrete.

India Standard Time is UTC+5:30. To convert a local IST time to UTC, subtract five hours and thirty minutes. A flight that departs at 14:30 IST departs at 09:00 UTC. Gulf Standard Time in the UAE is UTC+4. A landing logged at 23:15 GST is 19:15 UTC. In both cases the region sits east of UTC, the offset is positive, and the conversion is a subtraction.

West of UTC the arithmetic flips. US Eastern Time in winter is UTC−5, so a 22:00 local departure is 03:00 UTC the next day. That rollover past midnight is itself a common slip, and it is worth pausing on whenever a leg straddles 0000 UTC.

Daylight saving time

The second half of the rule is the part that changes underfoot. UTC does not observe daylight saving time. Local civil time does in many regions, which means the offset you apply is not fixed across the year.

The pattern is consistent within each region that uses DST. UK time is UTC+0 as GMT in winter and UTC+1 as BST in summer. Central European Time runs UTC+1 as CET in winter and UTC+2 as CEST in summer. US Eastern Time alternates between UTC−5 as EST and UTC−4 as EDT. US Pacific Time alternates between UTC−8 as PST and UTC−7 as PDT. A pilot who memorises the winter offset and applies it in July is off by exactly one hour, and a one-hour error in block time is large enough to matter and small enough to miss on a quick read. If you fly under a specific authority, the regional guides go deeper, including converting local time to UTC for your logbook under the FAA and recording entries in UTC under EASA.

Two of the regions in Wingman's most active cohorts sidestep this entirely. India does not observe DST, so IST stays UTC+5:30 year-round. The UAE does not observe DST either, so GST stays UTC+4 year-round. For pilots based there the offset is constant, but the moment a trip touches a DST region the seasonal shift comes back into play, so the habit of checking still pays. Indian licence holders can see how this fits the wider record in our guide to logging your times in UTC, and Gulf-based pilots can follow the GST to UTC conversion steps for the UAE.

Common logbook errors and what they cost

The errors pilots actually make cluster into three types.

The first is the mixed entry: logging departure in local time and arrival in UTC, or the reverse. The block time computed from a mixed pair is wrong by the full offset, and because each individual time looks plausible, nothing flags it at the point of entry.

The second is the forgotten DST shift, described above. It produces a one-hour error that is consistent across a whole season of entries, which makes it harder to spot than a single typo.

The third is the reversed sign: adding the offset where you should subtract, or subtracting where you should add. This doubles the error. Converting 14:30 IST by adding 5:30 gives 20:00 instead of 09:00, an eleven-hour miss.

What these cost is rarely a dramatic event. A logbook inconsistency discovered during a licence application, a type rating check, or an audit can require you to resubmit corrected logs, and that resubmission can delay an approval you were counting on. The work of fixing a converted-wrong entry six months later, with no clear record of the original local time, is far greater than the work of recording it correctly once.

Quick reference: offsets for major hubs

The table below covers the six regions called out in this post. Standard offset applies in the local winter; the DST offset applies during the local summer for regions that observe it. For a fuller lookup across other regions, the world time zone map is a useful reference.

Region	Zone	Standard offset	Observes DST	Summer offset
India (Delhi, Mumbai)	IST	UTC+5:30	No	n/a
UAE (Dubai, Abu Dhabi)	GST	UTC+4	No	n/a
United Kingdom (London)	GMT / BST	UTC+0	Yes	UTC+1
Central Europe (Frankfurt, Paris)	CET / CEST	UTC+1	Yes	UTC+2
US East (New York)	EST / EDT	UTC−5	Yes	UTC−4
US West (Los Angeles)	PST / PDT	UTC−8	Yes	UTC−7

These offsets are the global standard maintained for civil and aviation use; ICAO sets UTC as the reference time across the system.

How Wingman handles the conversion

The most reliable way to avoid a conversion error is to not do the conversion by hand. Wingman records departure and arrival times in UTC automatically, using the device clock and GPS location at the time of entry. You note the event when it happens, and the entry that lands in your logbook is already in UTC, with the correct offset and the correct DST state applied for where you were.

That removes all three error types at once. There is no mixed entry, because both times come from the same source. There is no forgotten DST shift, because the offset is resolved from location and date rather than memory. There is no reversed sign, because there is no manual sign to reverse. The same logbook syncs across iOS, Android, and Web, so the UTC record is consistent on every device you open. If you are weighing apps, our breakdown of automatic UTC recording shows how this holds up against LogTen Pro.

The flow below shows the manual path and where Wingman replaces it.

If you are setting up a clean record after switching apps, the same principle applies to your historical data, and it is worth reading our notes on choosing a logbook that fits your workflow and how Wingman compares to other logbook apps before you commit. For Indian licence holders preparing a submission, the steps for uploading your logbook to eGCA assume your times are already in UTC, which is one more reason to get the recording right at source.

FAQ

Do I have to log flight times in UTC or can I use local time? The logbook record is expected in UTC. ICAO Annex 1 and the national licensing regulations built on it require logbook entries to be recorded in UTC, so the entry can be verified against other aviation records without a conversion step. You may note local time for your own reference, but the logged figure should be UTC.

What is the UTC offset for India? India Standard Time is UTC+5:30, and it stays that way year-round because India does not observe daylight saving time.

How do I convert IST to UTC? Subtract five hours and thirty minutes from the local IST time. A 14:30 IST event is 09:00 UTC. A 02:00 IST event is 20:30 UTC on the previous day, so watch the date rollover when the local time is early in the morning.

Does UTC change with daylight saving time? No. UTC does not observe daylight saving. Local civil time does in many regions, which shifts the offset between a winter value and a summer value. The offset you apply changes with the season; UTC itself does not.

What happens if my logbook has entries in local time instead of UTC? The inconsistency may not surface until your record is read carefully, often during a licence application, a type rating check, or an audit. At that point you can be asked to resubmit corrected logs, and that can delay the approval. Correcting entries long after the fact is harder, because the original local time and offset may no longer be obvious.

Does Wingman automatically record UTC? Yes. Wingman records departure and arrival times in UTC automatically, using the device clock and GPS location at the time of entry, so the figure in your logbook is already converted.

Start clean

UTC conversion is a solved problem the moment the conversion stops being manual. Start free with Wingman. Your times log in UTC automatically.