Fritz/Fritts Family History

Our Family's Journey Through America

Search Results


Matches 1 to 27 of 27 for First Name starts with GEORGE

Heat Map

 #  Last Name, Given Name(s)    Person ID   Born/Christened    Location   Tree 
1
Beeker, George Albert Sr
I335  b. 11 May 1907 Davidson County, North Carolina, USA  Fritz/Fritts
2
Beeker, George Albert Jr
I340  b. 2 Feb 1939  Fritz/Fritts
3
Byerly, George
I36    Fritz/Fritts
4
Cornelison, George
I47  b. Abt 1846  Fritz/Fritts
5
Davis, George Lewis
I1330    Fritz/Fritts
6
Erath, George Snider
I1636    Fritz/Fritts
7
Fritts, George Sr.
I4  b. 1753 Shenandoah County, Virginia, British America  Fritz/Fritts
8
Fritts, George Jr
I24  b. 19 Jun 1788  Fritz/Fritts
9
Fritts, George
I536  b. About 1796 Lincoln, NC  Fritz/Fritts
10
Fritts, George
I1411  b. 1807  Fritz/Fritts
11
Fritts, Captain George
I37  b. 23 Jan 1807 Rowan County, North Carolina, USA  Fritz/Fritts
12
Fritts, George
I1107  b. 1832 Roane County, Tennessee, USA  Fritz/Fritts
13
Fritts, George
I1116  b. 1858 Roane County, Tennessee, USA  Fritz/Fritts
14
Fritts, George Edward
I838  b. 13 Feb 1901 Mount Vernon, Indiana, USA  Fritz/Fritts
15
Fritts, George Edward
I889    Fritz/Fritts
16
Fritts, George M.
I1245  b. 10 Jun 1879 Tennessee, USA  Fritz/Fritts
17
Fritts, George M.
I138  b. 1889  Fritz/Fritts
18
Fritts, George W.
I135  b. Abt 1859  Fritz/Fritts
19
Fritts, George W.
I1066  b. Apr 1883 Illinois, USA  Fritz/Fritts
20
Fritts, George Washington
I1292  b. 28 May 1836 Roane County, Tennessee, USA  Fritz/Fritts
21
Fritts, George Washington "Gip"
I1507  b. 22 Jun 1872  Fritz/Fritts
22
Hood, George T.
I1667  b. 29 Jun 1866 Roane County, Tennessee, USA  Fritz/Fritts
23
Ledford, George
I1448  b. 1880  Fritz/Fritts
24
Lopp, George
I127  b. 1893  Fritz/Fritts
25
Lopp, George J
I129  b. 1925  Fritz/Fritts
26
Morgan, George
I522    Fritz/Fritts
27
Septor, George
I833    Fritz/Fritts

Heat Map



Webmaster Message

We strive to document all of our sources in this family tree. If you have something to add, please let us know. We will be happy to make any change if there is better documentation than what we have.