Reported crossing traffic situation involving the second of a flight of 2 VFR military F16's departi...

Attributes
ACN	370766
Time
Date	199706
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sju
State Reference	PR
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : sju
Operator	other
Make Model Name	Fighting Falcon F16
Operating Under FAR Part	other : other
Navigation In Use	Other Other
Flight Phase	climbout : initial cruise other
Route In Use	departure other
Flight Plan	VFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : takeoff climbout : initial
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar pilot : private
Experience	flight time total : 100
ASRS Report	370766
Person 2
Affiliation	government : military
Function	flight crew : single pilot
Qualification	pilot : military
Events
Anomaly	conflict : airborne less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa other other : unspecified
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 200 vertical : 1000
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

I was working the local position in the sju tower. The cabin attendant coordinator position was not manned, and a flow, to call departure control on all IFR departures, was established due to d-brite OTS. At approximately XX37Z aircraft #1 (VFR) was taxied into position and hold, awaiting arrival traffic to clear runway 10. Called departure control for release on aircraft #2, which departure control released. An air carrier was inbound for runway 10, starting right base. Local controller asked aircraft #1 how long they will stay on runway 10. Response was 'minimum time, ready for takeoff.' as per LOA with sju cerap, switch aircraft #1 to departure control frequency and cleared him for takeoff. Put aircraft #2 on runway 8 on position and hold. Change air carrier to land on runway 8. First F16 took off on a 350 degree heading, crossing runway 8 northbound. Cleared aircraft #2 for takeoff due to proximity of the air carrier. Noticed second F16 still rolling off on runway 10. Cleared aircraft #2 to abort takeoff and then, ask if they could stop. Aircraft #2 advised unable to stop. Aircraft #2 was cleared to a 100 degree heading, to which flight crew stated unable, and flew runway heading. First F16 has already crossed northbound runway 8. Second F16 noticed traffic departing runway 8 and climbed straight up and then banked northbound. Aircraft #2 stayed low, and advised that they had F16 in sight. Aircraft #2 was turned northbound and switched. Poor planning, blocked both runways. Never block both runways. I could take the air carrier northbound and resequence him for another approach. Second option, keep aircraft #2 on position and hold, and give the air carrier a go around. Third option, put the air carrier on left 360 degree turn for spacing and land on runway 10, keeping aircraft #2 on hold.

Original NASA ASRS Text

Title: RPTED XING TFC SIT INVOLVING THE SECOND OF A FLT OF 2 VFR MIL F16'S DEPARTING RWY 10 TURNING TO A 350 DEG HDG ON A CONVERGING COURSE WITH AN ACR B737 DEPARTING RWY 8. BOTH ACFT HAD THE OTHER IN SIGHT AND AVOIDED EACH OTHER.

Narrative: I WAS WORKING THE LCL POS IN THE SJU TWR. THE CAB COORDINATOR POS WAS NOT MANNED, AND A FLOW, TO CALL DEP CTL ON ALL IFR DEPS, WAS ESTABLISHED DUE TO D-BRITE OTS. AT APPROX XX37Z ACFT #1 (VFR) WAS TAXIED INTO POS AND HOLD, AWAITING ARR TFC TO CLR RWY 10. CALLED DEP CTL FOR RELEASE ON ACFT #2, WHICH DEP CTL RELEASED. AN ACR WAS INBOUND FOR RWY 10, STARTING R BASE. LCL CTLR ASKED ACFT #1 HOW LONG THEY WILL STAY ON RWY 10. RESPONSE WAS 'MINIMUM TIME, READY FOR TKOF.' AS PER LOA WITH SJU CERAP, SWITCH ACFT #1 TO DEP CTL FREQ AND CLRED HIM FOR TKOF. PUT ACFT #2 ON RWY 8 ON POS AND HOLD. CHANGE ACR TO LAND ON RWY 8. FIRST F16 TOOK OFF ON A 350 DEG HDG, XING RWY 8 NBOUND. CLRED ACFT #2 FOR TKOF DUE TO PROX OF THE ACR. NOTICED SECOND F16 STILL ROLLING OFF ON RWY 10. CLRED ACFT #2 TO ABORT TKOF AND THEN, ASK IF THEY COULD STOP. ACFT #2 ADVISED UNABLE TO STOP. ACFT #2 WAS CLRED TO A 100 DEG HDG, TO WHICH FLC STATED UNABLE, AND FLEW RWY HDG. FIRST F16 HAS ALREADY CROSSED NBOUND RWY 8. SECOND F16 NOTICED TFC DEPARTING RWY 8 AND CLBED STRAIGHT UP AND THEN BANKED NBOUND. ACFT #2 STAYED LOW, AND ADVISED THAT THEY HAD F16 IN SIGHT. ACFT #2 WAS TURNED NBOUND AND SWITCHED. POOR PLANNING, BLOCKED BOTH RWYS. NEVER BLOCK BOTH RWYS. I COULD TAKE THE ACR NBOUND AND RESEQUENCE HIM FOR ANOTHER APCH. SECOND OPTION, KEEP ACFT #2 ON POS AND HOLD, AND GIVE THE ACR A GAR. THIRD OPTION, PUT THE ACR ON L 360 DEG TURN FOR SPACING AND LAND ON RWY 10, KEEPING ACFT #2 ON HOLD.

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.

Reported crossing traffic situation involving the second of a flight of 2 VFR military F16's departing runway 10 turning to a 350 degree heading on a converging course with an air carrier B737 departing runway 8. Both aircraft had the other in sight and avoided each other.