<< >> NASA ASRS Report 385907, November 1997

Reported loss of separation when an air carrier B737 was vectored too close behind an air carrier cargo DC8 for a different runway.

Attributes
ACN	385907
Time
Date	199711
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : msy
State Reference	LA
Altitude	agl bound lower : 300 agl bound upper : 300
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : msy
Operator	common carrier : air carrier
Make Model Name	DC-8 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	385907
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe
Independent Detector	other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 17100 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

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.

Related reports:

• During normal ILS approach, no different than thousands of p...
• Less than standard separation between 2 small aircraft aircr...
• Standard separation was lost between two aircraft that were ...
• Loss of separation between 2 air carrier aircraft on vectors...
• Flight crew of a cessna citation C750, on 2 different occasi...
• Two N90 TRACON controllers vectored descending/climbing airc...

	Enter your search terms Submit search form
	Web www.37000feet.com

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.