Battle of Proctor's Creek

The Battle of Proctor's Creek, also known as Drewry's Bluff or Fort Darling, was fought May 12–16, 1864, in Chesterfield County, Virginia, during the Bermuda Hundred Campaign of the American Civil War. Proctor's Creek was named for Charles Proctor, who lived and farmed on the land surrounding most of the creek.

Battle of Proctor's Creek
Part of the American Civil War
DateMay 12, 1864 (1864-05-12) – May 16, 1864 (1864-05-16)
Location
Chesterfield County, Virginia
Result Confederate victory
Belligerents
United States (Union) CSA (Confederacy)
Commanders and leaders
Benjamin F. Butler P. G. T. Beauregard
Strength
30,000 [1] 18,000 [1]
Casualties and losses
6,600 [1]

Battle
Map of Proctor's Creek Battlefield core and study areas by the American Battlefield Protection Program.

After his repulse at Swift Creek and Fort Clifton on May 9, Union Maj. Gen. Benjamin Butler withdrew into his entrenchments at Bermuda Hundred. A Confederate army of 18,000 was patched together under command of Gen. P.G.T. Beauregard to confront Butler's 30,000. On May 12, Butler moved north against the Confederate line at Drewry's Bluff, but again adopted a defensive posture when his attack was not supported by gunboats. On May 13, a Union column struck the right flank of the Confederate line at the Wooldridge House, carrying a line of works. Butler remained cautious, however, giving Beauregard time to concentrate his forces. On May 16 at dawn, Maj. Gen. Robert Ransom's Confederate division opened an attack on Butler's right flank, routing many units. Subsequent attacks lost direction in the fog, but the Federals were disorganized and demoralized. After severe fighting, Butler extricated himself from battle, withdrawing again to his Bermuda Hundred Line.

Aftermath

There were about 6,600 total casualties. This battle stopped Butler's offensive against Richmond.

The battlefield is now part of the Richmond National Battlefield Park.

gollark: Unlikely, even the voice audiosource bit is synchronous.
gollark: I have various choices:- copy-paste internal API code, make async, use- reimplement internal API asynchronously (unlikely)- make it somehow wait for the asynchronous thing synchronously?
gollark: Oh dear, I think this is some undocumented internal API. It's not even async.
gollark: Why does discord.py contain its own OGG parser? I mean, it's helpful, but still.
gollark: So now it's working without buffering *but* using 11% of my CPU and still entirely launched by running a bunch of ++magic commands.

References
  1. National Park Service battle description



This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.