 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller witnessed a runway incursion when landing traffic exited the runway only to re-enter the runway safety area at another intersection. The reporter indicated the reduced visibility as a possible contributor to the incident.
| Attributes | |
| ACN | 1040665 |
| Time | |
| Date | 201210 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | IAD.Airport |
| State Reference | DC |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Baron 58/58TC |
| Flight Phase | Landing |
| Person 1 | |
| Function | Approach Departure |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
This is a known event; reported initially as a go around within 1/2 mile of runway. A BE58; on short final runway 19C; was sent around because an E145 had exited runway 19C on Y5; got disoriented; and re-entered the runway safety area on Y6. The E145 crew reported this to ground control 2 and local control 3 immediately sent the BE58 around. Upon further review; it was determined that a possible pilot deviation and runway incursion had occurred. There was no asde-X alert nor was there a loss of separation between the BE58 and the E145 due to the swift reaction by local control 3. Take home from this event: 1. Our newer controllers may not have worked traffic before under the weather conditions that existed during this incident. The runway and exits were not visible from the tower. Ground control 2 did not catch the fact that the E145 was heading back toward the runway. More experienced controllers are on guard for the possibility that crews might make a wrong turn and end up heading back to the runway. Therefore; they remember to scan the asde to ensure aircraft join the parallel taxiway; instead of the next high speed. A lesson's learned session using the video is needed.
Original NASA ASRS Text
Title: Tower Controller witnessed a runway incursion when landing traffic exited the runway only to re-enter the runway safety area at another intersection. The reporter indicated the reduced visibility as a possible contributor to the incident.
Narrative: This is a known event; reported initially as a go around within 1/2 mile of runway. A BE58; on short final Runway 19C; was sent around because an E145 had exited Runway 19C on Y5; got disoriented; and re-entered the runway safety area on Y6. The E145 crew reported this to Ground Control 2 and Local Control 3 immediately sent the BE58 around. Upon further review; it was determined that a possible pilot deviation and runway incursion had occurred. There was no ASDE-X alert nor was there a loss of separation between the BE58 and the E145 due to the swift reaction by Local Control 3. Take home from this event: 1. Our newer controllers may not have worked traffic before under the weather conditions that existed during this incident. The runway and exits were not visible from the Tower. Ground Control 2 did not catch the fact that the E145 was heading back toward the runway. More experienced controllers are on guard for the possibility that crews might make a wrong turn and end up heading back to the runway. Therefore; they remember to scan the ASDE to ensure aircraft join the parallel taxiway; instead of the next high speed. A lesson's learned session using the video is needed.
Data retrieved from NASA's ASRS site as of July 2013 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.