Joseph HOTCHKISS

Joseph HOTCHKISS[1, 2]

Male 1678 - 1740  (62 years)

Personal Information    |    Sources    |    All    |    PDF

  • Name Joseph HOTCHKISS  [3
    Born 8 Jun 1678  New Haven, New Haven, CT, USA Find all individuals with events at this location  [3
    Gender Male 
    Died 31 Jul 1740  Guilford Twp., New Haven, CT, USA Find all individuals with events at this location  [3
    Buried Guilford, New Haven County, Connecticut, United States of America Find all individuals with events at this location  [3
    Person ID I7732  Ancestrees
    Last Modified 8 Jul 2022 

    Father John HOTCHKISS,   b. 1643, New Haven, New Haven, CT, USA Find all individuals with events at this location,   d. 23 Sep 1689, New Haven, New Haven, CT, USA Find all individuals with events at this location  (Age 46 years) 
    Mother Elizabeth PECK,   b. 16 Mar 1649, New Haven, New Haven, CT, USA Find all individuals with events at this location,   d. 1730  (Age 80 years) 
    Married 4 Dec 1672  New Haven, New Haven, CT, USA Find all individuals with events at this location 
    Family ID F6997  Group Sheet  |  Family Chart

    Family Hannah CRUTTENDEN,   b. 27 Mar 1678, Guilford, New Haven County, Connecticut, United States of America Find all individuals with events at this location,   d. 28 Mar 1756, Guilford, New Haven County, Connecticut, United States of America Find all individuals with events at this location  (Age 78 years) 
    Married Apr 1699  Guilford Twp., New Haven, CT, USA Find all individuals with events at this location 
    Last Modified 8 Jul 2022 
    Family ID F1923  Group Sheet  |  Family Chart

  • Sources 
    1. [S2755] Donald Lines Jacobus, Families of Ancient New Haven (Baltimore, Genealogical Publishing Co., Inc, 1974).

    2. [S2847] Charles Henry Stanley Davis, Early Families of Wallingford, Connecticut (Baltimore, MD, Genealogical Pub. Co., c1979).

    3. [S208] U.S., Find a Grave Index, 1600s-Current, Ancestry.com, (Ancestry.com Operations, Inc. Date:2012 Place:Lehi, UT, USA), 1,60525::0. (Reliability: 0).