ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Seven Myths About Custer's Last Stand

Updated on June 19, 2015

Common misconceptions surrounding the famous battle.

On June 25th, 1876, one of the most iconic battles in American history took place in southeastern Montana. On that day, George Custer led his men of the 7th Cavalry into battle against Indian warriors of the Lakota, Sioux and Cheyenne tribes. We’ve all heard of the story, but there are misconceptions associated with it. Following are seven common myths about the battle.

1. The 7th Cavalry was completely massacred at the Little Big Horn Battle. Simply not true. Not every soldier involved in the fighting died at Little Big Horn. Custer actually divided his force into three columns. He led one while Major Marcus Reno and Captain Fredrick Benteen led the other two respectively. Each column would become involved on different parts of the battlefield. The confusion comes over Custer’s column. It was wiped out to the last man, but many men in Reno’s and Benteen’s columns survived.

2. Ever the gallant leader, Custer bravely led his men into battle first. Nope. Custer was not the first to engage the enemy. That distinction goes to Major Reno. He attacked the Indian village that day from the south, while Custer planned to attack from the north. Reno was quickly beaten back and retreated to one of the surrounding hills where he fought defensively.

3. Custer rode into the battle unaware of the size of the Indian war party. In fact, Custer was not mistaken about the size of the Indian camp as many believe. He viewed it from a distance and wrote a hasty note to Benteen, directing him to reinforce at once. “Benteen – Come on. Big Village. Be quick. Bring Packs. P.S. Bring Pacs (sic).” The packs were ammunition. Custer knew he would need them because of the “big village.”

4. Surrounded, Custer and his men fought to the last man, ending the battle. Not quite. The battle involving Custer and his men was not the final fight. Benteen caught up with Reno and reinforced him instead of Custer. Reno and Benteen fought off the Indian advance that day and again the following morning. Custer and his men were roughly three miles away, isolated and involved in a desperate struggle for their lives while Reno and Benteen dug in.

5. At least Custer and his men fought valiantly and in an orderly fashion to the last man. Not really. According to Indian testimony and battlefield archaeology, Custer’s column quickly fragmented and it more or less became every man for himself. Some tried to make a run for it, where they were cut down while others used the last bullet on themselves. However, it is probably true that the rest, including Custer, realized their hopeless fate and fought until killed.

6. The reason for the Custer debacle was because he disobeyed orders and dashed into an attack without waiting on reinforcements, due to his ego and lust for glory. Although Custer was, by many accounts, egotistical and somewhat reckless in battle tactics, he did not disobey orders. His superior, Brigadier General Alfred Terry, advised Custer before his fateful ride to “use your own judgment and do what you think best if you strike the trail.” Custer may not have made the best decisions that day, but technically he did not disobey orders.

7. The lone survivor of the Custer column was a horse named Comanche. In fact, several horses from the Custer column survived, but had to be destroyed after the battle due to their wounds. Comanche’s wounds were not as serious, and he was thus spared. Many of the horses in the 7th Cavalry were shot by the soldiers themselves and used for cover.

For additional information, the reader is invited to consult the following online resources, some of which were used in the compilation of this article:

“Little Bighorn Battlefield,” various articles. A National Park Service website.

“How the Battle of Little Bighorn Was Won”. A website.

“Grim Facts of Custer’s Last Stand: Revelations from the Remains of Battle.”

“Archaeology of the Battle of the Little Bighorn.” A National Park Service Website.


    0 of 8192 characters used
    Post Comment

    • profile image


      3 years ago

      I love history , and each of these points is very true ! I think history , as taught to us in elementary and high school , is simply too incomplete , shallow in detail and depth . That's all , but as we age those of us who still have interests in history fill in between the gaps . Great hub !


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, 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:

    Show Details
    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 or domains, for performance and efficiency reasons. (Privacy Policy)
    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)
    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.
    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)