Narrative:

At chicago pal-waukee airport, we were taxiing from the ramp to the active runway 16. We were asked to taxi on runway 30R and to hold short of runway 16/34. As we approached runway 6/24 (which we were cleared to cross) we saw two intersecting strips of concrete. We knew that the first was runway 6/24, and assumed that the next was a service road or taxiway, because it was unmarked. As we taxied across this strip of concrete, we were informed that we were busting our hold short clearance, and told to expedite across the runway for landing traffic. Upon returning home, I contacted the tower manager. He informed me that there was no runway sign at that intersection, and that this has been a problem for some time. I believe that had the runway been properly marked, no incursion would have occurred.

Google
 

Original NASA ASRS Text

Title: SMT RWY INCURSION DUE TO NO RWY SIGNAGE.

Narrative: AT CHICAGO PAL-WAUKEE ARPT, WE WERE TAXIING FROM THE RAMP TO THE ACTIVE RWY 16. WE WERE ASKED TO TAXI ON RWY 30R AND TO HOLD SHORT OF RWY 16/34. AS WE APCHED RWY 6/24 (WHICH WE WERE CLRED TO CROSS) WE SAW TWO INTERSECTING STRIPS OF CONCRETE. WE KNEW THAT THE FIRST WAS RWY 6/24, AND ASSUMED THAT THE NEXT WAS A SVC ROAD OR TXWY, BECAUSE IT WAS UNMARKED. AS WE TAXIED ACROSS THIS STRIP OF CONCRETE, WE WERE INFORMED THAT WE WERE BUSTING OUR HOLD SHORT CLRNC, AND TOLD TO EXPEDITE ACROSS THE RWY FOR LNDG TFC. UPON RETURNING HOME, I CONTACTED THE TWR MGR. HE INFORMED ME THAT THERE WAS NO RWY SIGN AT THAT INTXN, AND THAT THIS HAS BEEN A PROB FOR SOME TIME. I BELIEVE THAT HAD THE RWY BEEN PROPERLY MARKED, NO INCURSION WOULD HAVE OCCURRED.

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