Pavaday Gounden

About this record

Pavaday Gounden appears in the Natal indenture register as an arrival from the Madras Presidency. Between 1860 and 1911, roughly 152,000 indentured labourers were shipped from Madras to Natal under a five-year contract to work on the sugar, tea, coffee and wattle estates of what is today KwaZulu-Natal. Each arrival was recorded at the Durban depot with a name, father’s name, age, native district (zillah), often a specific village, the ship they came on, the arrival date, and the estate they were assigned to. The Gandhi-Luthuli Documentation Centre at the University of KwaZulu-Natal (GLDC) holds the master copies of these registers today; the National Archives and Records Service of South Africa (NARSSA) maintains parallel estate-employment records that name spouses and children not always captured on the arrival register. TamizhConnect indexes both, cross-referenced by immigration number.

This arrival falls in the peak volume years. Between 1890 and 1902, roughly half of all Natal indenture arrivals across the entire 1860-1911 window were recorded. At the peak, ships ran two to three per month from Madras, and estate labour registers were kept in triplicate to handle the assignment paperwork. Records from this window are the densest in the archive but also carry the most transcription-error risk: the Durban depot clerks were often processing 400 to 700 arrivals in a single afternoon.

South Arcot's coastline gave labourers a shorter overland route to the Madras depot, and the Cuddalore-Villupuram belt was a heavy sending zone through the 1880s and 1890s. This district's labourers often carry names with French orthographic influence (Karikal was administered by the French until 1954) — Ou spellings where English would use U, terminal S kept on names that were dropped in the Anglo-Indian columns.

The PONGOLA XXVIII crossing, 1898

The PONGOLA XXVIII sailed to Natal in 1898. A typical crossing from Madras to Durban took ten to twelve weeks under sail and steam. Ships boarded at the Madras roads offshore of Chennai, called at Karaikal or Nagapattinam to complete the Madras-side manifest, then ran a great-circle course across the Indian Ocean towards Port Natal. Conditions below decks were tight — most vessels carried 400 to 700 labourers per voyage in bunks stacked three deep — and colonial regulations required a ship’s surgeon, cooked rice rations twice a day, and separate quarters for women and children. Departure spellings of names were often Anglicised phonetically by the Madras depot clerk; arrival spellings were sometimes corrected, sometimes compounded further by the Durban clerk. Either way the spelling on the paper record is rarely how the family spells the name today.

Reading the record like a historian

Colonial spelling drift is the single hardest thing about using indenture records. Because the ancestor on this page is recorded as Pavaday Gounden, “Palanisamy” appears as Palanisami, Palanissamy and Palany Sami. “Perumal” as Peroumal, Peroumall and Perumall. The Tamil retroflex ‘l’ in Perumal has no English equivalent, so clerks improvised — a doubled ‘ll’, a silent ‘e’, or occasionally a dropped consonant. Alongside those name-specific shifts, the general rules apply: vowel doubling (“oo” for “u”) was common; terminal consonants often lost their trailing vowel (“Padayat” for “Padayachi”); French-transliterated names from Karaikal (Karikal) or Pondicherry appear with “ou” where English would use “u”; and names starting with an aspirated consonant (Th, Ch, Dh) were often written without the h. When you compare this record against family memory, treat the paper spelling as one candidate variant and check against three or four phonetic alternatives before dismissing a match.

Reaching the Tamil Nadu side

The origin village on this record (Agaram, South Arcot district) is the anchor point for finding the extended family that stayed behind. The Tamil Nadu Election Commission publishes annual voter rolls at village-level detail; if a family with the same surname still lives at Agaram, they may well descend from the siblings and cousins Pavaday Gounden left behind in the 1860s to 1900s. Search the voter roll for the village and any surname pattern you can guess; a match is not proof of a shared line by itself, but it usually surfaces a living contact who knows the family history the archive can’t reach. For the mechanics of that reverse- lookup, the guide Find Tamil ancestors by village name walks the exact search sequence.

Next steps if this is your ancestor

If this record matches what your family already knew, the practical next step is to save it as an anchor point in a documented family tree and start pulling the related records that radiate from it — the ship manifest for other same-village passengers, the estate register for co-workers who arrived together, and the Tamil Nadu voter roll for the origin village. If the match is only partial (right name, wrong village, or right village, wrong ship year), it’s worth treating this as a lead rather than a confirmation and looking for a second and third source before incorporating it. The three-source rule from the records-search guide is the standard bar, and the three sources have to be genuinely independent: an indenture register, an oral history from an elder who did not learn it from the same paper, and a third source of a DIFFERENT type — a temple archanai or marriage record, a land/patta title, a school admission register, or a colonial-era postcard, letter, or photograph. Two land documents (a patta plus another land record) are the same type of evidence and don’t count as separate corroboration.

Pavaday Gounden's record carries no other named kin in the NARSSA estate index, which is more common than descendants expect — the estate clerks recorded a spouse or child only when a specific event (marriage, birth, death, insurance claim) triggered the entry. The absence of kin here doesn't mean the ancestor was alone; it means the estate paperwork never had a reason to record the family. Ship-manifest co-passengers and same-village emigrants (both listed on this page) are the strongest alternative anchors when kin is thin.