Xjet Denver incident

triple7

Well-Known Member
If nothing else,this illustrates why we need to be paid more. I knew the ca, FA, and I believe the fo was very new. Engine failure on final and cockpit/cabin filled with smoke so thick they couldn't see out the window. From my understanding they landed using ra call outs by the fo... I'm very impressed.

By Simon Hradecky, created Tuesday, Apr 3rd 2012 21:05Z, last updated Tuesday, Apr 3rd 2012 21:05Z
An Expressjet Embraer ERJ-145 on behalf of United, registration N15973 performing flight EV-5912/UA-5912 from Peoria,IL to Denver,CO (USA) with 22 people on board, was cleared to land on runway 34R. Tower controller was issuing instructions to other aircraft when he interrupted in surprise at 08:33L (14:33Z) and exclaimed "he hit the lights" followed by "runway 34R is closed" instructing the next arriving aircraft to cancel approach clearance, maintain 9000 feet and continue on the localizer, all airport frequencies began to report an ongoing emergency on the airport, traffic on runway 34L and departures on runway 25 were also temporarily halted. The Embraer rolled out and stopped on the runway remaining there disabled, tower advised emergency services were deploying. The crew of another aircraft advised they were observing the landing and they had the impression the Embraer had hit the approach lights then touched down really hard but when they taxied closer to have a look onto the aircraft it didn't appear they would have struck the lights but they aren't sure, tower commented in response they'll have the approach and runway lights inspected. The Embraer was evacuated due to smoke on board.

The airport reported the crew reported smoke in the cockpit, the aircraft was evacuated. One passenger was taken to a hospital, the extent of injuries was not known. The aircraft remained disabled on the runway, the runway was closed for 2.5 hours.

The airline reported the aircraft was evacuated onto the runway because of smoke on the aircraft.

http://flightaware.com/live/flight/ASQ5912/history/20120403/1230Z/KPIA/KDEN

Metars:
KDEN 031553Z 33014KT 3/4SM R35L/3500V5000FT -SN BR BKN005 OVC017 00/M02 A3019 RMK AO2 SLP229 P0004 T00001017
KDEN 031453Z 32013KT 1/2SM R35L/3500V4500FT -SN FG BKN003 OVC013 00/M01 A3018 RMK AO2 TWR VIS 3/4 SLP224 P0004 60013 T00001011 51015
KDEN 031440Z 32011KT 1/2SM R35L/3500V4500FT -SN FG SCT003 BKN011 OVC028 00/M01 A3018 RMK AO2 TWR VIS 3/4 P0004
KDEN 031422Z 33012KT 1/2SM R35L/3000V3500FT SN FZFG SCT003 OVC009 M01/M02 A3017RMK AO2 TWR VIS 3/4 P0002
KDEN 031404Z 34013KT 1/2SM R35L/3000V4500FT -SN FZFG SCT005 OVC013 M01/M02 A3016 RMK AO2 TWR VIS 3/4 P0001
KDEN 031353Z 35013KT 3/4SM R35L/4000V5500FT -SN BR SCT005 OVC015 M01/M02 A3016 RMK AO2 SLP217 P0006 T10061017
KDEN 031449Z 31013KT 3/4SM R35L/4000V5000FT -SN BR BKN003 OVC013 00/M01 A3018 RMK AO2 P0004
KDEN 031322Z 35011KT 1 1/4SM R35L/5500VP6000FT -SN BR BKN005 OVC013 M01/M02 A3014 RMK AO2 P0003
KDEN 031305Z 35013KT 2SM -SN BR OVC007 M01/M02 A3013 RMK AO2 P0001
KDEN 031253Z 36012KT 1 1/4SM R35L/6000VP6000FT -SN BR OVC005 M01/M02 A3013 RMK AO2 SLP206 P0003 T10061017
KDEN 031246Z 36013KT 3/4SM R35L/4500VP6000FT -SN BR OVC005 M01/M02 A3012 RMK AO2 P0003
KDEN 031232Z 36016KT 3/4SM R35L/3500V4500FT -SN BR BKN003 OVC008 M01/M02 A3011 RMK AO2 P0002
KDEN 031209Z 01014G21KT 1 1/4SM R35L/6000VP6000FT -SN BR OVC003 M01/M02 A3010 RMK AO2 P0001
KDEN 031153Z 35015KT 3/4SM R35L/5000VP6000FT -SN BR BKN003 OVC008 00/M01 A3009 RMK AO2 PK WND 36027/1110 SLP190 P0003 60011 70013 T00001011 10017 20000 55015



