Nct controller experienced operational error at 4200 ft when traffic on vectors to visual for sfo failed to turn as directed conflicting with parallel runway traffic.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	806563
Time
Date	200810
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : sfo.vor
State Reference	CA
Altitude	msl single value : 4200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : nct.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : nct.tracon
Operator	common carrier : air carrier
Make Model Name	EMB ERJ 145 ER&LR
Operating Under FAR Part	Part 121
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller limited radar : 1 controller military : 1.5 controller radar : 20 controller time certified in position1 : 19
ASRS Report	806563
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : investigated
Miss Distance	horizontal : 12000 vertical : 800
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Aircraft X was inbound from the southeast of sfo being vectored for a visual approach. The regional jet was being worked by the north final controller for a visual approach. The bases were about 3700 ft and the tops were about 5000 ft. Aircraft X was essentially on a base and I issued him a left turn to 290 degrees; which he read back verbatim. Aircraft X was cleared to 4000 ft initially; and 2500 ft later. The regional jet was turned sbound when the other controller heard me issue aircraft X a left turn to 290 degrees. The regional jet was level at 5000 ft. Aircraft X failed to execute the turn to 290 degrees and went 3 mi before I issued another turn toward the airport. Aircraft X then turned; but ended up within less than our required IFR separation (1000 ft vertical; 3 mi lateral). If aircraft X had initiated the turn he was issued; the loss of separation would not have occurred. FAA management was treating this as an operational error on the part of the controller.

Original NASA ASRS Text

Title: NCT CTLR EXPERIENCED OPERROR AT 4200 FT WHEN TFC ON VECTORS TO VISUAL FOR SFO FAILED TO TURN AS DIRECTED CONFLICTING WITH PARALLEL RWY TFC.

Narrative: ACFT X WAS INBOUND FROM THE SE OF SFO BEING VECTORED FOR A VISUAL APCH. THE REGIONAL JET WAS BEING WORKED BY THE N FINAL CTLR FOR A VISUAL APCH. THE BASES WERE ABOUT 3700 FT AND THE TOPS WERE ABOUT 5000 FT. ACFT X WAS ESSENTIALLY ON A BASE AND I ISSUED HIM A L TURN TO 290 DEGS; WHICH HE READ BACK VERBATIM. ACFT X WAS CLRED TO 4000 FT INITIALLY; AND 2500 FT LATER. THE REGIONAL JET WAS TURNED SBOUND WHEN THE OTHER CTLR HEARD ME ISSUE ACFT X A L TURN TO 290 DEGS. THE REGIONAL JET WAS LEVEL AT 5000 FT. ACFT X FAILED TO EXECUTE THE TURN TO 290 DEGS AND WENT 3 MI BEFORE I ISSUED ANOTHER TURN TOWARD THE ARPT. ACFT X THEN TURNED; BUT ENDED UP WITHIN LESS THAN OUR REQUIRED IFR SEPARATION (1000 FT VERT; 3 MI LATERAL). IF ACFT X HAD INITIATED THE TURN HE WAS ISSUED; THE LOSS OF SEPARATION WOULD NOT HAVE OCCURRED. FAA MGMNT WAS TREATING THIS AS AN OPERROR ON THE PART OF THE CTLR.

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