YouTube Google+ Blog RSS Instagram

Bagram pilots save 60 Soldiers during convoy ambush

BAGRAM AIRFIELD, Afghanistan (AFNS) --

Two A-10 Thunderbolt II pilots assigned to the 74th Expeditionary Fighter Squadron, provided close-air support to 60 U.S. Soldiers July 24.

The Soldiers were part of a routine clearance patrol that was ambushed after their lead vehicle in a convoy of 12 turned over during a patrol of an Afghanistan highway. The situation forced the Soldiers to establish an overnight base while they pulled the vehicle out of a ravine. As the sun rose, the unit began to receive heavy fire from a nearby tree line. The members were pinned behind their vehicles and three of the Soldiers suffered injuries. The unit was under fire and the wounded members needed a casualty evacuation so they called for close-air support.

However, there was one problem; the ground unit didn't have a way to confirm the enemy's position. The unit did have a joint fire observer who was able to communicate an estimated location to the A-10 pilots who arrived on scene shortly after receiving the call from a local base's joint terminal air controller responsible for coordinating aerial engagements.

"I flew over to provide a show of force while my wingman was looking for gunfire below," said the flight lead of the two-ship A-10 mission. "Our goal with the show of force was to break the contact and let the enemy know we were there, but they didn't stop. I think that day the enemy knew they were going to die, so they pushed even harder and began moving closer to our ground forces."

When the enemy combatants didn't flee after the show of force, the A-10 pilots decided to deliver air-to-surface munitions to protect the friendly ground forces.

"Even with all our (top-of-the-line) tools today, we still rely on visual references," said the lead pilot, who is on his first deployment from Moody Air Force Base, Ga. "Once we received general location of the enemy's position, I rolled in as lead aircraft and fired two rockets to mark the area with smoke. Then my wingman rolled in to shoot the enemy with his 30 millimeter rounds."

According to the pilots, that really stirred up the attacking force. The enemy moved even closer to the friendlies in an attempt to prevent the A-10 from attacking again. The ground forces were now taking on a large amount of fire from the trees and surrounding high terrain.

"We just kept putting down more 30 mm rounds," said the second A-10 pilot, also deployed from Moody AFB. "The bad guys were closing in and according to the muzzle flashes there were a lot of them, but because people were shooting all over the place, the JTAC didn't feel safe bringing in helicopters in to evacuate the wounded personnel."

The pilots said usually after the first or second pass, the enemy runs away, but this enemy force was large and willing to fight. The pilots continued to fire 30 mm rounds, but the enemy force refused to fall back. Now, the enemy force was close enough to engage the unit with grenades, so the convoy's commander approved the pilots to engage "danger-close." The term is meant to clearly communicate to the ground and air forces that the need for support is so grave the ground commander is willing to accept the potential risk to the friendly unit for the life-saving employment from the air.

"We train for this, but shooting danger-close is uncomfortable, because now the friendlies are at risk," the second A-10 pilot said. "We came in for a low-angle strafe, 75 feet above the enemy's position and used the 30-mm gun -- 50 meters parallel to ground forces -- ensuring our fire was accurate so we didn't hurt the friendlies.

The engagement lasted two hours that day, and in that time, the A-10s completed 15 gun passes, fired nearly all their 2,300, 30-mm rounds, and dropped three 500-pound bombs on the enemy force.

 "That last gun runs must have made them give up," the two pilots agreed "because the firing stopped."

Shortly after the engagement was complete, an MC-12 aircraft specializing in intelligence, surveillance and reconnaissance arrived and began scanning the area for enemy forces that might be regrouping. Sometimes when close-air support leaves, enemy forces will attack again, so the A-10s remained on-station until all the Soldiers were safe.

"We wanted to make sure the area was safe because we had the pararescuemen from the 83rd Expeditionary Rescue Squadron coming to transport the injured to Bagram's hospital," said the second pilot. "The flight doctor assigned to our squadron treated the wounded in the emergency room. It was an example of a successful mission with contributions from all assets of our base."

