Narrative:

There are two departure sectors; one for northbound aircraft; one for southbound. A B737 departed and contacted me on the southbound sector (santan). He had filed a northbound SID; the st. Johns 5 SID. The computer had assigned him the southbound SID; MAXXO1. He checked on frequency with me. I radar identified him and climbed him. He then turned northbound into the other sector's airspace (navajo). I pointed him out to navajo and turned the aircraft south. The B737 was confused; as he was expecting something else. I had to give him instructions several times. His slow turn then began bringing him into the local air force base's airspace; with active F-16 flights. He was pointed out to the air force base controllers. The situation became unsafe as more departures rolled off phx and the B737 continued to question control instructions. The whole basis of separation at phx tower is for aircraft to turn the proper direction (north or south). The pilot's file for something and the computer routinely amends the route. The tower has no responsibility to ensure what SID the aircraft is on. They merely confirm the beacon code only. It is assumed the aircraft has read his ACARS or however he gets his routing; but no one ever confirms his routing! If the routing was confirmed on the ground this would not happen. We have three parallel runways; it is common to have two aircraft on two runways departing at the same time. If we assume they are both going to turn the correct way; it is dangerous. An accident is waiting to happen. This same situation has happened to me four times.

Related reports:

Google
 

Original NASA ASRS Text

Title: A P50 Controller expressed concern about the failure of Tower controllers to insure departing aircraft are assigned the correct SID routing which results in aircraft departing on the wrong departure frequency.

Narrative: There are two departure sectors; one for northbound aircraft; one for southbound. A B737 departed and contacted me on the southbound sector (Santan). He had filed a northbound SID; the St. Johns 5 SID. The computer had assigned him the southbound SID; MAXXO1. He checked on frequency with me. I RADAR identified him and climbed him. He then turned northbound into the other sector's airspace (Navajo). I pointed him out to Navajo and turned the aircraft south. The B737 was confused; as he was expecting something else. I had to give him instructions several times. His slow turn then began bringing him into the local Air Force Base's airspace; with active F-16 flights. He was pointed out to the Air Force Base Controllers. The situation became unsafe as more departures rolled off PHX and the B737 continued to question control instructions. The whole basis of separation at PHX Tower is for aircraft to turn the proper direction (north or south). The pilot's file for something and the computer routinely amends the route. The Tower has NO RESPONSIBILITY to ensure what SID the aircraft is on. They merely confirm the beacon code ONLY. It is ASSUMED the aircraft has read his ACARS or however he gets his routing; but no one ever confirms his routing! If the routing was confirmed on the GROUND this would not happen. We have three parallel runways; it is common to have two aircraft on two runways departing at the same time. If we ASSUME they are both going to turn the correct way; it is dangerous. An accident is waiting to happen. This same situation has happened to me four times.

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