Narrative:

The run-up area for runway 27L at oak airport is on the other side of runway 27R. Runway 27R has been closed for some weeks up to this point, and just recently has been reopened. During the time of closure, we used runway 27L, along with its associated run-up area. In order to taxi to the run-up area for runway 27L, you must cross the approach end of runway 27R. The taxiway doesn't actually cross the runway, but nevertheless, there are hold short bars on the taxiway due to the fact that it is near the threshold of runway 27R. Multiple taxiway closures due to construction in the vicinity has complicated matters, making the taxi phase of flight confusing at times. The clearance I received to taxi was 'taxi runway 27R.' out of habit, I taxied to the run-up area of runway 27L, thereby crossing the approach threshold of runway 27R. There was no traffic conflict, as there was no other airplane in the immediate vicinity nor on approach. The tower queried me as to whether I had crossed runway 27R, then informed me that I needed to heed the hold short lines to the runway. The taxi instructions were understood properly when given, so there was no communication confusion. I have flown out of this airport for the last 4 yrs virtually every day, so there was no confusion as to where the correct runway and run-up area were. There was no cargo on the aircraft, so there was no rush to maintain a schedule. However, the previous night, I had gotten only 3 hours sleep. As a freight pilot for a carrier that operates light aircraft, the hours are long and grueling, with little time at home each day. Fatigue no doubt was a contributing factor in this incident. It was the first time this type of incident has occurred with me, and it shocked me very much.

Google
 

Original NASA ASRS Text

Title: BEECH 99 CARGO PLT DID NOT HOLD SHORT AT THE RWY HOLD SHORT LINES FOR THE APCH EXTENSION OF AN ACTIVE PARALLEL RWY.

Narrative: THE RUN-UP AREA FOR RWY 27L AT OAK ARPT IS ON THE OTHER SIDE OF RWY 27R. RWY 27R HAS BEEN CLOSED FOR SOME WKS UP TO THIS POINT, AND JUST RECENTLY HAS BEEN REOPENED. DURING THE TIME OF CLOSURE, WE USED RWY 27L, ALONG WITH ITS ASSOCIATED RUN-UP AREA. IN ORDER TO TAXI TO THE RUN-UP AREA FOR RWY 27L, YOU MUST CROSS THE APCH END OF RWY 27R. THE TXWY DOESN'T ACTUALLY CROSS THE RWY, BUT NEVERTHELESS, THERE ARE HOLD SHORT BARS ON THE TXWY DUE TO THE FACT THAT IT IS NEAR THE THRESHOLD OF RWY 27R. MULTIPLE TXWY CLOSURES DUE TO CONSTRUCTION IN THE VICINITY HAS COMPLICATED MATTERS, MAKING THE TAXI PHASE OF FLT CONFUSING AT TIMES. THE CLRNC I RECEIVED TO TAXI WAS 'TAXI RWY 27R.' OUT OF HABIT, I TAXIED TO THE RUN-UP AREA OF RWY 27L, THEREBY XING THE APCH THRESHOLD OF RWY 27R. THERE WAS NO TFC CONFLICT, AS THERE WAS NO OTHER AIRPLANE IN THE IMMEDIATE VICINITY NOR ON APCH. THE TWR QUERIED ME AS TO WHETHER I HAD CROSSED RWY 27R, THEN INFORMED ME THAT I NEEDED TO HEED THE HOLD SHORT LINES TO THE RWY. THE TAXI INSTRUCTIONS WERE UNDERSTOOD PROPERLY WHEN GIVEN, SO THERE WAS NO COM CONFUSION. I HAVE FLOWN OUT OF THIS ARPT FOR THE LAST 4 YRS VIRTUALLY EVERY DAY, SO THERE WAS NO CONFUSION AS TO WHERE THE CORRECT RWY AND RUN-UP AREA WERE. THERE WAS NO CARGO ON THE ACFT, SO THERE WAS NO RUSH TO MAINTAIN A SCHEDULE. HOWEVER, THE PREVIOUS NIGHT, I HAD GOTTEN ONLY 3 HRS SLEEP. AS A FREIGHT PLT FOR A CARRIER THAT OPERATES LIGHT ACFT, THE HRS ARE LONG AND GRUELING, WITH LITTLE TIME AT HOME EACH DAY. FATIGUE NO DOUBT WAS A CONTRIBUTING FACTOR IN THIS INCIDENT. IT WAS THE FIRST TIME THIS TYPE OF INCIDENT HAS OCCURRED WITH ME, AND IT SHOCKED ME VERY MUCH.

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.