North Carolina Nexus

 

Finding a possible nexus between the Tyson line and the Hardee line, especially leading back to Pitt County, North Carolina, may have been helpful, but the next step is to find actual documentation. For someone said to have been born in 1701—that would be Susannah Tyson, daughter of Mathias and Mary—that next step can cause trouble.

Why? It's fairly simple. Given not only the date over three hundred years ago—not to mention the change of government—the chances of the records we need to verify family connections being in decent condition are slim. Worse, those records might currently be non-existent, if we take into account courthouse fires, wars, and other catastrophes.

One encouraging note, however, was the possible discovery of a will which might have been penned by Susannah's father, Mathias Tyson—or Tisson, as the clerk fashioned that name back on April 5, 1710. I say "possible" because the page upon which the will was written was torn or bent just after the phrase, "last will and testament of." There is one word inserted, but hidden, before the next line continues with Mathias Tison's name.

Granted, at the end of the document, where Mathias Tison left his mark, the clerk inscribed the name as "Mthyas Tisson," which is, I guess, close enough for me.

The document stated that this Mathias was an inhabitant of "Baith County" in North Carolina. As it turns out, there was a county named Bath in North Carolina, but it is now called an extinct county. The county was in existence as part of the British Colony of what is now North Carolina, from the county's establishment in 1696 through 1739.

At that time, Bath County contained three precincts, one of which eventually became known as Beaufort Precinct. When Bath County was officially abolished, Beaufort Precinct became a county in its own right. And, as the years passed, Beaufort County itself eventually was carved out to form additional counties, one of which—as you might have suspected—became known as Pitt County.

Thus, at least for this Tison line which led, through Mathias' daughter Susannah, to her husband and eventually the Hardee family descendant who married Job Tyson's son William, we now have a connection back to Pitt County, North Carolina. But what about Job, himself?

If we can't draw our way up the family tree by virtue of Job's as-yet-unknown father, perhaps we can discover a way down from Mathias Tison back to Job's own generation. We'll take a closer look at Mathias Tison's will tomorrow.

How Twisted and Tedious the Trail

 

If we can't figure out a family line based on one side of a married couple, how about trying the other side? That seemed like a viable premise when I realized that my fourth great-grandfather, Job Tyson, eventually had a daughter-in-law whose roots reached back to another Tyson relationship. Added bonus: that relationship led to the location of the supposed roots of Job Tyson's family, too. Surely, I'd be led straight back to the answer in Pitt County, North Carolina, by following this other line.

That line belonged to the Hardee family of Pitt County—the very line conveniently said to belong to my newfound kazillionth cousin, according to "Relatives Around Me."

To use a trailblazer to outline a family's generations seems straightforward, at face value: find a published genealogy maintaining that connection—in my case, the Tyson and Hardee families of Pitt County—and then verify by finding documentation.

That was easily said. Not so easily done, at least in this case. So far, I've wandered through several manuscripts, thankfully posted either at FamilySearch or at Ancestry. While reading, I've outlined the names and dates of pertinent family members.

Next step: find the documents. That's the not-so-easily done part of the equation. So far, I have eighteen tabs open on my computer. My brain can't hold all that information in one night's setting. Though not quite to the stroke of midnight, I had to give up last night, even though it meant trying to remember everything once again in the morning.

It is likely time to pull out the old yellow warning sign to post on each name I've entered—tentatively—in my family tree. Having a place to diagram the relationships helps, but snaring any unsuspecting passer-by into thinking that posted entry was correct would be a disservice to fellow researchers. But sometimes, finding the facts can take time, yet remembering everything found without a work space can be a challenge.

So far, I've outlined the proposed generations of Job's daughter-in-law, William Tison's first wife Mary Ellis Hardee, back to her ancestor John Hardee, who married someone named Susannah Tyson. Next will be to find adequate documentation to verify the stories handed down through those typewritten genealogies of past generations of the Hardee and Tyson families. There are several resources yet to consult, leading down a twisted and tedious trail, indeed.

