Date: 202109
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: Embraer Jet Undifferentiated or Other Model
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Situational Awareness; Training / Qualification; Workload
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was asked to train a CPC-IT with over a decade of radar experience and with over half of the allocated hours allowed for the position at hand. Traffic was light and I kept getting distracted by the Data position near the radar scope. I had to stand further away than I usually would because of the constant traffic in and out of the data position; noise from the load speaker; and trying to have some social distancing for COVID.  I have made many complaints about the data position being a complete distraction and today it most certainly was a contributing factor to a NMAC.Aircraft X departed ZZZ and the tower put the aircraft on a 250 heading. The aircraft never checked in and I scrambled to call the tower so they could climb and switch the aircraft before it crossed directly over the obstruction depicted on the video map and below the MVA (Minimum Vectoring Altitude). While this was going on; there were 2 other aircraft on frequency that were becoming a conflict. Once I realized that the trainee was not doing any of the instructions me or the supervisor was giving; I took over the frequency to prevent a loss of separation. Unfortunately; in my scramble to coordinate with all the appropriate sectors and facilities that Aircraft X was seconds from violating; I missed a readback from Aircraft X and they took another aircraft's instruction. I did not notice Aircraft X turning northeast bound immediately because of the coordination at hand and Aircraft X turned right at Aircraft Y that was VFR on frequency. I instructed Aircraft X to turn left and climb; but Aircraft X was already too far in the turn and I continued the right turn back to the east. I however did expect Aircraft X to climb in a timely manner in which they did not. This in turn created a dangerous situation that forced Aircraft Y to turn to the north to avoid the traffic. Although traffic was issued to Aircraft X; I did not see how close the aircraft actually got from the distance I was forced to be from the scope and my coordination efforts that needed to be done.I believe this event happened from combination of multiple events and some expectation bias.  The Data position being a major distraction; COVID social distancing; ZZZ tower procedures allowing an aircraft to depart on a heading at an obstruction and maintaining an altitude below the MVA; Aircraft X not checking in; training on the position; expecting the CPC-IT to not freeze up; Aircraft X not climbing in the timely manner that I assumed they would have; and most importantly; I take responsibility and will definitely lose sleep over the fact that in my scramble; I missed the read back that ended up putting 2 planes in a dangerous situation.My recommendations to hopefully minimize any such event from occurring again would be to:MOVE THE DATA POSITION!Change the departure pie for ZZZ departures off Runway XX.




Synopsis: TRACON Controller reported an airborne conflict and possible descent below minimum altitude occurred when the controller became distracted with the data position; social distancing requirements and supervising a trainee.