Narrative:

Conditions in the vicinity of abq airport: broken, RA, windshear, virga. Prior to push from the gate, the first officer dispatch, and I were involved in computing, recomputing takeoff data and amending the flight release, because on conditions in the vicinity of abq airport (see conditions above). After pushback, engine start and call for taxi, we were advised to 'hold your position -- a runway change was in progress' (runway 17 to runway 8). After taxi clearance to runway 8 and during taxi, the first officer recomputed takeoff data for runway 8, the checklist(south) were accomplished and takeoff procedures were discussed (windshear/adverse conditions). While holding in position on runway 8 (first officer's takeoff), and during our continued discussion of the takeoff (takeoff conditions, procedures and techniques), a cleared for takeoff call was issued by abq TR. The first officer responded 'XXX cleared for takeoff' and began the takeoff roll. After a very short time period (approximately 3-4 seconds) abq tower controller responded with 'XXX, hold your position' then 'the takeoff clearance was not for you.' with that, I aborted the takeoff roll after rolling an estimated 700-750 ft (short of the landing end of runway 8), approximately 2000 ft from the intersection of runways 17 and 8 at a very low speed (estimated 40 KTS or less). Airline took off on runway 17. After checking takeoff data again and cleared for takeoff by abq tower, we accomplished takeoff and climb out on runway 8. Upon arrival in oak, I called XXX, XXXX, abq tower for discussion of the event.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-300 CREW BEGAN TKOF WHEN A CLRNC WAS ISSUED FOR ANOTHER ACFT AT ABQ.

Narrative: CONDITIONS IN THE VICINITY OF ABQ ARPT: BROKEN, RA, WINDSHEAR, VIRGA. PRIOR TO PUSH FROM THE GATE, THE FO DISPATCH, AND I WERE INVOLVED IN COMPUTING, RECOMPUTING TKOF DATA AND AMENDING THE FLT RELEASE, BECAUSE ON CONDITIONS IN THE VICINITY OF ABQ ARPT (SEE CONDITIONS ABOVE). AFTER PUSHBACK, ENG START AND CALL FOR TAXI, WE WERE ADVISED TO 'HOLD YOUR POS -- A RWY CHANGE WAS IN PROGRESS' (RWY 17 TO RWY 8). AFTER TAXI CLRNC TO RWY 8 AND DURING TAXI, THE FO RECOMPUTED TKOF DATA FOR RWY 8, THE CHKLIST(S) WERE ACCOMPLISHED AND TKOF PROCS WERE DISCUSSED (WINDSHEAR/ADVERSE CONDITIONS). WHILE HOLDING IN POS ON RWY 8 (FO'S TKOF), AND DURING OUR CONTINUED DISCUSSION OF THE TKOF (TKOF CONDITIONS, PROCS AND TECHNIQUES), A CLRED FOR TKOF CALL WAS ISSUED BY ABQ TR. THE FO RESPONDED 'XXX CLRED FOR TKOF' AND BEGAN THE TKOF ROLL. AFTER A VERY SHORT TIME PERIOD (APPROX 3-4 SECONDS) ABQ TWR CTLR RESPONDED WITH 'XXX, HOLD YOUR POS' THEN 'THE TKOF CLRNC WAS NOT FOR YOU.' WITH THAT, I ABORTED THE TKOF ROLL AFTER ROLLING AN ESTIMATED 700-750 FT (SHORT OF THE LNDG END OF RWY 8), APPROX 2000 FT FROM THE INTXN OF RWYS 17 AND 8 AT A VERY LOW SPD (ESTIMATED 40 KTS OR LESS). AIRLINE TOOK OFF ON RWY 17. AFTER CHKING TKOF DATA AGAIN AND CLRED FOR TKOF BY ABQ TWR, WE ACCOMPLISHED TKOF AND CLBOUT ON RWY 8. UPON ARR IN OAK, I CALLED XXX, XXXX, ABQ TWR FOR DISCUSSION OF THE EVENT.

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.