Engage

T
Logo
T
Logo
T
Logo
F
Logo
T
Logo
F
Logo
T
Logo
T
Logo
T
Logo
F
Logo
T
Logo
T
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
F
Logo
F
Logo
Facebook
1,997,400
Like Us
Twitter
406,833
Follow Us
YouTube Google+ Blog RSS Instagram

Two B-52 crews help save disoriented pilot

MINOT AIR FORCE BASE, N.D. (AFNS) --

During a routine exercise over Alaska, a seven-man B-52H Stratofortress crew from here, call sign HAIL13, and a B-52H crew from Barksdale Air Force Base, call sign HAIL14, received a call for help from the Anchorage Air Traffic Control Center Nov. 13. The whereabouts of a small Cessna aircraft had become unknown after its pilot became disoriented while flying through bad weather.

Air traffic control was unable to communicate with him over the radio because the pilot dropped too low in altitude, leaving him completely alone in the Alaska sky.

"(Air traffic control) called and said they had a pilot over the radio squawking emergency and had completely lost contact with him," said Capt. Andrew J. DesOrmeaux, a 69th Bomb Squadron B-52H Stratofortress pilot. "They asked if we could try and find him and make contact. We didn't know if he was still airborne, or if we would find a crash site."

HAIL13 was approximately 200 miles away from the Cessna pilot's estimated location when they got the distress call. Before committing to help locate the pilot, both aircraft crews needed to ensure their own well-being.

"The first thing we did was calculate our fuel to make sure we had enough," said Capt. Joshua M. Middendorf, the 69th Bomb Squadron aircraft commander of HAIL13. "We also had to ensure our wingman, HAIL14, would have enough fuel to make it back to Barksdale (AFB)."

After ensuring they both had enough fuel to make the trip, HAIL13 and HAIL14 headed west in search of the Cessna pilot.

One hundred miles into their detour, HAIL13 was able to locate and make contact with the pilot. He was flying low to the ground through a valley surrounded by rugged Alaska terrain.

"Because we were so high up, we were able to relay messages between him and ATC," explained Middendorf.

Communicating between air traffic control and the pilot, HAIL13 relayed the weather ahead of the pilot and his best shot at finding the nearest airport.

As the pilot approached Calhoun Memorial Airport in Tanana, Alaska, HAIL13 communicated over a common traffic advisory frequency to get the brightness of the airfield lights turned up, effectively guiding the pilot safely to the ground.

"It was in the middle of Alaska on a Sunday night, there was no one there," Middendorf said. "We were probably his only chance at communicating with anyone. After our flight ATC personnel contacted our base and from their perspective, we saved his life."

Although both crews flew hundreds of miles off course, they did not allow the detour to compromise their mission.

"Something the 69th has been really mindful about is saving fuel," explained DesOrmeaux. "Because we were so diligent about being fuel efficient early on, it was no problem to go out there, fly back on course, and still make everything on time."

The fuel saved in the beginning stages of the mission by HAIL13 and HAIL14, allowed them to fly faster back to their original course, putting them back on schedule. In the end, HAIL13 and their wingman were able to complete every mission checkpoint, resulting in a successful mission.

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