Narrative:

Sju tower issued takeoff clearance runway 8 stating 'no delay.' we acknowledged, pulled onto runway 8, pwred up, began takeoff roll. After takeoff, thrust was set, sju tower called our flight. The captain responded flight rolling. Sju tower then asked if we could abort or stop takeoff roll. Captain responded 'negative.' (at the speed we were at, near V1, it would have been unsafe to abort, we could see that the runway was clear in front of us.) after liftoff, sju tower requested we turn right to 100 degrees. At that point I could see 2 F16's that had just departed runway 10 and were in a climbing left turn toward our aircraft. We leveled off at approximately 500 ft. The F16's climbed over our flight path. We then continued climb out. I knew the F16's, if they saw us, could outclb our aircraft, and the second F16 seemed to climb more aggressively than just to be doing a join-up with the first F16. To prevent recurrence: 1) sju tower could have asked us to abort on his first call rather than waiting. Tower also could have told us what to look for! 2) the F16's were, I assume, on UHF. We were on VHF. Callback conversation with reporter revealed the following information: reporter stated that the captain had called the following day and talked with the supervisor who indicated that there was a less than standard separation of separation between the 2 flts and that the controller would receive remedial training. Reporter stated that the F16 traffic was not given to them. Reporter reiterated that they would have been able to abort the takeoff the first time the controller called them. Reporter alleged the controller was hesitant in his actions to prevent the conflict.

Related reports:

Google
 

Original NASA ASRS Text

Title: LTSS BTWN A FLT OF 2 F16'S DEPARTS FROM RWY 10 AND AN ACR B737 DEPARTING RWY 8. CTLR FIRST ATTEMPTED TO ABORT THE ACR AND THEN ISSUED A TURN TOWARD THE F16'S. THE FLC OF THE B737 HAD THE TFC IN SIGHT AND STOPPED THEIR CLB TILL THE F16'S HAD PASSED.

Narrative: SJU TWR ISSUED TKOF CLRNC RWY 8 STATING 'NO DELAY.' WE ACKNOWLEDGED, PULLED ONTO RWY 8, PWRED UP, BEGAN TKOF ROLL. AFTER TKOF, THRUST WAS SET, SJU TWR CALLED OUR FLT. THE CAPT RESPONDED FLT ROLLING. SJU TWR THEN ASKED IF WE COULD ABORT OR STOP TKOF ROLL. CAPT RESPONDED 'NEGATIVE.' (AT THE SPD WE WERE AT, NEAR V1, IT WOULD HAVE BEEN UNSAFE TO ABORT, WE COULD SEE THAT THE RWY WAS CLR IN FRONT OF US.) AFTER LIFTOFF, SJU TWR REQUESTED WE TURN R TO 100 DEGS. AT THAT POINT I COULD SEE 2 F16'S THAT HAD JUST DEPARTED RWY 10 AND WERE IN A CLBING L TURN TOWARD OUR ACFT. WE LEVELED OFF AT APPROX 500 FT. THE F16'S CLBED OVER OUR FLT PATH. WE THEN CONTINUED CLBOUT. I KNEW THE F16'S, IF THEY SAW US, COULD OUTCLB OUR ACFT, AND THE SECOND F16 SEEMED TO CLB MORE AGGRESSIVELY THAN JUST TO BE DOING A JOIN-UP WITH THE FIRST F16. TO PREVENT RECURRENCE: 1) SJU TWR COULD HAVE ASKED US TO ABORT ON HIS FIRST CALL RATHER THAN WAITING. TWR ALSO COULD HAVE TOLD US WHAT TO LOOK FOR! 2) THE F16'S WERE, I ASSUME, ON UHF. WE WERE ON VHF. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE CAPT HAD CALLED THE FOLLOWING DAY AND TALKED WITH THE SUPVR WHO INDICATED THAT THERE WAS A LTSS OF SEPARATION BTWN THE 2 FLTS AND THAT THE CTLR WOULD RECEIVE REMEDIAL TRAINING. RPTR STATED THAT THE F16 TFC WAS NOT GIVEN TO THEM. RPTR REITERATED THAT THEY WOULD HAVE BEEN ABLE TO ABORT THE TKOF THE FIRST TIME THE CTLR CALLED THEM. RPTR ALLEGED THE CTLR WAS HESITANT IN HIS ACTIONS TO PREVENT THE CONFLICT.

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.