Reader Comments:
Weather
By Erik on Wednesday, Apr 4th 2012 14:48Z

The weather was crappy! Low ceilings and it was a mix of snow and freezing drizzle.

Weather at the time....
By Brian on Wednesday, Apr 4th 2012 04:47Z

According to ADDS, the metars at 1422Z (8:22 MT) and 1440Z (8:40 MT) are as follows:

KDEN 031440Z 32011KT 1/2SM R35L/3500V4500FT -SN FG SCT003 BKN011 OVC028 00/M01 A3018 RMK AO2 TWR VIS 3/4 P0004

KDEN 031422Z 33012KT 1/2SM R35L/3000V3500FT SN FZFG SCT003 OVC009 M01/M02 A3017 RMK AO2 TWR VIS 3/4 P0002

According to the last radar hit was at 8:31am at 6000' (approx 500-600 agl).

Not a nice morning.

weather?
By Steve on Wednesday, Apr 4th 2012 03:00Z

Anyone know what the weather was at time?

Active Fire
By Erik on Wednesday, Apr 4th 2012 02:56Z

While listening to the emergency operations during the Alert, a firefighter made reference to an active fire in the cockpit, and deployed an agent to stop the fire. The firefighter then reported back to command that the Halon extinguished the fire. Then advised command of only seeing hot spots behind an electrical panel.

The captain also mentioned to the fire chief that he activated the fire suppression system in the rear cargo pit. Another ARFF crew checked the rear pit, but only reported a haze from the Halon.



By Paulo on Wednesday, Apr 4th 2012 00:34Z

Either way, MSA 360º around the airport is 9200'. 9000' isn't "a tad too high" :)


By Paulo on Wednesday, Apr 4th 2012 00:31Z

(continued)
MSL 5351 (darn keyboard)


By Paulo on Wednesday, Apr 4th 2012 00:30Z

