Narrative:

Aircraft was cleared for immediate takeoff (traffic inside the marker) on runway 22. We taxied onto runway and told tower we needed a moment to check our departure routing with our WX radar (storms in the area, raining at the airport). We realized our heading was not correct for assigned runway and at that moment tower called us to cancel takeoff clearance because we were lined up on runway 26. We taxied clear and held short of runway 22 for landing traffic. We took off on runway 22 and proceeded without incident. Possible contributing factors were poor visibility and WX (rain), confusing runway intersection and tower's request for an immediate takeoff. Suggest possible warning page (similar to houston hobby) to clarify multiple runway ends.

Google
 

Original NASA ASRS Text

Title: FLC OF AN MLG ACR ACFT INADVERTENTLY TAXIED INTO POS FOR TKOF ON THE WRONG RWY.

Narrative: ACFT WAS CLRED FOR IMMEDIATE TKOF (TFC INSIDE THE MARKER) ON RWY 22. WE TAXIED ONTO RWY AND TOLD TWR WE NEEDED A MOMENT TO CHK OUR DEP ROUTING WITH OUR WX RADAR (STORMS IN THE AREA, RAINING AT THE ARPT). WE REALIZED OUR HDG WAS NOT CORRECT FOR ASSIGNED RWY AND AT THAT MOMENT TWR CALLED US TO CANCEL TKOF CLRNC BECAUSE WE WERE LINED UP ON RWY 26. WE TAXIED CLR AND HELD SHORT OF RWY 22 FOR LNDG TFC. WE TOOK OFF ON RWY 22 AND PROCEEDED WITHOUT INCIDENT. POSSIBLE CONTRIBUTING FACTORS WERE POOR VISIBILITY AND WX (RAIN), CONFUSING RWY INTXN AND TWR'S REQUEST FOR AN IMMEDIATE TKOF. SUGGEST POSSIBLE WARNING PAGE (SIMILAR TO HOUSTON HOBBY) TO CLARIFY MULTIPLE RWY ENDS.

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.