ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel
  • »
  • Education and Science»
  • History & Archaeology»
  • History of the Americas

Largest Mass Execution in U.S. History, Mankato, MN. 1862

Updated on December 22, 2012

The Hangings at Mankato

The hanging of 38 Santee Sioux Indian men at Mankato, Minnesota, on December 26th 1862 became the largest mass execution in the United States on record. It also became an indelible mark of shame and a copious stain in American History.

Governor Alexander Ramsey’s statement on September 9th of 1862 reflects how the Sioux were viewed by white Americans at the time. "The Sioux Indians of Minnesota must be exterminated or driven forever beyond the borders of the state." Ramsey later placed bounties on their scalps and sent expeditions into Dakota Territory to hunt them down.

However, the story actually begins before their surrender at the end of the short lived U. S. Dakota War of 1862. It was preceded by a number of violent incidents. On August 17th, four starving young Dakota warriors were hunting for food in Action Township.

During that hunt one stole a few eggs and killed five white settlers. Their leader, Chief Little Crow, decided to continue attacks to drive out the whites because of their failure to keep their promises and inhumane treatment they had received at their hands.

The next day he led a group that attacked the Lower Sioux, or Redwood, Agency where Andrew Myrick, the representative of the government traders was one of those killed. The Dakota continued their attacks by storming the settlement of New Ulm on August 19th, and again the following day. At first the war party had decided not to attack Fort Ridgely and instead hit the town of New Ulm, killing settlers along the way. However, defenders of the town, having gotten word of the uprising had fortified their town with barricades and managed to hold their attackers at bay. Though, the Indians managed to breech a few points and burn much of the town.

With this building their confidence they turned to the Fort which they assaulted on August 20th and 22nd. Although, not able to take the fort, they were able to ambush a relief party, raid farms and other settlements throughout south central Minnesota and eastern Dakota Territory.

American forces suffered a major defeat at the Battle of Birch Coulee on September 2nd when Dakota warriors attacked a detachment of 150 American soldiers during a three hour early morning clash, about 16 miles from Fort Ridgely.

After the assault, 13 soldiers had been killed and 47 others wounded. The Dakota suffered only two casualties. Upon hearing about the battle, the commander at Fort Ridgely immediately sent 240 soldiers to relieve the battered detachment at Birch Coulee. Between late August and September, the Dakota continued with several failed attacks on Fort Abercrombie. Most Dakota fighters surrendered shortly after the Battle of Wood Lake at Camp Release, September 26th.

Surely, they would be treated humanely as prisoners of war. However, once again, the U.S. Government failed to honor its treaties with the Indian Nations who had already turned over a million acres of their land…for which they were never paid.

Although the U.S. Government may have thought the Indians had been paid, in actuality the money they were promised mostly ended up lining the pockets of unscrupulous Indian agents and private contractors, their food sold to white settlers. They were given the spoiled and rotten leftovers to eat and treated worse than dogs.

Lincoln's Order Authorizing Execution of 39 Men
Lincoln's Order Authorizing Execution of 39 Men

The price they were to receive for their lands was also far below what the government had paid for other land of similar value. In light of their appalling and unspeakable living conditions, they were forced to send hunting parties off their reservation to find food. And for this, they were branded war criminals.

It was November 7, 1862, when about 1,700 Dakota Indians, mostly women and children, were force marched at gunpoint to a concentration camp at Fort Snelling, and then shackled and transported to another concentration camp at Mankato. At Mankato they were separated, the men from women and children.

The next day, following a quick, brief trial, they were tried and convicted as war criminals in what amounted to nothing more than a kangaroo court. The tribunal condemned 307 men to death by hanging and 16 to prison sentences. The condemned men were imprisoned to await their execution orders from President Lincoln. Military authorities and Minnesota representatives urged the president to approve the executions.

However, Lincoln was still dealing with the Civil War and was concerned an execution of that number might enrage European nations who might in turn support the Confederacy. So, the number was pared down to 39. One other name was later taken off the list.

The remaining prisoners, mostly women, children, sick, and the elderly, were marched at gunpoint back to Fort Snelling and confined in St. Paul’s concentration camp to endure a freezing, difficult winter. While on their way to the camp they were paraded through towns where white citizens greeted them as they would a circus side show. They were taunted and assaulted. Sticks and rocks were thrown and some were beaten. Reportedly, at least on one occasion, boiling water was thrown. It’s not known how many died on that journey, or even what happened to their bodies.

Then, on December 26th the 38 were lynched all at once by the U.S. military on a single scaffold. In a way the irony was profound. One day Americans celebrated the birth of Jesus Christ, and the next, cheered the execution of 38 people.

In May 1863, the remaining survivors of the Fort Snelling concentration camp were transported by boat to Davenport, Iowa, where most spent an additional three years of confinement. About one third died before they were released. Those surviving the ordeal, were shipped down the Mississippi River to St. Louis and then up the Missouri River to the Crow Creek Reservation in South Dakota.

Unfortunately, their deaths didn’t bring an end to the atrocities inflicted upon Native Americans. After the Civil War, General Sherman declared a personal war against the Plains Indians. He was determined to bring about a “final solution of the Indian problem.” By 1890, all of the Plains Indians had either been killed or placed on reservations. His plan had become reality.

Comments

    0 of 8192 characters used
    Post Comment

    • aviannovice profile image

      Deb Hirt 5 years ago from Stillwater, OK

      John, there was no Indian "problem". The US was settled by Europeans, so in effect, they were trespassing on land owned by the Indians. Now, this "civilized" country reminds me a bit of Nazi Germany. Doesn't this story sound a bit like it?

    • JY3502 profile image
      Author

      John Young 5 years ago from Florence, South Carolina

      eHealer, Yes you told me you liked them, so I decided to write this one especially for you...and more coming.

    • dianetrotter profile image

      G. Diane Nelson Trotter 5 years ago from Fontana

      It breaks my heart to read about atrocities like this.

    • NateB11 profile image

      Nathan Bernardo 5 years ago from California, United States of America

      Very important subject, good to bring it to light to educate people about what had happened and think about it in consideration of what can happen.

    • eHealer profile image

      Deborah 5 years ago from Las Vegas

      Hey John, great story! I love when you do these interesting historical hubs, you really know how to organize events and make them interesting! Excellent, voted up, pinned and facebooked!

    • point2make profile image

      point2make 5 years ago

      This is a part of our history that most Americans know nothing about. The widespread ignorance of the population, about what really happened to the Native Americans, will not change the stark reality of the truth. We, as a nation, have much to be proud about over the course of our long history.........and we also have much to be ashamed about. Your hub was well done...thank-you for bringing this story to light. voted this hub up and shared.

    • JY3502 profile image
      Author

      John Young 5 years ago from Florence, South Carolina

      Thanks. I don't know about wanting to go back to the good old days. Maybe, but not quite that far back.

    • JY3502 profile image
      Author

      John Young 5 years ago from Florence, South Carolina

      Thanks. I don't know about wanting to go back to the good old days. Maybe, but not quite that far back.

    • gmarquardt profile image

      gmarquardt 5 years ago from Hill Country, Texas

      Nicely written, great job. And people want to go back to the good ole days???

    • JY3502 profile image
      Author

      John Young 5 years ago from Florence, South Carolina

      Yes, it was. Thanks for the comment.

    • Paradise7 profile image

      Paradise7 5 years ago from Upstate New York

      What a terrible tragedy!

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)