Narrative:

The event began at westchester county airport, white plains, ny, while awaiting an IFR release and takeoff clearance for an IFR flight to niagara falls, ny. I was the PIC, handling communications and navigation, along with a copilot, who was the PF for this trip. The WX was VFR, although thunderstorms were approaching rapidly from the northwest. We were #1 for departure, holding short of runway 34. Simultaneous runway operations were in use with traffic landing and departing runways 34 and 29. The tower controller was very busy handling numerous inbound airline and GA aircraft. We were told to hold short of runway 34 in the run-up pad adjacent to taxiway left, awaiting IFR release. After approximately 10 mins, we were told that our release was received and to contact tower. I contacted tower advising that we were ready for takeoff runway 34. We were told to hold short for landing traffic, which we did. After the next aircraft landed and cleared the runway we were instructed by the tower controller, 'aircraft X cleared for immediate takeoff, keep it rolling, traffic on a 2 mi final.' I replied, 'air carrier X cleared for takeoff, we'll keep it rolling.' just as we were lining up on the centerline of the runway, the controller said again, 'aircraft X keep it rolling, traffic on short final.' I replied, 'aircraft X is rolling.' as the copilot advanced the power levers to takeoff power and the aircraft began to accelerate the controller announced, 'aircraft X taxi across and exit the runway and hold on the opposite taxiway.' by this point the aircraft was already rolling and accelerating rapidly. I replied, 'aircraft X is on takeoff roll, unable.' receiving no reply I announced again, 'aircraft X is on takeoff roll, advise.' the next response I heard from the controller was instructing a commuter airline flight to go around. We continued our takeoff which was executed without incident. I feel a large contributing factor to this situation was the high workload for the tower air traffic controller. Handling numerous inbound and outbound aircraft, with severe WX approaching the area, was very hectic and there seemed to be some confusion on both ground and tower frequencys as to the position of several aircraft. My first impression when given the taxi clear instruction was that the controller may have confused our aircraft 'north' number with some other aircraft's. In addition I feel the controller should not have issued the initial takeoff clearance in such a manner, especially knowing the speed and distance of the approaching commuter airline aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: KING AIR 200 CAPT CONTINUES TKOF AFTER TWR CTLR AMENDED TKOF CLRNC TO TAXI ACROSS AND EXIT RWY DUE TO LNDG TFC BECAUSE TKOF ROLL HAD COMMENCED, TWR SENT THE OTHER ACFT AROUND.

Narrative: THE EVENT BEGAN AT WESTCHESTER COUNTY ARPT, WHITE PLAINS, NY, WHILE AWAITING AN IFR RELEASE AND TKOF CLRNC FOR AN IFR FLT TO NIAGARA FALLS, NY. I WAS THE PIC, HANDLING COMS AND NAV, ALONG WITH A COPLT, WHO WAS THE PF FOR THIS TRIP. THE WX WAS VFR, ALTHOUGH TSTMS WERE APCHING RAPIDLY FROM THE NW. WE WERE #1 FOR DEP, HOLDING SHORT OF RWY 34. SIMULTANEOUS RWY OPS WERE IN USE WITH TFC LNDG AND DEPARTING RWYS 34 AND 29. THE TWR CTLR WAS VERY BUSY HANDLING NUMEROUS INBOUND AIRLINE AND GA ACFT. WE WERE TOLD TO HOLD SHORT OF RWY 34 IN THE RUN-UP PAD ADJACENT TO TXWY L, AWAITING IFR RELEASE. AFTER APPROX 10 MINS, WE WERE TOLD THAT OUR RELEASE WAS RECEIVED AND TO CONTACT TWR. I CONTACTED TWR ADVISING THAT WE WERE READY FOR TKOF RWY 34. WE WERE TOLD TO HOLD SHORT FOR LNDG TFC, WHICH WE DID. AFTER THE NEXT ACFT LANDED AND CLRED THE RWY WE WERE INSTRUCTED BY THE TWR CTLR, 'ACFT X CLRED FOR IMMEDIATE TKOF, KEEP IT ROLLING, TFC ON A 2 MI FINAL.' I REPLIED, 'ACR X CLRED FOR TKOF, WE'LL KEEP IT ROLLING.' JUST AS WE WERE LINING UP ON THE CTRLINE OF THE RWY, THE CTLR SAID AGAIN, 'ACFT X KEEP IT ROLLING, TFC ON SHORT FINAL.' I REPLIED, 'ACFT X IS ROLLING.' AS THE COPLT ADVANCED THE PWR LEVERS TO TKOF PWR AND THE ACFT BEGAN TO ACCELERATE THE CTLR ANNOUNCED, 'ACFT X TAXI ACROSS AND EXIT THE RWY AND HOLD ON THE OPPOSITE TXWY.' BY THIS POINT THE ACFT WAS ALREADY ROLLING AND ACCELERATING RAPIDLY. I REPLIED, 'ACFT X IS ON TKOF ROLL, UNABLE.' RECEIVING NO REPLY I ANNOUNCED AGAIN, 'ACFT X IS ON TKOF ROLL, ADVISE.' THE NEXT RESPONSE I HEARD FROM THE CTLR WAS INSTRUCTING A COMMUTER AIRLINE FLT TO GO AROUND. WE CONTINUED OUR TKOF WHICH WAS EXECUTED WITHOUT INCIDENT. I FEEL A LARGE CONTRIBUTING FACTOR TO THIS SIT WAS THE HIGH WORKLOAD FOR THE TWR AIR TFC CTLR. HANDLING NUMEROUS INBOUND AND OUTBOUND ACFT, WITH SEVERE WX APCHING THE AREA, WAS VERY HECTIC AND THERE SEEMED TO BE SOME CONFUSION ON BOTH GND AND TWR FREQS AS TO THE POS OF SEVERAL ACFT. MY FIRST IMPRESSION WHEN GIVEN THE TAXI CLR INSTRUCTION WAS THAT THE CTLR MAY HAVE CONFUSED OUR ACFT 'N' NUMBER WITH SOME OTHER ACFT'S. IN ADDITION I FEEL THE CTLR SHOULD NOT HAVE ISSUED THE INITIAL TKOF CLRNC IN SUCH A MANNER, ESPECIALLY KNOWING THE SPD AND DISTANCE OF THE APCHING COMMUTER AIRLINE ACFT.

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.