Narrative:

Our initial taxi instructions were to follow another aircraft for an intersection takeoff on runway 28L at the intersection of runways 23 and 28L. The instructions were later modified for us to continue on our own after the other aircraft decided to takeoff at the F1 intersection. Clearance delivery had given us a release time and while on taxiway D the controller reconfirmed the time, then retracted it and told us he could get us airborne immediately. Then he told us to taxi to runway 28L via runway 23, proceed onto and down the runway. I switched to tower frequency and continued the before takeoff and taxi checklists. As we approached runway 28L our taxi speed was decreasing and I thought we were going to stop. I looked back into the cockpit to finish the last few checklist items. Shortly afterward tower called, the nose of the aircraft was moving onto the edge of the runway and tower wanted to know if we were ready for takeoff since we were on the runway. We were cleared for takeoff and airborne shortly thereafter. No aircraft were on final and we did not create a conflict. I had assumed the captain would not go onto the runway until being cleared by tower. Slowing down as we approached the runway further convinced me he was going to stop. Having arrived at the runway and thinking the captain was maneuvering to a stop I continued the checklists. This diverted my attention inside and I did not realize we were encroaching on the runway. An unfamiliar airport at night, a short taxi, and numerous calls from ground control delayed the completion of the checklists until reaching the runway. Those factors coupled with the long day (10 hours) could have contributed to the captain's misunderstanding of the taxi instructions. He still maintains that we were cleared onto the active by ground control. I, on the other hand, have never been cleared by ground control onto an active runway and would never enter the active without tower approval. This is probably why I was so convinced the captain was slowing to a stop as we approached the active. Callback conversation with reporter revealed the following information: reporter states several factors involved in this situation. Ground controller had a sense of urgency in his communication. Kept repeating instruction with no change and used 'we'll get you off right away' each time. Only 4 aircraft on frequency but made it sound very busy. The ramp area is hugh and at night you just point in the direction of taxiway D and search. It is hard to locate. Reporter had delayed checklist until sure they were established on D then began procedures. Looking at airport diagram he feels it makes no sense to taxi on runway 23. Should not use it at night.

Google
 

Original NASA ASRS Text

Title: ACR TAXIES ONTO ACTIVE RWY WITHOUT CLRNC.

Narrative: OUR INITIAL TAXI INSTRUCTIONS WERE TO FOLLOW ANOTHER ACFT FOR AN INTXN TKOF ON RWY 28L AT THE INTXN OF RWYS 23 AND 28L. THE INSTRUCTIONS WERE LATER MODIFIED FOR US TO CONTINUE ON OUR OWN AFTER THE OTHER ACFT DECIDED TO TKOF AT THE F1 INTXN. CLRNC DELIVERY HAD GIVEN US A RELEASE TIME AND WHILE ON TAXIWAY D THE CTLR RECONFIRMED THE TIME, THEN RETRACTED IT AND TOLD US HE COULD GET US AIRBORNE IMMEDIATELY. THEN HE TOLD US TO TAXI TO RWY 28L VIA RWY 23, PROCEED ONTO AND DOWN THE RWY. I SWITCHED TO TWR FREQ AND CONTINUED THE BEFORE TKOF AND TAXI CHKLISTS. AS WE APCHED RWY 28L OUR TAXI SPD WAS DECREASING AND I THOUGHT WE WERE GOING TO STOP. I LOOKED BACK INTO THE COCKPIT TO FINISH THE LAST FEW CHKLIST ITEMS. SHORTLY AFTERWARD TWR CALLED, THE NOSE OF THE ACFT WAS MOVING ONTO THE EDGE OF THE RWY AND TWR WANTED TO KNOW IF WE WERE READY FOR TKOF SINCE WE WERE ON THE RWY. WE WERE CLRED FOR TKOF AND AIRBORNE SHORTLY THEREAFTER. NO ACFT WERE ON FINAL AND WE DID NOT CREATE A CONFLICT. I HAD ASSUMED THE CAPT WOULD NOT GO ONTO THE RWY UNTIL BEING CLRED BY TWR. SLOWING DOWN AS WE APCHED THE RWY FURTHER CONVINCED ME HE WAS GOING TO STOP. HAVING ARRIVED AT THE RWY AND THINKING THE CAPT WAS MANEUVERING TO A STOP I CONTINUED THE CHKLISTS. THIS DIVERTED MY ATTN INSIDE AND I DID NOT REALIZE WE WERE ENCROACHING ON THE RWY. AN UNFAMILIAR ARPT AT NIGHT, A SHORT TAXI, AND NUMEROUS CALLS FROM GND CTL DELAYED THE COMPLETION OF THE CHKLISTS UNTIL REACHING THE RWY. THOSE FACTORS COUPLED WITH THE LONG DAY (10 HRS) COULD HAVE CONTRIBUTED TO THE CAPT'S MISUNDERSTANDING OF THE TAXI INSTRUCTIONS. HE STILL MAINTAINS THAT WE WERE CLRED ONTO THE ACTIVE BY GND CTL. I, ON THE OTHER HAND, HAVE NEVER BEEN CLRED BY GND CTL ONTO AN ACTIVE RWY AND WOULD NEVER ENTER THE ACTIVE WITHOUT TWR APPROVAL. THIS IS PROBABLY WHY I WAS SO CONVINCED THE CAPT WAS SLOWING TO A STOP AS WE APCHED THE ACTIVE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES SEVERAL FACTORS INVOLVED IN THIS SITUATION. GND CTLR HAD A SENSE OF URGENCY IN HIS COM. KEPT REPEATING INSTRUCTION WITH NO CHANGE AND USED 'WE'LL GET YOU OFF RIGHT AWAY' EACH TIME. ONLY 4 ACFT ON FREQ BUT MADE IT SOUND VERY BUSY. THE RAMP AREA IS HUGH AND AT NIGHT YOU JUST POINT IN THE DIRECTION OF TAXIWAY D AND SEARCH. IT IS HARD TO LOCATE. RPTR HAD DELAYED CHKLIST UNTIL SURE THEY WERE ESTABLISHED ON D THEN BEGAN PROCS. LOOKING AT ARPT DIAGRAM HE FEELS IT MAKES NO SENSE TO TAXI ON RWY 23. SHOULD NOT USE IT AT NIGHT.

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.