LAX Close Call

Instinct

New Member
http://www.latimes.com/news/printedition/la-me-lax29jul29,0,1299374.story?track=mostviewed-homepage
From the Los Angeles Times
Pilot Narrowly Averts Collision at LAX

By Jennifer Oldham
Times Staff Writer

July 29, 2006

Two small airliners on the ground at Los Angeles International Airport came within moments of colliding earlier this week after a malfunctioning system designed to alert controllers to potential collisions was partially disabled.

The pilot of one of the planes, which was taking off, averted disaster by pulling up suddenly — risking a stall — to avoid a regional jet that had just landed and strayed onto its runway. He cleared the aircraft by less than 50 feet, according to initial reports from the control tower.

Controllers described the incident as the closest call they have seen at LAX in seven years.

The incident began about 4 p.m. Wednesday, after America West Flight 6008 from Phoenix landed on the airport's southernmost runway. Controllers instructed the pilot to leave the runway on a taxiway known as "Mike" and stop short of the inner runway.

Even though the pilot read back the instructions correctly, he drove onto the inner runway and into the path of a departing United Express turboprop, said Laura Brown, a Federal Aviation Administration spokeswoman.

Horrified controllers watched the incident unfold from the LAX tower.

"Traffic unauthorized crossing downfield!" a controller yelled into the radio to warn the United Express pilot, who told authorities that he pulled up early after hearing the transmission.

Brown said the United Express pilot was "past the point where he could have stopped."

"It was fortunate in this case that the air traffic controller noticed the conflict and immediately alerted the pilot," she said, adding that a preliminary FAA investigation showed the vertical distance between the two aircraft was "less than 150 feet."

United Express Flight 6037 to Monterey, Calif., was taking off less than halfway down the runway in what's known as an "intersection departure."

Because of the incident, the city's airport agency said Friday that it will call a meeting of the FAA, pilots and airline officials to review "specifically whether midfield takeoffs are in the best interests of everyone's safety."

It's likely that the close call will be classified by the FAA as a Category A or Category B, the two most serious designations, Brown said. Officials attributed the incident to an error by the America West pilot, who told investigators he "got confused" when he reached "hold bars" on the taxiway that indicated where he was supposed to stop and instead continued forward onto the runway.

Controllers said the incident is likely to be deemed the most serious near-collision at LAX since Nov. 22, 1999, when an Aeromexico MD-80 that had just landed mistakenly crossed a runway on which a United Boeing 757 was taking off. The United pilot saw the Aeromexico jet and quickly got airborne, clearing it by 100 feet. Former Republican presidential contenders Bob and Elizabeth Hanford Dole were aboard the United flight.

Wednesday's incident came less than two weeks after a power outage and radar failure at a Palmdale center that controls high-altitude flights snarled air traffic across the country and prompted concerns about the vulnerability of the backup power system.

At the time of this week's incident, an audible alarm on a ground radar system designed to warn controllers that planes are too close was not operating, Brown said. Officials in the tower shut off the alarm after the system put out a false alert, but controllers could still see airplanes on the screen, she added.

Had the alarm been on, controllers said, they might have had a chance to warn the United Express pilot to abort his takeoff.

The incident marked the second time in less than a week that a close call between two aircraft occurred when the radar system, known as AMASS, or Airport Movement Area Safety System, was not operating properly. In Chicago on Sunday, a departing United Airlines Boeing 737 came within 300 feet of colliding with a Boeing 747 cargo plane on an intersecting runway at O'Hare International Airport. The incident was attributed to controller error.

The FAA hoped that AMASS, which the agency began installing at busy U.S. airports in the late 1990s, would help prevent collisions. Safety experts have criticized the equipment, which is prone to false alarms that sometimes prompt controllers to shut down the system.

Controllers also say that they are forced to shut the equipment off during bad weather because sheets of rain show up on the screen. Some experts question whether the system gives controllers adequate time to respond to its signals.

Experts say federal officials need to focus on communication between pilots and air traffic controllers as part of efforts to eliminate close calls.

"AMASS has a lot of serious problems," said Najmedin Meshkati, a professor of engineering the Viterbi School of Engineering at USC who studies aviation safety and runway incursions. "We really need to concentrate on human factors and not get bogged down in technological fixes."

With an ever-increasing number of takeoffs and landings at the nation's crowded airports, safety experts have warned that potential collisions between aircraft on the ground remain one of the biggest threats to commercial aviation today.

The rate of close calls at LAX has remained high despite years of efforts by local and federal officials to ensure that pilots and controllers follow federal rules allowing only one plane at a time on or near a runway. Among the nation's airports, LAX is unusual because airplanes cross active runways about 900 times a day.

There have been six close calls at LAX this year, compared with five for a similar period in 2005.

Wednesday's close call at LAX occurred just days before the city's airport agency is scheduled to start construction on the southern runway complex that it hopes will reduce near-collisions.

Officials will shut down the airport's southernmost runway, known as 25L, today and start rebuilding it 55 feet closer to El Segundo. In March, the agency will reopen the runway and start building a center taxiway in between the two runways to the south of the terminals.

Local and federal aviation officials hope that by separating the runways and installing a center taxiway, they will be able to significantly reduce close calls at LAX. About 80% of such incidents occur on the airport's south side after pilots land on the outer runway and use taxiways to cross the inner runway on their way to the terminals.

