nc1700sJordan DNA Project


It is important for folks to understand the difference between my project begun 10 years ago and the project called JORDAN SURNAME PROJECT.  Our projects do impact each other.

When I submitted my first kit for our Great Uncle, I was a member of JORDAN SURNAME PROJECT. I’ve done research for over 37 years and the only way I know how to research is actively.  When our results populated I was contacted by the administrator and told my next step was to determine HOW our Matthew related to the JORDAN she claims in her work as her earliest ancestor, a Richard Jordan who died in Surry County VA in 1620.  Her ancestor was the MASTHEAD of the JG3 Jordan tree.  Both the administrator’s family and ours share the same JORDAN CLAN tree and will ultimately track back to a common ancestor.  The question is who and where?

My next step after receiving my results was to closely examine the JORDAN SURNAME PROJECT.  What I found was  1/3 of the kits were dormant deficient kits. In other words, some Jordan men had submitted kits quite some time ago. When genealogical DNA began one could only order 12 markers.  Sadly some of the participants in the Surname project had never upgraded their kit to 37 markers.  So I was left wondering if there was a match for Matthew hiding in plain sight!  Maybe one of the 12-25 marker kits held the answers I yearned to find.  So I began to reach out to the JG3 kit owners and asked all to upgrade their kits so proper comparisons could be made. That is what genealogical DNA does, it compares one or more different kits. The analogy of ships passing in the night applied.  It took me nine months. The degree of cooperation was wonderful. Everyone I found who had a deficient kit upgraded their kit.  One family whose family member had submitted a kit had passed on to glory was very kind and had a son submit a brand new kit to establish their branch in the FTDNA database!  PROGRESS!

At the end of the nine months I realized two things.  The JORDAN SURNAME PROJECT was not an active research project.  There was no effort in place to actually help identify missing branches for any of the established JG trees.  There were no updates from the project manager.  I found inconsistencies in research protocols.  For instance, I found 0nly one kit submitted and managed by the administrator to establish her RICHARD of SURRY.  Remember it takes three kits to CONFIRM a BRANCH.  There also was no uploaded gedcom (a digital pedigree chart) for Richard of Surry on FTDNA for the kit managed by the administrator.  I found both most odd. There was a copyrighted rootsweb site the administrator referred folks like me who returned as JG3.  I found conflicts on that website, conflicts with our test results, and more questions than answers.

Also I found several mistakes in submissions to the project in the JG3 JORDAN TREE.  The administrator explained a change in FTDNA policy prevented her from correcting mistakes.  I felt my best option was to concentrate on NORTH CAROLINA JORDANS.  SPECIFICALLY JORDANS who lived in NC during the 1700s.  This was the time frame our Matthew was born.  And as I reviewed the JORDAN SURNAME PROJECT I found over and over where many researchers were stymied here in Carolina.  So the obvious solution was to establish all of the branches possible!

I hope to learn how to add tables and charts soon.  I have worked since 2008 to try and reach JORDANS whose branches were/are not established in the FTDNA.com database.  I also realized the necessity to establish other CLAN lines.  I have over 140 active kits at the moment,  a new Georgia JORDAN kit found its way to the lab today!  Success will be determined by the cooperation and level of participation achieved.  I have confidence and high hopes!  But

