Marietta Civil War Battle

1864 map of the Marietta, Georgia vicinity and the surrounding battles
Photo: public domain
During the Atlanta Campaign, Sherman maneuvered Johnston's Confederate army out of several successive defensive positions in Cobb County.
Continued Battle Description and Results
This strategy spared the Union army from making costly frontal attacks on the well-situated Confederates.

Sherman first found Johnston's army entrenched in the Marietta area on June 9. The Confederate's had established defensive lines along Brushy, Pine, and Lost Mountains.

Sherman extended his forces beyond the Confederate lines, causing a partial Rebel withdrawal to another line of positions. After further pressure and skirmishing from Union forces, Johnston withdrew to an arc-shaped position centered on Kennesaw Mountain on June 18 and 19.

Sherman made some unsuccessful attacks on this position but eventually extended the line on his right and forced Johnston to withdrawal from the Marietta area on July 2-3.

Results: Union victory
General Information
BulletLocation: Cobb County
BulletOther Name: Marietta Operations
BulletBattles Associated with the Operations: Brushy Mountain, Gilgal Church, Lost Mountain, Mcaffee's Cross Road, Mud Creek, Neal Dow Station, Noonday Creek, Pine Hill, Pine Mountain, Rottenwood Creek, Ruff's Mill
BulletCampaign: Atlanta Campaign (1864)
BulletDates: June 9-July 3, 1864
BulletPrincipal Commanders: Maj. Gen. William T. Sherman [US]; Gen. Joseph E. Johnston [CS]
BulletForces Engaged: Military Division of the Mississippi [US]; Army of Tennessee [CS]
BulletEstimated Casualties: Unknown
Visiting the Site Today
The maneuvering around Marietta in June 1864 is remembered as much for Sherman's patient flanking as for any single clash, a pattern that repeated across the whole Atlanta Campaign. Marietta's historic square and several nearby Civil War trail markers today trace the Confederate defensive lines Johnston held before withdrawing.

We use cookies to run this site and, with your consent, to measure traffic and site performance. Read our cookie policy.