In the wake of Sept. 11, Capt. Mitch Nelson leads a U.S. Special Forces team into Afghanistan for an extremely dangerous mission. Once there, the soldiers develop an uneasy partnership with the Northern Alliance to take down the Taliban and its al-Qaida allies. Outgunned and outnumbered, Nelson and his forces face overwhelming odds in a fight against a ruthless enemy that takes no prisoners.
While military appreciation month is in May, the cinematic equivalent is in January. There has been quite a few military films released during the first month of the year. Most recently was Michael Bay’s “Thirteen Hours” which is a film that I quite enjoy. However, the main issue that plagued that movie was the sub par character work, and that sadly is the same case with 12 Strong.
12 Strong isn’t a bad movie, but it doesn’t really manage to be anything above serviceable. This film gets just about an equal amount of things right and wrong. Some of the dialogue can be cheesy like a lot Hemsworth’s conversations with an ally. However, the humor is rather smart. With a lot of films like this, I feel like they are trying too hard to be funny, but that’s not the case here.
13 Hours did a great job of making you feel that characters in the film were in a real sense of danger throughout. 12 Strong on the other hand does not have that same feeling to it, even to me, someone who was not familiar with the true story before seeing the film. Sure there are some character issues with 12 Strong, but it also does have its fair share of entertaining action set pieces. Some of the battle scenes are really damn entertaining, but what connects them together is average at best.
All in all, the word I would to use 12 Strong is fine. It really nothing above fine, and not really a bad movie either. January usually serves a breeding ground for terrible movies, but so far this year there hasn’t been anything even close to what I would say is terrible. 12 Strong is another one of those movies not close to great, but even further from terrible.