 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ground controller reported an runway incursion because of a bad read back.
| Attributes | |
| ACN | 1627711 |
| Time | |
| Date | 201903 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Super King Air 200 |
| Flight Phase | Taxi |
| Aircraft 2 | |
| Make Model Name | Citationjet (C525/C526) - CJ I / II / III / IV |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | VFR |
| Person 1 | |
| Function | Ground Instructor |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2.7 |
| Events | |
| Anomaly | Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
I was training someone on ground control. He requested a poor crossing because there was an aircraft a little too close he didn't see. The local controller denied the crossing. Then the ground controller then read the hold short instructions correctly to the pilot of aircraft X. The pilot read back the hold short instructions incorrectly although the language barrier and/or order he used made it difficult to understand his incorrect read back. The aircraft then crossed runway xxl at alpha with aircraft Y on about 3/4 mile final. I saw the aircraft X entering the runway and immediately told local control to send around aircraft Y on final. I was going to have aircraft X stop; but he was already too far forward so I had him continue across runway xxl and hold short of runway xxr. Aircraft Y landed without a go-around because aircraft X had crossed the runway. I have said this before; but I think this facility needs to have a safety logic system. There are a multitude of disparate reasons that there are so many runway incursions here; but because of this very reason; no single procedural change will fix it all. A safety logic system adds a needed layer of safety and should be considered as soon as possible.
Original NASA ASRS Text
Title: Ground Controller reported an runway incursion because of a bad read back.
Narrative: I was training someone on Ground Control. He requested a poor crossing because there was an aircraft a little too close he didn't see. The Local Controller denied the crossing. Then the Ground Controller then read the hold short instructions correctly to the pilot of Aircraft X. The pilot read back the hold short instructions incorrectly although the language barrier and/or order he used made it difficult to understand his incorrect read back. The aircraft then crossed Runway XXL at Alpha with Aircraft Y on about 3/4 mile final. I saw the Aircraft X entering the runway and immediately told Local Control to send around Aircraft Y on final. I was going to have Aircraft X stop; but he was already too far forward so I had him continue across RWY XXL and hold short of RWY XXR. Aircraft Y landed without a go-around because Aircraft X had crossed the runway. I have said this before; but I think this facility needs to have a safety logic system. There are a multitude of disparate reasons that there are so many runway incursions here; but because of this very reason; no single procedural change will fix it all. A safety logic system adds a needed layer of safety and should be considered as soon as possible.
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.