Engage

T
Logo
T
Logo
T
Logo
T
Logo
T
Logo
F
Logo
T
Logo
T
Logo
T
Logo
T
Logo
F
Logo
T
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
F
Logo
Facebook
2,040,256
Like Us
Twitter
387,942
Follow Us

Investigation board determines cause of KC-135 crash in May

SCOTT AIR FORCE BASE, Ill. (AFNS) --

Air Mobility Command has released the results of an accident investigation that examined what caused the May 3, 2013, crash of a KC-135 Stratotanker in the Kyrgyz Republic. The crew of three, en route from the Transit Center at Manas to Afghanistan on a combat aerial refueling mission, perished in the mishap.

Upon takeoff, a flight control system malfunction, the board found, generated directional instability, causing the aircraft's nose to slowly drift from side-to-side or "rudder-hunt." This condition, not fully diagnosed by the crew, progressed into a more dangerous oscillatory instability known as a "Dutch roll." The board identified that a poor layout of key information in the inflight manual and insufficient crew training contributed to the mishap by detracting from the crew's ability to act on critical information during their troubleshooting to turn off either of two cockpit switches which may have eliminated the malfunction.

Having not recognized the Dutch roll condition, the crew initiated a left turn to remain on-course along the planned route of flight and used a small amount of left rudder to coordinate the turn. The use of rudder, while in a Dutch roll, increased the aircraft's oscillatory instability. The ensuing large side-to-side movements of the aircraft varied the crew member's foot pressure on the rudder pedal which caused inadvertent fluctuations in rudder position. These fluctuating rudder movements, coupled with slight right rudder use while rolling out of the turn, compounded the Dutch roll severity and produced extreme airframe stress that caused the KC-135's tail section to separate from the aircraft. The subsequent, uncontrollable descent resulted in an in-flight explosion.

"Our hearts go out to the family members and friends of these Airmen," said Brig. Gen. Steve Arquiette, who led the accident investigation board. "Having attended the memorial service at Manas and later interviewing many co-workers, I know these Airmen were highly regarded and are greatly missed. The investigation team, with the help of our industry and Kyrgyz government partners, pushed through months of intense fact finding for the primary purposes of understanding what happened that day and to honor the crew's service to our nation."

The three Airmen who perished are:

Tech. Sgt. Herman Mackey III, 30, of Bakersfield, Calif. 

Capt. Victoria Ann Pinckney, 27, of Colorado Springs, Colo.

Capt. Mark Tyler Voss, 27, of Boerne, Texas

A unique combination of six factors -- flight control malfunctions, insufficient crew force training, incomplete crew checklist response, use of rudder while in a Dutch roll condition, crew composition, and cumbersome procedural guidance -- all came together during the flight's short 11-minute duration and resulted in this accident.

"The crew encountered a condition that they had not realistically experienced in training, and when coupled with decisions based on their relatively low recent experience levels, were presented with an unrecognized hazardous and difficult situation to overcome," Arquiette said. "It has been the focus of our investigative team, throughout these months of hard work and travel to the accident scene in the Kyrgyz Republic, to do everything we can to fully understand the facts surrounding this tragic string of events."

The aircraft was assigned to the 22nd Air Refueling Wing at McConnell Air Force Base, Kan., and was flown by members of the 92nd Air Refueling Wing at Fairchild Air Force Base, Wash. The crew and aircraft were flying out of the 376th Air Expeditionary Wing at the Transit Center Manas.

The report is available on the Air Force Freedom of Information Act Reading Room website, http://www.foia.af.mil/reading/.

(Courtesy of Air Mobility Command Public Affairs)

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