Aircraft was instructed to abort takeoff. Flight crew complied with instructions.

Attributes
ACN	161795
Time
Date	199011
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : fay
State Reference	NC
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : fay
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport
Flight Phase	climbout : takeoff other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time total : 10200
ASRS Report	161795
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : rejected takeoff other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Cleared for takeoff on runway 4 at fayetteville, nc, power on both engines open full and airspeed indication just coming alive (probably 500-600' of roll) when tower cancelled our takeoff clearance. Takeoff rejected at low speed with no problem and we cleared the runway. I asked the tower why and was told there was pop-up traffic in the departure corridor. I asked if the traffic was IFR and was told to stand by. After clearing the runway we contacted dispatch/maintenance concerning any requirements for paperwork concerning the rejected takeoff. While I was talking to the company, the tower told the first officer that our takeoff clearance was cancelled because the departure controller at the last instant, decided he wasn't ready to take the traffic. Tower apologized! WX conditions were perfect, slow speed/high power reject was no problem. The problem is that, under other circumstances, it could have been a very unsafe situation. It also frightens the heck out of a plane full of passengers who are apprehensive enough about flying. This was very poor coordination between ATC facs, but lack of communication between ATC sectors and facs seems to be everyday occurrences.

Original NASA ASRS Text

Title: ACFT WAS INSTRUCTED TO ABORT TKOF. FLC COMPLIED WITH INSTRUCTIONS.

Narrative: CLRED FOR TKOF ON RWY 4 AT FAYETTEVILLE, NC, PWR ON BOTH ENGS OPEN FULL AND AIRSPD INDICATION JUST COMING ALIVE (PROBABLY 500-600' OF ROLL) WHEN TWR CANCELLED OUR TKOF CLRNC. TKOF REJECTED AT LOW SPD WITH NO PROB AND WE CLRED THE RWY. I ASKED THE TWR WHY AND WAS TOLD THERE WAS POP-UP TFC IN THE DEP CORRIDOR. I ASKED IF THE TFC WAS IFR AND WAS TOLD TO STAND BY. AFTER CLRING THE RWY WE CONTACTED DISPATCH/MAINT CONCERNING ANY REQUIREMENTS FOR PAPERWORK CONCERNING THE REJECTED TKOF. WHILE I WAS TALKING TO THE COMPANY, THE TWR TOLD THE F/O THAT OUR TKOF CLRNC WAS CANCELLED BECAUSE THE DEP CTLR AT THE LAST INSTANT, DECIDED HE WASN'T READY TO TAKE THE TFC. TWR APOLOGIZED! WX CONDITIONS WERE PERFECT, SLOW SPD/HIGH PWR REJECT WAS NO PROB. THE PROB IS THAT, UNDER OTHER CIRCUMSTANCES, IT COULD HAVE BEEN A VERY UNSAFE SITUATION. IT ALSO FRIGHTENS THE HECK OUT OF A PLANE FULL OF PAXS WHO ARE APPREHENSIVE ENOUGH ABOUT FLYING. THIS WAS VERY POOR COORD BTWN ATC FACS, BUT LACK OF COM BTWN ATC SECTORS AND FACS SEEMS TO BE EVERYDAY OCCURRENCES.

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.