Narrative:

Controller in charge (controller in charge) was combined at ground control (ground control) for lunch breaks. I was working local control (local control) with no traffic on frequency. Ground control requested to cross runway 1 with a mower. I scanned the runway and final; checked my pad then approved the crossing. It seemed like a few minutes went by when a challenger called ready and requested a back taxi for full length (about 800 ft) at runway 1 bravo intersection; due to construction alpha taxiway for full length is closed. Again; I scanned the runway; final and checked my pad and cleared the challenger for back taxi and takeoff. While the aircraft was back taxing; approach called to apreq an opposite direction arrival about 40 miles away. I expanded my radar to see the target. As I was approving the apreq I observed the challenger slowing to a stop about 2;500 ft from the approach end. I wondered why he was doing that until I saw the mower come from behind the tower window stanchion. Delta taxiway where the mower crossed runs east/west and is almost completely obscured by the window stanchion in front of the local control position. The ground control/controller in charge was busy issuing clearances had apparently cleared the mower from a great distance from the runway and it took longer than I expected for him to get across. The ground control/controller in charge was busy and did not observe the incident. The pilot turned around for full length and departed without further incident. The ground control should have waited until the mower got to the runway before requesting the crossing. I should have slid the 12 inches to the right or left and looked at delta taxiway.

Google
 

Original NASA ASRS Text

Title: Local Controller and Ground Controller described an aborted takeoff event when an aircraft observed a mower crossing down field. Failed coordination between Local and Ground reportedly led to the occurrence.

Narrative: Controller In Charge (CIC) was combined at Ground Control (GC) for lunch breaks. I was working Local Control (LC) with no traffic on frequency. Ground Control requested to cross Runway 1 with a mower. I scanned the runway and final; checked my pad then approved the crossing. It seemed like a few minutes went by when a Challenger called ready and requested a back taxi for full length (about 800 FT) at Runway 1 Bravo Intersection; due to construction Alpha Taxiway for full length is closed. Again; I scanned the runway; final and checked my pad and cleared the Challenger for back taxi and takeoff. While the aircraft was back taxing; Approach called to APREQ an opposite direction arrival about 40 miles away. I expanded my RADAR to see the target. As I was approving the APREQ I observed the Challenger slowing to a stop about 2;500 FT from the approach end. I wondered why he was doing that until I saw the mower come from behind the Tower window stanchion. Delta Taxiway where the mower crossed runs east/west and is almost completely obscured by the window stanchion in front of the LC position. The GC/CIC was busy issuing clearances had apparently cleared the mower from a great distance from the runway and it took longer than I expected for him to get across. The GC/CIC was busy and did not observe the incident. The pilot turned around for full length and departed without further incident. The GC should have waited until the mower got to the runway before requesting the crossing. I should have slid the 12 inches to the right or left and looked at Delta Taxiway.

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.