Born in the US Before 1967? Your Birth Chart May Be an Hour Off
Before 1967 the US had no national summer-time law, so astrology software guesses the clock. In most of Ohio that guess casts summer births an hour early. What one wrong hour does to your Lagna, Navamsa and dasha dates, and how Supastro corrects it.

If you were born in the United States before 1967, in summer, your chart rests on a guess about the clock. Almost every astrology app guesses the same way, and for a large group of births it is wrong by exactly one hour, with no warning.
What do daylight saving time and a UTC offset mean?
Daylight saving time, or summer time, means setting clocks an hour ahead for part of the year. A UTC offset is how far a local clock sits from Universal Time (UTC), the world clock astronomers use: New York runs at UTC−5 in winter and UTC−4 on daylight saving.
Software turns your birth time into Universal Time with the offset in force at that moment, and only then places the planets. Wrong offset, wrong moment. Parashara counted birth time in ghatis of 24 minutes from local sunrise; the wall clock is a modern layer the software must peel off correctly.
Why did the US have no national summer-time rule before 1967?
National war time ended in 1945. Until the Uniform Time Act of 1966 took effect in 1967, each state, city or town chose for itself. By the mid-1960s the map was a patchwork. Two babies born the same summer afternoon in the same state could have certificates written on clocks an hour apart.
Which parts of Ohio kept standard time all summer?
Astro-Databank, Astrodienst's research database, takes its time zones from the atlas professional astrologers use, and many of its entries come from birth certificates. Its Ohio records from 1947 to 1966 split the state:
| Part of Ohio | Summer clock, 1947 to 1966 | UTC offset in summer |
|---|---|---|
| West and central, west of 82.25° W: Cincinnati, Dayton, Columbus, Toledo, Lima, Hamilton, Middletown, Chillicothe, Portsmouth, Sandusky and more | Standard time every summer | −5 |
| Northeast: Cleveland, Akron, Canton, Youngstown, Warren, Steubenville | Daylight time in most summers | −4 in most summers |
On the same summer afternoon, a Canton birth, in the northeast, is usually recorded on daylight time and a Dayton birth on standard time. Cincinnati's clocks ran fast even without a summer shift: at about 84.5° West, Eastern time already sets them some 38 minutes ahead of the Sun.

Why do most astrology apps get it wrong?
Almost all software, astrology apps included, takes clock history from the global time zone database. It files all of Ohio under New York City, which moved its clocks forward every summer, so a 1962 Dayton summer birth gets UTC−4 instead of UTC−5. The database's own documentation is frank about its limits: it only promises that the clocks inside each zone agree after 1970.
In November 2026 we tested AstroSage, Drik Panchang and Prokerala with a made-up test birth: Cincinnati, 15 July 1965, at noon. All three applied daylight saving, UTC−4. Prokerala labels it "EDT (-04:00), DST Applied" and AstroSage shows "Time Zone -4.0". Their planets matched Supastro's to about one arc-minute: the astronomy was right, the clock was not, and each cast the sky one hour before the birth. They trust the database everyone trusts.
What does one wrong hour do to a Vedic chart?
The Lagna, or ascendant, is the sign and degree rising in the east at birth; it fixes all twelve houses. A nakshatra is one of 27 lunar mansions, 13°20' each; a pada is a quarter of one. The Navamsa (D9) cuts each sign into nine slices; I read it for marriage, dharma and real planetary strength. The D10, ten slices per sign, is the career chart (how they differ). Vimshottari dasha, the sequence of planetary periods that times events, starts from the Moon's exact place in its nakshatra.
I ran 2,000 sample births across Ohio from 1947 to 1966 through Supastro's engine, each cast twice, one hour apart. Here is what moved:
- Planets almost always keep their signs, which is why a wrong chart can look almost right.
- The Moon moves about half a degree: a new nakshatra in only about 1 chart in 20, a new pada in about 1 in 6.
- The Lagna moves 12 to 26 degrees, 15 on average: a new sign about half the time, which changes every house.
- The D9 rising sign changed in every one of the 2,000 charts.
- The D10 rising sign changed in about 19 charts out of 20.
- Every Vimshottari dasha date shifts 3 to 11 months, depending on the period you were born in. See yours in the free dasha calculator.
In a reading, that is a career period turning a season away from the date you were given.

How does Supastro find the right clock for your birth?
- Coordinates, not the city name. We find your time zone from your birthplace's exact latitude and longitude.
- Your birth date's offset, not today's. We work out the UTC offset in force at your exact birth date and time.
- A historical correction layer. Where real clocks differed from the database, we add a rule built from birth-certificate atlas records and checked against them in every build. The first: Ohio west of 82.25° West, 1947 to 1966, UTC−5 all year. Northeast Ohio, whose towns changed their minds year by year, keeps the database's answer.
Born there and then? Enter the time exactly as written on your certificate. More: daylight saving time and your birth chart and how Supastro works.
Born elsewhere in the US before 1967?
Ohio is our first rule; elsewhere Supastro uses the global database, like almost every app. If your birth certificate names the time used, that settles it. Our seven chart accuracy tests show what else to check.
Were births in India affected by old clocks too?
India's Second World War clock, an hour ahead of IST, is in the database, and Supastro applies it. Two city clocks need your attention: Bombay time, 39 minutes behind IST, until 1955, and Calcutta time, about 23 minutes ahead, until 1948. If an old record was written in city time, convert it to IST first.
Frequently asked questions
I was born in Cleveland in the summer of 1960. Is my chart affected?
Probably not. Northeast Ohio kept daylight time in most summers, which matches the database, and Supastro leaves northeast Ohio births unchanged. If your record says standard time, trust the record.
How can I tell if another app got my chart wrong?
If it shows the offset, read it. A summer birth from 1947 to 1966 in Ohio west of 82.25° West (roughly Newark, Lancaster and Chillicothe westward) should show −5. If it shows −4 or "DST applied", the chart is an hour early. Where you can set the zone by hand, set −5 with daylight saving off.
Should I just change my birth time by an hour?
No. Fix the offset, never the time. Subtracting the hour feels natural and doubles the error to two hours. Cancelling a wrong UTC−4 means adding an hour, which you will forget the next time you enter your details.
Can one hour really move my dasha dates by months?
Yes. The first dasha's balance depends on how far the Moon had travelled through its nakshatra. An hour moves the Moon about half a degree, near 4 percent of a nakshatra; 4 percent of Venus's 20-year period is about ten months, and every later date moves with it.
Does Supastro change the birth time I saved?
No. Your saved time stays exactly as you typed it. The correction changes only the offset used to turn it into Universal Time, so an affected chart is recast from the right moment the next time it is drawn.


