Narrative:

Aircraft #2 was vectored too close behind aircraft #1 on final to a different runway, low IFR WX, missed approach was not protected. I was relieved prior to loss of separation and out of TRACON. Callback conversation with reporter revealed the following information: reporter stated the DC8 was on approach for runway 10 and the B737 on approach for runway 1. Reporter indicated that due to WX the required separation was for the B737 to be no closer than 3 mi from the DC8 in order to protect for a possible missed approach on runway 1. Reporter stated he had worked the DC8 and another was working the B737. Reporter alleged that the regional personnel made a determination that the incident was a non event and not an operational error.

Google
 

Original NASA ASRS Text

Title: RPTED LOSS OF SEPARATION WHEN AN ACR B737 WAS VECTORED TOO CLOSE BEHIND AN ACR CARGO DC8 FOR A DIFFERENT RWY.

Narrative: ACFT #2 WAS VECTORED TOO CLOSE BEHIND ACFT #1 ON FINAL TO A DIFFERENT RWY, LOW IFR WX, MISSED APCH WAS NOT PROTECTED. I WAS RELIEVED PRIOR TO LOSS OF SEPARATION AND OUT OF TRACON. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THE DC8 WAS ON APCH FOR RWY 10 AND THE B737 ON APCH FOR RWY 1. RPTR INDICATED THAT DUE TO WX THE REQUIRED SEPARATION WAS FOR THE B737 TO BE NO CLOSER THAN 3 MI FROM THE DC8 IN ORDER TO PROTECT FOR A POSSIBLE MISSED APCH ON RWY 1. RPTR STATED HE HAD WORKED THE DC8 AND ANOTHER WAS WORKING THE B737. RPTR ALLEGED THAT THE REGIONAL PERSONNEL MADE A DETERMINATION THAT THE INCIDENT WAS A NON EVENT AND NOT AN OPERROR.

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