Lloyd Paul Moore

‹ Back to Moore surname

Is your surname Moore?

Connect to 5,000+ Moore profiles on Geni
Start your family tree now

Lloyd Paul Moore's Geni Profile

Share your family tree and photos with the people you know and love

  • Build your family tree online
  • Share photos and videos
  • Smart Matching™ technology
  • Free!
Get Started

Lloyd Paul Moore

Birthdate:
Birthplace: Salem, WV, United States
Death: December 20, 1977 (66)
Clarksburg, WV, United States
Immediate Family:

Son of Orval Moore and Tabitha Myers
Husband of Sarah Elizabeth Moore (Law)
Father of Private; Freda Mae Moore; James "Bud" Edward Moore; Melvin "Hoppy" Eugene Moore; Mary Elizabeth Moore and 8 others

Managed by: Private User
Last Updated:
View Complete Profile

Historical records matching Lloyd Paul Moore

Lloyd Paul Moore in FamilySearch Family Tree
Lloyd Paul Moore in MyHeritage family trees (Slack Web Site)
Lloyd Paul Moore in MyHeritage family trees (Chesser Web Site)
Lloyd Paul Moore in MyHeritage family trees (devericks Web Site)
Lloyd Paul Moore in MyHeritage family trees (Cozad Web Site)
Lloyd Paul Moore in MyHeritage family trees (Lindzy Web Site)
Lloyd Paul Moore in MyHeritage family trees (Family site (Family Tree Legends))
Lloyd Paul Moore in MyHeritage family trees (Robison Web Site)
Lloyd Paul Moore in MyHeritage family trees (Barrett Web Site)
Lloyd Moore in U.S. Social Security Death Index (SSDI)
Lloyd Paul Moore in MyHeritage family trees (law Web Site)
view all 16

Immediate Family

view all 16

Lloyd Paul Moore's Timeline

1911
August 29, 1911
Birth of Lloyd Paul Moore
Salem, WV, United States
1933
April 5, 1933
Birth of Freda Mae Moore
WV, United States
1936
July 23, 1936
Birth of James "Bud" Edward Moore
1938
March 24, 1938
Birth of Melvin "Hoppy" Eugene Moore
1940
April 9, 1940
Birth of Mary Elizabeth Moore
Follow UsLike Us
English (US)   eesti   Svenska   Español (España)   Français   עברית   Norsk (bokmål)   dansk   Nederlands   Deutsch   »
close
settings
By using Geni you agree to our use of cookies as identifiers and for other features of the site as described on our Privacy page.