
Keselowski doubles down on anthem controversy
After expressing Sunday night that he does not support those individuals who do not stand for the national anthem, Brad Keselowski posted a series of tweets Tuesday night going even deeper into the matter.
//platform.twitter.com/widgets.js
The Team Penske NASCAR driver followed up that post with five more. In doing so, the outspoken 2012 Cup champion informed his followers why he and his family stand at attention each weekend during pre-race activities, which includes the national anthem. Keselowski also celebrates each of his victories by holding a giant American flag out the window of his No. 2 Ford.
//platform.twitter.com/widgets.js
//platform.twitter.com/widgets.js
//platform.twitter.com/widgets.js
//platform.twitter.com/widgets.js
//platform.twitter.com/widgets.js
NASCAR, along with its owners and drivers, has come to the forefront of the mainstream media's attention following comments made by Richard Petty and Richard Childress over the weekend. Both team owners essentially said they would fire anyone on their teams who did not stand for the national anthem.
The latter is an act that has been widespread in the National Football League. More than 100 players and owners either took a knee or some other action last weekend to express solidarity and bring awareness to what they believe to be inequality in the United States.

After President Trump tweeted his support for NASCAR, the sanctioning body released the following statement Monday afternoon:
"Sports are a unifying influence in our society, bringing people of differing backgrounds and beliefs together. Our respect for the national anthem has always been a hallmark of our pre-race events. Thanks to the sacrifices of many, we live in a country of unparalleled freedoms and countless liberties, including the right to peacefully express one's opinion."
Latest News
Comments
Comments are disabled until you accept Social Networking Cookies. Update cookie preferences
If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.





