Muster Roll helps readers find Civil War soldier and unit entries. Battles adds engagement context, and the 384 Battles Index organizes principal battles chronologically. Together they provide research leads. A matching surname or a regiment’s battle list does not prove a family connection or an individual soldier’s presence.
Key facts
- Muster Roll draws from the NPS Soldiers and Sailors System.
- Battles supplies engagement context and available unit information.
- The website index covers 384 principal battles, not every encounter.
A reader once typed her own last name into a search box on my website. Thirty seconds later she read six words that changed how she saw her family. Her great-great-grandfather earned the Medal of Honor.
That is the kind of moment I built these tools for. I write novels about the Civil War, and somewhere along the way I started building software too. It began with a simple question. Readers of Cadets to Captains kept asking if their own ancestors fought in the battles I described. I could not answer quickly. So I built a way to find out.
What can Muster Roll tell you?
The first tool is called Muster Roll. It draws from the National Park Service’s Civil War Soldiers and Sailors System. That public database covers both Union and Confederate service. Type a surname into the search box, and the app returns every soldier who carried that name.
Each result goes further than a bare list. The app resolves the soldier’s unit code into a readable name, like “18th Regiment, Virginia Infantry.” It shows the branch of service, infantry, cavalry, artillery, or one of several others. It shows rank at enlistment and rank at discharge, and flags a promotion when the record shows one. Where a unit fought, the app lists the battles by name and links each one to its full record.
None of that data invents anything. The National Park Service describes its own records as “just an index,” with sparse detail for enlisted men. No birth date. No hometown. I built the app to show readers everything the source holds, and nothing it does not.
The reader I mentioned above is one story among many. She found several ancestors in the database that day, all connected, all real people who marched into real battles. A name on a page is not the same as a name in your own family. When the two meet, something shifts. She now has a unit reference and a list of its battles to investigate. Individual participation requires further evidence. She found that in under a minute.
Battles: What Happened, Where, and Why It Mattered
The second app, Battles, works from the opposite direction. Instead of tracing a soldier, it maps a fight.
Search for a battle by name and the app opens a detail page. It shows the date, location, and commanding generals. Troop strength appears where the record allows it, along with a short account of the day. For the battles tied to my novels, readers can see the exact regiments my characters stood beside in the story.
The order of battle is the part that took the longest. Union rosters are well documented. Confederate rosters, especially for smaller engagements, scatter across dozens of sources that do not always agree with each other. I built the Confederate order of battle one engagement at a time. I checked each unit’s participation against multiple accounts. I left a battle blank rather than guess when the sources ran dry.
Ten battles in the database show no Confederate units at all. That is correct, not a gap. No Confederate forces fought in those engagements. The app now says so plainly instead of showing a confusing empty page.
That kind of care is slow work. It is also the only way I know to keep the history honest. A reader checking a battle in the app gets the same answer a historian gets from the Official Records.
How does the Battle Index help you browse?
The newest piece is smaller than the other two, and it exists for a simple reason. Not every reader wants to search. Some want to browse.
The Battle Index lists 384 principal Civil War battles in chronological order. It runs from Fort Sumter in April 1861 to Palmito Ranch in May 1865. A reader can scroll the whole war on one page, or filter it down to a single state or year. Some battles carried two names, one used by the Union and one by the Confederacy, like Bull Run and Manassas. The index shows both names where they exist, as with Antietam and Sharpsburg. Most battles never carried a second name, and the page says that plainly instead of pretending otherwise.
The index is meant to sit next to the other two tools as a starting point. A reader who does not know what to search for yet can open the index. From there, they can find a battle near their home state and follow the link into the full record.
Try It Yourself
Search your own surname in Muster Roll right now. It takes less than a minute, and you might turn up your own six-word moment, the way that reader did. If a name catches your eye, confirm the soldier’s identity, then open Battles to investigate engagements involving the unit.
Search Muster Roll: https://www.google.com/url?q=https://bit.ly/tfo-muster-roll-app&source=gmail&ust=1786304062526000&sa=E
Search Battles: https://www.google.com/url?q=https://bit.ly/tfo-battles-app&source=gmail&ust=1786304062526000&sa=E
Browse the 384 Battles Index.
Read the Series
These tools grew out of the Steel and Honor series. The series follows two West Point cadets, one bound for the Union and one for the Confederacy. It traces them from their cadet years into the war that split the country.
Book One, Cadets to Captains: 1848-1860:
Paperback: https://www.google.com/url?q=https://bit.ly/tfo-c2c-paperback&source=gmail&ust=1786304062526000&sa=E
Hardcover: https://www.google.com/url?q=https://bit.ly/tfo-c2c-hardcover&source=gmail&ust=1786304062526000&sa=E
Book Two, Antietam: From Secession to the Bloodiest Day, is published. Explore its formats and reading preview.
Coming soon, Book Three, Gettysburg and Vicksburg: Summer of Decision, the next chapter in the McAllister and Tanner story.
What Should I Build Next?
I keep a running list of what to add. A map view that plots each battle by location sits near the top of that list. So does a way to chain related battles into a single campaign. That would let a reader follow the Overland Campaign or the fall of Vicksburg one fight at a time. No one would lose the thread. Both ideas came from watching how readers already use the tools, not from a plan I set at the start.
If you use Muster Roll or Battles and think of a feature that would help, tell me about it. I read every message. I am always glad to hear a good idea for where to take these tools next.
More from the series: https://www.google.com/url?q=https://tomfoconnor3.com&source=gmail&ust=1786304062526000&sa=E
Frequently asked questions
What does Muster Roll search?
It searches soldier entries drawn from the National Park Service’s Civil War Soldiers and Sailors System.
How does Battles differ from Muster Roll?
Muster Roll begins with a soldier’s name. Battles begins with an engagement and its historical context.
Does a unit battle list prove my ancestor was present?
No. Confirm identity and compare individual service dates, duty status, and additional evidence with the unit’s movements.
Comments
Trackback: Homepage
lauren webbefy
Yes this is true
William Read Gilmore
Tom, this is an amazing piece of work.
I have been researching my Civil War ancestors for over a decade. I entered my great grandfather’s name – Lewis Read – in the Muster Search and he popped up as a Private in Company F, 14th Virginia.
That is correct. He and his younger brother, Stephen P. Read, were members of a militia company, the “Chambliss Grays” of the 98th Militia Regiment in Mecklenburg County, Virginia. That unit became Company F of the 14th Virginia.
I have a couple of suggestions. I would stress that the information you are offering in the Muster file should be a starting point. Soldiers sometimes changed units. A shortcoming in the NPS list (which is very useful) is that it only shows that first unit. I would love to get your Battle list in chronological order.
On Fold3 (likely available for free at a local library) you may be able to get a soldier’s monthly muster report, transcribed (sometimes with errors) on those Compiled Military Service Record (CMSR) index cards. The 14th Virginia’s are available through the September-October 1864 period and I’ve been able to reconstruct the roster of that company.
The list of battles shows ones that the unit was in, and not necessarily the soldier. It’s hard to verify that a soldier actually participated in a battle. Company F never reached the “drill manual” strength of 100 men for an infantry company. When the May-June 1862 muster was taken on the Charles City Road on the way to Malvern Hill, there were 74 officers and men on the books and only 48 in the ranks.
The only way you can definitively establish that a relative was in a certain battle is through personal recollections (which can be spurious) and casualty records. Even if a soldier is shown as “Present” on the CMSR card for the period before a battle, you still can’t be sure that he wasn’t detailed, injured, got sick, or straggled before the battle. Even the June 30, 1863 muster roll in Chambersburg, PA doesn’t prove that a Confederate relative stepped off in “Pickett’s Charge.”
The list of battles that popped up with Lewis Read for the 14th Virginia is incomplete. The list starts with Seven Pines. Lewis was home in Mecklenburg County on sick furlough for that battle and Malvern Hill. His little brother had been elected 2LT and was on detail as the regimental commissary officer. Whether 2LT Stephen Read left the commissary wagon and went into the fight, I do not know.
The 14th Virginia was in Armistead’s Brigade. They were in Huger’s Division for the Seven Days, and may have seen some action before Malvern Hill. Huger and Magruder were left in the trenches before Richmond and McClellan did probe them. I would agree that “The Battle of the Axes” at Glendale does not warrant an inscription on the 14th Virginia’s battle flag; Huger did not make it into the fight.
The battle list doesn’t include Second Manassas, although Anderson’s Division (R.H. Anderson took over from Huger) was Longstreet’s reserve and was not decisively engaged. At Antietam, Armistead’s Brigade may well have been the only Confederate Brigade that was not decisively engaged. The rest of Anderson’s Division was sent to the Sunken Road, but Armistead’s men were peeled off and sent over to the left near the Dunker Church. One of the few casualties suffered by the Brigade that day was Gen. Armistead, who was hit in the leg by a bouncing cannonball. Col. Hodges of the 14th Virginia took command of the brigade and reported to Gen. Early just after the final Union charge had been repelled.
Armistead’s Brigade was part of the infantry support for Pendleton’s disastrous action at Shepherdstown as Lee crossed back over into Virginia. That was the only action in which my Confederate relatives may have exchanged fire – across the Potomac — with the one Yankee relative I can identify. Archibald Gilmore, a great uncle and Scotch-Irish immigrant, joined the 5th NY Zouaves just three days after that unit was cut to ribbons on Chinn Ridge at Second Manassas.
My Read GGF may have been at Antietam and Shepherdstown, since he was mustered on the Second Manassas battlefield on August 31. But Armistead’s Brigade suffered a significant amount of straggling. 2LT Stephen Read was commanding the company – the CO and 1LT fell out sick at Leesburg before they crossed over into Maryland – so I’d like to think Lewis gutted it out and stayed with his brother and the company. But I don’t really know.
The 14th Virginia missed Chancellorsville. They were involved in the fighting around Suffolk with Longstreet.
And obviously, Armistead’s Brigade and the 14th Virginia were at Gettysburg. However, my GGF was not with them anymore. I don’t know whether he got tired of taking orders from his little brother or just got tired of walking, but in January 1863, he furnished a substitute – who promptly deserted – and took JEB Stuart’s advice and “Jined the Cavalry.” So, if he was at Gettysburg, it was with Company A, 3rd Virginia Cavalry.
To my surprise and disappointment, that unit kept very poor records. I’d like to be able to say that my GGF was at “Custer’s First Last Stand” at Trevillian Station, but I can’t document Lewis Read’s activities in the cavalry. His pension application does say that he brought two good horses to the War, which suggests that he saw some action.
Armistead’s Brigade, now commanded by Seth Barton, was involved in the abortive attempt to retake New Bern in early February 1864. Barton’s performance was criticized because he refused to replicate the Union Army’s experience at Burnside’s Bridge at Antietam. Sent on a wide flanking movement to get behind and cut off New Bern from the coast, he found a flooded creek covered by a blockhouse and decided not to attack. Pickett – and Lee – thought he should have made the effort. For my cousins on 2LT Read’s side of the family, I’m glad he didn’t.
Barton’s unfair treatment after New Bern somewhat dimmed my admiration for Lee. He did sometimes have a temper. And he approval a bizarrely complicated battle plan put forward by young Gen. Hoke of North Carolina (I strongly suspect there was a political aspect to the 1864 attempt to retake New Burn; the authorities in Richmond needed to mollify the North Carolinians.).
Company F also fought at Chester Station, which happened right before Proctor’s Creek. At Proctor’s Creek, the CO of Company F was killed and Stephen Read became the CO. They were subsequently involved with fighting along the Howlett Line during the siege of Petersburg. Not really a battle, but men were killed just as dead skirmishing on the Howlett Line as the ones who fell at Malvern Hill and Gettysburg. BTW, the Confederate OOB at Proctor’s Creek does not include Armistead’s old brigade, now under Col. Birkett Fry after Seth Barton was unjustly relieved at Chester Station.
My bottom line on your Muster app is that I would encourage folks to use it as a starting point. But they should dig deeper.
Your list of battles is great, but I’m still learning to navigate it. It would be helpful not to have to enter my name and email address every time I use it. The write ups of the individual battles are impressive and the inclusion of the OOB and brief commentary is helpful. It would be greatly improved if it was in chronological order. To understand my relatives’ wartime experiences, I want to know what news they were getting. The ebb and flow of the tides of war had to have an impact on morale.
For example, in late October, 1862, there was a small but decisive Confederate victory at Ball’s Bluff (which, because of its political ramifications, I like to tell people was the most important Civil War battle most Americans have never heard of). While the stunning victory may have raised morale, for my Read relatives guarding the guns along the James under Magruder, there was a major burr under the saddle.
In their sixth month in the Army, the Read boys had yet to fire their muskets in anger. A Mecklenburg County civilian, a rich neighbor whose widowed mother owned a very large plantation with 115 slaves, was mentioned in the Ball’s Bluff after-action report of the cavalry commander. The Read boys, from a modest farm family with eight slaves (four adults), had joined the Army and put up with bad food, bad water, constant drill, manual labor (they dug the Square Redoubt at Jamestown), boredom, sickness and the death of friends (typhoid was rampant). R.L. Hendrick (who is also a relative on my father’s side), continued to enjoy civilian life. He left Mecklenburg County down on the North Carolina border and showed up in Loudon County on the Potomac across from Maryland in time to win laurels for participating in one cavalry charge. While I have no account of how Lewis and Stephen took the news, I imagine they were frosted. I certainly would have been.
As an aside – and evidence of the need to keep digging to learn about your relatives – a distant cousin sent me a copy of a letter written in 1862 that explained why Robert L. Hendrick was up in Leesburg in October. He was getting married. The fact that this rich civilian was “mentioned in dispatches” and then went on a honeymoon REALLY had to tick the Read boys off.
You have clearly done a lot of work and I encourage you to keep refining it. There always seems to be more to add. For example, the technology section for Ball’s Bluff – which I think is a great idea – doesn’t mention a Union innovation that presages WWI technology. Union forces along much of the front strung telegraph wire as tanglefoot which, aided by thick fog, broke up the attacking Confederate formations.
I look forward to seeing what else you do with this.
Tom
Thank you for your kind comments.
Tom O’Connor ‘73
Trackback: ไวอากร้าไทย
lauren webbefy
William,
Thank you for the detailed walk through of the Read boys. I enjoyed your narrative. I am glad to hear you found them right away.
I agree I should add a disclaimer that this app should be used primarily as a starting point. I will try to figure out how to update the app so it doesn’t require your information each time you log in. Right now the option is to create a pay wall. I want to keep the app free.
The information for the soldiers comes from the National Park Services (NPS) Civil War records. Unfortunately, the Confederate records are not complete. The Confederate government burned many of the personel records before they left Richmond in early April 1865. If you have been working on this for ten plus years, I am sure you already were aware of this issue.
If you see any other issues I should address, please contact me again.
Topm O’Connor ’73