TRACON Controller reported Tower IFR release was transferred in conflict with Helicopter flight resulted in a pilot reported NMAC.
Synopsis
TRACON Controller reported Tower IFR release was transferred in conflict with Helicopter flight resulted in a pilot reported NMAC.
Narrative
ZZZ Tower Controller requested release for Aircraft X departing Runway XXR. Release was given turning left heading 200. There were no conflicts at that time. ZZZ Tower Controller apparently issued clearance to a helicopter departing ZZZ westbound. This created the first conflict of this scenario. Despite new instructions to turn Aircraft X north-east heading 050; ZZZ Tower Controller waited for Aircraft Y to out-climb departing helicopter traffic then proceeded with the left turn heading 200. This caused conflict with a flight of helicopters that were touring over the ZZZ area between 36 and 39 MSL. Aircraft X passed within 1/4m laterally and 100 feet vertically of Helicopter traffic. Before switching Aircraft X to me; ZZZ Tower Controller - of his own accord - issued continuing left turn direct destination ZZZZZ. On initial contact with me; Aircraft X complained of the near-miss saying; 'that was really close.' I informed the pilot that the continuing left turn would put him back into conflict with the flight of helicopters. Since Aircraft X was already established in the left turn; I asked for pilot preference. Pilot and I concurred that a right-hand turn direct ZZZ1 was best. Had Pilot requested to remain in the left-hand turn I would have issued a climb however; the right-hand turn alleviated potential conflicts without assigning an undesired climb which would have necessitated further coordination with ZZZ2. I worked at ZZZ as a contractor for eight years and cannot fathom why the Controller on duty there wouldn't simply hold the departing helicopter for thirty seconds to ensure there would be no conflict with the departing IFR traffic. Failing that; I cannot fathom why the amended climbout heading 050 was not issued. In the future I can only say that micro-managing ZZZ's Class-D may be necessary. It's easy to armchair-quarterback or suggest that all ZZZ Runway XXR departures should be issued heading 050 but I'm not in the habit of vectoring aircraft away from their filed course/destination when there are no traffic conflicts - until another Controller creates one. Contractors have the same responsibility to separate aircraft as FAA air traffic specialists. ZZZ Controller should be instructed to protect their departure corridor.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.