Narrative:

We were cleared to taxi from parking at pwk out for runway 16 via taxiway left. We both looked at the airport diagram and agreed that we had to taxi out on taxiway P and take the first left which would be taxiway left. I then went 'inside' the aircraft commencing the taxi checks. Shortly after, I felt the aircraft turn sharply to the left. I heard the captain say something and I looked outside and noticed that we were entering runway 16/34, the active. The captain continued the left 180 degree turn and taxied off the runway and back on taxiway P. There was an aircraft on final that decided to go around. I believed that plane was another bizjet. At the time of this incursion, there was construction work in progress at the airport. When we landed 40-45 mins earlier we advised, on request, which taxiway we were taxiing off on, as the controller wasn't sure. He thought it was taxiway left, but we never saw any signs for taxiway left, which we advised him of. It was taxiway P, as per the airport chart. Before taxiing out for departure, we looked down taxiway P and agreed that the next piece of crossing paved area must be taxiway left, as per the chart. However, it is actually runway 16/34. As it turns out, taxiway left does no longer exist. It's all dug up, just dirt. There is a hold sign for runway 16/34 on taxiway P, but being inside doing taxi checks, I never noticed. We were eventually cleared to taxi across runway 16/34 and via taxiway K to runway 16, the only way to get there. Causes: I think the fact that the airport diagram didn't match with the ongoing construction work confused us (the pilots) as well as the controllers. We were cleared to taxi onto a non existing taxiway. We never noticed the runway hold line/signal for runway 16, having our minds set on it being taxiway left with a missing sign. ATC never noticed us entering the runway, not until the captain told them he was on it and turning around. I think vigilance applies for pilots and controllers -- and is imperative under these conditions where the map doesn't match the terrain!

Google
 

Original NASA ASRS Text

Title: A C560 CREW, TAXIING FOR TKOF AT PWK, TAXIED ONTO THE DEP RWY.

Narrative: WE WERE CLRED TO TAXI FROM PARKING AT PWK OUT FOR RWY 16 VIA TXWY L. WE BOTH LOOKED AT THE ARPT DIAGRAM AND AGREED THAT WE HAD TO TAXI OUT ON TXWY P AND TAKE THE FIRST L WHICH WOULD BE TXWY L. I THEN WENT 'INSIDE' THE ACFT COMMENCING THE TAXI CHKS. SHORTLY AFTER, I FELT THE ACFT TURN SHARPLY TO THE L. I HEARD THE CAPT SAY SOMETHING AND I LOOKED OUTSIDE AND NOTICED THAT WE WERE ENTERING RWY 16/34, THE ACTIVE. THE CAPT CONTINUED THE L 180 DEG TURN AND TAXIED OFF THE RWY AND BACK ON TXWY P. THERE WAS AN ACFT ON FINAL THAT DECIDED TO GO AROUND. I BELIEVED THAT PLANE WAS ANOTHER BIZJET. AT THE TIME OF THIS INCURSION, THERE WAS CONSTRUCTION WORK IN PROGRESS AT THE ARPT. WHEN WE LANDED 40-45 MINS EARLIER WE ADVISED, ON REQUEST, WHICH TXWY WE WERE TAXIING OFF ON, AS THE CTLR WASN'T SURE. HE THOUGHT IT WAS TXWY L, BUT WE NEVER SAW ANY SIGNS FOR TXWY L, WHICH WE ADVISED HIM OF. IT WAS TXWY P, AS PER THE ARPT CHART. BEFORE TAXIING OUT FOR DEP, WE LOOKED DOWN TXWY P AND AGREED THAT THE NEXT PIECE OF XING PAVED AREA MUST BE TXWY L, AS PER THE CHART. HOWEVER, IT IS ACTUALLY RWY 16/34. AS IT TURNS OUT, TXWY L DOES NO LONGER EXIST. IT'S ALL DUG UP, JUST DIRT. THERE IS A HOLD SIGN FOR RWY 16/34 ON TXWY P, BUT BEING INSIDE DOING TAXI CHKS, I NEVER NOTICED. WE WERE EVENTUALLY CLRED TO TAXI ACROSS RWY 16/34 AND VIA TXWY K TO RWY 16, THE ONLY WAY TO GET THERE. CAUSES: I THINK THE FACT THAT THE ARPT DIAGRAM DIDN'T MATCH WITH THE ONGOING CONSTRUCTION WORK CONFUSED US (THE PLTS) AS WELL AS THE CTLRS. WE WERE CLRED TO TAXI ONTO A NON EXISTING TXWY. WE NEVER NOTICED THE RWY HOLD LINE/SIGNAL FOR RWY 16, HAVING OUR MINDS SET ON IT BEING TXWY L WITH A MISSING SIGN. ATC NEVER NOTICED US ENTERING THE RWY, NOT UNTIL THE CAPT TOLD THEM HE WAS ON IT AND TURNING AROUND. I THINK VIGILANCE APPLIES FOR PLTS AND CTLRS -- AND IS IMPERATIVE UNDER THESE CONDITIONS WHERE THE MAP DOESN'T MATCH THE TERRAIN!

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.