My work, the NC 1700s JORDANS focused on NORTH CAROLINA JORDANS who lived here during the 1700s.  They could have pushed off before, during, or after either of the wars.  I began with an interest in only JG3 JORDANS.  As I worked to establish direct lines my interest included JG1, JG3, JG4, JG5, JG8, JG25, and JG 35 – the last two Clans were developed as a result of my effort.  That is the single most profound difference between the JORDAN SURNAME PROJECT and my PROJECT.  I work every day to try and advance the work. I don’t sit by and hope someone will someday match our family kits.  I had a Great Uncle in his late eighties who kindly did a kit for me and a family who has wanted to know more about our JORDANS for a long time.   Our reach was limited by missing records and conflicting published pedigree work.  DNA has offered us new hope and real evidence to help us find our way. I also have kits for men like Cornelius Jordan of Edgecombe who turned out to be a JG8 Jordan and tracked back to THOMAS THE QUAKER’s tree.  Some of THOMAS’s descendants who settled in the deep south need JORDANS who called BEDFORD to LYNCHBURG to CHARLOTTESVILLE home during the 1700s and into the early 1800s to establish their branches.  A Smith family from Stone Mountain has a NC Civil War Major’s BIBLE.  They do have a Jordan great+ grandma but they don’t seem be able to reconcile the Northampton CIVIL WAR JORDAN who moved his family up to Portsmouth VA after the war  with the DICKSON JORDAN branch whom they can track through real records.

Over and over it comes back to missing branches.  JORDANS who called Carolina (aka CARALANA) home during the 1700s being properly established. I am actively working to help JORDANS solve their mysteries, break through their brick walls, and in the process we will have a better understanding of some of the earliest settlers to Caralana.   Hopefully, with enough cooperation on both sides of the Atlantic from JORDANS, we can also find our migration ribbons back to the OLD COUNTRY, whatever COUNTRY that might turn out to be!

The map at the top of this page illustrates the vast area during the 1700s which is my focus.  FTDNA’s JORDAN SURNAME PROJECT includes anyone who carries the Jordan Surname anywhere in the world. And their subclades do not necessarily represent men who carry JORDAN CLAN ID.  Some of the JORDAN SURNAME PROJECT’s subclades belong to men who may legally carry the JORDAN SURNAME but their genetic CLAN ID belongs to a different CLAN than JORDAN.  Keep in mind though the JORDAN SURNAME PROJECT is not a true research project, it is a specialized repository.   It is my hope that others who have long roots in the research window of the NC1700sJordans now NCFAMILYGENETICGENEALOGY DNA Project will submit a DNA kit through FTDNA to help advance the work.  Whenever there is a surname switch there is a particular generation node that offers the solution.  My project uses both the Ymarker test and the family finder autosomal test so we can properly DNA map a clan line.   I welcome the opportunity to work alongside all who have long deep southern ancestral roots.

NC1700sJordans DNA Project expanded as of August 2019 and now is part of a larger genetic genealogy project called NCFAMILYGENEALOGY.  The work over the last decade has made clear families who track back to early Carolina belong to CLAN trees which include more than one surname.  There has been a divergence between the classic genealogy work of past generations and what we can accomplish today.   What began as SURNAME PROJECTS are more accurately CLAN PROJECTS.  The JORDAN SURNAME PROJECT has always included some subgroups, particular JG trees, for men who carry the Jordan name now but whose Ymarker information was and is NOT JORDAN.  For some JG trees there’s an understood specific generation node where a FEMALE JORDAN passed on her surname to a boy child instead of the carrying the surname of his father. There are numerous explanations which may explain a surname switch and in order to properly reach a conclusion one must DNA map CLAN lines.   The JORDAN SURNAME PROJECT does not include specifics, and offers no such help.  It is only a repository.

The NC1700sJordans Project will explore to solve any surname switch at any generational node paying close attention to families who called NC home during or before the 1700s.

It is necessary to properly establish each line in one’s pedigree work by getting a boy to do a Ymarker37 or greater DNA kit via FTDNA.com. The boy who does the kit will be able to GEOGRAPHICALLY establish his line only as far back as his PLACE of BIRTH.  Generationally he may be able to establish his line farther back than his own birth but not geographically!  NC1700sJordans and NCFamilyGeneticGenealogy uses genetic genealogy tools to DNA MAP and CONFIRM family lines geographically as well as generationally.  FTDNA’s Jordan Surname Project acts only as a repository for a submitter to learn what clan or JG tree one belongs. It does not map any particular clan generationally or geographically.


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.