Showing posts with label casualties. Show all posts
Showing posts with label casualties. Show all posts

Tuesday, August 3, 2010

In Memoriam

From Nicole Belle at Crooks and Liars, the casualty reports from last week, in which we lost 11 service members in Afghanistan:

US Marines LtCol Mario D Carazo, 41, Springfield, OH
US Marines Maj James M Weis, 37, Toms River, NJ
US Army SSG Conrad A Mora, 24, San Diego, CA
US Army SGT Daniel Lim, 23, Cypress, CA
US Army SPC Joseph A Bauer, 27, Cincinnati, OH
US Army SPC Andrew L Hand, 26, Enterprise, AL
US Marines LCpl Frederik E Vazquez, 20, Melrose Park, IL
US Marines Abram L Howard, 21, Williamsport, PA
US Navy PO3 Jarod Newlove, 25, Renton, WA
US Army CPT Jason E Holbrook, 28, Burnet, TX
US Army SSG Kyle R Warren, 28, Manchester, NH

These are real people with real families, and whose loss will be felt forever.  May our leaders somehow see through all the fog and finally have the aha! moment when they realize that there is really no good reason for our continued combat presence in that country.

And as for these unlucky souls, may they rest in peace.

Wednesday, May 26, 2010

Death Hits Close to Home: RIP Army SSG Richard J. Tieman


Army SSG Richard J. Tieman (photo credit here)

Nicole Belle at Crooks and Liars has posted last week's casualties, based upon a Pentagon release of the names of eleven service members killed in Afghanistan:

US Navy PO3 Zarian Wood, 29, Houston, TX US Marines
CPL Nicholas D Parada Rodriguez, 29, Stafford, VA
US Marines SSGT Adam L Perkins, 27, Antelope, CA
US Army COL John M McHugh, 46, New Jersey
US Army LTC Paul R Bartz, 43, Waterloo, WI
US Army LTC Thomas P Belkofer, 44, Perrysburg, OH
US Army SSG Richard J. Tieman, 28, Waynesboro, PA
US Army SPC Joshua A Tomlinson, 24, Dubberly, LA
US Marines LCPL Patrick Xavier Jr, 24, Pembroke Pines, FL
US Army SSG Shane S Barnard, 38, De Smet, SD
US Army PFC Billy G Anderson, 20, Alexandria, TN

According to iCasualties, the total number of allied service members killed in Iraq is 4,717; in Afghanistan, 1,783. During this same period, Iraq Body Count lists 78 Iraqi civilian deaths. The Army announced this week that they would launch an investigation into the illegal deaths of Afghan civilians.

The 7th name on the list strikes home: Army SSG Richard J. Tieman, 28, Waynesboro, PA. He was from a community just a few miles away.  I did not know him personally, but his death will leave a hole in his family that can never be filled.

While I continue to strongly feel that continuing the Afghanistan venture is ill-advised and basically a no-win situation, I applaud the sacrifices made by all service members, who can take satisfaction from the fact that they are doing their duty to the best of their abilities. We have a seemingly endless war, coming with a blank check (i.e., no estimate as to costs), no success criteria, and no discernable exit strategy.

Richard Tieman deserves better.

Thursday, May 20, 2010

The 1861 Battle of Falling Waters

 (Engraving from The Illustrated London News, image credit here)


Henry Kyd Douglas, from I Rode With Stonewall:

It was only a little "affair at Falling Waters," as General Johnston called it, and few were hurt. To me it was of memorable importance; for there for the first time I heard the whiz of a musket ball and the shriek of a cannon shot....Nothing came of it, but the war had made a beginning.

This post will pull together some American Civil war history, some Chesapeake and Ohio Canal history, some of course some ultrarunning. Please read on....

One of my favorite places to run long is the C + O Canal, which now is a National Park along the Potomac River in Maryland and the District of Columbia.

In the 1830s, in an idea that dated back to George Washington, since the Potomac River was not navigable, why not dig a canal immediately beside it, control the water levels thru a brilliantly engineered series of dams and locks, and use it to float boats for heavy hauling? So eventually it was done, accomplished over several decades...but ultimately doomed in the 1920s by the increasing dominance of the railroad.

What remains today is a 185 mile long woody corridor right along the Potomac, complete with historical locks, dams, and structures, preserved via the National Park designation. While the canal bed itself is largely overgrown with trees, there are a couple of sections that have been rewatered to show the canal as it once was 150+ years ago.

The main draw for a runner, though, is the so-called "towpath," the dirt road beside the canal bed where the mules once walked to pull canal barges. It's a perfect running surface, a double-track dirt or fine gravel road, and with enough trees in the summer to provide 99% shade and in the winter to provide a decent windbreak. The JFK 50 Miler uses some 26 miles of the canal towpath as part of its route.

