Close

Member Login

Logging In
Invalid username or password.
Incorrect Login. Please try again.

not a member? sign-up now!

Signing up could earn you gear and it helps to keep offensive content off of our site.

Audio: Controllers Under Investigation for Ignoring Distress Call

By Stephen Pope / Published: Apr 10, 2012
Rate it! 60% or 40%
Denver International Airport

Controllers at Denver International Airport
are currently under investigation for dismissing
a real emergency call as a prank.

The full details are still unknown, but the FAA is investigating a bizarre April 3 incident at Denver International Airport in which controllers are heard on a tower audio recording ignoring an emergency call from a United Airlines flight with smoke in the cockpit, apparently deciding the call is a hoax. A controller is heard telling co-workers the emergency request is “B.S.” before the airliner touches down and passengers begin evacuating on the runway.

According to the audio recording, a pilot aboard the United Flight 5912 radioed the Denver tower as the airplane approached for landing, requesting emergency ground assistance. “This is 5912, emergency, smoke in cockpit, roll trucks, please,” the pilot says.

But the tower controller did not hear who was calling.

“And who was that?” the controller replied.

“United 5912,” the pilot responded – but the controller apparently heard only “United 12.”

“United 12, what’s your position?” the controller asked.

The pilot did not respond, possibly attending to the more vital “aviate” and “navigate” responsibilities on approach. That’s when the controller apparently decided the call was a hoax and should be ignored.

“Did you hear that?” the controller asked another controller. “I know that’s B.S. I know it is. United 12. You know of United 12 anywhere?” he asked a controller. “And, I apologize. If you probably heard there, that’s not real what we’re hearing on the frequency,” the controller tells co-workers.

The United flight reportedly made an emergency landing believing that fire crews had been dispatched and were ready to assist. After the airplane landed and no assistance was provided, the pilots called the tower again. “We’re on the runway. We’ve been evacuating. We’ve been evacuating. 34 Right,” the pilot says.

Still, even with the airplane on the ground, the controllers still apparently do not believe the emergency is real.

“12, verify that wasn’t you,” the controller says.

The FAA so far hasn’t commented on the incident, which raises a host of questions about emergency procedures and controller and pilot responsibilities when emergencies arise. It is unclear whether the crew of the United flight squawked the emergency distress code 7700, but given that the airplane was on approach to the airport and in contact with controllers at the time, the pilots might have decided not to switch transponder codes. The pilot of the United flight could be considered guilty of using non-standard radio phraseology -- somewhat understandable given the circumstances.

The reaction by controllers to the emergency call, on the other hand, defies explanation.

Comments (17) Post a comment

All Comments

vandy58's picture

The controllers did seem a little cavalier but the pilot didn't help matters by not remaining calm on the radio and communicating better.

KKDD's picture

This is indeed a bizarre story. Has the mainstream media picked up on the air traffic controller angle yet? That's something they could really sink their teeth into. Great reporting, as usual, from Flying.

DMW's picture

The controllers should be put on probation and possibly lose their job - there is no excuse for this type of attitude. What if they had been fully engulfed by the time the pilots stopped the plane?

hanrahan's picture

If it is a potential emergency, treat it as an emergency. Controller sounds distracted. Ignore the union rhetoric, and put a camera on that controller while he is working a control position. This is a safety issue and the only way the controller can be held accountable for his actions. It's the only way to be sure what happened in any incident. How can problems be corrected, if we don't really know what happened? (LEX)

Lambo805's picture

I agree, the pilot of the multi-million dollar aircraft with priceless lives on board is clearly at fault for not communicating better with an airborne fire apparently developing. Where's the rolling eyes smiley?

I applaud the captain and crew for executing a safe landing and evacuation personally...the controller should be fired.

airsteve172's picture

The controllers' jobs should be on the line at least to the same extent that the lives are on the line of those who they control.

Ozzie33's picture

First no one knows how they are going to respond in an emergency like smoke in the cockpit. I am sure that is a very scary scenario. What I can't understand is that there has to be several aircraft on frequency and why didn't another aircraft correct the controller when he called out for "United 12" when I'm sure other pilots heard the correct call sign 5912. But as typical of a "screw up" it is a combination of factors that become a problem and the chain wasn't broken. Thank goodness no one was injured according to the report.