According to the charts (KDEN, ILS RWY 34R (Cat II or even CAT III), you should be at 10.000ft over BOOBU then descent to 9000' to be leveled at BENGL and then maintain 9000' till RLESS (about 4.7nm), following the G/S from there until you land at KDEN, MSL.

Mile High City
By (anonymous) on Tuesday, Apr 3rd 2012 21:48Z

Denver is 5400 ft MSL.


By John Doe on Tuesday, Apr 3rd 2012 21:37Z

When referring to the 'next arriving aircraft', had the aircraft already intercepted the localiser at 9,000 feet (AAL presumably)? Surely that's a tad too high?

Add your comment: (max 1024 characters)
Your IP address 174.232.132.65 is being tracked. We reserve the right to remove any comment
for any reason. Profanities, personal attacks (against any physical or legal person),
false statements or similiar as well as copyrighted materials from third parties will not
be tolerated, those messages will summarily be deleted. Links and mail addresses are
not permitted and will not appear in the display, posts trying to circumvent the
restriction of links/mail addresses will be removed. We ask for your valid e-mail address
in the email field. This address is only used by us to establish contact with you in case
of further questions, it will not be displayed anywhere or be used otherwise.
 
So that was the emergency! I was coming in from YQR and we were told the runway had changed due to an emergency aircraft.
 
Incredible story. No glory though, if it were mainline UAL you know it would be front page of CNN.
 
RJ or not, I'm surprised the news hasn't picked up on this. Crazier than most all of the the emergency landings that make the news in the Bay Area.
 
Related article-

http://www.9news.com/news/article/261127/339/Controller-during-emergency-landing-Thats-BS


Air controller during emergency landing: 'I know that's BS'


Video: Air controller during emergency landing: 'I know that's BS'

DENVER - NTSB investigators and Federal Aviation Administration officials are investigating air traffic controllers' actions at Denver International Airport's main control tower Tuesday morning during an emergency landing.

Investigators are looking at whether controllers' confusion delayed first responders as the plane was on its final approach, 9NEWS Aviation Analyst Greg Feith, a former NTSB investigator, said.

Only one of the 21 people on board the plane was taken to the hospital after the incident.

Tuesday morning around 8:30, United Express Flight 5912, operated by ExpressJet, declared an emergency landing during its final approach to DIA after being cleared to land, according to a control-tower recording provided by an FAA source. The emergency landing was because of smoke in the cockpit.

On the recording, a voice from the cockpit, either the co-pilot or pilot, is heard saying, "Emergency, smoke in the cockpit, roll trucks, please."

A controller in the tower responds, asking, "Who was that?"

The voice responded, "5912."

The controller responds, after about 10 seconds, asking, "United 12, what's your position?"

After no response, more time elapses and the controller asks someone, "Did you hear that? I know that's BS. I know it is."

Another controller responds, "That's what?"

The first controller responds, "United 12. You know of United 12 anywhere?"

Feith says the controller may have been distracted, only hearing the last part of the flight number.

"So when they hear an oddball number," Feith said, "whether it's real or perceived, like in this case United 12. That's a bogus number so all of a sudden now you're spring-loaded towards, 'That's a phantom call.'"

Although rare, Feith says phantom or fake calls can originate from someone near the airport on the same frequency as the control tower.

"It's very complex because we've had these bogus calls in the past," Feith said.

"It sounded like somebody just (sic) on a handheld somewhere to me," the controller said later in the recording. "Did you hear that though?"

Another controller responds, "Yeah, I did."

"That didn't sound good," the first controller said.

"I know," responded the other controller.

The controllers then direct other traffic for another 30 seconds when the pilot makes another emergency call saying the plane had landed and was evacuating on the runway.

The controller tries to verify with the pilot, but after no response, he tells another pilot, "I apologize if you probably heard [something] there. That's not real. They're what we're hearing on the frequency."

Ultimately, nearly five minutes passed before the controller confirms to the pilot help is on the way, according to the recording.

According to his sources, Feith, said fire trucks did not deploy until after the plane had landed on the runway.

A passenger on flight 5912, Linda Irwin, says she saw smoke in the cabin during the landing, and said the pilot and co-pilot landed the plane extremely well, considering snowy conditions and smoke in the cockpit.

She also says the flight attendant remained calm during the evacuation from the front of the plane.

Irwin learned of the control tower recordings Thursday.

"One would hope that with all of the investigations that go on after any incident, one would hope that those communications would be checked out because when there are lives at stake," she said. "You don't want to make assumptions about what's real, what's not real. What's serious and what's not serious, you want to go with the worst case scenario and make sure you've addressed it."

Feith says NTSB investigators are looking at whether the Embraer 145 regional jet's right engine failed during final approach.

An FAA report says firefighters extinguished a fire in the instrument panel.

(KUSA-TV © 2012 Multimedia Holdings Corporation)
 
"One would hope that with all of the investigations that go on after any incident, one would hope that those communications would be checked out because when there are lives at stake," she said. "You don't want to make assumptions about what's real, what's not real. What's serious and what's not serious, you want to go with the worst case scenario and make sure you've addressed it."

Feith says NTSB investigators are looking at whether the Embraer 145 regional jet's right engine failed during final approach.

An FAA report says firefighters extinguished a fire in the instrument panel.

Sounds like the controller only heard part of the transmission. That happens. Unlike Podunk, USA airport, there's likely not alot of time to figure out what it was with all the other traffic being worked. And the flightcrew was likely too busy trying to get the plane on the ground to correct the transmission on short final. Good thing is, it all worked out in the end. Emergencies often share one of the same issues that's seen in combat: first thing to go to hell in a handbasket is comms.
 
Yeah, the slides coming out aren't real. All those people running around outside, also not real.

After they touched down, yes. Prior to that, likely lots of confusion over one transmission that seems to not have been fully heard.
 
Sounds like the controller only heard part of the transmission. That happens. Unlike Podunk, USA airport, there's likely not alot of time to figure out what it was with all the other traffic being worked. And the flightcrew was likely too busy trying to get the plane on the ground to correct the transmission on short final. Good thing is, it all worked out in the end. Emergencies often share one of the same issues that's seen in combat: first thing to go to hell in a handbasket is comms.

Aviation, Navigate, Communicate.

Handle it, secure it, talk about it when you can. Assume you're going to be on your own.
 
Back
Top