When a Local Time Happens Twice
A time zone converts a clock reading into a real instant, but for one hour at each of the two daylight-saving changes it cannot.
The hour that runs twice
When clocks go back at the end of daylight saving, an hour of local time is repeated. In New York on 2 November 2025 the clocks fell from 02:00 to 01:00, so every reading between 01:00 and 02:00 happened twice: once on daylight time, and again an hour later on standard time.
A record saying 01:30 is therefore not enough to name an instant. There are two of them:
| Reading | Offset | Actual instant |
|---|---|---|
| 01:30 EDT | UTC−04:00 | 05:30 UT — before the clocks went back |
| 01:30 EST | UTC −05:00 | 06:30 UT — after the clocks went back |
Both are correct readings of a real clock in a real room, and they are an hour apart.
This is not a shortcoming of the time zone database. The database knows the transition perfectly well; what it cannot know is which side of it the person writing 01:30 was standing on. The information is missing from the record itself, and no amount of lookup will recover it.
Why it cannot be guessed
The obvious choice, taking the first of the two, is what most software does without saying so, and it is right half the time.
When it is wrong, the error is large. An hour of error is 15° of sky, which moves the Ascendant half a sign on average and more than a whole sign when a fast-rising sign is on the horizon, taking every house cusp with it. A guess made without saying so produces a chart that looks normal and is an hour wrong in the parts most sensitive to time.
Nothing inside the record settles it
Where a time falls inside an overlap, both readings are equally well formed: the earlier occurrence and the later, each implying its own offset, an hour apart. The record contains nothing that distinguishes them, so whatever settles the question comes from outside it.
Once settled, the answer belongs with the record rather than with the moment it was given. A saved chart re-opened next year resolves to the same instant it did the first time only if the resolution was stored alongside it.
The hour that never runs at all
The spring transition has the opposite problem and it is much less trouble.
When clocks jump forward, an hour of local time is skipped — in New York on 9 March 2025 the clocks went straight from 02:00 to 03:00, so 02:30 never existed. A record claiming 02:30 that morning is naming a time that did not happen.
Here there is nothing to choose between, so nothing needs asking: such a time is shifted forward by the length of the gap. The reading was wrong; the correction is unambiguous.
Where the answer comes from
Most times are unambiguous and the question never arises. It is rare by construction — one hour a year, in places that observe daylight saving at all.
When it does arise, what settles it is the source of the record, not astronomy:
- A birth certificate or official record generally states standard or daylight time somewhere, or the hospital's own paperwork settles it.
- A time relayed from memory decades later often cannot be settled at all, and the chart then carries an hour of uncertainty.
Where it stays unsettled, the size of that uncertainty is itself a known quantity: the two candidate charts are 15° of sky apart. Sometimes that difference carries the Ascendant across a sign boundary and remakes the chart; sometimes it moves nothing worth noticing.
What comes next
The location is now complete: two angles, a height, a zone, and — where it was needed — a resolution for the one hour a year the zone could not settle alone.
From here the category turns from what a place is to what a place fixes, beginning with the shape of the sky above it.
Next: The Sky as a Sphere.