 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Two las tower controllers and a flight crew reported an airborne conflict resulting from takeoff clearances from intersecting runways.
| Attributes | |
| ACN | 1371915 |
| Time | |
| Date | 201607 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | LAS.Airport |
| State Reference | NV |
| Aircraft 1 | |
| Make Model Name | Light Transport |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Large Transport |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
| Miss Distance | Horizontal 0 Vertical 500 |
Narrative:
Local 1 coordinated the intersection to local 2 for a runway 19R departure. Local 2 coordinated it back after aircraft X departed. I picked up the stop strip to scan a call for release on a STAAV6 departure to the tracon. I must not have put the stop strip back down on my 25R departure. I was discussing with the assist the need to get a release from approach control reference a 290 heading prop that departed. Looking at the tower radar display we notice the 290 prop had been turned and no release was needed. Forgetting that I released the 19R departure; I rolled aircraft Y off runway 25R. I looked at the numbers of 19R but didn't continue my scan to the departure end. Aircraft Y started his roll; broke ground and the airport surface detection equipment model X (asde-X) went off. I located aircraft X rolling off runway 19R; noticed aircraft Y was climbing above him; issued traffic; he answered he was doing his best to get above. Aircraft was then switched to departure. Follow local procedures. Use the stop strip the way its supposed to be used. Increase my scan to the full length of the intersecting runways. In my scan look at the light to ensure that I own the intersection.
Original NASA ASRS Text
Title: Two LAS Tower Controllers and a flight crew reported an airborne conflict resulting from takeoff clearances from intersecting runways.
Narrative: Local 1 coordinated the intersection to Local 2 for a Runway 19R departure. Local 2 coordinated it back after Aircraft X departed. I picked up the stop strip to scan a call for release on a STAAV6 departure to the Tracon. I must not have put the stop strip back down on my 25R departure. I was discussing with the assist the need to get a release from approach control reference a 290 heading prop that departed. Looking at the tower radar display we notice the 290 prop had been turned and no release was needed. Forgetting that I released the 19R departure; I rolled Aircraft Y off Runway 25R. I looked at the numbers of 19R but didn't continue my scan to the departure end. Aircraft Y started his roll; broke ground and the Airport Surface Detection Equipment Model X (ASDE-X) went off. I located Aircraft X rolling off Runway 19R; noticed Aircraft Y was climbing above him; issued traffic; he answered he was doing his best to get above. Aircraft was then switched to departure. Follow local procedures. Use the stop strip the way its supposed to be used. Increase my scan to the full length of the intersecting runways. In my scan look at the light to ensure that I own the intersection.
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.