The following information was assembled from numerous sources and cannot be used directly as proof of Qualifying Service or Lineage.
It is considered a research aid and is intended to assist in locating sources that can be used as proof.
Author: Paul Cashion
Joshua Jones was born in Albemarle County Virginia circa 1748 and lived around the "Pritties Creek" area. Between 1777 and 1778 Joshua along with his wife Elender and their children moved from Virginia to Burke County, North Carolina. In April 1779 Joshua entered into a land grant for 200 acres on Gunpowder Creek located in Burke County. After living a few years in Burke County Joshua along with family moved to Wilkes County, NC. Joshua entered a land grant for 100 acres on the Middle Fork of Kings Creek area in 1781 where he signed another Oath of Allegiance. Joshua continued living in Wilkes County until the late 1790's. in 1786 he was listed on the Wilkes County, NC Tax List in Captain Ferguson's District. Research shows that Joshua came down from Wilkes County to fight the British during the Battle of Kings Mountain. In Pat Alderman's book, "The Overmountain Men" Joshua is shown as wounded in the battle. After the Revolutionary War, Joshua and his growing family moved to Buncombe County, North Carolina. His first land entry was 22 October 1803 where he purchased 300 acres. This land ran into the French Broad River and Hominy Creek which was perfect for farming. In 1810, he purchased an additional 300 acres that joined his property and in 1819 added an additional 320 acres. This is where Joshua would spend the remainder of his life farming and spending time and precious moments with family and friends. Joshua and his wife Elender still lay at rest on this beautiful land that they once called home. Joshua and his wife died circa 1839 and are buried in the Jones Burying Ground located on a knoll above Long Branch and the French Broad River. Joshua and Elender had 9 children and numerous grandchildren and their property became part of the Biltmore Estates in the late 1800's. Joshua and Elender's legacy will continue to be remembered through generations of family members that cherish their memories, traditions, and understand the sacrifices and struggles they encountered and endured to make us who we are today. Even today, their land remains a part of history that both current and future generations will explore and enjoy and make new memories of their own. They will also be able to observe the scenic beautiful mountain views that brought Joshua and Elender here over 200 years ago.
Send a biographical sketch of your patriot!
Patriot biographies must be the original work of the author, and work submitted must not belong to another person or group, in observance with copyright law. Patriot biographies are to be written in complete sentences, follow the established rules of grammar, syntax and punctuation, be free of typographical errors, and follow a narrative format. The narrative should unfold in a logical manner (e.g. the narrative does not jump from time period to time period) or have repeated digressions, or tell the history of the patriot's line from the patriot ancestor to the author. The thinking here is that this is a patriot biography, not a lineage report or a kinship determination project or other report published in a genealogy journal. The biography should discuss the qualifying service (military, patriotic, civil) of the patriot ancestor, where the service was rendered, whether this was a specific state or Continental service, as well as significant events (as determined by the author) of the patriot's life. This is the entire purpose of a patriot's biography.
Additional guidelines around the Biography writeup can be found here:
Send your submission1, in a Microsoft Word compatible format, to patriotbios@sar.org for inclusion in this space 1Upon submission of a patriot biography, the patriot biography becomes the property of the National Society of the Sons of the American Revolution, and may be edited to conform to the patriot biography submission standards.