Narrative:

I was receiving a position brief in the local control position and the airport was in a west operation. Runways xxl/xxr and [runway] yy were the runaways in use. Ground had control of runway yy for crossings and taxiing. Just prior to the brief I heard the ground controller issue taxi instructions to a cessna for a runway xxl departure via delta crossing runway yy. Almost immediately the local controller requested runway yy for an arrival on runway yy. Ground gave local the runway and took the 'all runways to local' rid he placed it on the console at his position. Ground immediately amended the instructions for a cessna to 'hold short of runway yy.' local began briefing me in accordance with the checklist and had 6-8 aircraft doing pattern work to all both parallel runways as well as a piper on final for [runway] yy. As the outgoing controller was clearing an aircraft for takeoff on runway xxl; I saw an aircraft I had not heard discussed crossing the hold short line north of runway yy at echo taxiway. I alerted the outgoing controller and he stopped his transmission to the aircraft at runway xxl and advised the piper of the incursion ahead. Ground first read the cessna's call sign and then corrected it to 'C172; hold short.' the piper and the cessna came to rest approximately 20-30 ft apart at a nearly right angle; one on the centerline and one perpendicular to it. The piper and the cessna both used echo to the ramp as piper had passed it on his pull out. The ground controller stated 'I forgot I had two aircraft; I never held him short.' both pilots were following instructions correctly at the time of the incident. The ground controller in this case has been reported in past for the exact same type of scenario; crossing a runway without permission. I am concerned for this controller's cavalier disregard of local and FAA procedures. I am aware of at least 4 runway incursions since february of this year.

Google
 

Original NASA ASRS Text

Title: Tower Local Controller described a potential ground conflict event when the Ground Controller failed to issue appropriate taxi instructions. The reporter claimed the Ground Controller has erred on many occasions.

Narrative: I was receiving a position brief in the Local Control position and the airport was in a west operation. Runways XXL/XXR and [Runway] YY were the runaways in use. Ground had control of Runway YY for crossings and Taxiing. Just prior to the brief I heard the Ground Controller issue taxi instructions to a Cessna for a Runway XXL Departure via Delta crossing Runway YY. Almost immediately the Local Controller requested Runway YY for an arrival on Runway YY. Ground gave Local the runway and took the 'all runways to local' RID he placed it on the console at his position. Ground immediately amended the instructions for a Cessna to 'hold short of Runway YY.' Local began briefing me in accordance with the checklist and had 6-8 aircraft doing pattern work to all both parallel runways as well as a Piper on final for [Runway] YY. As the outgoing controller was clearing an aircraft for takeoff on Runway XXL; I saw an aircraft I had not heard discussed crossing the hold short line north of Runway YY at Echo Taxiway. I alerted the outgoing Controller and he stopped his transmission to the aircraft at Runway XXL and advised the Piper of the incursion ahead. Ground first read the Cessna's call sign and then corrected it to 'C172; hold short.' The Piper and the Cessna came to rest approximately 20-30 FT apart at a nearly right angle; one on the centerline and one perpendicular to it. The Piper and the Cessna both used Echo to the ramp as Piper had passed it on his pull out. The Ground Controller stated 'I forgot I had two aircraft; I never held him short.' Both pilots were following instructions correctly at the time of the incident. The Ground Controller in this case has been reported in past for the exact same type of scenario; crossing a runway without permission. I am concerned for this Controller's cavalier disregard of LOCAL and FAA procedures. I am aware of at least 4 runway incursions since February of this year.

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.