I love running along the C + O Canal and always look forward eagerly to logging some miles. One of my favorite routes is to run downstream of Williamsport (the closest access point for me by car, only 30 minutes from my home). About 5 miles downstream is a locale called Falling Waters, after the stream on the West Virginia side that empties into the Potomac. 

So, to keep the geography straight, I'm running on the north, or Maryland, side, where the C + O Canal is, and the 1861 action in question--called the Battle of Falling Waters--took place across the river on the West Virginia side.  Of course, in 1861, it was all Virginia--Unionist western Virginia had not yet been peeled off into the state of West Virginia.  It is this 1861 battle that I wish to focus on.  It actually took place some 5 miles or so south of the river.

(NOTE:  don't get this Battle of Falling Waters (West Virginia in 1861) confused with the 1863 Battle of Falling Waters Road (on the Maryland side of the river), which is better known due to its connection to the Confederate retreat from Gettysburg.  I will post something on that 1863 action tomorrow).

Back to 1861 and what happened.  From the Civil War News website:

Falling Waters was the first Civil War engagement in the Shenandoah Valley, fought on July 2, 1861, approximately five miles south of the Potomac River in what is now West Virginia. The majority of the fighting was around the Porterfield House, a large log structure built by the grandfather of the Alamo's Davy Crockett.

This battle, actually little more than a skirmish by later standards, was quickly overshadowed by the Battle of Manassas (Bull Run) less than three weeks later.

Although generally known, both now and during the war, as Falling Waters, this little battle was given a number of names, which has helped to keep it obscure. Of course the use of different conventions by the North and South to name battles is a lot of the issue.

For example the Confederate rank and file frequently called the battle "Hainesville" after the last village they passed through as they marched toward the engagement. The Harper's Weekly correspondent called it "Hoke's Run," referring to the first water Federal troops encountered after the fight as they pursued the withdrawing Confederates.

Falling Waters, a tiny hamlet not far north of the site and containing a small waterfall, conveniently met both naming criteria.

This winter, with the leaves off the trees, I finally got a real good look across the river from MD to WV and was able to see this tributary stream, and just smiled to myself, thinking, "So that's why this place is called Falling Waters!"

Also this winter I was re-reading Henry Kyd Douglas' I Rode With Stonewall. Douglas was a Confederate officer on General Stonewall Jackson's staff, whose memoirs remained undiscovered until the 1940s, when their publication created quite a stir among Civil War historians.  Let me repeat my lead-in to this post.  Writing in his first chapter of the "Affair at Falling Waters," here's what Douglas says about the 1861 action, and I've highlighted what piqued my interest:

It was only a little "affair at Falling Waters," as General Johnston called it, and few were hurt. To me it was of memorable importance; for there for the first time I heard the whiz of a musket ball and the shriek of a cannon shot....Nothing came of it, but the war had made a beginning.
I guess I'm struck by the fact that while Douglas (understandably) referred to the numbers as "few," if you were one of the few, the life changing effect of being shot (if you survived) would certainly give you quite a different perspective.

So I surfed the net eagerly, looking for what was meant by "few were hurt." I found limited and inconsistent data, but in the course of my research I had the wonderful good fortune to connect with Gary Gimbel, a local historian, one of whose passions is the 1861 Battle of Falling Waters (the Falling Waters Battlefield Association info is here).

In a marvelous coincidence, Gary G wrote back to say: "It is ironic that one of my current projects is trying to determine not just the exact number of casualties, but actually the names of the soldiers on both sides who were killed, wounded, captured or missing." He was unhesitatingly willing to share his data with a fellow researcher, and went on to provide the following information:

I don't (yet) have a polished, footnoted document to send you listing the July 2, 1861 casualties. However I will give you a summary of what I know at this time. It is quite different than what you find on the internet and in the claims by both sides at the time. I have documentation on these figures and in most cases even the soldiers' names.

Union:
   Killed 3
   Wounded 18 (one of these mortally, dying at the end of August)
   Captured 49

Confederate:
   Killed 2
   Wounded 14
   Captured/Missing 9

It is very likely that some (1 to 3 possibly) of the missing Confederates were left on the field dead (even Jackson admitted that in a letter to his wife). Some were definitely captured and I would guess there were some desertions at that point too. The grand total of all Confederate casualties is 25 and is confirmed in a number of sources.

Please note that frequently [Confederate cavalry leader J. E. B.] Stuart gets credit for all 49 Union soldiers captured and that they were all from the 15th Pennsylvania. That is not the case. One of the biggest problems I have in putting this list together are aging veterans (both north and south) claiming in newspaper articles that they received a wound at Falling Waters that wasn't reported at the time.
So, some 149 years ago, on that summer day back in 1861, when the American Civil War was new, exciting, and still a grand adventure, some 37 or more men were shot by musket ball or artillery. 37 human beings (the so-called "few" who were hurt) underwent a life changing experience. War surely did not seem so glorious when you were on the receiving end of a projectile tearing through your flesh at high speed.

Historians, and those who read histories, sometimes tend to think of history in terms of the grand overview of events.  However, to me real history is comprised of those personal events that were actually lived by the participants.  I always try to remember that the people written of in histories were as real as you and me.

Wednesday, May 12, 2010

The Cost of Iraq

In my reading I've come across two reckonings of the cost of Iraq, the first at the macro scale, and the second at the micro (human impact) level.

1. The macro view...
 In a post by Matt Yglesias, he discusses an effort to "...tally up the full cost of Iraq—human, financial, and strategic—and discover that the price was very, very, very high."

We certainly have paid a severe price, squandering our nation's blood, treasure, and international moral authority.

Matt's link is to The Center for American Progress, here. From that Center for American Progress post, I found this quote to be most germane.

But when weighing those possible benefits against the costs of the Iraq intervention, there is simply no conceivable calculus by which Operation Iraqi Freedom can be judged to have been a successful or worthwhile policy. The war was intended to show the extent of America’s power. It succeeded only in showing its limits.

2. The micro view....

Per Nicole Belle at Crooks and Liars, in her regular weekly feature, the U.S. last week lost nine service members killed in Iraq and Afghanistan (I also linked to her a week ago, here)

US Army 1LT Salvatore S Corma, 24, Wenonah, NJ
US Army SGT Anthony O Magee, 29, Hattiesburg, MI
US Air Force A1C Austin H Gates Benson, 19, Hellertown, PA
US Army SGT Ralph Mena, 27, Hutchinson, KS
US Army MSG Mark W Coleman, 40, Centerville, WA
US Marines 1st Lt Brandon A Barrett, 27, Marion, IN
US Army SPC Eric M Finniginam, 26, Colonia, FM
US Army SPC Wade A Slack, 21, Waterville, ME
US Marines LCpl Richard R Penny, 21, Fayetteville, AR

According to iCasualties, the total number of service members killed in Iraq is 4,715; in Afghanistan, 1,752. During this same period, Iraq Body Count lists 40 Iraqi civilians killed.

Tuesday, May 4, 2010

7 Service Members Killed Last Week

Over at the political blog Crooks and Liars, a regular--and sobering--weekly feature is called This Week in Memoriam.

Sunday's post, here, by Nicole Belle, lists the 7 service members who were killed in Iraq and Afghanistan this past week. You should head over there to see Nicole's post because she has clickable links to each of the dead, often with a photograph.

It is good for us to gaze at the images of the dead, for they died on our behalf.


US Army SSG Christopher D Worrell, 35, Virginia Beach, VA
US Army SGT, 21, Ronald A Kubik, Brielle, NJ
US Army SGT Jason A Santora, 25, Farmingville, NY
US Marines LCpl Thomas E Rivers Jr, 22, Birmingham, AL
US Army SGT Grant A Wichmann, 27, Golden, CO
US Army SGT Keith A Coe, 30, Auburndale, FL
US Army SGT Nathan P Kennedy, 24, Claysville, PA

According to iCasualties, this brings the total number of allied service members killed in Iraq to 4,712; in Afghanistan, 1,741.

Christopher Worrell leaves his wife, Katrina, and four children ages 7 months to 6 years; Ronald Kubik was on his third deployment, and is survived by parents and two sisters; Jason Santora was on his fourth deployment, survived by parents and a sister; Thomas Rivers wanted to be a Marine all his life; Grant Wichmann died from wounds he suffered last month in Afghanistan; Keith Coe is survived by his wife, two sons, and a daughter; Nathan Kennedy, who was due to come home is less than a month, is survived by his father, two sisters and a brother.

The facts I teased out of the stories don’t come close to capturing the anguish that their families feel. Seven families ripped asunder. Seven families whose lives will NEVER be the same. Seven families whose loved one died for a cause whose origins are suspect and whose continuation is of dubious merit.

These families likely will project a stiff upper lip and assert that their loved one died in the cause of freedom, because to say that they died is vain is just too terrible to contemplate....but I am convinced that 50 years from now historians will be shaking their heads and asking, "What on earth was the United States thinking?"

I know that I could not look these families in the eye and tell them that their loved one's service and sacrifice was worth it.  The satisfaction will have to come from the fact that they did their duty. Stonewall Jackson, the Confederate general and fervently devout Christian, once commented on reconciling military service with his Christian beliefs.

One of his sayings (that may not have originated with him) was:

Duty is ours; consequences are God's.

Rest in peace.



Photo credit here, of the return of Keith A. Coe's remains and his family