Operation deviation.

Attributes
ACN	288724
Time
Date	199411
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dma
State Reference	AZ
Altitude	msl bound lower : 4500 msl bound upper : 4500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : tus tower : tus
Operator	other
Make Model Name	Thunderbolt II (Warthog A-10)
Operating Under FAR Part	other : other
Flight Phase	descent : approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Challenger CL600
Operating Under FAR Part	other : unknown
Flight Phase	climbout : intermediate altitude cruise other
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller non radar : 7 controller radar : 12
ASRS Report	288724
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	conflict : airborne less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : unable
Consequence	faa : investigated
Miss Distance	horizontal : 3000
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

I was vectoring the A10 to PAR final for runway 30. I attempted to hand him off to the PAR final controller but was unable because the aircraft was about 1/2 mi left of course. The tucson local controller had a challenger in the right traffic pattern for runway 29R. The challenger flew a wide pattern and ended up head on with my traffic on final for runway 30, at about the same altitude. The local controller did not point out the aircraft before he left his airspace. The local controller realized the challenger left his airspace so he pointed him out but it was too late. I issued traffic as soon as I was aware of it but the A10 said he was going to file a hatr. The challenger had the A10 in sight and was maintaining visual separation. I feel this could have been prevented if the local controller had either insured the challenger remained in his airspace or done a timely point out. Please feel free to contact me if you need further information.

Original NASA ASRS Text

Title: OP DEV.

Narrative: I WAS VECTORING THE A10 TO PAR FINAL FOR RWY 30. I ATTEMPTED TO HAND HIM OFF TO THE PAR FINAL CTLR BUT WAS UNABLE BECAUSE THE ACFT WAS ABOUT 1/2 MI LEFT OF COURSE. THE TUCSON LCL CTLR HAD A CHALLENGER IN THE R TFC PATTERN FOR RWY 29R. THE CHALLENGER FLEW A WIDE PATTERN AND ENDED UP HEAD ON WITH MY TFC ON FINAL FOR RWY 30, AT ABOUT THE SAME ALT. THE LCL CTLR DID NOT POINT OUT THE ACFT BEFORE HE LEFT HIS AIRSPACE. THE LCL CTLR REALIZED THE CHALLENGER LEFT HIS AIRSPACE SO HE POINTED HIM OUT BUT IT WAS TOO LATE. I ISSUED TFC AS SOON AS I WAS AWARE OF IT BUT THE A10 SAID HE WAS GOING TO FILE A HATR. THE CHALLENGER HAD THE A10 IN SIGHT AND WAS MAINTAINING VISUAL SEPARATION. I FEEL THIS COULD HAVE BEEN PREVENTED IF THE LCL CTLR HAD EITHER INSURED THE CHALLENGER REMAINED IN HIS AIRSPACE OR DONE A TIMELY POINT OUT. PLEASE FEEL FREE TO CONTACT ME IF YOU NEED FURTHER INFO.

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.