When Two Families Collide

 

It was at a local genealogical society meeting when, just for fun, several of those in attendance pulled out their phones, logged in to the FamilySearch app, and fired up "Relatives Around Me." The goal was to see whether—at least, according to the universal tree at FamilySearch.org—anyone in the meeting room that day was sitting near a distant cousin. You never know when, generations past, two families' ancestral lines might have collided.

It turned out that one woman in the meeting just happened to get a result indicating that she and I were distant cousins. Her ancestor? Someone surnamed Hardee. Mine? My brick wall fourth great-grandfather, Job Tyson. Supposed shared origin for those two? Pitt County, North Carolina.

Now, I know that sometimes the universal tree at FamilySearch.org can contain mistakes. I didn't get too excited about that discovery back then—and even now, I'm struggling to find documentation to cement the connection. But I didn't ignore it, either. My newfound cousin and I have been collaborating, as time permits, to seek out the explanation for how those two lines are related.

But Hardee. And Pitt County. While I'm stuck with that designation of Pitt County, North Carolina, for the origin of my Tyson ancestors, I did remember that Relatives Around Me readout pointed to that other surname, Hardee or Hardy. I kept looking for an explanation that might make sense. This weekend's discovery of a Hardee family history manuscript, a copy of which I found posted at Ancestry.com, reminds me that this is a worthwhile route to re-examine.

Sure enough, pushing the line back far enough—starting from Job Tyson's son William Tison, to William's wife Mary Ellis Hardee—I then continued the Hardee line, according to what was written in the David Hardy manuscript. Mary's father, Thomas Ellis Hardee, was said to have been son of John Hardee and Sarah Ellis.

Following the family line upwards from there two additional generations, the Tyson surname once again popped up in this Hardee manuscript. This time, the manuscript contained a mention of the wife of another John Hardee: he had married someone named Susannah Tyson. The line entry for this couple noted they were in Pitt County, North Carolina.

With that brief outline, I now had another possible connection between the two families. More importantly, the line brought the Hardee family from Camden County in Georgia—not far from where Job Tyson lived in Glynn County, and the same county where the witness to Job's will, another ancestor named Charles McClellan, also lived at that time.

With connections seemingly pointing in the right direction, it was time to check out this assertion with actual documentation, a task on my to-do list for this week. 

Exploring the Back Stories

 

We're halfway through the month, and so far I've been unable to find any solid connection between my fourth great-grandfather Job Tyson and either possible location of his birth. Lacking any further leads—at least until yesterday's discoveries—I decided it was time to explore collateral lines for any sign of the Tyson/Tison back story.

That's essentially what has been happening behind the scenes over the past two weeks: looking for the back story. Since today was time for my biweekly count, I was surprised to see what an impact that effort could make. All during the time I was writing about not finding any documentation to connect Job Tyson to either North or South Carolina—two alternate possibilities for his roots—I've been exploring the ThruLines connections to the Tyson family and building a line of descent for each of those collateral relatives.

What was the result for this two weeks of grunt work? I actually added 263 more documented individuals to my family tree, all from this Tyson line descending from Job and his wife, Sidnah Sheffield. That pushes the tree's total to 41,574. Bringing a family's history down to the present time from a point on the timeline spanning over 225 years can add a lot of names—and I'm nowhere close to being done.

The test results blossoming from holiday DNA tests are now finally hitting my count, as well. I've gained ten more matches at Ancestry DNA, more than my usual one or two for each biweekly stretch. Though it doesn't help my focus for this month's candidate for my Twelve Most Wanted, I also found a Zegarski match to my father's side of the family tree. I'll be watching for more from the Tyson or Tison side of the story as the rest of these holiday tests keep appearing in my results. Likewise for every other company where I've tested.

