Aircraft came in close proximity to opposite direction traffic.

Attributes
ACN	130301
Time
Date	198912
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : spa
State Reference	SC
Altitude	msl bound lower : 9500 msl bound upper : 10000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : ztl
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	cruise other
Flight Plan	None
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : cfi pilot : atp
Experience	flight time last 90 days : 25 flight time total : 2600 flight time type : 1000
ASRS Report	130301
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : nmac other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 499
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

I was working ZTL under VFR advisory service. Center called traffic at my 10 O'clock descending from 10,000 to 9000'. I said that I had traffic in sight but to please advise me if there would be a conflict (since he was at close range, converging, and descending through my altitude). I watched the target's lights grow larger and finally made an evasive turn (unsure of the altitude difference, if any). The traffic passed slightly below me but close enough that 1) the radar returns should've overlapped, and 2) it could be considered a near miss. After landing, I spoke with ZTL area supervisor (by landline) and he acknowledged a probable controller judgement error. I would be interested to review both the tapes and radar records, since the target was on another frequency. I'm not sure he ever had me in sight. I believe there are several concerns/contributing factors: 1) see and avoid. Difficult to determine altitude, course convergence, closure rates, etc at night, even when target is in sight. 2) controller should not have cleared the target through the altitude of a known conflict with as little horizontal separation as existed.

Original NASA ASRS Text

Title: ACFT CAME IN CLOSE PROX TO OPPOSITE DIRECTION TRAFFIC.

Narrative: I WAS WORKING ZTL UNDER VFR ADVISORY SERVICE. CENTER CALLED TFC AT MY 10 O'CLOCK DESCENDING FROM 10,000 TO 9000'. I SAID THAT I HAD TFC IN SIGHT BUT TO PLEASE ADVISE ME IF THERE WOULD BE A CONFLICT (SINCE HE WAS AT CLOSE RANGE, CONVERGING, AND DESCENDING THROUGH MY ALT). I WATCHED THE TARGET'S LIGHTS GROW LARGER AND FINALLY MADE AN EVASIVE TURN (UNSURE OF THE ALT DIFFERENCE, IF ANY). THE TFC PASSED SLIGHTLY BELOW ME BUT CLOSE ENOUGH THAT 1) THE RADAR RETURNS SHOULD'VE OVERLAPPED, AND 2) IT COULD BE CONSIDERED A NEAR MISS. AFTER LNDG, I SPOKE WITH ZTL AREA SUPVR (BY LANDLINE) AND HE ACKNOWLEDGED A PROBABLE CTLR JUDGEMENT ERROR. I WOULD BE INTERESTED TO REVIEW BOTH THE TAPES AND RADAR RECORDS, SINCE THE TARGET WAS ON ANOTHER FREQ. I'M NOT SURE HE EVER HAD ME IN SIGHT. I BELIEVE THERE ARE SEVERAL CONCERNS/CONTRIBUTING FACTORS: 1) SEE AND AVOID. DIFFICULT TO DETERMINE ALT, COURSE CONVERGENCE, CLOSURE RATES, ETC AT NIGHT, EVEN WHEN TARGET IS IN SIGHT. 2) CTLR SHOULD NOT HAVE CLRED THE TARGET THROUGH THE ALT OF A KNOWN CONFLICT WITH AS LITTLE HORIZONTAL SEPARATION AS EXISTED.

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.