37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 987027 |
Time | |
Date | 201201 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | LAX.Tower |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Flight Data / Clearance Delivery |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
I was working clearance delivery/flight data (clearance delivery/FD) when I noticed the flm walking over to the south side of the tower; between local assist 1 and ground control 1. I looked over there to see a B757; an arrival to the inboard runway 25R; just touching down. Local control 1 immediately told a B737 (the #1 in line to depart 25R) to line up and wait on runway 25R. Another 25R arrival was about 5 miles out. The B757 started to exit at B6; but stopped before reaching taxiway B. The B757's tail was still well past the hold bars; on runway 25R. Local control 1 cleared the B737 for take off; and then asked ground control 1 to keep the B757 moving. Local control 1 knew the B757 was not fully off the runway. As the B737 began take off roll; the flm started saying 'keep him moving;' as if trying to will the B757 off the runway before the B737 passed them. It did not work. The B757 had just started to move again; tail still not past the 25R hold bars; when the B737 passed the B757 about 50 ft above them. I believe that the only reason that the asde-X did not go off; was because the B757's tag on the asde-X was spinning and jumping back and for forth around the intersection. I can't really recommend anything; the reason is; because in order to change; you first have to care. In my time at lax; it has been explicitly clear to me that lax tower does not care about safety. Their management will read you mandatory safety briefings and roll their eyes at it. They push the safer controllers to move more traffic; and turn their backs on the controllers who move the traffic while breaking the rules. They watch runway incursions happen and then say that they 'dropped their pen and saw nothing'. I know that no facility can be perfect; and that everyone makes mistakes. However; there is a difference in following the rules and making a mistake; and completely disregarding the rules entirely. Lax has such a horrific safety incident history because no one there cares to follow the rules; and as long as management can be absolved from a controllers 'mistake'; then management will continue to push to unsafely move the traffic; and continue turn their back to any rule breaking.
Original NASA ASRS Text
Title: LAX Controller described a probable loss of separation event when a landing aircraft had not yet cleared the runway with a departure flying overhead; the reporter voicing concern regarding LAX management as condoning these types of safety concerns.
Narrative: I was working Clearance Delivery/Flight Data (CD/FD) when I noticed the FLM walking over to the south side of the Tower; between Local Assist 1 and Ground Control 1. I looked over there to see a B757; an arrival to the inboard Runway 25R; just touching down. Local Control 1 immediately told a B737 (the #1 in line to depart 25R) to line up and wait on Runway 25R. Another 25R arrival was about 5 miles out. The B757 started to exit at B6; but stopped before reaching Taxiway B. The B757's tail was still well past the hold bars; on Runway 25R. Local Control 1 cleared the B737 for take off; and then asked Ground Control 1 to keep the B757 moving. Local Control 1 knew the B757 was not fully off the runway. As the B737 began take off roll; the FLM started saying 'keep him moving;' as if trying to will the B757 off the runway before the B737 passed them. It did not work. The B757 had just started to move again; tail STILL not past the 25R hold bars; when the B737 passed the B757 about 50 FT above them. I believe that the only reason that the ASDE-X did not go off; was because the B757's tag on the ASDE-X was spinning and jumping back and for forth around the intersection. I can't really recommend anything; the reason is; because in order to change; you first have to care. In my time at LAX; it has been explicitly clear to me that LAX Tower does not care about safety. Their management will read you mandatory safety briefings and roll their eyes at it. They push the safer controllers to move more traffic; and turn their backs on the controllers who move the traffic while breaking the rules. They watch runway incursions happen and then say that they 'dropped their pen and saw nothing'. I know that no facility can be perfect; and that everyone makes mistakes. However; there is a difference in following the rules and making a mistake; and completely disregarding the rules entirely. LAX has such a horrific safety incident history because no one there cares to follow the rules; and as long as management can be absolved from a controllers 'mistake'; then management will continue to push to unsafely move the traffic; and continue turn their back to any rule breaking.
Data retrieved from NASA's ASRS site as of July 2013 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.