Why Pitru Paksha Follows the Sun Into Kanya, Not the Calendar

Most religious observances get pinned to a month and a number. Pitru Paksha refuses that. It begins on the Pratipada tithi of the Krishna Paksha, the waning fortnight, that falls after the Sun enters Kanya rashi, the zodiacal segment the Western tradition calls Virgo. When the Sun crosses that boundary, the fortnight of ancestral rites opens. When the Sun leaves Kanya, it closes. No printed date can capture this in advance without doing the astronomy first.

The boundary itself is not arbitrary. The ecliptic, the Sun's apparent path across the sky, is divided into twelve segments of thirty degrees each. Kanya occupies the sixth. The Sun's entry into each segment, called a Sankranti, has marked ritual time in the subcontinent for at least two thousand years. Kanya Sankranti is the one that opens Pitru Paksha. The moment of crossing is computed from the Sun's actual position, which is why the Gregorian date shifts by a day or two from year to year.


The rishis who formalised the Vedic calendar were not working from intuition. They were working from observation. The Vedanga Jyotisha, one of the oldest astronomical texts associated with the Vedic corpus, records solar and lunar positions with the explicit purpose of fixing ritual time. The system they built is a luni-solar calendar: the Moon governs tithis, the Sun governs the larger seasonal frame.


Pitru Paksha sits inside that frame deliberately. By the time the Sun reaches Kanya, the monsoon is withdrawing across most of the subcontinent. Agriculturally, this is the pause between the labour of sowing and the labour of harvest, a window that ancient communities could actually use for extended ritual. The astronomy and the ecology agreed, so the calendar was built around the agreement.


The tithis within the fortnight run from Pratipada to Amavasya, the new moon. Each tithi is associated with a specific category of ancestor. Amavasya itself, Mahalaya, is the most significant, the day when the veil between the living and the ancestral realm is held to be thinnest. That day is computed from the Moon's position, not from a clock. The Sun sets the frame; the Moon sets the detail.

The Gregorian calendar is a solar calendar, but it tracks a different solar year than the Vedic system uses. The Gregorian year is tropical, it resets at the March equinox. The Vedic sidereal year tracks the Sun's position against the fixed stars of the nakshatra system. Because of a slow wobble in Earth's axis called the precession of the equinoxes, roughly 50 arc-seconds per year, the two systems drift apart by about one day every seventy-two years.

This is why Kanya Sankranti now falls in mid-September on the Gregorian calendar rather than in late August, where it would have sat roughly fifteen centuries ago. The stars have not moved relative to each other. Earth's axis has shifted its orientation slightly. The Vedic calendar tracks the stars; the Gregorian calendar tracks the equinox. They are measuring different things, and the gap between them is called the ayanamsha. Most Indian astronomical almanacs, the Panchanga, use the Lahiri ayanamsha, adopted by the Government of India's Calendar Reform Committee in 1955, to convert between the two systems.

The practical consequence is simple: you cannot look at a Gregorian wall calendar and find Pitru Paksha. You look at a Panchanga, which has already done the conversion from the Sun's actual ecliptic position.

It is worth being exact about what ancient Indian astronomers could and could not do. They could not measure the Sun's position with the arc-second precision of a modern ephemeris. What they could do, and did, with instruments like the Jantar Mantar observatories built in the eighteenth century to refine earlier calculations, was track the Sun's crossing of each rashi boundary with enough accuracy to fix ritual time reliably across generations.

The Jantar Mantar in Jaipur, built by Maharaja Jai Singh II, contains the Samrat Yantra, a sundial whose gnomon shadow moves at roughly six centimetres per second at noon. It could read local solar time to an accuracy of about two seconds. That level of precision was not decorative. It was in service of exactly this kind of calendar computation: knowing when a Sankranti occurred, down to the ghatika and the pala, units of roughly twenty-four minutes and twenty-four seconds respectively.

Modern Panchanga computation uses the same underlying solar longitude but calculates it with planetary ephemeris data accurate to fractions of an arc-second. The ritual intent is the same as it was two thousand years ago. The arithmetic is now done by software running the same orbital mechanics that ISRO uses for mission planning.

The question of why Kanya specifically, and not any of the other eleven rashi boundaries, was chosen for Pitru Paksha sits partly outside astronomy. The texts associate Kanya with a period of thinning between realms, with the southward journey of the Sun after the summer solstice having reached a particular stage, and with the Moon's nodes, Rahu and Ketu in the Navagraha system, in configurations that the tradition holds significant for ancestral connection. These are cultural and cosmological claims that astronomy can sit alongside without adjudicating.

What astronomy does settle is this: the boundary is real, the crossing is measurable, and the calendar built around it is internally consistent in a way that a fixed Gregorian date could never replicate. Pitru Paksha moves because the Sun moves, and the people who designed the system wanted the rite to follow the sky, not a number printed in advance by a press that had no access to the sky at all.

The fortnight ends with Mahalaya Amavasya, the new moon that closes Kanya, and then the Sun moves into Tula, Libra, and the ritual window closes with the same astronomical precision with which it opened. The calendar was not approximate. It was tracking something.