Military controller, providing approach control services to civil airport, unable to provide positiv...

Attributes
ACN	419899
Time
Date	199811
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : law
State Reference	OK
Environment
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Flight Phase	climbout : intermediate altitude
Route In Use	departure other enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	other
Flight Phase	descent : approach landing other
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : local
Experience	controller non radar : 22
ASRS Report	419899
Person 2
Affiliation	government : military
Function	other personnel other
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : insufficient time
Consequence	Other
Miss Distance	horizontal : 5900
Supplementary
Air Traffic Incident	Inter Facility Coordination Failure Operational Error other

Narrative:

Air carrier #1, an SF34, had taxied for departure off runway 17. Runway 35 was active but the winds were light and almost a direct crosswind. Ft sill arac runs the approach control for the lawton area and gave us traffic on 2 T38's on PAR approachs to ft sill. I called for a release on air carrier #1 and was told to give him a right turn to heading 240 degrees and they would call back with a release. A short time later, the radar controller amended the heading to a left turn to 090 degrees and would call back with a release. I taxied air carrier #1 into position and hold on runway 17. At approximately XX25, the radar controller released air carrier #1 with a left turn to 090 degrees. The radar controller called back a short time later, requesting the position of air carrier #1. The aircraft was midfield and airborne and the radar controller was so advised. When air carrier #1 was starting his left turn, less than 1/2 mi east of the runway, the radar controller asked me to change his heading to a right turn to 240 degrees. I complied. As the air carrier #1 was turning southwest, I observed a T38 northbound, less than 1 mi to the southeast of air carrier #1. Both aircraft were on IFR flight plans.

Original NASA ASRS Text

Title: MIL CTLR, PROVIDING APCH CTL SVCS TO CIVIL ARPT, UNABLE TO PROVIDE POSITIVE SEPARATION BTWN T38 INBOUND OPPOSITE DIRECTION TO A RELEASED SF34.

Narrative: ACR #1, AN SF34, HAD TAXIED FOR DEP OFF RWY 17. RWY 35 WAS ACTIVE BUT THE WINDS WERE LIGHT AND ALMOST A DIRECT XWIND. FT SILL ARAC RUNS THE APCH CTL FOR THE LAWTON AREA AND GAVE US TFC ON 2 T38'S ON PAR APCHS TO FT SILL. I CALLED FOR A RELEASE ON ACR #1 AND WAS TOLD TO GIVE HIM A R TURN TO HDG 240 DEGS AND THEY WOULD CALL BACK WITH A RELEASE. A SHORT TIME LATER, THE RADAR CTLR AMENDED THE HEADING TO A L TURN TO 090 DEGS AND WOULD CALL BACK WITH A RELEASE. I TAXIED ACR #1 INTO POS AND HOLD ON RWY 17. AT APPROX XX25, THE RADAR CTLR RELEASED ACR #1 WITH A L TURN TO 090 DEGS. THE RADAR CTLR CALLED BACK A SHORT TIME LATER, REQUESTING THE POS OF ACR #1. THE ACFT WAS MIDFIELD AND AIRBORNE AND THE RADAR CTLR WAS SO ADVISED. WHEN ACR #1 WAS STARTING HIS L TURN, LESS THAN 1/2 MI E OF THE RWY, THE RADAR CTLR ASKED ME TO CHANGE HIS HEADING TO A R TURN TO 240 DEGS. I COMPLIED. AS THE ACR #1 WAS TURNING SW, I OBSERVED A T38 NBOUND, LESS THAN 1 MI TO THE SE OF ACR #1. BOTH ACFT WERE ON IFR FLT PLANS.

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.

Military controller, providing approach control services to civil airport, unable to provide positive separation between T38 inbound opposite direction to a released SF34.