Who was Samuel Chapman?

Samuel Chapman (1745–1748) was born in East Haddam, Middlesex, Connecticut, United States and died in East Haddam, Middlesex, Connecticut, United States. 2 researchers on YourRoots have this ancestor in their family trees.

How many people are researching Samuel?

Right now, 2 researchers on YourRoots have Samuel in their trees. The ancestor migration map traces 10 generations of this lineage.

What records do they have for Samuel?

Records vary by researcher and can include census, vital, parish, cemetery, and family sources.

How do I compare family trees?

Use Compare Tree on an available researcher profile to compare overlapping people and records.

Samuel Chapman 1745–1748

Public Tree Person

What is a Public Tree Person?

A Public Tree Person is an ancestor documented independently by multiple YourRoots tree owners. When several researchers' family histories converge on the same person, we publish a shared page that combines what they've documented.

Why this is a Public Tree Person

Full name consistent across 2 independent trees

Birth year and location consistent across 2 trees

Death year and location consistent across 2 trees

Compare a Public Tree Person with your own tree using Compare Tree.

B Reliability

Reliability Score: B

Medium — based on the source tree

Grade scale

A 3 criteria (Strong)
B 2 criteria (Medium)
C 1 criteria (Basic)

Verification checklist

Record available
Descendant's record available
Star tree owner

2 researchers on YourRoots have Samuel Chapman in their family trees — each with their own records and documentation. Trace the migration path across 10 generations. If this ancestor is in your tree too, you can compare what you've found and fill in the gaps together.

Last updated: July 22, 2026 · Reliability: B — verified across 2 independent trees

Born 21 Sep 1745 · East Haddam, Middlesex, Connecticut, United States

Died 15 Aug 1748 · East Haddam, Middlesex, Connecticut, United States

Father Caleb Champan

Mother Elizabeth Church

Siblings Asa Chapman, Caleb Chapman, Elizabeth Chapman, Miriam Chapman, Ozias Chapman, Timothy Chapman, Zachariah Chapman

Compare Tree

Researchers connected through Samuel Chapman 1745–1748

and 1 more tree owner connected with Samuel Chapman 1745–1748

Immediate Family

Parents

Caleb Champan

Elizabeth Church

Spouse(s)

No spouse recorded

Children

No children recorded

Biography

Samuel Chapman was born in 1745 in East Haddam, Middlesex, Connecticut, United States, the child of caleb champan and elizabeth church. Samuel Chapman passed away in 1748 in East Haddam, Middlesex, Connecticut, United States.

Sources

Life Timeline

1745

Birth of Samuel Chapman in East Haddam, Middlesex, Connecticut, United States

Birth

1748

Death of Samuel Chapman in East Haddam, Middlesex, Connecticut, United States

Death

Oldest Ancestor Line from Samuel Chapman

This ancestor line traces from Thaxted, Essex, , England (1491) to East Haddam, Middlesex, Connecticut, United States (1745) across 10 generations.

Direct Lineage

generations

Frequently Asked Questions

: Samuel Chapman (1745–1748) was born in East Haddam, Middlesex, Connecticut, United States and died in East Haddam, Middlesex, Connecticut, United States. 2 researchers on YourRoots have this ancestor in their family trees, each with their own records. This page combines what they've independently documented and assigns a Reliability Score (B) based on cross-tree validation.
: Right now, 2 researchers on YourRoots have Samuel in their trees. They're working independently, so connecting with them is a good way to cross-check your records and find things you might have missed. You can also explore the ancestor migration map that traces 10 generations of this lineage geographically.
: It varies by researcher — some have census records, others have marriage certificates, parish registers, or family Bible entries. Scroll up to see exactly what each person has cited.
: Use the "Compare Tree" button on any researcher's profile above. You can compare your tree side by side with theirs, see where your records overlap or differ, and collaborate to fill gaps.