Narrative:

While departing oakland international airport I was cleared for taxi to runway 27R from the local FBO office by the ground controller. While continuing to monitor ground I began taxiing to runway 27R via the access taxiway. Without noticing any stop lines, or red runway indicator signs, I turned right and followed the taxi lines toward an area marked 'run-up' now occupied by another aircraft stopping prior to a yellow hold line. At this point the ground controller informed me that I had crossed the runway and was now in the run-up area for runway 27L. After apologizing I was told to contact the tower. Looking on the map it is clear that the taxiway intersects runway 27R, off the end of the runway, prior to the threshold. It was not clear, however, from the cockpit window, due to the lack of signs and other indicators that this would occur. As PIC, it is my responsibility to assure that I do not cross active runways and in the past I always ask if I may cross even when it is already clear from the instructions given. I was therefore surprised when I was told that I had done so, yet in hindsight I should have asked for progressive and or read the runway layout diagram close prior to taxiing. At the time, it seemed clear that the taxiway would lead me to the run-up area. I believe the things leading to this incursion are: 1) my decision not to ask for progressive, 2) my decision not to study the map closer prior to taxiing, 3) the lack of proper indicators, both yellow stop lines and red runway signs, at the end of the taxiway prior to the turn off toward the run-up area for runway 27L, and 4) only 1 'run-up' sign visible from the taxiway, for runway 27L and not for runway 27R. In the future, especially when taxiing at larger airports, I will study the runway diagram closely prior to taxiing and ask for progressive if I am confused in the least. I will be especially cognizant of this approach when operating out of airports that have ongoing construction such as oak.

Google
 

Original NASA ASRS Text

Title: PLT OF UNIDENTED ACFT TYPE CROSSED THE RWY 27R AT OAK WITHOUT CLRNC WHILE ENRTE TO RUN-UP AREA TO WHICH HE BELIEVED HIMSELF TO HAVE BEEN CLRED.

Narrative: WHILE DEPARTING OAKLAND INTL ARPT I WAS CLRED FOR TAXI TO RWY 27R FROM THE LCL FBO OFFICE BY THE GND CTLR. WHILE CONTINUING TO MONITOR GND I BEGAN TAXIING TO RWY 27R VIA THE ACCESS TXWY. WITHOUT NOTICING ANY STOP LINES, OR RED RWY INDICATOR SIGNS, I TURNED R AND FOLLOWED THE TAXI LINES TOWARD AN AREA MARKED 'RUN-UP' NOW OCCUPIED BY ANOTHER ACFT STOPPING PRIOR TO A YELLOW HOLD LINE. AT THIS POINT THE GND CTLR INFORMED ME THAT I HAD CROSSED THE RWY AND WAS NOW IN THE RUN-UP AREA FOR RWY 27L. AFTER APOLOGIZING I WAS TOLD TO CONTACT THE TWR. LOOKING ON THE MAP IT IS CLR THAT THE TXWY INTERSECTS RWY 27R, OFF THE END OF THE RWY, PRIOR TO THE THRESHOLD. IT WAS NOT CLR, HOWEVER, FROM THE COCKPIT WINDOW, DUE TO THE LACK OF SIGNS AND OTHER INDICATORS THAT THIS WOULD OCCUR. AS PIC, IT IS MY RESPONSIBILITY TO ASSURE THAT I DO NOT CROSS ACTIVE RWYS AND IN THE PAST I ALWAYS ASK IF I MAY CROSS EVEN WHEN IT IS ALREADY CLR FROM THE INSTRUCTIONS GIVEN. I WAS THEREFORE SURPRISED WHEN I WAS TOLD THAT I HAD DONE SO, YET IN HINDSIGHT I SHOULD HAVE ASKED FOR PROGRESSIVE AND OR READ THE RWY LAYOUT DIAGRAM CLOSE PRIOR TO TAXIING. AT THE TIME, IT SEEMED CLR THAT THE TXWY WOULD LEAD ME TO THE RUN-UP AREA. I BELIEVE THE THINGS LEADING TO THIS INCURSION ARE: 1) MY DECISION NOT TO ASK FOR PROGRESSIVE, 2) MY DECISION NOT TO STUDY THE MAP CLOSER PRIOR TO TAXIING, 3) THE LACK OF PROPER INDICATORS, BOTH YELLOW STOP LINES AND RED RWY SIGNS, AT THE END OF THE TXWY PRIOR TO THE TURN OFF TOWARD THE RUN-UP AREA FOR RWY 27L, AND 4) ONLY 1 'RUN-UP' SIGN VISIBLE FROM THE TXWY, FOR RWY 27L AND NOT FOR RWY 27R. IN THE FUTURE, ESPECIALLY WHEN TAXIING AT LARGER ARPTS, I WILL STUDY THE RWY DIAGRAM CLOSELY PRIOR TO TAXIING AND ASK FOR PROGRESSIVE IF I AM CONFUSED IN THE LEAST. I WILL BE ESPECIALLY COGNIZANT OF THIS APCH WHEN OPERATING OUT OF ARPTS THAT HAVE ONGOING CONSTRUCTION SUCH AS OAK.

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.