HomeNewsArticle Display

Finally home: A look back at the history of the 167th AES

Maj. Gen. Donald William Shepperd (left), the Director of the Air National Guard from 1994 to 1998, poses with the members of the 167th Aeromedical Evacuation Squadron who won the inaugural Aeromedical Evacuation Squadron Rodeo trophy June 29, 1996. The 167th AES faced numerous challenges competing for the award that year and were helped by the 130th Airlift Wing. The 167th AES would later be relocated to the 130th Airlift Wing in Charleston, W.Va. ( courtesy photo )

Maj. Gen. Donald William Shepperd (left), the Director of the Air National Guard from 1994 to 1998, poses with the members of the 167th Aeromedical Evacuation Squadron who won the inaugural Aeromedical Evacuation Squadron Rodeo trophy June 29, 1996. The 167th AES faced numerous challenges competing for the award that year and were helped by the 130th Airlift Wing. The 167th AES would later be relocated to the 130th Airlift Wing in Charleston, W.Va. ( courtesy photo )

Lt. Col. Joseph Buonocore holds the Aune-Paget trophy from the 1996 Air Mobility Command Rodeo. Bonocore was a member of the five-man rodeo team from the 167th Aeromedical Evacuation Squadron that won the inaugural Best Aeromedical Evacuation Squadron award. Bunoncore is a 35-year veteran of the West Virginia Air National Guard who was a part of the 167th AES at both the 167th Airlift Wing and 130th Airlift Wing. (U.S. Air National Guard photo by Tech. Sgt. De-Juan Haley)

Lt. Col. Joseph Buonocore holds the Aune-Paget trophy from the 1996 Air Mobility Command Rodeo. Bonocore was a member of the five-man rodeo team from the 167th Aeromedical Evacuation Squadron that won the inaugural Best Aeromedical Evacuation Squadron award. Bunoncore is a 35-year veteran of the West Virginia Air National Guard who was a part of the 167th AES at both the 167th Airlift Wing and 130th Airlift Wing. (U.S. Air National Guard photo by Tech. Sgt. De-Juan Haley)

MCLAUGHLIN AIR NATIONAL GUARD BASE, W.Va. --

Why is there a 167th Aeromedical Evacuation Squadron at the 130th Airlift Wing? This questions is posed by many people when they discuss the storied legacy of the 130th Airlift Wing. It seems odd to them that at McLaughlin Air National Guard Base, there would be a unit with the same numerical designation as our sister unit in Martinsburg, West Virginia, the 167th.

The explanation, while seemingly unordinary in Air Force terms, has significance to the members, and particularly Lt. Col. Joseph Buonocore, who’ve served in the unit before it was moved to Charleston in 2012.

That significance of the two unit’s ties spans multiple decades, back to the 1990’s where they participated in missions together in the Gulf War, then to the Air Mobility Command Rodeo and later Operations Enduring Freedom and Iraqi Freedom come into play.

“When I joined the 167th in 1985, 97 percent of aeromedical evacuation personnel in the entire Air Force were in the Guard and Air Force Reserve,” Buonocore recounted. “We were told in the event of a major military operation, we would without a doubt, be going to war.”

In just five short years after enlisting, Buonocore found himself deployed to the Middle East supporting the war effort for Operation Desert Shield/Desert Storm as an aeromedical evacuation technician. While his unit’s aircraft were stationed in Germany, Buonocore found himself flying AE missions with the 130th Airlift Wing, which had been deployed to the area of responsibility.

“No one at our home unit [the 167th AW] really understood Aeromedical Evacuation or its mission and what we did,” he said. “Our aircraft were stationed in Germany, flying support missions into the area while our AES members were scattered across the AOR, which is where the 130th AW aircraft were stationed. We deployed half way around the world and our sister unit, from our own state, ended up flying our missions.”

While this seemed like a one off experience for Buonocore, to work hand-in-hand with his unit’s counterpart in Charleston, this experience would be repeated numerous times throughout the rest of his career.

In 1996, Air Mobility Command hosted their biennial rodeo event, where units from around the Air Force competed in mobility exercises, which, for the first time, included aeromedical evacuation in its competition. The event showcased the best of the United States’ and international mobility forces’ abilities and provided a forum for them to share best practices, tactics and techniques that are crucial to continued pursuit of coalition operations around the world.

 Since this was the first time any AES would compete in the competition, Buonocore and the members of the 167th weren’t really sure how to put together their team, what to train for specifically, or how they would even get to the competition, since their aircrew and planes weren’t participating.

“The team developed our own lesson plans and practiced in the evenings after work or school, depending on the crew member,” he said. “We didn't know what to expect despite having a list of rules of engagement for the competition. The whole culture and experience of the rodeo was new for us.”

But the team faced a bigger problem - not knowing how they would get to the competition. It was later agreed that the crew and their equipment would be flown down to Charleston by the 167th AW and then to McChord AFB aboard 130th AW C-130s. From there, the AES members received unwavering support from the 130th.

Buonocore noted, “we were blown away by the support we received by the 130th AW, 130th Family Support, and 130th AW Rodeo Team. From the moment we arrived in Charleston, they treated us as if we were in the same unit.”

He continued, “the day we left for the rodeo, Brig. Gen. William Fleshman, the West Virginia Adjutant General for Air was there to see the competitors off for competition. He asked for a team photo, but we felt somewhat left out since we weren’t a part of the unit, but the general asked to have a photo taken with ‘the world’s best aeromedical unit’ and we snickered and agreed for a photo.” 

After the competition was completed, the 167th AES team assured themselves that they hadn’t placed and went to the awards ceremony early to get a good seat.

“When the announcement of the winner of the inaugural aeromedical evacuation rodeo trophy came over the loudspeaker - ‘The one…..sixty…..seventh,’ we all stared at one another, frozen. Then we said, ‘oh wait! That’s us!’”

When the team went to accept their award, they were overwhelmed with support from the 130th.
 
“We walked up to accept the award and take pictures and as we exited the stage, the 130th came pouring out of the bleachers waving the state flag and congratulating us for our victory,” he reminisced. “If it wasn't for the 130th we wouldn’t have competed, let alone won.”

That winning trophy adorns the case inside the 167th Aeromedical Evacuation Squadron at the 130th, highlighting the partnership the two units have built over the years.

Years later, when the wars in Iraq and Afghanistan were at their height, the 167th and 130th once again found themselves serving alongside one another, providing airlift for the war and supporting the AES mission from the 167th.

In 2002, the 167th Airlift Wing in Martinsburg, West Virginia, underwent a mission conversion from flying the C-130H to the C-5 Galaxy. Ten years after that, the 167th found itself permanently stationed as a part of the 130th Airlift Wing in Charleston.

Since that time, the 167th and 130th have seamlessly fallen into a battle rhythm - one that seems to have always been there and is both supportive and cohesive. Necessary elements for mission success.

Buonocore celebrated nearly 32 years with the two units recently and his retirement from the West Virginia Air National Guard became official in April.

“It’s fitting,” Buonocore mentioned in closing, “that the trophy now resides at McLaughlin Air National Guard base, whom we received so much support from over the years.” 


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.