Narrative:

I was relieved from local control at XA22. The runway 13/31 was going to be closed very soon. I went on break; and both the relieving local controller and the ground controller later told me that at XA24; 3 vehicles entered runway 13/31 and stayed on the runway; apparently to begin their day's work. The airport authority/authorized verbally told us and issued NOTAMS stating the runway would close at XA30. While it was only 6 mins; an open and available runway is an open and available runway. (This runway is adjacent to our only FBO; and is often used for departures.) I'd like to think this was because of poorly trained contractors; and not careless airport workers. (To verify; there was no radio communication between the vehicles and tower). To the best of my knowledge; the supervisor never questioned or followed up on this when told about it.

Google
 

Original NASA ASRS Text

Title: RWY INCURSION INCIDENT WHEN ARPT VEHICLES ENTERED RWY FOR WORK PROJECT 6 MINS PRIOR TO NOTAMED RWY CLOSURE TIME.

Narrative: I WAS RELIEVED FROM LCL CTL AT XA22. THE RWY 13/31 WAS GOING TO BE CLOSED VERY SOON. I WENT ON BREAK; AND BOTH THE RELIEVING LCL CTLR AND THE GND CTLR LATER TOLD ME THAT AT XA24; 3 VEHICLES ENTERED RWY 13/31 AND STAYED ON THE RWY; APPARENTLY TO BEGIN THEIR DAY'S WORK. THE ARPT AUTH VERBALLY TOLD US AND ISSUED NOTAMS STATING THE RWY WOULD CLOSE AT XA30. WHILE IT WAS ONLY 6 MINS; AN OPEN AND AVAILABLE RWY IS AN OPEN AND AVAILABLE RWY. (THIS RWY IS ADJACENT TO OUR ONLY FBO; AND IS OFTEN USED FOR DEPS.) I'D LIKE TO THINK THIS WAS BECAUSE OF POORLY TRAINED CONTRACTORS; AND NOT CARELESS ARPT WORKERS. (TO VERIFY; THERE WAS NO RADIO COM BTWN THE VEHICLES AND TWR). TO THE BEST OF MY KNOWLEDGE; THE SUPVR NEVER QUESTIONED OR FOLLOWED UP ON THIS WHEN TOLD ABOUT IT.

Data retrieved from NASA's ASRS site as of January 2009 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.