Orange County, North Carolina GenealogyEdit This Page

From FamilySearch Wiki

Revision as of 18:21, 28 March 2012 by Jaburgess (Talk | contribs)


Orange County, North Carolina
Map
Map of North Carolina highlighting Orange County
Location in the state of North Carolina
Map of the U.S. highlighting North Carolina
Location of North Carolina in the U.S.
Facts
Founded 1752
County Seat Hillsborough
Courthouse
Adopt-a-wiki page
Logonew small.gif This page adopted by:
NCGenWeb Project
who welcome you to contribute.
County Coordinator
Orange Co. NCGenWeb
Adopt a page today

United States  Gotoarrow.png  North Carolina  Gotoarrow.png  Orange County

Contents

County Courthouse

Orange County North Carolina
200 S Cameron St
Hillsborough, NC 27278
919-245-2675

Courthouse burned 1789
Reg of Deeds has B & D rec from 1913
m & land rec from 1754, div rec from 1869
pro rec from 1756 & ct rec from 1865

Orange county created from Bladen,
Granville, Johnson 31 Mar 1752

History

Parent County

1752--Orange County was created from Bladen, Granville and Johnston Counties.
County seat: Hillsborough [1]

Boundary Changes

Record Loss

Places/Localities

Populated Places

Neighboring Counties

Resources

Cemeteries

Church

Court

Family Histories

  • [Clendenin] White, Jo White. "Clendenin of Orange County, North Carolina: An Exercise in Southern Genealogical Problem Solving," The Genealogist, Vol. 6, No. 2 (Fall 1985):186-190.

Land

Local Histories

Maps

Military

Civil War

Civil War Confederate units - Brief history, counties where recruited, etc.

-1st Regiment, North Carolina Infantry, usually known as the Bethel Regiment.
-1st Regiment, North Carolina Infantry
-6th Regiment, North Carolina Infantry
-11th Regiment, North Carolina Infantry

Newspapers

Probate

Taxation

Vital Records

Yearbooks

Societies and Libraries 

Family History Centers

Web Sites

References

  1. The Handybook for Genealogists: United States of America,10th ed. (Draper, UT:Everton Publishers, 2002).

 

Need wiki, indexing, or website help? Contact our product teams.


Did you find this article helpful?

You're invited to explain your rating on the discussion page (you must be signed in).