37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 516529 |
Time | |
Date | 200104 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : lax.airport |
State Reference | CA |
Altitude | msl bound lower : 5000 msl bound upper : 6000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : lax.tower tower : gmu.tower |
Operator | common carrier : air carrier |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : lax.tower |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 2600 flight time type : 1200 |
ASRS Report | 516529 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : ground critical non adherence : clearance non adherence : required legal separation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : took evasive action flight crew : executed go around flight crew : took precautionary avoidance action |
Miss Distance | horizontal : 4500 vertical : 500 |
Supplementary | |
Problem Areas | Environmental Factor Airspace Structure Airport ATC Human Performance Flight Crew Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
My aircraft was on a visual approach to runway 24L at lax. We were staggered behind another company aircraft on approach to runway 24R. As we descended through approximately 1000 ft MSL on final, tower crossed an aircraft that had landed on runway 24R across runway 24L. This was accomplished without incident and was no factor to us as we were still at 2 mi final. As we descended through 5600 ft MSL on 3/4 mi final, tower instructed air carrier B737 holding short for takeoff to cross runway 24L and hold short runway 24R. I was shocked to hear this instruction as we were on very short final but were unable to make any calls due to radio congestion. The thought that I had heard in error crossed my mind so I watched the B737 closely and decided that if in fact they did cross the hold line and incur the runway I was approaching, I would go around. The air carrier aircraft apparently saw us and applied a great deal of power to expedite their crossing. In their position, I would have refused to move, held short, and questioned the controller as the instruction was obviously a mistake. As they passed the hold short line, I applied power and initiated the go around. Before the nose obscured the runway, I noticed that the B737 was racing across the runway, apparently in the hope that I would accept their crossing and continue my landing. I, however, was not going to play that game. Due to the tower's almost continuous instructions to various aircraft, neither I nor my first officer were able to call our go around. The tower called us and instructed us to climb to 2000 ft and maintain runway heading. We were vectored back for approach and landed uneventfully. As an air carrier pilot who has operated out of lax for 2 yrs, I know full well how busy that airport is and I appreciate the effort the controllers put into expediting traffic flow. However, this was well over the line. To cross an aircraft that is static with traffic approximately 20 seconds from touchdown is unconscionable. If the controller had just waited 20 seconds for me to land, then crossed the B737, there would have been no need for paperwork and no risk of disaster.
Original NASA ASRS Text
Title: ON SHORT FINAL AT LAX FOR RWY 24L, LCL CTLR ISSUES XING CLRNC TO B737 CAUSING AN 3120 TO EXECUTE A GAR.
Narrative: MY ACFT WAS ON A VISUAL APCH TO RWY 24L AT LAX. WE WERE STAGGERED BEHIND ANOTHER COMPANY ACFT ON APCH TO RWY 24R. AS WE DSNDED THROUGH APPROX 1000 FT MSL ON FINAL, TWR CROSSED AN ACFT THAT HAD LANDED ON RWY 24R ACROSS RWY 24L. THIS WAS ACCOMPLISHED WITHOUT INCIDENT AND WAS NO FACTOR TO US AS WE WERE STILL AT 2 MI FINAL. AS WE DSNDED THROUGH 5600 FT MSL ON 3/4 MI FINAL, TWR INSTRUCTED ACR B737 HOLDING SHORT FOR TKOF TO CROSS RWY 24L AND HOLD SHORT RWY 24R. I WAS SHOCKED TO HEAR THIS INSTRUCTION AS WE WERE ON VERY SHORT FINAL BUT WERE UNABLE TO MAKE ANY CALLS DUE TO RADIO CONGESTION. THE THOUGHT THAT I HAD HEARD IN ERROR CROSSED MY MIND SO I WATCHED THE B737 CLOSELY AND DECIDED THAT IF IN FACT THEY DID CROSS THE HOLD LINE AND INCUR THE RWY I WAS APCHING, I WOULD GO AROUND. THE ACR ACFT APPARENTLY SAW US AND APPLIED A GREAT DEAL OF PWR TO EXPEDITE THEIR XING. IN THEIR POS, I WOULD HAVE REFUSED TO MOVE, HELD SHORT, AND QUESTIONED THE CTLR AS THE INSTRUCTION WAS OBVIOUSLY A MISTAKE. AS THEY PASSED THE HOLD SHORT LINE, I APPLIED PWR AND INITIATED THE GAR. BEFORE THE NOSE OBSCURED THE RWY, I NOTICED THAT THE B737 WAS RACING ACROSS THE RWY, APPARENTLY IN THE HOPE THAT I WOULD ACCEPT THEIR XING AND CONTINUE MY LNDG. I, HOWEVER, WAS NOT GOING TO PLAY THAT GAME. DUE TO THE TWR'S ALMOST CONTINUOUS INSTRUCTIONS TO VARIOUS ACFT, NEITHER I NOR MY FO WERE ABLE TO CALL OUR GAR. THE TWR CALLED US AND INSTRUCTED US TO CLB TO 2000 FT AND MAINTAIN RWY HDG. WE WERE VECTORED BACK FOR APCH AND LANDED UNEVENTFULLY. AS AN ACR PLT WHO HAS OPERATED OUT OF LAX FOR 2 YRS, I KNOW FULL WELL HOW BUSY THAT ARPT IS AND I APPRECIATE THE EFFORT THE CTLRS PUT INTO EXPEDITING TFC FLOW. HOWEVER, THIS WAS WELL OVER THE LINE. TO CROSS AN ACFT THAT IS STATIC WITH TFC APPROX 20 SECONDS FROM TOUCHDOWN IS UNCONSCIONABLE. IF THE CTLR HAD JUST WAITED 20 SECONDS FOR ME TO LAND, THEN CROSSED THE B737, THERE WOULD HAVE BEEN NO NEED FOR PAPERWORK AND NO RISK OF DISASTER.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.