Narrative:

On the job training was being performed on arrival and departure sectors. I was the instructor on the arrival sector. Tower local control called us to coordinate a departure left on the SID. We were unaware of this situation prior to them calling. Realizing our confusion; local control hung up and called the supervisor. We told the departure sector to keep the aircraft runway heading on departure because we had an aircraft in the downwind for a runway that would have conflicted with the departure had it stayed on the SID. The supervisor over rode both myself and the departure controller and insisted the departure be left on the SID. No further coordination was made with us and the departure took off and entered our airspace on the SID. Another controller resequenced the aircraft on downwind so as to not conflict with the departure. The departure had to be taken off the SID anyway due to conflicts with other aircraft.I would recommend that the supervisor not override the two controllers whose airspace this aircraft was going to enter. This aircraft should have been left on runway heading thus staying well clear of any conflicting traffic. Instead; it was left on the SID and flown through 2 final vector sectors and an arrival sector that had inbound traffic. If the supervisor was so insistent on keeping the aircraft on the SID; they should have coordinated all of this well ahead of the traffic about to depart. In my opinion it was an unnecessary risk that caused confusion with 3 sectors and 5 different controllers.

Related reports:

Google
 

Original NASA ASRS Text

Title: A TRACON Arrival Controller reported a Supervisor disregarded the Sector Controller's wishes and approved a route for an aircraft that caused the controllers to have to move other aircraft out of the way.

Narrative: On the job training was being performed on arrival and departure sectors. I was the Instructor on the arrival sector. Tower Local Control called us to coordinate a departure left on the SID. We were unaware of this situation prior to them calling. Realizing our confusion; Local Control hung up and called the Supervisor. We told the departure sector to keep the aircraft runway heading on departure because we had an aircraft in the downwind for a runway that would have conflicted with the departure had it stayed on the SID. The Supervisor over rode both myself and the Departure Controller and insisted the departure be left on the SID. No further coordination was made with us and the departure took off and entered our airspace on the SID. Another Controller resequenced the aircraft on downwind so as to not conflict with the departure. The departure had to be taken off the SID anyway due to conflicts with other aircraft.I would recommend that the Supervisor not override the two controllers whose airspace this aircraft was going to enter. This aircraft should have been left on runway heading thus staying well clear of any conflicting traffic. Instead; it was left on the SID and flown through 2 final vector sectors and an arrival sector that had inbound traffic. If the Supervisor was so insistent on keeping the aircraft on the SID; they should have coordinated all of this well ahead of the traffic about to depart. In my opinion it was an unnecessary risk that caused confusion with 3 sectors and 5 different controllers.

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.