Narrative:

I am a front line manager and was in the tower monitoring ground control. Controller working ground was working about 4 aircraft and a vehicle. The vehicle was proceeding from the fire station requiring 2 runway crossings. The ground controller had an air carrier pushing back and a small aircraft he had taxied out to runway xy at intersection east for departure off runway xy. Aircraft X; VFR requesting taxi. Aircraft X was enroute to ZZZ. Certified professional controller (cpc) tells aircraft X taxi runway xzl via romeo; delta; cross runway xy. Aircraft X read back the instructions but did not say cross runway ab. The controller talks to another aircraft and then goes back and tells aircraft X to make a left turn followed by an immediate right turn; cross runway ab. Aircraft X read back in my opinion was garbled (later in the elevator controller agreed it was garbled but he understood it). I even said out loud 'nice radio'. The stars display at ground control was covered by a sheet (more on this later) so I looked behind me at the stars display at local-2. I did not see any traffic on final but as I soon realized there was traffic on final. It must have been the distance or angle from the stars display that told my mind there was not traffic. I looked back at aircraft X and also noticed the controller was heads down looking for a strip when I noticed aircraft X was passing taxiway delta and heading for runway xzl. I told the controller he did not make his turn and the controller took immediate action but unfortunately used the wrong call sign and talked to the aircraft who was holding short of runway ab. He told the aircraft to hold short of runway xzl. That pilot advised him he was holding short of runway ab. About the same time aircraft X stopped short of the runway xzl surface area but past the hold short lines. The cpc then told aircraft X to make an immediate 180 degree turn. Aircraft X complied and replied he was sorry. The controller then gave instructions to get him on his way. About the time I noticed aircraft X was not turning; out of the corner of my eye I noticed aircraft Y over the numbers runway xzl. I am not 100% sure exactly where aircraft Y turned right off the runway but it was prior to runway xy/ab.I really don't think what was going on in the tower was a contributing factor but feel I need to explain what was going on because a piece of equipment I would have used to see arrival aircraft was covered up. I also know that the controller was not exactly in the space he would normally be; nor was his strips. We had 11 people in the tower. Myself monitoring ground control; a controller working ground control; local control; flight data/clearance delivery. Two workers installing film on the tower windows; a tech ops person watching them and another tech ops person working on the runway xl engine generator panel. We also had a cpc on ground control-2 waiting for a brief from ground control (we were moving ground from ground control-1 to ground control-2 because the window people wanted to work on windows in front of local control and ground control where we normally work). We also had a controller at local-2 getting the briefing from local-1 (we were moving this position to the other side of the tower).window people had equipment laying around; stuff they had moved (like plexy glass) so they could work. They also had sheets over equipment in the area they were working. The controller at ground control that I was watching had moved to his right to avoid them and had moved his strips off the bay and were laying in front of him on the counter thus a more heads down was required. The noise level was ok considering. I had actually told the workers to wait a couple minutes until we were able to move ground control to the other side of the tower so they would not block his view; they were complying. Again I'm not using this as any excuse but if I would have seen the traffic on final I might have had the controller get a betterread back from aircraft X on the second read back.I also feel the controller was not in his comfort zone by having to move out of his space. Bottom line is the pilot did not follow instructions which resulted in the runway incursion and I believe the pilot knew he messed up because he said he was sorry. After situation happened my mind was going a million miles a minute and I forgot to have anyone issue aircraft X the brasher statement. We did try and pass a message through TRACON but I'm not sure if pilot got the statement. When I have things happen it's no problem remembering this but for some reason because I had been so close to this situation it just slipped my mind to get this done. The controller and I got relieved right after the event; the controller was going to fill out an atsap and I went and told my operations manager.I should have looked out the window behind me to see if there was traffic instead of just looking at the stars display. I believe I would have seen the flight and insisted on #2. Insist the controller get a better read back on the second transmission.pay better attention to call signs so if something like this happens again I could key up; override the controller and tell the aircraft to stop or tell the controller he was using wrong call sign. There would not had been that few second delay. Explain again to controllers the importance of clear read backs. Don't set pilots up to fail. Small aircraft generally do not have the experience professional pilots have so you have to treat them differently and spoon feed them; don't take any chances that close to an active runway especially with traffic on final.

Related reports:

Google
 

Original NASA ASRS Text

Title: Tower Controller reported an aircraft did not comply with taxi instructions and proceeded onto a runway another aircraft was landing on.

