| LORETHA M: LECLERC, HEISEL, GARDNER - people search, genealogy, find deceased relatives and locate ancestors |
| Name | | SSN  | Date of birth | Date of death | Lived | State | Zip Code (Last Residence) | Zip Code (Lump Tax payment) |
|---|
| LORETHA M HURLEY | | 310-07-1924 | April 8, 1910 | June 1, 1989 | 79 years | | | |
| |
| LORETHA M MATTHEWS | | 243-36-2274 | October 4, 1928 | October 13, 1989 | 61 years | NC | 28401 (Hightsville, New Hanover County) | 28401 (Hightsville, New Hanover County) |
| |
| LORETHA M ODLE | | 456-07-7315 | August 7, 1918 | April 1, 1990 | 71 years | | | |
| |
| LORETHA M NEAL | | 448-44-5701 | September 13, 1922 | November 21, 1992 | 70 years | OK | 73110 (Midwest City, Oklahoma County) | |
| |
| LORETHA M HEISEL | | 479-46-8285 | December 18, 1917 | January 19, 1994 | 76 years | IA | 52556 (Fairfield, Jefferson County) | |
| |
| LORETHA M BRUNSON | | 310-01-1840 | January 17, 1906 | January 22, 1994 | 88 years | IN | 46036 (Elwood, Madison County) | |
| |
| LORETHA M SMITH | | 241-22-2013 | October 8, 1923 | January 24, 1996 | 72 years | NC | 27405 (Greensboro, Guilford County) | |
| |
| LORETHA M BERRY | | 505-24-6679 | May 2, 1922 | September 14, 1996 | 74 years | NE | 68025 (Fremont, Dodge County) | |
| |
| LORETHA M GIVINS | | 264-68-2847 | June 3, 1942 | March 6, 1998 | 55 years | | 33705 | |
| |
| LORETHA M MELLOR | | 524-20-3512 | September 15, 1914 | October 1, 1998 | 84 years | CO | 80033 (Wheat Ridge, Jefferson County) | 80033 (Wheat Ridge, Jefferson County) |
| |
| LORETHA M MITCHELL | | 455-86-3609 | October 1, 1943 | July 28, 1999 | 55 years | TX | 76470 (Ranger, Eastland County) | |
| |
| LORETHA M LECLERC | | 310-18-8673 | January 7, 1923 | March 5, 2001 | 78 years | IN | 46835 (Fort Wayne, Allen County) | |
| |
| LORETHA M BRADLEY | | 562-22-3097 | July 17, 1917 | March 6, 2001 | 83 years | CA | 94550 (Livermore, Alameda County) | |
| |
| LORETHA M COUSIN | | 436-13-8978 | July 23, 1935 | November 3, 2001 | 66 years | LA | 70445 (Lacombe, St. Tammany County) | |
| |
| LORETHA M BURROW | | 460-28-8197 | April 18, 1924 | July 7, 2002 | 78 years | TX | 75496 (Wolfe City, Hunt County) | 75496 (Wolfe City, Hunt County) |
| |
| LORETHA M WAGNER | | 523-20-8683 | July 14, 1925 | October 4, 2002 | 77 years | CO | 80524 (Fort Collins, Larimer County) | |
| |
| LORETHA M KIRKLAND | | 259-02-5409 | April 27, 1936 | August 4, 2003 | 67 years | GA | 31601 (Valdosta, Lowndes County) | |
| |
| LORETHA M HANCOCK | | 215-28-1567 | October 6, 1931 | September 14, 2003 | 71 years | MD | 21222 (Dundalk, Baltimore County) | |
| |
| LORETHA M GARDNER | | 458-56-2789 | October 8, 1932 | April 10, 2004 | 71 years | LA | 70544 (Jeanerette, Iberia County) | |
| |
| LORETHA M WHATLEY | | 509-28-5392 | April 4, 1930 | July 31, 2004 | 74 years | CA | 91001 (Altadena, Los Angeles County) | |
| |
| LORETHA M KUIPER | | 430-68-3800 | February 3, 1939 | June 23, 2006 | 67 years | OK | 74901 (Arkoma, Le Flore County) | 92225 (Blythe, Riverside County) |
| |
| LORETHA M WARD | | 225-41-0457 | October 11, 1980 | August 2, 2009 | 28 years | VA | 24230 (Coeburn, Wise County) | |
| |
Death statistics by year for last name HURLEY
Average age at death for last name HURLEY
Is any person on this list your grandfather, grandmother, father, mother, uncle, aunt, other family member, or a friend?
- Click on the
"Add information" button next to this person's name to connect with his or her family, friends, add an obituary or other information.
- Click on the
"Add photo" button to add this person's photograph or picture of the gravestone.
Death statistics by state for last name HURLEY
Last name popularity statistics for persons named HURLEY per 10,000 residents in every state
- Popularity of last name HURLEY decreased from 0.015% in 1990 to 0.014% (38971 people) in year 2000. Last name HURLEY moved from 807th to 808th place on the most common names list in the USA
Based on public records. Inadvertent errors are possible.
LocateAncestors.com does not guarantee the accuracy or timeliness of any information on this site. Use at your own risk.
