ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Debacle on the Powder River Sept. 1865

Updated on July 2, 2010

The Powder River campaign of 1865 had only one purpose: to search and then destroy Indians, wherever found. There were three columns of troops descending from different forts upon the Tongue and Powder Rivers in Wyoming and Montana.  In charge of it all was Brig. General Connor, whose column of left Ft. Laramie and arrived at the Tongue to build a new military fort, Fort Connor, starting in mid-August. Two other columns, one under Col. Cole with 1400 men left Omaha on July 1, and another under Col. Walker, of 600 men, left Ft. Laramie. These two columns failed to find Connor’s troops but were able to meet each other near the Black Hills and then moved through the Badlands to the Powder reaching it at the start of September. These two columns were huge affairs comprising of 1200 horses,185 wagons and crossing areas with no roads.

Connor was greatly worried when the Walker and Cole columns failed to show up. It was for good cause. Neither Walker nor Cole had any experience whatsoever in fighting Indians, neither leader liked the other, neither knew anything about the area and both were recent transfers from the Civil War. Both men had the same rank. Adding to this were their men, many had been forced into the mission after they tried to mutiny because their enlistments were up. Thus, Connor sent out a posse to find the lost columns.

On Sept 1, the two columns reached the junction of the Powder River and Alkai Creek and were jumped by 300 indians, some had rifles.  Once repelled, the column continued downstream to the Mizpah River and due to snow and ice cold weather well below zero, had lost 2-300 horses. Being lost, the columns then reversed and traveled upstream and by Sept 4, had left behind many supplies to reduce the load. On the 5th, Crazy Horse and Roman Nose attacked with 1000 indians and 12 rifles. The battle ran three hours. The columns artillery did  an amazing job of keeping the Indians at bay, but soon ammo for artillery and rifles were rationed. Then food was rationed. After the three hour ordeal, none of the cavalry pursued the Indians, as many of the Cheyennes left. The reason were their horses were too weak from lack of food. The Lakotas remained in attack and harass mode and regrouped to attack in full on the 8th.  By now, the columns had reached modern day Powderville, Montana (so far off course) when climatic conditions slammed them with minus 40 temps, ice and snow. There the column stopped. When the storm cleared, they had lost 600 horses. Many of the men were in tattered clothes. The  Lakotas continued to harass and attack. Had the Indians more rifles, they easily could have finished off the columns.

Connor’s posse finally found them on the 13th, and redirected them towards Ft. Connor, some 80 miles away! Despite the impossible odds, the lost columns reached the fort on the 20th in despicable condition of a ragtag army. Many soldiers were shoeless and near death from starvation. They managed to survive by eating the dead horses. Only 600 sickly horses came back.

The Indians failed only because they lacked rifles, their bow and arrows, spears simply were not enough. Even though the Indians attacked at will against an ill trained, defense only force on rations, it was enough to make them ineffective. For the most part, it kept the Indians at bay.

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://corp.maven.io/privacy-policy

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)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)