D10 controller recognizes conflicting event between SF34, under his control, and an MD80 tracking through the adjoining final approach course on another D10 controller's frequency.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	460870
Time
Date	199912
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : ttt.vor
State Reference	TX
Altitude	msl bound lower : 5000 msl bound upper : 5700
Environment
Flight Conditions	VMC
Weather Elements	other
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	SF 340B
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 31r
Flight Phase	descent : approach
Route In Use	approach : instrument precision
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : d10.tracon
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 12 controller time certified in position1 : 4.5
ASRS Report	460870
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne critical non adherence : required legal separation non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	atc equipment : conflict alert other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took evasive action
Consequence	faa : investigated
Miss Distance	horizontal : 3000 vertical : 0
Supplementary
Problem Areas	Airspace Structure Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

I was working a feeder/arrival position. Air carrier X was established on the runway 31R final at 5000 ft. I noticed an aircraft (air carrier Y) descending through 5700 ft and converging. I issued traffic as conflict alert activated. The SF34 saw the MD80 off his left at less than 1 mi and descending. I instructed him to maintain visual and he elected to climb to avoid. I believe the MD80 did not follow control instructions which caused the near midair collision. Also, conflict alert may not have activated quickly enough. A situation on AR1 position may have distraction the controller in charge of air carrier Y causing him to miss the fact that air carrier Y had not taken the turn. Neither pilot apparently had TCASII alerts. Air carrier X did not mention TCASII or RA.

Original NASA ASRS Text

Title: D10 CTLR RECOGNIZES CONFLICTING EVENT BTWN SF34, UNDER HIS CTL, AND AN MD80 TRACKING THROUGH THE ADJOINING FINAL APCH COURSE ON ANOTHER D10 CTLR'S FREQ.

Narrative: I WAS WORKING A FEEDER/ARR POS. ACR X WAS ESTABLISHED ON THE RWY 31R FINAL AT 5000 FT. I NOTICED AN ACFT (ACR Y) DSNDING THROUGH 5700 FT AND CONVERGING. I ISSUED TFC AS CONFLICT ALERT ACTIVATED. THE SF34 SAW THE MD80 OFF HIS L AT LESS THAN 1 MI AND DSNDING. I INSTRUCTED HIM TO MAINTAIN VISUAL AND HE ELECTED TO CLB TO AVOID. I BELIEVE THE MD80 DID NOT FOLLOW CTL INSTRUCTIONS WHICH CAUSED THE NMAC. ALSO, CONFLICT ALERT MAY NOT HAVE ACTIVATED QUICKLY ENOUGH. A SIT ON AR1 POS MAY HAVE DISTR THE CTLR IN CHARGE OF ACR Y CAUSING HIM TO MISS THE FACT THAT ACR Y HAD NOT TAKEN THE TURN. NEITHER PLT APPARENTLY HAD TCASII ALERTS. ACR X DID NOT MENTION TCASII OR RA.

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.