TRACON controller described a loss of separation event claiming the introduction of oapm airspace as...

Narrative:

Aircraft X was on a vector southbound @5000 feet in my airspace. I had another aircraft in very close proximity to him that I was trying to sequence him with (he was passing the other aircraft). As I went to call traffic I saw a limited data block descending out of about 5800 feet descending southwest bound on a converging course. I immediately turned aircraft X southwest-bound and descended him to 3000 feet and called traffic. The aircraft probably got within 500 feet and 2 miles. I did not get to watch a replay so that is just a recollection.1. Since [the introduction of] optimization of airspace and procedures in the metroplex (oapm) airspace changes very few people (including myself) know exactly where their airspace is without looking; thus many people violate your airspace accidentally or without knowing where their actual airspace is.2. This aircraft was a medical emergency. It was tagged with a yellow 'me' but now since non-RNAV aircraft are also in yellow you no longer associate a 'yellow' color with a medical emergency (as it used to be one of the only things yellow and since you didn't see them that often you automatically noticed them easier)3. Many of us are still used to descending to 5000 feet on feeder east and sometimes it still 'slips out' although I do not know if that happened in this case or not.4. Way too much 'look and go' through other people's airspace without proper point-outs. (Again; I do not know if this was the case here. 5. With three supervisors in the tracon; someone could have walked over to ZZZ north and showed me the aircraft and pointed out that the aircraft was going direct to the airport to try to accommodate the descent for him. This is how it should happen! When I am controller in charge I always walk over to other positions and make sure they are aware of the emergency! 1. Stop all of the 'look and go' in the tracon and ensure that controllers are making proper point outs. 2. Make procedures for the supervisors that they ensure ll controllers effected or who may be effected are aware of the situation. 3. It is too late about the lack of training on the oapm stuff that I know was atsaped numerous times.

Original NASA ASRS Text

Title: TRACON Controller described a loss of separation event claiming the introduction of OAPM airspace as well as some current procedures contributed to the incident.

Narrative: Aircraft X was on a vector southbound @5000 feet in my airspace. I had another aircraft in very close proximity to him that I was trying to sequence him with (he was passing the other aircraft). As I went to call traffic I saw a limited data block descending out of about 5800 feet descending SW bound on a converging course. I immediately turned Aircraft X southwest-bound and descended him to 3000 feet and called traffic. The aircraft probably got within 500 feet and 2 miles. I did not get to watch a replay so that is just a recollection.1. Since [the introduction of] Optimization of Airspace and Procedures in the Metroplex (OAPM) airspace changes very few people (including myself) know exactly where their airspace is without looking; thus many people violate your airspace accidentally or without knowing where their actual airspace is.2. This aircraft was a medical emergency. It was tagged with a yellow 'ME' but now since non-RNAV aircraft are also in yellow you no longer associate a 'yellow' color with a medical emergency (as it used to be one of the only things yellow and since you didn't see them that often you automatically noticed them easier)3. Many of us are still used to descending to 5000 feet on feeder east and sometimes it still 'slips out' although I do not know if that happened in this case or not.4. Way too much 'look and go' through other people's airspace without proper point-outs. (again; I do not know if this was the case here. 5. With THREE supervisors in the tracon; someone could have walked over to ZZZ North and showed me the aircraft and pointed out that the aircraft was going direct to the airport to try to accommodate the descent for him. This is how it SHOULD happen! When I am CIC I always walk over to other positions and make sure they are aware of the emergency! 1. Stop all of the 'look and go' in the Tracon and ensure that controllers are making proper point outs. 2. Make procedures for the supervisors that they ensure ll controllers effected or who may be effected are aware of the situation. 3. It is too late about the lack of training on the OAPM stuff that I know was ATSAPed numerous times.

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	1211613
Time
Date	201410
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
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 Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

TRACON controller described a loss of separation event claiming the introduction of oapm airspace as well as some current procedures contributed to the incident.