Air carrier aircraft asked ARTCC radar controller if he had traffic for him at his altitude. Controller did, but had not seen the potential conflict and said that the conflict alert did not activate. Controller turned himself in on the error.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	345255
Time
Date	199608
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : sqs
State Reference	MS
Altitude	msl bound lower : 16000 msl bound upper : 16000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Route In Use	enroute airway : zme
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 17
ASRS Report	345255
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : investigated
Miss Distance	horizontal : 10200 vertical : 100
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error
Situations
ATC Facility	other physical facility

Narrative:

I was assigned R66 (jan-low) with moderate traffic. The air carrier asked if I had traffic for him at 16000 ft, up to this time I had not seen the confliction. Conflict alert did not activate nor did the conflict monitor system activate. I had to turn myself in for the loss of separation between the 2 aircraft. The conflict alert system needs to work not just from pass performance but from the actual route of flight the aircraft has filed.

Original NASA ASRS Text

Title: ACR ACFT ASKED ARTCC RADAR CTLR IF HE HAD TFC FOR HIM AT HIS ALT. CTLR DID, BUT HAD NOT SEEN THE POTENTIAL CONFLICT AND SAID THAT THE CONFLICT ALERT DID NOT ACTIVATE. CTLR TURNED HIMSELF IN ON THE ERROR.

Narrative: I WAS ASSIGNED R66 (JAN-LOW) WITH MODERATE TFC. THE ACR ASKED IF I HAD TFC FOR HIM AT 16000 FT, UP TO THIS TIME I HAD NOT SEEN THE CONFLICTION. CONFLICT ALERT DID NOT ACTIVATE NOR DID THE CONFLICT MONITOR SYS ACTIVATE. I HAD TO TURN MYSELF IN FOR THE LOSS OF SEPARATION BTWN THE 2 ACFT. THE CONFLICT ALERT SYS NEEDS TO WORK NOT JUST FROM PASS PERFORMANCE BUT FROM THE ACTUAL RTE OF FLT THE ACFT HAS FILED.

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.