 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Lax tower controllers reported a taxiway incursion prompting them to send landing traffic to go-around.
| Attributes | |
| ACN | 1415649 |
| Time | |
| Date | 201701 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | LAX.Tower |
| State Reference | CA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 19 |
| Person 2 | |
| Function | Handoff / Assist |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Taxiway |
Narrative:
Aircraft X was instructed to cross runway 25L northbound at taxiway G and turn right on taxiway H. Aircraft X crossed the runway; but turned before he reached H. His data tag dropped since he was in a masked area of the asde-X. He turned right (eastbound) between the runway and the taxiway. When aircraft X realized his mistake he started making a right turn toward the runway. I sent an aircraft around and got aircraft X facing northbound and had him cross runway 25R as well.the issue here is the runway markings at 25L and G and H. This is at least the 5th such incident in the past few months of our current closure (shortening of runway 25R). Management is aware of this problem yet it continues. This needs to be fixed. The lead in lines are confusing and keep leading aircraft to turn onto runway 25L. We need help from the airport to get this done. Not sure why the airport has not yet fixed this; but they apparently need more motivation.this is actually a place where a confused aircraft could cause an accident. Had I not stopped aircraft X; he appeared to be heading back to runway 25L. The safety logic would not have sounded until he re-entered the non-masked area on the runway. This could easily have led to a crash. It is shameful that it has not been fixed yet.
Original NASA ASRS Text
Title: LAX Tower Controllers reported a taxiway incursion prompting them to send landing traffic to go-around.
Narrative: Aircraft X was instructed to cross Runway 25L northbound at Taxiway G and turn right on Taxiway H. Aircraft X crossed the runway; but turned before he reached H. His data tag dropped since he was in a masked area of the ASDE-X. He turned right (eastbound) between the runway and the taxiway. When Aircraft X realized his mistake he started making a right turn toward the runway. I sent an aircraft around and got Aircraft X facing northbound and had him cross Runway 25R as well.The issue here is the runway markings at 25L and G and H. This is at least the 5th such incident in the past few months of our current closure (shortening of Runway 25R). Management is aware of this problem yet it continues. This needs to be fixed. The lead in lines are confusing and keep leading aircraft to turn onto Runway 25L. We need help from the airport to get this done. Not sure why the airport has not yet fixed this; but they apparently need more motivation.This is actually a place where a confused aircraft could cause an accident. Had I not stopped Aircraft X; he appeared to be heading back to Runway 25L. The safety logic would not have sounded until he re-entered the non-masked area on the runway. This could easily have led to a crash. It is shameful that it has not been fixed yet.
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.