 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Lax tower local assist reported releasing an aircraft off smo. There was a loss of separation between it and a lax departure.
| Attributes | |
| ACN | 1421022 |
| Time | |
| Date | 201701 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | LAX.Tower |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID FIXIT4 |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Handoff / Assist Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.9 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Was working LA2 (local assist) during a very busy time. Fixit departures were on; requiring additional in trail spacing; which was adding complexity to the already busy traffic. I had a sequence set for aircraft Y off of smo but when I requested release from malibu sector they were overwhelmed and needed to call me back. Meanwhile the fixit departures were canceled and we went back to regular spacing; which changed the sequence again. Instead of giving smo a '1 min heads up' for departure I told them it would be a while because I was waiting for malibu to call me back. Smo holds all departures back from the runway due to noise and pollution restrictions at their airport; we give them the 1 min warning so they can taxi the aircraft out to be ready to go. We had one last departure rolling when malibu called and released aircraft Y. I released aircraft Y off of smo thinking the aircraft would still need to taxi out for departure. But both aircraft ended up airborne at the same time. Just under 4 miles apart. In the future I will verify with smo where there aircraft is to ensure separation.
Original NASA ASRS Text
Title: LAX Tower Local Assist reported releasing an aircraft off SMO. There was a loss of separation between it and a LAX departure.
Narrative: Was working LA2 (Local Assist) during a very busy time. FIXIT departures were on; requiring additional in trail spacing; which was adding complexity to the already busy traffic. I had a sequence set for Aircraft Y off of SMO but when I requested release from Malibu sector they were overwhelmed and needed to call me back. Meanwhile the FIXIT departures were canceled and we went back to regular spacing; which changed the sequence again. Instead of giving SMO a '1 min heads up' for departure I told them it would be a while because I was waiting for Malibu to call me back. SMO holds all departures back from the runway due to noise and pollution restrictions at their airport; we give them the 1 min warning so they can taxi the aircraft out to be ready to go. We had one last departure rolling when Malibu called and released Aircraft Y. I released Aircraft Y off of SMO thinking the aircraft would still need to taxi out for departure. But both aircraft ended up airborne at the same time. Just under 4 miles apart. In the future I will verify with SMO where there aircraft is to ensure separation.
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.