 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ground controller reported a runway incursion due to developmental on local not scanning runway to ensure arrival was clear of runway.
| Attributes | |
| ACN | 1594673 |
| Time | |
| Date | 201811 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Cessna Aircraft Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Person 1 | |
| Function | Ground |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.9 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Ground Incursion Runway |
Narrative:
I was working ground control; and our supervisor was training on local 1. I had an aircraft call me clear of runway 28L at taxiway G1 (aircraft X). I immediately noticed he was not clear of runway 28L and appeared his tail was partially over [runway] 28L. I alerted local control as aircraft Y was departing runway 28L and airborne as they passed aircraft X. I then taxied the aircraft to transient ramp. The trainee on LC1 did not observe the issue until I pointed out and had an aircraft on takeoff roll and airborne before noticing the event. The supervisor was involved and notified of the event when it happened. I estimate 10/15ft lateral separation; and 50ft (at the most) vertical separation when the event occurred. I recommend recurrent training for the trainee involved and/or emphasis on scan especially when issuing departure/landing clearances. I believe the lack of scan and tower cab awareness led to the event happening. This trainee is near their max hours; recommend an evaluation to see whether or not they can truly make it at ZZZ.
Original NASA ASRS Text
Title: Ground Controller reported a runway incursion due to developmental on Local not scanning runway to ensure arrival was clear of runway.
Narrative: I was working Ground Control; and our Supervisor was training on Local 1. I had an aircraft call me clear of Runway 28L at Taxiway G1 (Aircraft X). I immediately noticed he was not clear of Runway 28L and appeared his tail was partially over [Runway] 28L. I alerted Local Control as Aircraft Y was departing Runway 28L and airborne as they passed Aircraft X. I then taxied the aircraft to transient ramp. The trainee on LC1 did not observe the issue until I pointed out and had an aircraft on takeoff roll and airborne before noticing the event. The Supervisor was involved and notified of the event when it happened. I estimate 10/15ft lateral separation; and 50ft (at the most) vertical separation when the event occurred. I recommend recurrent training for the trainee involved and/or emphasis on scan especially when issuing departure/landing clearances. I believe the lack of scan and tower cab awareness led to the event happening. This trainee is near their max hours; recommend an evaluation to see whether or not they can truly make it at ZZZ.
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.