In a very special episode of “things you didn’t know,” Team Mighty decided to give a shout out to the youngest branch of the U.S. military (aka the Air Force), and fill in the blanks to help people, civilians and non-Airmen alike, learn a few things about those who live in fame or go down in flame.
1. The Air Force tracks Santa.
On December 24, 1955 a newspaper ad told kids that they could call Santa at an included phone number. The number listed called the U.S. Air Defense Command. The colonel on duty ordered his team to give all kids Santa’s “current location.” This tradition now handles calls from over 200 countries.
2. The Air Force shares its birthday with the CIA.
Both were founded on September 18, 1947.
3. It used to be in the Army.
On Aug. 1, 1907, the U.S. Army Signal Corps formed the Aeronautical Division, which later evolved into the U.S. Army Air Force. The National Defense Act of 1947 created an independent Air Force.
4. An Airman first broke the sound barrier.
In 1947, then-Air Force Capt. Chuck Yeager broke the sound barrier in his Bell X-1 rocket-powered aircraft, kicking off a race of pilots who competed to do the next big thing, eventually leading to outer space and a man on the moon.
5. Airmen welcome their new commander by stomping on his or her roof.
A “roof stomp” is an Air Force tradition where airmen welcome a new commander or celebrate a special occasion by climbing up on the commander’s roof and making noise while others are banging on the windows and doors. Kind of like an episode of “The Walking Dead” but without the zombies.
6. They built a supercomputer out of Sony Playstations.
The Air Force Research Lab built a supercomputer called the Condor Cluster to analyze HD satellite imagery. The supercomputer is made up entirely of 1760 Playstation 3’s. It’s the 33rd most-powerful computer in the world.
7. Airmen get hairier every spring.
Every year, Airmen participate in a Mustache March, a tradition where airmen grow mustaches throughout the month of March to honor USAF legend, WWII and Vietnam veteran, and triple ace Brig. Gen. Robin Olds.
8. An Ace isn’t just a good pilot. They’re the best combat pilots.
An “ace” is a pilot who has shot down five or more enemy aircraft. The top jet ace in USAF history is Joseph C. McConnell, a “Triple ace” who shot down 16 MiG fighters during the Korean War over a four month period, bagging three on his last combat mission of the war. His record still stands.
9. Airmen respect North Dakota.
At the height of the Cold War, North Dakota was home to so many USAF nuclear weapons that if it seceded from the Union, it would have been the third largest nuclear power in the world.
That’s not North Dakota, that’s South Dakota, but you probably didn’t notice because we’re not in a nuclear war.
10. Some Airmen took the “Live in Fame” part of the Air Force song to heart.
Johnny Cash, George Carlin, Willie Nelson, Morgan Freeman, Hunter S. Thompson, and James Stewart are just a few celebrities who were Airmen. Stewart flew missions in World War II and Vietnam and rose to the rank of Brigadier General while still working in Hollywood.
11. Chuck Norris was a member
While Chuck Norris was stationed in Korea, he realized he wasn’t physically able to do his job as an Air Policeman (now called Security Forces) and developed an interest in martial arts. This is also where he earned the nickname Chuck.
12. The Air Force boasts two Presidents.
Ronald Reagan and George W. Bush served as airmen. Reagan served in WWII when the branch was still the Army Air Forces. Bush served in the Texas Air National Guard before transferring to the AF Reserve during the Vietnam era.
13. “Air Force One” isn’t a plane.
It’s the radio call name for any AF plane carrying the President of the United States. The same as the Marine helicopter carrying POTUS is Marine One.
14. Their F-117 fighter uses aerodynamics discovered from bumblebee flight.
15. Their weathermen are special forces.
They go through Army Airborne School at Fort Benning, Georgia, Air Force Basic Survival School, Air Force Water Survival Training, Air Force Underwater Egress Training, Combat Control School at Pope Field, North Carolina, and Special Tactics Training at Hurlbert Field. They work primarily with Air Force and Army Special Operations Forces but can also be attached to Marine MARSOC and Navy SEAL teams.
16. The Air Force is the only branch to directly fight the Soviet Union.
The U.S. and the Soviet Union fought one pitched battle — a dogfight during WWII over the Serbian town of Niš. The outcome wasn’t clear and both governments classified details of the incident.
17. The Air Force has an official band.
They do more than Souza marches, they drop singles and shoot music videos.
Whether the new battle rifle is based on the M110 Semi-Automatic Sniper System, the new M110A1 Compact Semi-Automatic Sniper System, the M14EBR, or some other contender, the Army will want the reach and hitting power of this cartridge in the hands of more grunts.
Every rifleman a designated marksman?
2. A new scout helicopter
The Army has retired the OH-58 Kiowa Warrior, but there has been no replacement. The hot-rod that was the RAH-66 Comanche got chopped in 2004. The ARH-70 Arapahoe was killed in 2008. Then, the planned OH-58F Block II got the axe in 2014 thanks to sequestration.
Look, the Apache is not a bad helicopter, but the Kiowa worked well as a scout bird. UAVs are nice, but sometimes, you need a manned scout to do the job.
3. More Dragoons
The Stryker got a firepower upgrade last year in the form of a 30mm Bushmaster II chain gun. These Strykers got a new designation (M1296) and a new name (Dragoon). However, there are a lot of places the grunts could use that extra firepower.
After Carl (Gustav) lost the weight, it came back with some new features that will make it far more user-friendly. The system is now a permanent part of infantry platoons, and gives them a weapon capable of firing anti-armor, illumination, smoke, anti-building, and anti-personnel rounds.
But let’s get those systems there faster, please.
5. Bring back the W48 and merge it with the Excalibur GPS tech
Everyone knows being a Blue Falcon is bad, but no one believes that they’re the blue falcon. Here are 7 indicators that maybe you should start shopping for nests.
1. When someone asks for volunteers, you immediately start thinking of who isn’t doing anything.
Look, it’s the platoon sergeant’s or the chief’s job to figure out who is doing what. If they don’t have a grip on their troop-to-task, that doesn’t make it O.K. for you to start naming who’s free for a tasking.
2. You find yourself saying, “Well, so-and-so did it earlier, first sergeant.”
Keep your mouth shut, snitch. First sergeant doesn’t need to know who snuck to the barracks first during those engrossing Powerpoint presentations battalion put together. Let him yell at you until he runs out of steam, then go back to the stupid briefings and suck it up.
3. You make the kind of mistakes that trigger company recalls.
Everyone screws up a few times a year, which is normal. Not everyone screws up so badly that the entire rest of their unit has to come in Saturday morning. Maybe keep your infractions a little more discreet in the future.
Or, make your mistakes epic enough that the unit will enjoy the recall just because they get to hear the story. “Wait, we’re here because Schmuckatelli crashed the general’s car with the installation command sergeant major’s daughter in the front seat? Can I make popcorn before you start, first sergeant?”
4. You frequently hear bus sounds or the words, “Caw! Caw!”
Yeah, your friends are trying to give you a hint, dude. You’re throwing people under the bus and then buddy f-cking them as they crawl out.
5. You take too much credit — especially for stuff you didn’t do with your own hands.
Always share credit. When you’re praised for rifle marksmanship, mention who helped you train. If you perform superbly at the board, mention the guys in your squad who quizzed you.
But, when you weren’t there, you shouldn’t take any credit. Say who actually did the work. Do not take the recognition, do not take the coin, do not tell stories about it later.
6. You’re always the guy that the team or squad leader has to pull aside.
Look, sucking at your job is a version of being the blue falcon. It’s not as malicious or direct as being a credit hog or a snitch, but not learning how to fulfill your position in the squad screws everyone else over. Read the manuals, practice the drills, watch the other guys in the squad. Learn your role.
7. Someone sent you this list or tagged you on Facebook in the comments.
Yeah, there’s a reason someone thought you, specifically, should read this list. Go back through it with a comb. Read each entry and keep a tally of which apply to you. Then, stop being a blue falcon. Caw caw.
Hollywood loves to make old fashion bloody war movies that have plenty of entertaining explosions and dramatic death scenes. While entertaining, these can hit pretty close to home for someone who’s been in the fight.
The graphic ones can be particularly realistic, but no matter what, they all represent the sucktitude of war.
Here are five you may want to stay away from before deploying to a combat zone.
1. Saving Private Ryan
Known as one of the most authentic and gruesome openings to a film ever, this Steven Spielberg-directed classic put audiences inside the minds of war-hardened characters as they storm the beaches of Normandy.
I think that guy had eggs for breakfast. (Image by Giphy)
2. Casualties of War
Marty McFly, I mean Michael J. Fox, plays an Army soldier who is coerced by Sgt. Tony Meserve (Sean Penn) to take advantage of a Vietnamese hostage-turned-sex-slave. When he refuses, the whole squad turns against him.
We guess they missed those team building exercises stateside. (Image via Giphy)
3. Hamburger Hill
John Irvin’s 1987 war epic depicts one of the most disastrous friendly fire accidents in the military in the Vietnam war.
Could you imagine that sh*t. (Image via Giphy)
4. The Deer Hunter
Because no one wants to think about the dangers of being a prisoner of war and playing Russian roulette at the same time.
No one wants to get left behind and eventually gunned down by the bad guys.
WHY ME?! (Image via Giphy)
Bonus: Pearl Harbor
This is a good one if you join the service with a buddy. In Micheal Bay’s “Pearl Harbor,” two childhood friends join the military as pilots. As one is off fighting in an aerial dogfight, the other stays back keeping his girlfriend company — eventually knocking her up.
Spoiler alert — he takes about a half dozen bullets for his buddy to buy himself some redemption. That is all.
It’s actually a good way to make things even. (Image via Giphy)
Why you should follow: Mat Best and the boys at Article 15 Clothing bring laughter in a way only veterans and active military personnel can relate to. They shoot anything that goes bang and make awesome videos.
Why you should follow: Stay up-to-date with the U.S. military’s most-trusted* news source (If you aren’t aware, Duffel Blog is a parody news organization offering pitch perfect satire on military and veterans issues).
It’s not unusual for troops to have a nonchalant or comical attitude about the worst of humanity. Sometimes comedy is all they have to make it through hardships that are unimaginable to most, and those who have deployed to remote locations and hot zones know this all too well.
It’s a mechanism to keep their sanity in the midst of snipers, ambushes, and IEDs, according to an article in Esquire. Sometimes the worse a situation gets, the more they laugh. One thing is for sure, troops go to comical heights to cope with the hand they’re dealt.
Here are nine examples of dark humor in the military:
The term “Broken Arrow” refers to more than a bad John Travolta movie. In military terminology, a Broken Arrow refers to a significant nuclear event — one that won’t trigger a nuclear war — but is a danger to the public through an accidental or unexplained nuclear detonation, a non-nuclear detonation or burning of a nuclear weapon, radioactive contamination from a nuclear weapon, the loss in transit of a nuclear asset (but not from theft), and/or the jettisoning of a nuclear weapon.
In 1980, the Department of Defense issued a report titled “Narrative Summaries of Accidents Involving U.S. Nuclear Weapons.” Keep in mind, this details eventsonly before 1980. There have been other incidents and scandals since then, not covered here.
The DoD report was released after public outcry following the 1980 Damascus Incident, covered in detail by Eric Schlosser’s 2014 book Command and Control: Nuclear Weapons, the Damascus Incident, and the Illusion of Safety. In this instance, DoD defined an “accident involving nuclear weapons” as:
An unexpected event involving nuclear weapons or nuclear weapons components that results in any of the following:
•Accidental or unauthorized launching or firing, or use by U.S. forces or supported allied forces of a nuclear-capable weapon system which could create the risk of an outbreak of war
• Nuclear detonation
• Non-nuclear detonation or burning of a nuclear weapon or radioactive weapon component, including a fully-assembled nuclear weapon, an unassembled nuclear weapon component, or a radioactive nuclear weapon component
• Radioactive contamination
• Seizure, theft, or loss of a nuclear weapon or radioactive nuclear weapon component, including jettisoning
• Public hazard, actual or implied
If the event occurred overseas, the location was not disclosed, except for the Thule, Greenland and Palomares, Spain incidents. There were no unintended nuclear explosions. The report included incidents from the Air Force and Navy, but not the Marine Corps, as they didn’t have nuclear weapons in peace time and not from the Army because they “never experienced an event serious enough to warrant inclusion.”
Somehow, the Army — of all branches — was the only branch not to lose a nuclear weapon over the course of 30 years.
1. February 13, 1950 – Pacific Ocean off the coast of British Columbia, Canada
A B-36 en route from Eielson AFB (near Moose Creek, Alaska) to Carswell AFB (Fort Worth, Texas) on a simulated combat profile mission developed serious mechanical difficulties six hours into the flight, forcing the crew to shut down three engines at 12,000 feet. Level flight could not be maintained due to icing, so the crew dumped the weapon from 8,000 feet over the Pacific Ocean. A bright flash occurred on impact, followed by the sound and shock wave. Only the high explosives on the weapon detonated. The crew flew over Princess Royal Island, where they bailed out. The plane’s wreckage was later found on Vancouver Island.
2. April 11, 1950 – Manzano Base, New Mexico
After leaving Kirtland AFB (Albuquerque, New Mexico) at 9:38 pm, a B-29 bomber crashed into a mountain three minutes later on Manzano Base, killing the crew. The bomb case for the weapon was demolished and some of the high explosive (HE) burned in the subsequent gasoline fire. Other HE was recovered undamaged, as well as four detonators for the nuclear asset. There was no contamination and the recovered components of the nuclear weapon were returned to the Atomic Energy Commission. The nuclear capsule was on board the aircraft, but was not inserted, as per Strategic Air Command (SAC) regulations, so a nuclear detonation was not possible.
3. July 13, 1950 – Lebanon, Ohio
A B-50 on a training mission from Biggs AFB, Texas flying at 7,000 feet on a clear day suddenly nosed down and flew into the ground near Mrs. Martha Bishop’s farm on Old Hamilton Road, killing four officers and twelve Airmen. The HE detonated on impact, but there was no nuclear capsule aboard the aircraft.
4. August 5, 1950 – Fairfield Suisun AFB, California
A B-29 carrying a weapon but no capsule experienced two runway propellers and landing gear retraction difficulties on takeoff from the base. The crew attempted an emergency landing and crashed an burned. The fire was fought for 12-15 minutes before the weapon’s high explosive detonated, killing 19 crew members and rescue personnel — including Brig. Gen. Robert F. Travis — who was flying the weapon to Guam at the request of Gen. Douglas MacArthur. The base was renamed Travis AFB in his honor.
5. November 10, 1950 – “Over Water, outside United States”
Because of an in-flight emergency, a weapon with no capsule of nuclear material was jettisoned over water from an altitude of 10,500 feet. A high explosive detonation was observed.
6. March 10, 1956 – Mediterranean Sea
A B-47 was one of four scheduled non-stop deployment aircraft sent from MacDill AFB, Florida to an overseas air base. Take off and its first refueling went as expected. The second refueling point was over the Mediterranean at 14,000 feet. Visibility was poor at 14,500 but the aircraft — carrying two nuclear capsules — never made contact with the tanker. An extensive search was mounted but no trace of the missing aircraft or its crew were ever found.
7. July 27, 1956 – “Overseas Base”
A B-47 with no weapons aboard was making “touch and go” landings during a training exercise when it suddenly lost control and slid off the runway, crashing into a storage igloo containing several nuclear weapons. No bombs burned or detonated and there was no contamination.
8. May 22, 1957 – Kirtland AFB, New Mexico
A B-36 ferrying a weapon from Biggs AFB, Texas to Kirtland AFB approached Kirtland at 1,700 feet when a weapon dropped from the bomb bay, taking the bomb bay doors with it. The weapon’s parachutes deployed but did not fully stop the fall because of the plane’s low altitude. The bomb hit 4.5 miles South of the Kirtland AFB control tower, detonating the high explosive on the weapon, making a crater 25 feet in diameter and 12 feet deep. Debris from the explosion scattered up to a mile away. Radiological surveys found no radiation except at the crater’s lip, where it was .5 milliroentgens (normal cosmic background radiation humans are exposed to every year is 200 milliroentgens).
9. July 28, 1957 – Atlantic Ocean
Two weapons were jettisoned off the East coast of the U.S. from a C-124 en route to Dover AFB, Delaware. Though three weapons and one nuclear capsule were aboard at the time, nuclear components were not installed on board. The craft experienced a loss of power from engines one and two and could not maintain level flight. The weapons were jettisoned at 4,500 feet and 2,500 feet – both are presumed to have hit the ocean and to have sunk immediately. The plane landed near Atlantic City, New Jersey with its remaining cargo. The two lost weapons were never recovered.
10. October 11, 1957 – Homestead AFB, Florida
A B-47 leaving Homestead AFB blew its tires during takeoff, crashing the plane into an uninhabited area only 3,800 feet from the end of the runway. The B-47 was ferrying a weapon and nuclear capsule. The weapon burned for five hours before it was cooled with water, but the weapon was intact. Even after two low intensity explosions, half the weapon was still intact. Everything was recovered and accounted for.
11. January 31, 1958 – “Overseas Base”
A B-47 with a weapon in strike configuration was making a simulated takeoff during an exercise when its rear wheel casting failed, causing the tail to hit the runway and a rupture to the fuel tank. The resulting fire burned for seven hours. Firemen fought the fire for ten minutes, then had to evacuate the area. There was no high explosive detonation but the area was contaminated after the crash, which was cleared after the wreckage was cleared.
12. February 5, 1958 – Savannah River, Georgia
A B-47 on a simulated combat mission out of Homestead AFB, Florida collided in mid-air with an F-86 Sabre near Savannah, Georgia at 3:30 am. The bomber tried three times to land at Hunter AFB, Georgia with the weapon on board but could not slow down enough to land safely. A nuclear detonation wasn’t possible because the nuclear capsule wasn’t on board the aircraft, but the high explosive detonation would still have done a lot of damage to the base. The weapon was instead jettisoned into nearby Wassaw Sound from 7,200 feet. it didn’t detonate and the weapon was never found.
13. March 11, 1958 – Florence, South Carolina
In late afternoon, four B-47s took off from Hunter AFB, GA en route to an overseas base. When they leveled off at 15,000 feet, one of them accidentally dropped its nuclear weapon into a field 6.5 miles from Florence, South Carolina — detonating the high explosive on impact — then returned to base. The nuclear capsule was not aboard the aircraft.
14. November 4, 1958 – Dyess AFB, Texas
A B-47 caught fire on takeoff, with three crew members successfully ejecting and one killed on impact from 1,500 feet. The high explosive detonated on impact, creating a crater 35 feet in diameter and six feet deep. Nuclear material was recovered near the crash site.
15. November 26, 1958 – Chennault AFB, Louisiana
A B-47 caught fire on the ground with a nuclear weapon on board. The fire destroyed the weapon and contaminated the aircraft wreckage.
16. January 18, 1959 – “Pacific Base”
An F-100 Super Sabre carrying a nuclear weapon in ground alert configuration caught fire after an explosion rocked its external fuel tanks on startup. A fire team put the fire out in seven minutes, with no contamination or cleanup problems.
17. July 6, 1959 – Barksdale AFB, Louisiana
A C-124 on a nuclear logistics mission crashed on take-off and it destroyed by a fire which also destroys the nuclear weapon. No detonation occurred but the ground beneath the weapon was contaminated with radioactivity.
18. September 25, 1959 – Off Whidbey Island, Washington
A U.S. Naby P-5M was abandoned in Puget Sound, Washington carrying an unarmed nuclear antisubmarine weapon, but the weapon was not carrying nuclear material. The weapon was not recovered.
19. October 15, 1959 – Hardinsberg, Kentucky
A B-52 left Columbus AFB, Mississippi and 2:30 pm CST as the the second position in a flight of two. A KC-135 tanker left Columbus AFB at 5:33 pn CST as the second tanker in flight of two, scheduled to refuel the B-52s. On a clear night near Hardinsberg, Kentucky at 32,000 feet, the two aircraft collided. Four crewmen on the B-52 were killed and the two nuclear weapons were recovered intact.
20. June 7, 1960 – McGuire AFB, New Jersey
A BOMARC supersonic ramjet missile in ready storage condition was destroyed after a high pressure helium tank exploded and ruptured the missile’s fuel tanks. The warhead was destroyed by the fire but the high explosive did not detonate and contamination was limited to the area beneath the weapon and the area where firefighting water drained off.
21. January 24, 1961 – Goldsboro, North Carolina
A B-52 on an airborne alert mission experienced structural failure of its right wing, resulting in two weapons separating from the aircraft during breakup between 2,000 and 10,000 feet and the deaths of three crewmembers. The parachute of the first bomb deployed successfully, and it was lightly damaged when it hit the ground. They hit the ground full force and broke apart. One of the weapons fell into “waterlogged farmland to a depth of 50 feet” and was not recovered. The Air Force later purchased land in this area and requires permission before digging nearby.
22. March 14, 1961 – Yuba City, California
A suddenly depressurized B-52 forced to descend to 10,000 feet and caused the bomber to run out of fuel. The crew bailed out, except for the aircraft commander, who steered it away from populated areas and bailed out at 4,000 feet. The two weapons aboard were torn from the aircraft upon ground impact with no explosive or nuclear detonation or contamination.
23. November 16, 1963 – Medina Base, Texas
123,000 pounds of high explosives from disassembled obsolete nuclear assets exploded at an Atomic Energy Commission storage facility. Since the nuclear components were elsewhere, there was no contamination and, amazingly, only three employees were injured.
24. January 13, 1964 – Cumberland, Maryland
A B-52 flying from Massachusetts to Turner AFB, Georgia crashed 17 miles southwest of Cumberland, Maryland carrying two nuclear weapons in tactical ferry configuration, but without electrical connections to the aircraft and the safeties turned on. Trying to climb to 33,000 feet to avoid severe turbulence, the bomber hit more turbulence, destroying the aircraft. Only the pilot and co-pilot survived the event, as the gunner and navigator ejected but were killed by exposure to sub-zero temperatures on the ground. The radar navigator went down with the bird. The weapons were found intact, but under inches of snow.
25. December 5, 1964 – Ellsworth AFB, South Dakota
Two Airmen respond to a security repair issue on a Minuteman I missile on strategic alert. During their work, a retrorocket below the missile’s re-entry vehicle fired, causing the vehicle to fall 75 feet to the floor of the silo, causing considerable damage to the vehicle structure and ripping it from the electronics on the missile. There was no detonation or contamination.
26. December 8, 1964 – Bunker Hill (now Grissom Air Reserve Base), Indiana
An SAC B-58 taxiing during an alert exercise lost control because of the jet blast from the aircraft in front of it combined with an icy runway. The B-58 slid off the runway, hitting runway fixtures, and caught fire as all three crew members began to abandon the aircraft. The navigator ejected but didn’t survive, and five nuclear weapons on board burned and the crash site was contaminated.
27. October 11, 1965 – Wright-Patterson AFB, Ohio
A C-124 being refueled caught fire, damaging the fuselage and the nuclear components the aircraft was hauling, contaminating the aircraft and the disaster response crews.
28. December 5, 1965 – “At Sea – Pacific”
An A-4 loaded with one nuclear weapon rolled off the elevator of an aircraft carrier and rolled into the sea. The pilot, aircraft and nuclear weapon were all lost more than 500 miles from land.
29. January 17, 1966 – Palomares, Spain
A B-52 bomber and KC-135 tanker collided during a routine high altitude air refueling operation, killing seven of the eleven crew members. The bomber carried four nuclear assets. One was recovered on land, another at sea, while the high explosive on other two exploded on impact with the ground, spreading radioactive material. 1400 tons of contaminated soil and vegetation were moved to the U.S. for storage as Spanish authorities monitored the cleanup operation. Palomares is still the most radioactive town in Europe.
30. January 21, 1968 – Thule, Greenland
A B-52 from Plattsburgh AFB, New York crashed and burned seven miles southwest of the runway while on approach to Thule AB, Greenland, killing one of its crew members. All four nuclear weapons carried by the bomber were destroyed by fire, contaminating the sea ice. 237,000 cubic feet of contaminated snow, ice, water, and crash debris were moved to the U.S. for storage over a four month cleanup operation as Danish authorities monitored the effort.
31. “Spring, 1968” – “At Sea, Atlantic”
“Details remain classified.”
32. September 19, 1980 – Damascus, Arkansas
During routine maintenance of a Titan II missile silo, an Airman dropped a tool, which fell and struck the missile, causing a leak in a pressurized fuel tank. The entire missile complex and surrounding area were evacuated with a team of specialists from Little Rock AFB called in for assessment. 8 1/2 hours after the initial damage, the fuel vapors exploded, killing one member of the team and injuring 21 other Air Force personnel. Somehow, the missile’s re-entry vehicle (and the warhead) was found intact, with no contamination.
Stockpiles of nuclear weapons in the global “Nuclear Club” of the U.S., Russia, the UK, France, China, Israel, India, Pakistan and North Korea number 15,600.
Below is a video detailing every nuclear blast ever detonated on Earth:
Despite President Donald Trump’s national-security advisers’ note reminding him “DO NOT CONGRATULATE” Russian President Vladimir Putin on his election victory during their call on March 20, 2018, Trump did anyway.
When asked whether Trump thought Putin’s election victory was free and fair during a press briefing that day, White House Press Secretary Sarah Huckabee Sanders demurred.
“We’re focused on our elections,” she said. “We don’t get to dictate how other countries operate.”
During another press briefing in February 2018, Sanders argued Trump had been “tougher on Russia in the first year than [former President Barack] Obama was in eight years combined.”
This argument has become a frequent line of defense Trump officials have used when pressed about the administration’s complicated relationship with Russia.
Trump, whose response to the US intelligence community’s assessment that Russia meddled in the 2016 US election has been lukewarm at best, is often perceived as being hesitant to confront the Kremlin’s aggression.
But the Trump administration has actually taken some concrete actions against Russia. Here are five examples:
Trump originally signed the sanctions bill — officially called the Countering America’s Adversaries Through Sanctions Act — August 2017, albeit begrudgingly.
The sanctions bill also imposes a wide range of sanctions on North Korea and Iran.
2. Closing of diplomatic facilities
After Congress approved Russia-related sanctions summer 2017, Russia expelled 755 American diplomats from the country.
In response, the Trump administration ordered Russia to close three of its diplomatic facilities in the US, including its consulate in San Francisco and two annexes in Washington, DC and New York City.
3. Arms sale to Ukraine
In December 2017, Trump announced his support for the sale of lethal munitions to the Ukrainian government in its fight against Russian-backed separatists in the country’s Donbas region, a move that angered Russia, which has been engaged in a hybrid war in the region for the past four years.
The State Department officially approved $47 million weapons sale in early March 2018. It included Javelin launchers and anti-tank missiles.
The US, the UK, France, and Germany all blamed Russia for the attack.
Although Trump initially failed to deliver a forceful condemnation of Russia for the attack, other officials in his administration picked up the slack.
“Over the past four years, Russia has engaged in a campaign of coercion and violence, targeting anyone opposed to its attempted annexation,” State Department spokeswoman Heather Nauert said in a statement.
“We stand behind those courageous individuals who continue to speak out about these abuses and we call on Russia to cease its attempts to quell fundamental freedoms of expression, peaceful assembly and association, and religion or belief.”
Secretary of State Rex Tillerson said the attack “clearly came from Russia” and US Ambassador to the US Nikki Haley said the US stood in “absolute solidarity” with the UK after the attack.
A full day after the UK blamed Russia, Trump told reporters that “as soon as we get the facts straight, if we agree with them, we will condemn Russia or whoever it may be.” Referring to the UK’s findings, he added, “It sounds to me like they believe it was Russia, and I would certainly take that finding as fact.”
National-security experts were baffled and alarmed by Trump’s delayed reaction to the chemical attack.
Trump then joined a statement with UK Prime Minister Theresa May, French President Emmanuel Macron, and German Chancellor Angela Merkel agreeing that there was “no plausible alternative explanation” than that Russia was to blame for the attack.
5. Trump officials repeatedly criticize Moscow
State Department spokeswoman Heather Nauert and US Ambassador to the UN Nikki Haley have been particularly critical of Russia.
On March 7, 2018, Nauert condemned Russia in a tweet, saying that it ignored a UN ceasefire agreement in Syria by bombing civilians in Damascus and Eastern Ghouta.
Her criticism elicited a direct response from Russia’s Ministry of Foreign Affairs (MFA), which told Nauert to “calm down.”
“Your propaganda machine is out of control — you’re spamming all of us,” the MFA added.
In January 2018, Nauert condemned Russia for supporting separatists in the country of Georgia. Trump recently promoted her to undersecretary of state for public diplomacy and public affairs.
Haley has also been critical of Russia over a variety of issues, including Moscow’s support for Bashar al-Assad’s regime in Syria and the Kremlin’s aggression in Ukraine.
Scenario #1: A young service member walks into their newly assigned barracks room and notices how nasty it is. And on top of that, they have to share the small space with two or three other people that may or may not be very clean. The struggle is real.
Scenario #2: A service member may just have received orders to go on a 13-month deployment wants to make some cash while they’re gone.
Both of these very real circumstances of military life can be strong motivators for troops to tie the knot — and not for love.
Often called a “contract marriage,” these pairings are purely for monetary gain or medical benefits. No one is suggesting you do this versus saving your money or getting a second job if your command allows, but if you do it, keep these very important things in mind.
If you do get a divorce, the military typically won’t stop the extra pay right away. So don’t go spending all that extra cash too fast. The government will take back every cent from your paycheck until they recoup what’s theirs.
The answer is, yes. (images via Giphy)You’re welcome America!
The group is passionate about supporting their own because after they came home from fighting a war their country sent them to fight, they were largely unsupported and even treated with hostility.
Vietnam vets don’t need to hear “thank you for your service” as much as, “welcome home.” So whether you know someone who served in southeast Asia or happen to pass one on your way to work, here are 9 actions you can take to give them the welcome home they never received:
1. Listen to them and learn their stories
Taking the time to learn and understand the experiences a veteran goes through helps you to understand them and appreciate their sacrifices on much more personal level.
2. Write them a letter
Giving a letter to a Vietnam veteran expressing your appreciation and support of what they sacrificed is something they can read on their own time and keep as a reminder that America ultimately cares about their era of service.
3. Give them a surprise welcome back
For extra effect, do this on the anniversary of the day they returned home from the war. Check around at local veteran organizations; you may be able to be part of a larger homecoming celebration, like the one in this video.
4. Perform community service together
Having an experience of serving together, no matter how small, is a shared experience you will both appreciate.
5. Organize a reunion for them
This may take a lot of planning, but coordinating an event that brings together Vietnam veterans who served together is going above and beyond showing how much you appreciate their service.
6. Organize their photos / records / awards into a scrapbook or shadowbox
Many vets have their memories in boxes or in storage somewhere. Ask to take them and display them so they will not be damaged but also displayed in an honorable way.
7. Give thanks by really helping them out
Ask if there is are any errands and chores you can do or to get to know them more, or see if there is anywhere you can go (museum, hike, etc.).
8. Have a memorial for the fallen
By visiting a memorial with them or having one of your own together, show them you honor the fallen and will never forget them.
9. Invite them to speak at a school class or social function
Having a veteran speak in a history class or at a social community event is a great way to educate the younger generation and your community about the services and sacrifices service members make.
College life and Navy life are very different, but there’s one thing they have in common: worried parents.
Whether you’re in college or the Navy, you can count on parents constantly checking in and asking a million questions. These conversations can feel like investigations; especially during deployments.
While Navy parents worry about their sons and daughters being in harm’s way, sailors are usually worried about more important things, like when’s the next port visit and what are their duty days. A little white lie can ease a parent’s worries. Here are some of the most common ones offered:
1. “I’m only allowed one call a month.”
2. “Sorry I won’t be able to call you during my next port visit, I have duty the entire time.”
3. “Of course I’m eating healthy, midrats is the healthiest meal of the day!”
4. “With the hours I work, I have no desire to stay out late.”
5. “Yes, I am spending my money wisely.”
6. “No, I never drink during port visits.”
7. “I spent my entire Hong Kong port visit sightseeing.”
Most people know about military working dogs, but there are some lesser known creatures that also conduct missions for the U.S. military:
Honeybees can smell explosives and other compounds nearly as well as dogs can, so researchers have begun training bees in bomb detection. The bees are trained to believe that sugar water is typically located near TNT. Once they make the association between TNT and sugar, they can be employed in two ways.
First, they can be restricted to glass tubes at check points. When people, cars, and packages are moved through the checkpoint, handlers watch the bees to see if they start moving their proboscis, a feeding tube that is part of their mouth. Movement in multiple bees is a sure sign that explosives are in the area. Alternatively, the bees can be fitted with radio transponders and released into a large area. Handlers then watch on computer screens to see where the bees swarm to and then check that spot for a mine.
2. Dolphins and Sea Lions
Though they’re slowly being replaced by drones, the Navy still uses trained dolphins and sea lions to hunt for mines and enemy swimmers. The animals are trained over a number of years and then deployed in vulnerable harbors, marking the mines and swimmers for human personnel to clear or capture. The aquatic mammals mark divers by attaching devices to their scuba tanks or limbs. They mark mines by attaching a cable or buoy to the mine. The mammals have been deployed to Vietnam, the Persian Gulf, and both U.S. coasts.
The Marine Corps has come up with a few innovative ideas for resupplying forward Marines, including stepping back to the days of pack animals and running mules. Mules were used in Afghanistan and the Marines maintain a training program at the Mountain Warfare Training Center in Bridgeport, California to prepare troops to use pack animals overseas.
4. Insect cyborgs
Currently going through development and testing in various DARPA programs, cyborg insects are designed for disaster relief and search-and-rescue missions. The bugs; muscles are controlled through implants. Researchers are experimenting with different power sources for the rig and any sensors strapped to the bug. One option that has been tested is nuclear cyborg bugs, where a low-radioactivity isotope is slowly broken down to power transmitters.
Most horse units were transitioned to mechanized in the lead up to World War II, and almost every U.S. horse unit has been shut down. But, there is an active law enforcement horse patrol in the U.S. Air Force. At Vandenberg Air Force Base, police have to clear launchpads and the surrounding area during missile launches and some of the area is too rough for ATVs. Also, patrols of the 40 miles of beach cannot always be done with vehicles due to a federally protected species that lives on the base. The horse patrols cover both the rough mountains and the beaches where vehicles can’t go. The U.S. also trains Marines and Special Forces to ride horses and other animals for certain operations.