Meanwhile, though I'm not researching anyone on my in-laws' side of the family, once again that tree grew by one additional name, thanks to follow up work after a phone call from a relative. It's so exciting to see younger members of the family taking interest in the details of their own family history, especially when they, too, are awaiting DNA test results and want to know how they connect to the bigger picture.  

A Detour Through the Sidelines

 

Sometimes, when I'm stumped with a collateral line, I go wandering. This time, still puzzling over the origin of my fourth great-grandfather Job Tyson, I started looking at DNA matches while exploring what became of Job's many children. Yes, I took a detour. Since I couldn't advance the record to Job's parents (or even siblings), I went exploring the sidelines of this Tyson family.

Reviewing the records I had already assembled about the children of Job Tyson and his wife, Sidnah Sheffield, my eye settled on one of their sons, William. There, I spotted one detail which stopped me: William had married a woman whose maiden name was Hardee.

That Hardee surname, I had learned when I first decided to make this Tyson project my Twelve Most Wanted focus for February, was the surname which my newly-discovered kazillionth cousin—thanks to FamilySearch's Relatives Around Me—had focused on. She was a Hardee descendant, and she knew exactly where, deep within their history, the family had once lived: in Pitt County, North Carolina, the same location where I simply cannot place our Job Tison.

Nearly holding my breath, I tried to draw up a quick and dirty sketch of that family line. Starting from William Tison, himself, his declaration for a passport provided his date and location of birth: August 6, 1812 in Glynn County, Georgia. I had already recorded that William had been married twice. As often happened in that time period, his first wife had apparently died young before 1850, making discovery of her family blurred in that time period of invisible women. However, as I spotted in a summary publication of D.A.R. members, this woman's surname was Hardee.

Hardee? In Georgia? How might she fit into the larger picture, and explain Job Tison's connection with the Hardee line—not to mention, tie him back in North Carolina? This woman, Mary Ellis Hardee, was apparently daughter of Thomas Ellis Hardee and his wife, Mary Ann Berrie.

This, though, was merely from a typewritten genealogy, The Hardy-Hardee Family, compiled by David L. Hardy (according to the source for the Ancestry.com collection from which this was drawn; but possibly David Lyddall Hardee, as noted in this manuscript collection). And how often we find errors in such collections.

No matter. Any published or unpublished genealogy can serve as a trailblazer, helping to find otherwise hidden details, if we only take a disciplined approach to verifying—or rejecting with support—the assertions made in the manuscript. That, in fact, is what I'll be doing next week, seeing what assertions can be corroborated in this case with actual documentation. If the genealogy turns out to be accurate, perhaps it will lead us to an explanation of just how our Job Tison was said to have originated in Pitt County, North Carolina, after all.

Catch Them if you Can

 

Perhaps this is just my unlucky day. I was hoping to catch a glimpse of my missing ancestor, Job Tyson, back in what was supposed to be his old stomping grounds. The tip was that he might have been seen in the old Beaufort District of South Carolina, since my attempt at snagging him in Pitt County, North Carolina, had left me empty-handed.

Granted, that last sighting would have been sometime between 1790 and the early years of the 1800s, when Job Tyson settled down in Glynn County, Georgia. But even though I could find mention of someone by that name in North Carolina, the dates and circumstances just didn't line up. I had to follow the lead of some clues, no matter how weak they might have been. When it comes to chasing brick wall ancestors, you try to catch them—wherever—if you can.

First, I tried searching for Job Tyson in Beaufort District, South Carolina. I selected as wide a date range as possible, just in case he needed to return home to clear up any legal business, long after his departure for Georgia. Though I performed my search on the FamilySearch Full Text Search, I found no results.

Yes, I also needed to try my search using the alternate spelling for his surname: Tison. Again, no results.

Then, remembering the disjointed history of the Beaufort District—first it was, then it wasn't, a geopolitical division—I tried changing the label on the specific location to see if I could get any better results. According to one website, the designation of the Beaufort District—actually, all Districts in South Carolina—was abolished in 1800, and replaced by its four underlying counties: Granville, Hilton, Lincoln, and Shrewsbury. 

