An air carrier crew does not understand the ATC policies regarding handling military.

Attributes
ACN	318392
Time
Date	199510
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : sfo
State Reference	CA
Altitude	msl bound lower : 5000 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : sfo
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	cruise other descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Military Transport
Operating Under FAR Part	other : other
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp pilot : commercial
Experience	flight time last 90 days : 150 flight time total : 14000 flight time type : 1000
ASRS Report	318392
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 165 flight time total : 12197 flight time type : 1200
ASRS Report	318600
Events
Anomaly	conflict : airborne less severe other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	Other
Miss Distance	horizontal : 6000 vertical : 300
Supplementary
Air Traffic Incident	other

Narrative:

Military flight departed sfo to the east directly into the path of all inbound traffic causing unexpected, last min and confusing air traffic control conditions for all acrs making approachs to the west. Suggestion: departures of military be conducted in a safe and orderly manner considering local airport traffic, ie, takeoff west. We realize the type of flight military require (fast), but taking off directly into the inbound flow created a starburst type of situation. At the very last min, we had our approach clearance canceled, told to turn off of the 'quiet bridge' procedure at approximately D15 and 4500 ft, given an immediate turn to 180 degrees, climb to 5000 ft directly into at least 5 sets of landing lights making the 'tip toe' approach from the south. After numerous vectors, somehow on a handoff, we were lost by ATC. Again more vectoring that resulted in a complete go around and finally more vectors for a visual approach to runway 28L. We have asked that the radar (ATC) tapes be saved for investigation by ATC and our pilot's union.

Original NASA ASRS Text

Title: AN ACR CREW DOES NOT UNDERSTAND THE ATC POLICIES REGARDING HANDLING MIL.

Narrative: MIL FLT DEPARTED SFO TO THE E DIRECTLY INTO THE PATH OF ALL INBOUND TFC CAUSING UNEXPECTED, LAST MIN AND CONFUSING AIR TFC CTL CONDITIONS FOR ALL ACRS MAKING APCHS TO THE W. SUGGESTION: DEPS OF MIL BE CONDUCTED IN A SAFE AND ORDERLY MANNER CONSIDERING LCL ARPT TFC, IE, TKOF W. WE REALIZE THE TYPE OF FLT MIL REQUIRE (FAST), BUT TAKING OFF DIRECTLY INTO THE INBOUND FLOW CREATED A STARBURST TYPE OF SIT. AT THE VERY LAST MIN, WE HAD OUR APCH CLRNC CANCELED, TOLD TO TURN OFF OF THE 'QUIET BRIDGE' PROC AT APPROX D15 AND 4500 FT, GIVEN AN IMMEDIATE TURN TO 180 DEGS, CLB TO 5000 FT DIRECTLY INTO AT LEAST 5 SETS OF LNDG LIGHTS MAKING THE 'TIP TOE' APCH FROM THE S. AFTER NUMEROUS VECTORS, SOMEHOW ON A HDOF, WE WERE LOST BY ATC. AGAIN MORE VECTORING THAT RESULTED IN A COMPLETE GAR AND FINALLY MORE VECTORS FOR A VISUAL APCH TO RWY 28L. WE HAVE ASKED THAT THE RADAR (ATC) TAPES BE SAVED FOR INVESTIGATION BY ATC AND OUR PLT'S UNION.

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.