gellisdds's picture

I agree that the controllers should have further probed into the origin of the emergency call and not just dismiss it as a prank but the pilot needs a little chat with his chief pilot about maintaining some composure to help the matter. Compare the way this pilot communicated his emergency to that of the way Sullenberger communicated the emergency when he had both engines flame out after a bird strike and landed in the Hudson. If you have heard that audio it is textbook on how to maintain composure in a cockpit during an emergency.

meyerjewel's picture

the controller and the supervisor should both be suspended. the pilot reported an emergency, the controller should have taken it seriously. if he couldnt find United 12 on his screen he certainly could find united 5912 and should have figured it out. then when he sees the plane on the runway, instead of asking the plane to leave the rinway, a light should have gone off in his head and put 2 and 2 together and come up with fire in teh cockpit, real emergency, instead he orders teh plane off the runway. where is the supervisor.

gburgess's picture

Can we see a picture of the controller so we can all see what STUPID really looks like?!?!

pete480's picture

The pilot may not have kept his composure because his emergency went ignored. He sounded pissed and I don't blame him one bit. The controller could have figured out who was calling.

ahwells's picture

I had an emergency once and had difficulty controlling the aircraft. The controller at Roanoak was great even though my communication was pretty confused. I'd give the controllers a chance to explain what happened before I jumped to conclusions.

RGPMedianet's picture

Under no circumstances should a distress call be considered a hoax until proven otherwise. I wouldn't want this guy in the tower when I call for help.

BruceB's picture

No-one is blameless in this situation, however both parties could seek to improve their performances.
If you want to get the controller's attention nothing beats "MAYDAY, MAYDAY, MAYDAY, United 5912. Smoke in cockpit. " Don't try telling the controller his/her job just communicate the problem. They will "roll trucks" or whatever the appropriate action is.
Controllers often have more than one voice coming over the speaker in tower environments and so transmissions can be missed( 20 Years' experience has allowed me to experience this.) but if you think there is an emergency declare it and take the appropriate action. Hunt down pranksters later.
Blaming individuals and demanding job losses will not help anyone. Do you think that controller, or anyone else involved, will ever take a potential emergency lightly again?
Learn and move on.

Demandit's picture

I'm a center controller and a majority of my co-controllers think a turbo prop is a plane with a "turbo" on the engine. Some beleive a C130 is a cessna. Less than 10 percent even begin to know what a VOR is led alone a VORTAC. Procedure turn? Please. You wanna shoot a GPS approach, you better ask for the initial you want cause they'll let you fly right past it while your thinking they know whats best for you. Soup, no idea what your talking about. Icing, you better "maintain 6800, thats my lowest altitude". Theres a new breed out there and they know even less the previous generation. I could go on for hours... "what do you mean a new C172 costs 300 grand, they only go 80 mph". Just got that response the other day. This controller in the tower is the new typical. Theres some pretty sharp ones coming along, but were few and far between. DEMANDIT

Tenerifediver's picture

I agree with Bruce B.
Why oh why are so many aviation 'professionals' so willing to constantly ignore the ICAO standard phraseology that was brought in for just this kind of event?
A Pan or Mayday followed by the FULL callsign might have helped a bit too.
I get sick of hearing this so frequently, particularly in my field as an aviation English teacher in the CIS.
These guys here are going to leave you guys behind, as they are more than willing to follow the rules. particularly given their often undeserved reputation.
It's time everybody sung off the same hymn sheet and leave the Hollywood-speak to the likes of Charlie Sheen!

aeropapa's picture

While I agree it's hard to know how we would act in an emergency, I know that the pilot's first words should have started with "Mayday". Frankly if I had heard the pilot's transmissions out of context, I too would have thought it was a hoax. He sounded just like what I think a teenage prankster would say. That being said, the controller certainly had a responsibility to treat it as legitimate until he could prove it wasn't. My final score: pilot's blame - 20% , controller's fault - 80%

Top Rated

Your Comment
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
All submitted comments are subject to the license terms set forth in our Privacy Policy and Terms of Use