When a Local Time Happens Twice
A time zone converts a clock reading into a real instant. Twice a year, for one hour, it cannot — and the applications will stop and ask you.
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. 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 instinct — pick the first one — is what most software does silently, and it is right half the time.
The applications will not do it silently, because the cost of being wrong is not small. 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 quietly becomes a chart that looks entirely normal and is an hour wrong in exactly the places that matter most.
What the applications do
They ask. Where a time falls inside an overlap, the applications stop and put both readings in front of you — the earlier occurrence and the later, each labelled with the offset it implies — rather than settling it quietly.
Your answer is stored with the record, not merely used and forgotten. That matters: a saved chart re-opened next year resolves to the same instant it did the first time, without asking again and without changing its mind.
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 is asked. The applications shift such a time forward by the length of the gap and carry on. The reading was wrong; the correction is unambiguous.
The practical advice
Most times are unambiguous and nothing appears. The dialog is rare by construction — one hour a year, in places that observe daylight saving at all.
When it does appear, it is asking a question about the source of your data, not about 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 usually cannot be settled at all, and the honest answer is that the chart has an hour of uncertainty in it.
If you genuinely cannot tell, it is worth casting both and seeing whether the difference changes anything you care about. Sometimes it moves an Ascendant across a sign boundary and matters enormously; 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. And the first thing it fixes is the shape of the sky above it.
Next: The Sky as a Sphere.