37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1212392 |
Time | |
Date | 201410 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | A380 |
Operating Under FAR Part | Part 129 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
While working combined LC1/LC2 (local control) shortly after our midnight traffic turned to over ocean procedures; ground control passed aircraft X's flight strip for departure off runway 24L. The north complex is used for opposite direction arrival traffic while the south complex is used for departures so it was a non standard situation already. Due to the many airport restrictions aircraft X could not make it to the south side of the airport as planned. Rather than delaying our over ocean traffic procedures to allow the (multiple) aircraft X type departures our flm chose to allow the unsafe situation to develop. I coordinated with the sct arrival area to build me a hole so that I could depart the north complex opposite direction. While aircraft X was going into position I noticed that the arrival aircraft (aircraft Y) had already begun to turn base despite the fact that the previously coordinated traffic had not yet begun to even roll for departure. I issued an immediate left turn heading 210 (standard over ocean departure procedure) to aircraft X. After every aircraft X type departure we are required to conduct a runway inspection afterwards so I coordinated with arrivals for aircraft Y to land on the parallel runway (6L) and issued an south turn to the north for spacing. While aircraft X was departing and turning the proximity became less than the required and visual separation could not be used since the type aircraft was a type where visual separation cannot be applied. The over ocean operation at lax is a dangerous situation. With the growing impact of design group 6 aircraft during the known traffic turn around it should be delayed or removed as a standard operation. Aircraft pushed off gate onto east well before the traffic turn around and when they were not imminently ready it led to this situation because it was stuck going to runway 24L since it has no other option to turn the aircraft around. There is only 1 taxiway available and to use the runway would mean that they have to taxi the length of the runway before it could exit and get to the south complex. Our over ocean operations tells us to issue a turn of 210 (not enough to provide 45 degree course divergence; 205 at least needed) and to use visual separation with our departure/arrival traffic but this cannot be done when there is this type of aircraft involved so we should not be faced with an impossible situation. If we were not forced to use over ocean traffic (at midnight) then this situation would have been completely routine.
Original NASA ASRS Text
Title: LAX Local Controller describes a loss of separation during a opposite direction operation.
Narrative: While working combined LC1/LC2 (local control) shortly after our midnight traffic turned to over ocean procedures; Ground Control passed Aircraft X's flight strip for departure off runway 24L. The north complex is used for opposite direction arrival traffic while the south complex is used for departures so it was a non standard situation already. Due to the many airport restrictions Aircraft X could not make it to the south side of the airport as planned. Rather than delaying our over ocean traffic procedures to allow the (multiple) Aircraft X type departures our FLM chose to allow the unsafe situation to develop. I coordinated with the SCT arrival area to build me a hole so that I could depart the north complex opposite direction. While Aircraft X was going into position I noticed that the arrival aircraft (Aircraft Y) had already begun to turn base despite the fact that the previously coordinated traffic had not yet begun to even roll for departure. I issued an immediate left turn heading 210 (standard over ocean departure procedure) to Aircraft X. After every Aircraft X type departure we are required to conduct a runway inspection afterwards so I coordinated with arrivals for Aircraft Y to land on the parallel runway (6L) and issued an S turn to the north for spacing. While Aircraft X was departing and turning the proximity became less than the required and visual separation could not be used since the type aircraft was a type where visual separation cannot be applied. The over ocean operation at LAX is a dangerous situation. With the growing impact of design group 6 aircraft during the known traffic turn around it should be delayed or removed as a standard operation. Aircraft pushed off gate onto E well before the traffic turn around and when they were not imminently ready it led to this situation because it was stuck going to runway 24L since it has no other option to turn the aircraft around. There is only 1 taxiway available and to use the runway would mean that they have to taxi the length of the runway before it could exit and get to the south complex. Our over ocean operations tells us to issue a turn of 210 (not enough to provide 45 degree course divergence; 205 at least needed) and to use visual separation with our departure/arrival traffic but this cannot be done when there is this type of aircraft involved so we should not be faced with an impossible situation. If we were not forced to use over ocean traffic (at midnight) then this situation would have been completely routine.
Data retrieved from NASA's ASRS site 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.