Back to the Full Text Search I went, this time searching for Job Tyson—or Tison—using each of the four new county designations, just in case. Nothing.

As a last-ditch effort, I also tried searching in each of those South Carolina locations for Charles McClellan, who eventually became a witness to Job Tyson's will in Georgia. Again, nothing.

My only consolation could be that not everyone faithfully remains in the same location for over ten years, so as to ensure their appearance in the subsequent decennial census enumeration. Perhaps our Job Tyson was one of those people, continually on the road until he finally found a place he could call home.

Ancestor Fatigue

 

It's been back to Pitt County, North Carolina, to put FamilySearch's Full Text Search through its paces. Entering my fourth great-grandfather's surname there by each of the two spelling variants—Tison and Tyson—I had plenty of documentation to consider. It looked like Pitt County might be tipping the genealogical scales in its favor with all the records this search for Job Tyson was providing. 

No matter how convenient it might be that FamilySearch's Full Text Search not only highlights my search terms but provides a transcription of the sometimes difficult to read handwriting, reading through court records of any time period can become wearying. In addition, with the Tyson family doing no differently than any affluent southern family of that time period in the 1700s by dealing in enslaved persons, there were several deeds entailing the trading of specific, named human beings. I was reaching ancestor fatigue in my search for Job Tyson's origin.

Then came two documents which were worthy of further consideration. One was an indenture drawn up on February 4, 1790—the same year in which we had found Job Tison listed in the census in South Carolina. The indenture named the two parties: John Tyson of Lincoln in North Carolina, and Job Tison in Pitt County, where the document was recorded. The purpose of the document was to record the exchange of property from John to Job for land on the north side of Black Swamp, for which Job paid what looked like 250 "Spanish mill'd dollars." 

The record noted that the land was originally patented by a man named John May on October 8, 1754, and apparently willed to his daughter, Elizabeth May. While the indenture was drawn up in February, the record noted that it was signed "in April Court" in 1790.

This caught my attention because 1790 was supposedly the year in which Job Tison married Sidnah, daughter of West Sheffield. Perhaps it was time to make arrangements to set up housekeeping.

A second document was of even more interest. Dated November 19, 1785, once again in Pitt County, this record was initiated by John Tison, with his residence this time listed as Pitt County. The record began, "for natural love and affection I have unto my grandson John Tison, son of Job Tison...." 

This line had my attention. Was this John Tison the answer to my research question for this month?

The record went on to detail a specific tract of land, lying on the east side of Black Swamp, originally patented to a Thomas Tison in 1738. The document also mentioned a second tract of land, granted to John Tison by "the Earl Granville."

This record, though drawn up toward the end of 1785, was presented in January Court in 1786. The names of two witnesses also caught my eye: Frederick Tison and Benjamin May. I was beginning to wonder whether names of the Tison collateral lines were unfolding before my eyes with these two documents.

But wait a minute. I had to think this thing over a bit. Maybe this ancestor fatigue was getting to me. It might have been great to discover a record which mentioned Job Tison, the very ancestor I've been looking for, but was it my Job Tison?

Hauling my mind back to reality, I looked up records I already had for Job Tison. Question number one: did my Job Tison have a son named John? And question number two: was he alive by 1786?

While my Job Tison did indeed have a son named John—John Mason Berrien Tison—he was born long after that record was drawn up in court in Pitt County, North Carolina. Indeed, if Job and Sidnah were married about 1790, there would not have been any children of this couple as early as 1785, let alone a grandson old enough to gain his grandfather's favor. 

While these two documents, to bleary, search-wearied eyes, may have seemed tempting, they simply do not work with the scenario already unfolding for the family of the Tison man who spend his adult life in Glynn County, Georgia. Perhaps a better approach would be to repeat the same exercise, only this time focus on the Beaufort District in South Carolina.