Center developmental reported that approach control and center radar controller created traffic conf...

Narrative:

To the best of my ability I will describe what I remember. I had just sat down to train. I was getting a briefing from the previous controller that did not mention the first impending traffic situation which was caused by approach launching an aircraft out of the arrival gate directly at an aircraft coming in the arrival gate at 12000 feet. I sit down and see the departing aircraft turned about 60 degrees right to barely miss an incoming aircraft at 12000 feet. This was a stupid situation caused by approach control. Then the radar controller cleared the departure direct turning him into another arrival. I was still trying to get my bearings on the sector as there was a lot of data block overlay. When the radar controller did so it became a separation problem. I was told to get higher on an aircraft by my trainer and while that was going on the radar controller never de-conflicted the aircraft and a loss of separation occurred about 160 feet. Interesting is that as the radar controller left he said 'that was a close one.' he almost had a separation error. I saw a separation error happen; but the conflict alert never went off so I believe he thinks it was not a conflict. This needs to be investigated as to why the alert never went off and no color of red or any that I know of ever showed up on the display.

Original NASA ASRS Text

Title: Center Developmental reported that Approach Control and Center Radar Controller created traffic conflicts by routing departures through the arrival routing.

Narrative: To the best of my ability I will describe what I remember. I had just sat down to train. I was getting a briefing from the previous controller that did not mention the first impending traffic situation which was caused by Approach launching an aircraft out of the arrival gate directly at an aircraft coming in the arrival gate at 12000 feet. I sit down and see the departing aircraft turned about 60 degrees right to barely miss an incoming aircraft at 12000 feet. This was a stupid situation caused by Approach Control. Then the Radar Controller cleared the departure direct turning him into another arrival. I was still trying to get my bearings on the sector as there was a lot of data block overlay. When the Radar Controller did so it became a separation problem. I was told to get higher on an aircraft by my trainer and while that was going on the Radar Controller never de-conflicted the aircraft and a loss of separation occurred about 160 feet. Interesting is that as the Radar Controller left he said 'that was a close one.' He almost had a separation error. I saw a separation error happen; but the Conflict Alert never went off so I believe he thinks it was not a conflict. This needs to be investigated as to why the alert never went off and no color of red or any that I know of ever showed up on the display.

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

Attributes
ACN	1624752
Time
Date	201903
Local Time Of Day	1201-1800
Place
Locale Reference	ZJX.ARTCC
State Reference	FL
Environment
Light	Daylight
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Direct
Flight Plan	IFR
Person 1
Function	Enroute Trainee
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Center developmental reported that approach control and center radar controller created traffic conflicts by routing departures through the arrival routing.