Narrative:

Our letter of agreement (LOA) with phx tower says that turboprop aircraft east flow are assigned a 050 heading climbing to 050. They must give miles in trail with northbound jets following; with the exception of one northbound SID. The laluz departure is runway heading to 4 miles east of the airport then turns left to approximately a 050 heading to fly to forpe intersection. The problem is that departure loses divergence within 4 miles of the aircraft departing with turboprop aircraft assigned a 050 heading. Again there is no restriction for in trail spacing with a turboprop assigned a 050 heading and a turbojet on the laluz. What happened specifically here and is normally the case is that the turboprop departed from runway 7R; soon as he crossed the runway 7L they departed the [jet] on the laluz departure. At 4 miles from the airport the [jet] turned left to continue the departure but the turboprop was not yet out of 040 to make a left turn due to the minimum vectoring altitude (MVA). Basically our procedures caused this. I have elevated this procedure for the last 2 years and nothing internally ever changes.I recommend to fix this problem the tower has to give miles in trail with a turboprop ahead of any jet including the laluz departure. I don't understand how everyone at this building can know that this procedure sets the controller up to have an operational error (oe) but nothing will be done. I mentioned this to our operations manager just last week and he said he didn't see the problem with us having to fix the deal from happening. Our facility has never had a safety culture and this is a great example. I plan to write many more reports on this until it is fixed.

Related reports:

Google
 

Original NASA ASRS Text

Title: P50 TRACON Controller reported receiving a jet departure on a conflicting route overtaking a turboprop departure from the Tower which was permitted according to current facility directives.

Narrative: Our Letter of Agreement (LOA) with PHX tower says that turboprop aircraft east flow are assigned a 050 heading climbing to 050. They must give miles in trail with northbound jets following; with the exception of one northbound SID. The LALUZ departure is runway heading to 4 miles east of the airport then turns left to approximately a 050 heading to fly to FORPE intersection. The problem is that departure loses divergence within 4 miles of the aircraft departing with turboprop aircraft assigned a 050 heading. Again there is no restriction for in trail spacing with a turboprop assigned a 050 heading and a turbojet on the LALUZ. What happened specifically here and is normally the case is that the turboprop departed from runway 7R; soon as he crossed the runway 7L they departed the [jet] on the LALUZ departure. At 4 miles from the airport the [jet] turned left to continue the departure but the turboprop was not yet out of 040 to make a left turn due to the Minimum Vectoring Altitude (MVA). Basically our procedures caused this. I have elevated this procedure for the last 2 years and nothing internally ever changes.I recommend to fix this problem the tower has to give miles in trail with a turboprop ahead of any jet including the LALUZ departure. I don't understand how everyone at this building can know that this procedure sets the controller up to have an Operational Error (OE) but nothing will be done. I mentioned this to our Operations Manager just last week and he said he didn't see the problem with us having to fix the deal from happening. Our facility has never had a safety culture and this is a great example. I plan to write many more reports on this until it is fixed.

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.