 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An aircraft taxiing to parking missed a turn and was proceeding toward an active runway. ATC noticed the deviation and corrected the pilot. The aircraft had been issued correct instructions and read the instructions back correctly.
| Attributes | |
| ACN | 1302239 |
| Time | |
| Date | 201510 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BOS.Airport |
| State Reference | MA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Ground |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2.5 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Ground Incursion Runway Ground Incursion Taxiway |
Narrative:
Aircraft X landed on runway 27. I issued exiting instructions: 'aircraft X; turn right on [taxiway] K then turn right on [taxiway] M.' they were read back correctly. I looked away for something else; then looked back and aircraft X had missed the right turn on M and was continuing straight ahead on K; which then crosses the active departure runway. I was able to stop the aircraft to avoid a runway incursion; but only because I had looked back in that direction in time.I am submitting this to add to the database of potential runway incursions. There is nothing else that can be done. Unfortunately; here at boston; the airport and runway layout is so complex that it is not conducive to mitigating runway incursions. In every configuration; active runway crossings with a majority of the traffic are necessary and more incursions are avoided only because of the vigilance of the controllers.
Original NASA ASRS Text
Title: An aircraft taxiing to parking missed a turn and was proceeding toward an active runway. ATC noticed the deviation and corrected the pilot. The aircraft had been issued correct instructions and read the instructions back correctly.
Narrative: Aircraft X landed on Runway 27. I issued exiting instructions: 'Aircraft X; turn right on [taxiway] K then turn right on [taxiway] M.' They were read back correctly. I looked away for something else; then looked back and Aircraft X had missed the right turn on M and was continuing straight ahead on K; which then crosses the active departure runway. I was able to stop the aircraft to avoid a runway incursion; but only because I had looked back in that direction in time.I am submitting this to add to the database of potential runway incursions. There is nothing else that can be done. Unfortunately; here at Boston; the airport and runway layout is so complex that it is not conducive to mitigating runway incursions. In every configuration; active runway crossings with a majority of the traffic are necessary and more incursions are avoided only because of the vigilance of the controllers.
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.