Narrative:

Takeoff on other than assigned runway! ATIS was received and recorded correctly. Clearance received, taxi instructions were issued. The aircraft was parked near to the takeoff runway used -- a 60 second taxi at most passenger had been dropped off and aircraft was an empty flight home. This presented a good training leg for a low time co-pilot. As PNF, I performed all checklist items and was monitoring the start of taxi. As we approached the landing runway in use, we were instructed to monitor the tower -- the usual busy air traffic and communications was present. The controller called us and asked if we were ready, cleared for takeoff traffic on short final. This meant I had to speed up the pretkof checks and hurry the copilot so as to accommodate the flow of events. Seeing the aircraft on close in final, I was pressed to hurry a rolling takeoff, however, we were cleared on runway 22L, the traffic was on runway 27L for landing. Thus seeing our traffic I assisted the takeoff but on runway 27L instead of runway 22L. The only factor that could have induced this kind of error is the onset of the extremely busy nature of O'hare airport and maybe that we had just shortly before, landed on runway 27L. When all system are ready for flight, the mental priority is sped up to accommodate the local environment. Couple this to a quasi training environment and it becomes a near single pilot operation, with all the potential that accompanies it. Another factor that comes to mind is that during 19 yrs of numerous operations into and out of O'hare, most of my departures were from runway 27L while arrs were on runway 32L. It seems possible that I could instinctively use runway 27L on this takeoff as well.

Related reports:

Google
 

Original NASA ASRS Text

Title: UNAUTH RWY ENTRY OP. UNAUTH TKOF. TKOF ON WRONG RWY.

Narrative: TKOF ON OTHER THAN ASSIGNED RWY! ATIS WAS RECEIVED AND RECORDED CORRECTLY. CLRNC RECEIVED, TAXI INSTRUCTIONS WERE ISSUED. THE ACFT WAS PARKED NEAR TO THE TKOF RWY USED -- A 60 SECOND TAXI AT MOST PAX HAD BEEN DROPPED OFF AND ACFT WAS AN EMPTY FLT HOME. THIS PRESENTED A GOOD TRAINING LEG FOR A LOW TIME CO-PLT. AS PNF, I PERFORMED ALL CHKLIST ITEMS AND WAS MONITORING THE START OF TAXI. AS WE APCHED THE LNDG RWY IN USE, WE WERE INSTRUCTED TO MONITOR THE TWR -- THE USUAL BUSY AIR TFC AND COMS WAS PRESENT. THE CTLR CALLED US AND ASKED IF WE WERE READY, CLRED FOR TKOF TFC ON SHORT FINAL. THIS MEANT I HAD TO SPD UP THE PRETKOF CHKS AND HURRY THE COPLT SO AS TO ACCOMMODATE THE FLOW OF EVENTS. SEEING THE ACFT ON CLOSE IN FINAL, I WAS PRESSED TO HURRY A ROLLING TKOF, HOWEVER, WE WERE CLRED ON RWY 22L, THE TFC WAS ON RWY 27L FOR LNDG. THUS SEEING OUR TFC I ASSISTED THE TKOF BUT ON RWY 27L INSTEAD OF RWY 22L. THE ONLY FACTOR THAT COULD HAVE INDUCED THIS KIND OF ERROR IS THE ONSET OF THE EXTREMELY BUSY NATURE OF O'HARE ARPT AND MAYBE THAT WE HAD JUST SHORTLY BEFORE, LANDED ON RWY 27L. WHEN ALL SYS ARE READY FOR FLT, THE MENTAL PRIORITY IS SPED UP TO ACCOMMODATE THE LCL ENVIRONMENT. COUPLE THIS TO A QUASI TRAINING ENVIRONMENT AND IT BECOMES A NEAR SINGLE PLT OP, WITH ALL THE POTENTIAL THAT ACCOMPANIES IT. ANOTHER FACTOR THAT COMES TO MIND IS THAT DURING 19 YRS OF NUMEROUS OPS INTO AND OUT OF O'HARE, MOST OF MY DEPS WERE FROM RWY 27L WHILE ARRS WERE ON RWY 32L. IT SEEMS POSSIBLE THAT I COULD INSTINCTIVELY USE RWY 27L ON THIS TKOF AS WELL.

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.