Narrative:

A PA28 asked for an IFR release with a cessna 182 on approach; I requested a release from flight director and was told released. I looked up saw the other IFR still on approach and asked am I supposed to maintain visual with the inbound IFR and was told I don't know I wasn't told anything. This is happening a lot these days as our SOP contradicts our procedures. We used to take the flash now we don't; but it seems some of the people at P50 are not aware of this and just keep releasing planes with telling us to maintain visual with the other IFR we are talking to. Recommendation; re-write our SOP so it relates to our procedures and make sure everyone at P50 and dvt are aware of the rules.

Google
 

Original NASA ASRS Text

Title: DVT controller described confused event when IFR traffic was released by P50 with IFR traffic on final reporter suggesting procedures between the two facilities and the DVT SOP need to be clarified and briefed.

Narrative: A PA28 asked for an IFR release with a Cessna 182 on approach; I requested a release from Flight Director and was told released. I looked up saw the other IFR still on approach and asked am I supposed to maintain visual with the inbound IFR and was told I don't know I wasn't told anything. This is happening a lot these days as our SOP contradicts our procedures. We used to take the FLASH now we don't; but it seems some of the people at P50 are not aware of this and just keep releasing planes with telling us to maintain visual with the other IFR we are talking to. Recommendation; re-write our SOP so it relates to our procedures and make sure everyone at P50 and DVT are aware of the rules.

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.