Narrative:

Jfk airport was hard IFR as indicated above. We were using the ILS runway 22L approach and departing runway 22R. We were unable to see even the taxiways so everything was being done by pilot reports and asde. There were 2 local controllers, one for traffic on the approach, and one was working the departures off runway 22R. All of the arrs eventually had to cross runway 22R to get to the terminals. The arrival local was holding them short and indicating which intersection through strip placement and marking. As my traffic permitted, I would authorize the arrival local to cross, when appropriate, also stating which intersection and/or how many. The arrival local acknowledged this coordination each time, and advised when clear. I cleared air carrier X for takeoff and put air carrier Z in position on the runway. I told air carrier Z it would be 'a moment or 2 in position for in trail restrictions.' the arrival local questioned my intentions with air carrier Z. O I explained that I was going to hold him for spacing behind a previous departure and to allow her to get some of her traffic across. (I did not state 'cross runway 22R' nor did she acknowledge a crossing). A min later, air carrier X advised that he aborted his takeoff because an air carrier Y had crossed the runway. Apparently, the arrival local had mistaken my answer to her question to be coordination, and had cleared air carrier Y to cross runway 22R. Callback conversation with reporter revealed the following information: the reporter stated the arrival local controller had cleared 3 aircraft to cross runway 22R in front of air carrier X on takeoff roll. Air carrier Y, large transport, had been cleared first at taxiway F. Air carrier X had just started takeoff roll, saw air carrier Y, and aborted departure. Closest proximity was 1000 ft. Both local controllers were decertified. Asde radar was giving a good presentation of aircraft on the runways.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X ON TKOF ROLL HAD LTSS WITH ACR Y XING RWY. ACR X EVASIVE ACTION TAKEN ABORTED TKOF. SYS ERROR.

Narrative: JFK ARPT WAS HARD IFR AS INDICATED ABOVE. WE WERE USING THE ILS RWY 22L APCH AND DEPARTING RWY 22R. WE WERE UNABLE TO SEE EVEN THE TAXIWAYS SO EVERYTHING WAS BEING DONE BY PLT RPTS AND ASDE. THERE WERE 2 LCL CTLRS, ONE FOR TFC ON THE APCH, AND ONE WAS WORKING THE DEPS OFF RWY 22R. ALL OF THE ARRS EVENTUALLY HAD TO CROSS RWY 22R TO GET TO THE TERMINALS. THE ARR LCL WAS HOLDING THEM SHORT AND INDICATING WHICH INTXN THROUGH STRIP PLACEMENT AND MARKING. AS MY TFC PERMITTED, I WOULD AUTHORIZE THE ARR LCL TO CROSS, WHEN APPROPRIATE, ALSO STATING WHICH INTXN AND/OR HOW MANY. THE ARR LCL ACKNOWLEDGED THIS COORD EACH TIME, AND ADVISED WHEN CLR. I CLRED ACR X FOR TKOF AND PUT ACR Z IN POS ON THE RWY. I TOLD ACR Z IT WOULD BE 'A MOMENT OR 2 IN POS FOR IN TRAIL RESTRICTIONS.' THE ARR LCL QUESTIONED MY INTENTIONS WITH ACR Z. O I EXPLAINED THAT I WAS GOING TO HOLD HIM FOR SPACING BEHIND A PREVIOUS DEP AND TO ALLOW HER TO GET SOME OF HER TFC ACROSS. (I DID NOT STATE 'CROSS RWY 22R' NOR DID SHE ACKNOWLEDGE A XING). A MIN LATER, ACR X ADVISED THAT HE ABORTED HIS TKOF BECAUSE AN ACR Y HAD CROSSED THE RWY. APPARENTLY, THE ARR LCL HAD MISTAKEN MY ANSWER TO HER QUESTION TO BE COORD, AND HAD CLRED ACR Y TO CROSS RWY 22R. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE ARR LCL CTLR HAD CLRED 3 ACFT TO CROSS RWY 22R IN FRONT OF ACR X ON TKOF ROLL. ACR Y, LGT, HAD BEEN CLRED FIRST AT TAXIWAY F. ACR X HAD JUST STARTED TKOF ROLL, SAW ACR Y, AND ABORTED DEP. CLOSEST PROX WAS 1000 FT. BOTH LCL CTLRS WERE DECERTIFIED. ASDE RADAR WAS GIVING A GOOD PRESENTATION OF ACFT ON THE RWYS.

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.