TRACON controller described a near loss of separation event when reliance upon an automated procedur...

Attributes
ACN	1108455
Time
Date	201308
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Cessna 310/T310C
Operating Under FAR Part	Part 91
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Narrative:

Working north radar; I took an automated point on two aircraft departing en route. First aircraft climbed to 8;000 and second to 4;000 prior to my boundary. Both aircraft were level crossing into my boundary westbound. I had an aircraft southeast bound at 7;000 which needed to be descended to 5;000 per LOA. After paths had crossed; I descended my aircraft to 5;000. The aircraft I had taken a point out on started climbing. He was out of 4;300; so I immediately turned my aircraft left 090 and to maintain 6;000. The other controller had climbed the aircraft; pointed out; and switched it to approach. I made two mistakes: assuming the aircraft was at his requested altitude and not issuing traffic. Do not make assumptions. There is still verbal coordination needed even with automation.

Original NASA ASRS Text

Title: TRACON Controller described a near loss of separation event when reliance upon an automated procedure was not followed up by needed human coordination to insure everyone was on the same page.

Narrative: Working North RADAR; I took an automated point on two aircraft departing en route. First aircraft climbed to 8;000 and second to 4;000 prior to my boundary. Both aircraft were level crossing into my boundary westbound. I had an aircraft southeast bound at 7;000 which needed to be descended to 5;000 per LOA. After paths had crossed; I descended my aircraft to 5;000. The aircraft I had taken a point out on started climbing. He was out of 4;300; so I immediately turned my aircraft left 090 and to maintain 6;000. The other Controller had climbed the aircraft; pointed out; and switched it to Approach. I made two mistakes: assuming the aircraft was at his requested altitude and not issuing traffic. Do not make assumptions. There is still verbal coordination needed even with automation.

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

TRACON controller described a near loss of separation event when reliance upon an automated procedure was not followed up by needed human coordination to insure everyone was on the same page.