"The whole reason we have them tearing up the runway is so we don't have them peeling off the runway at a high speed," said Diane Aceves, a controller at LAX and local president of the National Air Traffic Controllers Assn.

"Hopefully that will eliminate a lot of the runway incursions," Aceves said.
 
psalm91 said:
Le Whoops. Wouldn't wanna be in the debrief for this one.

Me neither. It's frustrating too see such an incursion occur, when it seems it could have been avoided easily by the AW crew. If you are going to be crossing an active runway, common sense dictates to look both ways before proceeding. It's just hard to understand how the crew did not see the EMB taking-off on the runway they were crossing.

I guess this close call can be related to a similar scenario while driving. Joe is the first in line at a busy 4-way stop light. The mili-second his light turns green, Joe punches the gas and enters the intersection, thinking it is safe to proceed. However some yahoo is in a hurry (or drunk) and decides to blow the red light that JUST turned red...yahoo is thinking, well the light just turned red a mili-second again, I should be safe.

Joe ends up being T-boned by yahoo.

This scenario can even occur if Joe's view of the intersection is blocked by a truck in the lane to his left. Light turns green, Joe enters intersection without being able to see what's coming from the left...BOOM. I always let the truck start moving in that situation.
 
I think a lot of us got used to how "high speeds" work at more modern airports. But if you take a "high speed" at LAX thinking you've got a lot room to slow down before the runway threshold, you're probably going to have a runway incursion.
 
Officials attributed the incident to an error by the America West pilot, who told investigators he "got confused" when he reached "hold bars" on the taxiway that indicated where he was supposed to stop and instead continued forward onto the runway.

Now I know people make mistakes all the time, but this is a big one here. He read back the hold short instructions, yet got "confused" and still crossed the hold line?

Something doesn't sound right about this one.

Also isn't it common practice to check for traffic priot to crossing an active runway? I know I do, ATC makes mistakes sometimes also.

I have to wonder if there is more to this story.
 
I haven't read the report, but here are some "thoughts":

a. The high speeds are extraordinarily short in LAX.
b. The FO generally does the talking, and the captain has control of the tiller and the brakes during taxi. There are times that I've had to exclaim "Stop! Stop! Stop!" and I even hit the brakes in BOS once.
c. Some people do 'secretarial work' like confirming the arriving gate or running after landing checklists while holding short, which is bad.
d. Gotta brief the hell out of LAX because people get in trouble there every day!
 
Doug Taylor said:
I haven't read the report, but here are some "thoughts":

a. The high speeds are extraordinarily short in LAX.
b. The FO generally does the talking, and the captain has control of the tiller and the brakes during taxi. There are times that I've had to exclaim "Stop! Stop! Stop!" and I even hit the brakes in BOS once.
c. Some people do 'secretarial work' like confirming the arriving gate or running after landing checklists while holding short, which is bad.
d. Gotta brief the hell out of LAX because people get in trouble there every day!

Once again your experience sheds some more light on things.

I can see this being a workload related thing, if they are pre-occupied with "Secretarial duties" during the taxi.

I think this can be a good lesson for all of us about screwing around with checklists and non-sense while rolling.
 
Officials will shut down the airport's southernmost runway, known as 25L, today and start rebuilding it 55 feet closer to El Segundo.

Damn, that means plane spotting from imperial hill wont be that good for a while. I presume 25R will stay open.

Is this the point of incursion?

800px-LAX_airport_map.png
 
I wonder if it's "politics" as usual in the cockpit. If the FO was taxiing at that time and went across the hold short lines onto the other runway, will the captain possibly face punishment or investigation as well??
 
I'm actually in LA on an overnight now... and believe it or not... I was on Imperial Hill today too! Didn't see the incident... but I'm sure we'll brief the hell out of it tonight when we leave for the red-eye back home.

Boeing 777-300, There are no runwaway closures at this time due to this incident...

Musketeer... the FO's don't Taxi... only the Captains due to the tiller being on his side... but... like Doug inferred... the brakes on both sides work! But... to answer the "spirit" of your question... the Captain is PIC... so if an FO screws up... then the Captain can and most likely will be cited for the incident.

Bob

PS: Saw John Travolta's 707 in Parked in LAX today too.
 
MusketeerMan said:
I wonder if it's "politics" as usual in the cockpit. If the FO was taxiing at that time and went across the hold short lines onto the other runway, will the captain possibly face punishment or investigation as well??

Even if the FO was taxiing, what FO's traditionally don't do at the airlines, the Captain is still at fault because he's the pilot-in-command.

Violations come in pairs in the airline business.
 
Captain_Bob said:
PS: Saw John Travolta's 707 in Parked in LAX today too.

I was at LAX on the 16th, it was there, so I think it's been there since before then.

We were United 1003, 757, for Kona (PHKO) departing 25R there was a KLM (I think) 744 landing just before us on 25L- By the time we got down a ways, you could see the 74 holding, barely contained in the bars, close.
 
LAX ATC has been on a terring spree. They yelled at me to taxi faster a few days ago. Then last night they yelled at a AA 767 to taxi faster.
 
mrivc211 said:
LAX ATC has been on a terring spree. They yelled at me to taxi faster a few days ago. Then last night they yelled at a AA 767 to taxi faster.

Uhmm, what gives them that authority in the first place...

LAX was a disaster today...this flow control program due to overcast and runway construction is insane. :confused:
 
Back
Top