Narrative: I am a Front Line manager and was in the Tower monitoring Ground Control. Controller working ground was working about 4 aircraft and a vehicle. The vehicle was proceeding from the fire station requiring 2 runway crossings. The Ground Controller had an air carrier pushing back and a small aircraft he had taxied out to runway XY at intersection E for departure off runway XY. Aircraft X; VFR requesting taxi. Aircraft X was enroute to ZZZ. Certified Professional Controller (CPC) tells Aircraft X taxi runway XZL via romeo; delta; cross runway XY. Aircraft X read back the instructions but did not say cross runway AB. The Controller talks to another aircraft and then goes back and tells Aircraft X to make a left turn followed by an immediate right turn; cross runway AB. Aircraft X read back in my opinion was garbled (later in the elevator Controller agreed it was garbled but he understood it). I even said out loud 'nice radio'. The STARS display at Ground Control was covered by a sheet (more on this later) so I looked behind me at the STARS display at Local-2. I did not see any traffic on final but as I soon realized there was traffic on final. It must have been the distance or angle from the STARS display that told my mind there was not traffic. I looked back at Aircraft X and also noticed the Controller was heads down looking for a strip when I noticed Aircraft X was passing taxiway Delta and heading for runway XZL. I told the Controller he did not make his turn and the Controller took immediate action but unfortunately used the wrong call sign and talked to the aircraft who was holding short of runway AB. He told the aircraft to hold short of runway XZL. That pilot advised him he was holding short of runway AB. About the same time Aircraft X stopped short of the runway XZL surface area but past the hold short lines. The CPC then told Aircraft X to make an immediate 180 degree turn. Aircraft X complied and replied he was sorry. The Controller then gave instructions to get him on his way. About the time I noticed Aircraft X was not turning; out of the corner of my eye I noticed Aircraft Y over the numbers runway XZL. I am not 100% sure exactly where Aircraft Y turned right off the runway but it was prior to runway XY/AB.I really DON'T think what was going on in the tower was a contributing factor but feel I need to explain what was going on because a piece of equipment I would have used to see arrival aircraft was covered up. I also know that the Controller was not exactly in the space he would normally be; nor was his strips. We had 11 people in the Tower. Myself monitoring Ground Control; a Controller working Ground Control; Local Control; Flight Data/Clearance Delivery. Two workers installing film on the tower windows; a Tech Ops person watching them and another tech ops person working on the runway XL engine generator panel. We also had a CPC on GC-2 waiting for a brief from Ground Control (we were moving ground from Ground Control-1 to Ground Control-2 because the window people wanted to work on windows in front of Local Control and Ground Control where we normally work). We also had a Controller at Local-2 getting the briefing from Local-1 (we were moving this position to the other side of the tower).Window people had equipment laying around; stuff they had moved (like plexy glass) so they could work. They also had sheets over equipment in the area they were working. The Controller at Ground Control that I was watching had moved to his right to avoid them and had moved his strips off the bay and were laying in front of him on the counter thus a more heads down was required. The noise level was ok considering. I had actually told the workers to wait a couple minutes until we were able to move Ground Control to the other side of the tower so they would not block his view; they were complying. Again I'm not using this as any excuse but if I would have seen the traffic on final I might have had the Controller get a betterread back from Aircraft X on the second read back.I also feel the Controller was not in his comfort zone by having to move out of his space. Bottom line is the pilot did not follow instructions which resulted in the runway incursion and I believe the pilot knew he messed up because he said he was sorry. After situation happened my mind was going a million miles a minute and I forgot to have anyone issue Aircraft X the brasher statement. We did try and pass a message through TRACON but I'm not sure if pilot got the statement. When I have things happen it's no problem remembering this but for some reason because I had been so close to this situation it just slipped my mind to get this done. The Controller and I got relieved right after the event; the Controller was going to fill out an ATSAP and I went and told my Operations Manager.I should have looked out the window behind me to see if there was traffic instead of just looking at the STARS display. I believe I would have seen the flight and insisted on #2. Insist the Controller get a better read back on the second transmission.Pay better attention to call signs so if something like this happens again I could key up; override the Controller and tell the aircraft to stop or tell the Controller he was using wrong call sign. There would not had been that few second delay. Explain again to controllers the importance of clear read backs. Don't set pilots up to fail. Small aircraft generally do not have the experience professional pilots have so you have to treat them differently and spoon feed them; don't take any chances that close to an active runway especially with traffic on final.

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.