Atx took evasive action to avoid an air carrier.

Attributes
ACN	121779
Time
Date	198909
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mmj airport : pit
State Reference	PA
Altitude	msl bound lower : 5000 msl bound upper : 6300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pit
Operator	common carrier : air taxi
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
ASRS Report	121779
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment other atc equipment : unspecified other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 6000 vertical : 300
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

I had atx X on a 220 degree heading at 6000' vector for a visibility approach to runway 10L. I had previously been very busy, and therefore was not watching full data blocks of departure sectors. At approximately XA45Z, atx X asked to deviate for jet traffic. This being an unusual request, I stared at the situation for a second, realized what was happening, and said (very loudly), 'yeah, deviate.' that is all that I had time to say. Thankfully, I believe that he was already deviating. What happened: departure control climbed air carrier Y, northbound, from 5000 to 7000' to stay beneath an en route at 8000' that was in his airspace. I believe that his en route data block and my atx X data block were overlapped, and departure control did not see atx X (6000'). Per phone conversation with atx X, he made a 40 degree bank and estimates that they missed by about 1 mi and 200 or 300'. Departure control was climbing through my airspace because SOP climbs were in effect. The C/a system alarmed, but was not soon enough and therefore ineffective. It did not alert us to the situation prior to atx X asking to deviate. Actually, WX was a factor, because the sky was perfectly clear. Otherwise, who knows what would have happened?

Original NASA ASRS Text

Title: ATX TOOK EVASIVE ACTION TO AVOID AN ACR.

Narrative: I HAD ATX X ON A 220 DEG HDG AT 6000' VECTOR FOR A VIS APCH TO RWY 10L. I HAD PREVIOUSLY BEEN VERY BUSY, AND THEREFORE WAS NOT WATCHING FULL DATA BLOCKS OF DEP SECTORS. AT APPROX XA45Z, ATX X ASKED TO DEVIATE FOR JET TFC. THIS BEING AN UNUSUAL REQUEST, I STARED AT THE SITUATION FOR A SECOND, REALIZED WHAT WAS HAPPENING, AND SAID (VERY LOUDLY), 'YEAH, DEVIATE.' THAT IS ALL THAT I HAD TIME TO SAY. THANKFULLY, I BELIEVE THAT HE WAS ALREADY DEVIATING. WHAT HAPPENED: DEP CTL CLBED ACR Y, NBND, FROM 5000 TO 7000' TO STAY BENEATH AN ENRTE AT 8000' THAT WAS IN HIS AIRSPACE. I BELIEVE THAT HIS ENRTE DATA BLOCK AND MY ATX X DATA BLOCK WERE OVERLAPPED, AND DEP CTL DID NOT SEE ATX X (6000'). PER PHONE CONVERSATION WITH ATX X, HE MADE A 40 DEG BANK AND ESTIMATES THAT THEY MISSED BY ABOUT 1 MI AND 200 OR 300'. DEP CTL WAS CLBING THROUGH MY AIRSPACE BECAUSE SOP CLBS WERE IN EFFECT. THE C/A SYS ALARMED, BUT WAS NOT SOON ENOUGH AND THEREFORE INEFFECTIVE. IT DID NOT ALERT US TO THE SITUATION PRIOR TO ATX X ASKING TO DEVIATE. ACTUALLY, WX WAS A FACTOR, BECAUSE THE SKY WAS PERFECTLY CLEAR. OTHERWISE, WHO KNOWS WHAT WOULD HAVE HAPPENED?

Data retrieved from NASA's ASRS site as of August 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.