Radar controller infringed on buffer zone between positions with air carrier Y potential less than standard separation with air carrier X. Operational deviation.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	189233
Time
Date	199109
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dfw
State Reference	TX
Altitude	msl bound lower : 9000 msl bound upper : 9000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dfw
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller military : 8 controller radar : 15
ASRS Report	189233
Person 2
Affiliation	government : faa
Function	controller : approach other personnel other
Qualification	controller : developmental
Events
Anomaly	conflict : airborne less severe non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Miss Distance	horizontal : 18000 vertical : 0
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Deviation

Narrative:

I was watching a radar developmental on feeder west. We were vectoring air carrier X to fit in the sequence for downwind traffic to runway 13R. The developmental turned air carrier X to fit behind another air carrier. Then he turned air carrier X right to 350. We then observed and were shown by a controller next to us a 9300 air carrier Y. Air carrier X was descending through 9700. The developmental told air carrier X turn right immediately 010 and issued traffic. Air carrier X said he saw air carrier Y. There was no conflict. My problem is the DR3 position a jet departure position was also conducting training. They turned their departure northbound but by my estimation they were so close to our airspace boundary as to be in it. They did not protect our airspace by 1 1/2 mi. The DR3 instructor said they had 3 mi and had us in sight but did not apply visual separation. I told him I thought even if he had 3 mi they did not protect the airspace by the required min. He said ok we won't do it again!

Original NASA ASRS Text

Title: RADAR CTLR INFRINGED ON BUFFER ZONE BTWN POSITIONS WITH ACR Y POTENTIAL LTSS WITH ACR X. OPDEV.

Narrative: I WAS WATCHING A RADAR DEVELOPMENTAL ON FEEDER W. WE WERE VECTORING ACR X TO FIT IN THE SEQUENCE FOR DOWNWIND TFC TO RWY 13R. THE DEVELOPMENTAL TURNED ACR X TO FIT BEHIND ANOTHER ACR. THEN HE TURNED ACR X R TO 350. WE THEN OBSERVED AND WERE SHOWN BY A CTLR NEXT TO US A 9300 ACR Y. ACR X WAS DSNDING THROUGH 9700. THE DEVELOPMENTAL TOLD ACR X TURN R IMMEDIATELY 010 AND ISSUED TFC. ACR X SAID HE SAW ACR Y. THERE WAS NO CONFLICT. MY PROBLEM IS THE DR3 POS A JET DEP POS WAS ALSO CONDUCTING TRAINING. THEY TURNED THEIR DEP NBOUND BUT BY MY ESTIMATION THEY WERE SO CLOSE TO OUR AIRSPACE BOUNDARY AS TO BE IN IT. THEY DID NOT PROTECT OUR AIRSPACE BY 1 1/2 MI. THE DR3 INSTRUCTOR SAID THEY HAD 3 MI AND HAD US IN SIGHT BUT DID NOT APPLY VISUAL SEPARATION. I TOLD HIM I THOUGHT EVEN IF HE HAD 3 MI THEY DID NOT PROTECT THE AIRSPACE BY THE REQUIRED MIN. HE SAID OK WE WON'T DO IT AGAIN!

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.