After the pilots landed and debriefed, they went to the hospital to see the wounded Soldier.

"He was laying there and next to him was a picture of his high-school girlfriend," the lead pilot said. "We were glad knowing we helped get him home alive. He said, 'Thank you for shooting those bad guys'. Luckily we were only a few minutes away and all the friendlies made it out that day."

Providing close-air support is the squadron's main mission here, and is the specialty of the aircraft they fly, the A-10 Thunderbolt II nicknamed the "Warthog."

"This was one of the most intense sorties our squadron has come into contact with in the last four months in theater," the lead pilot said. "Afterward the Afghan National Army said they found 18 enemy dead, so I can only imagine how many were out there. This was close-air support and this is what we train for."

USAF Comments Policy
If you wish to comment, use the text box below. AF reserves the right to modify this policy at any time.

This is a moderated forum. That means all comments will be reviewed before posting. In addition, we expect that participants will treat each other, as well as our agency and our employees, with respect. We will not post comments that contain abusive or vulgar language, spam, hate speech, personal attacks, violate EEO policy, are offensive to other or similar content. We will not post comments that are spam, are clearly "off topic", promote services or products, infringe copyright protected material, or contain any links that don't contribute to the discussion. Comments that make unsupported accusations will also not be posted. The AF and the AF alone will make a determination as to which comments will be posted. Any references to commercial entities, products, services, or other non-governmental organizations or individuals that remain on the site are provided solely for the information of individuals using this page. These references are not intended to reflect the opinion of the AF, DoD, the United States, or its officers or employees concerning the significance, priority, or importance to be given the referenced entity, product, service, or organization. Such references are not an official or personal endorsement of any product, person, or service, and may not be quoted or reproduced for the purpose of stating or implying AF endorsement or approval of any product, person, or service.

Any comments that report criminal activity including: suicidal behaviour or sexual assault will be reported to appropriate authorities including OSI. This forum is not:

  • This forum is not to be used to report criminal activity. If you have information for law enforcement, please contact OSI or your local police agency.
  • Do not submit unsolicited proposals, or other business ideas or inquiries to this forum. This site is not to be used for contracting or commercial business.
  • This forum may not be used for the submission of any claim, demand, informal or formal complaint, or any other form of legal and/or administrative notice or process, or for the exhaustion of any legal and/or administrative remedy.

AF does not guarantee or warrant that any information posted by individuals on this forum is correct, and disclaims any liability for any loss or damage resulting from reliance on any such information. AF may not be able to verify, does not warrant or guarantee, and assumes no liability for anything posted on this website by any other person. AF does not endorse, support or otherwise promote any private or commercial entity or the information, products or services contained on those websites that may be reached through links on our website.

Members of the media are asked to send questions to the public affairs through their normal channels and to refrain from submitting questions here as comments. Reporter questions will not be posted. We recognize that the Web is a 24/7 medium, and your comments are welcome at any time. However, given the need to manage federal resources, moderating and posting of comments will occur during regular business hours Monday through Friday. Comments submitted after hours or on weekends will be read and posted as early as possible; in most cases, this means the next business day.

For the benefit of robust discussion, we ask that comments remain "on-topic." This means that comments will be posted only as it relates to the topic that is being discussed within the blog post. The views expressed on the site by non-federal commentators do not necessarily reflect the official views of the AF or the Federal Government.

To protect your own privacy and the privacy of others, please do not include personally identifiable information, such as name, Social Security number, DoD ID number, OSI Case number, phone numbers or email addresses in the body of your comment. If you do voluntarily include personally identifiable information in your comment, such as your name, that comment may or may not be posted on the page. If your comment is posted, your name will not be redacted or removed. In no circumstances will comments be posted that contain Social Security numbers, DoD ID numbers, OSI case numbers, addresses, email address or phone numbers. The default for the posting of comments is "anonymous", but if you opt not to, any information, including your login name, may be displayed on our site.

Thank you for taking the time to read this comment policy. We encourage your participation in our discussion and look forward to an active exchange of ideas.
comments powered by Disqus