ARTCC controller at ZAU instructed controller at ord approach control to stop climbing traffic at FL210 for his traffic at FL220. The ARTCC controller did not notice that the ord controller read back a different call sign and the climbing aircraft was not stopped.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	419447
Time
Date	199811
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : eon
State Reference	IL
Altitude	msl bound lower : 16000 msl bound upper : 22000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau tracon : ord
Make Model Name	Commercial Fixed Wing
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Make Model Name	Lockheed Corp Undifferentiated or Other Model
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 15
ASRS Report	419447
Person 2
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence : required legal separation other anomaly other
Independent Detector	atc equipment other atc equipment : unspecified other controllera
Resolutory Action	none taken : insufficient time
Consequence	Other
Miss Distance	horizontal : 8400 vertical : 400
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Operational Error

Narrative:

I was working the eon low sector at ZAU when I called ord TRACON to stop aircraft Y at FL210 for traffic at FL220. The controller I was talking to at ord said that he was not working the departures but would relay the message. Unfortunately, he had picked the wrong aircraft and I had not noticed that he had read back the wrong call sign although I repeated the call sign. Aircraft Y was a lear jet and it was turbulent so he was climbing at a high rate so I lost the mode C readout at 16000 ft and did not get it back till he was at FL224 and about 1.4 mi from the traffic at FL220. I later found out that when the ord controller relayed the message, the departure controller said that he had already shipped the aircraft. No one informed me that the aircraft did not get the restr plus I still was not working the aircraft that was supposed to be stopped at FL210.

Original NASA ASRS Text

Title: ARTCC CTLR AT ZAU INSTRUCTED CTLR AT ORD APCH CTL TO STOP CLBING TFC AT FL210 FOR HIS TFC AT FL220. THE ARTCC CTLR DID NOT NOTICE THAT THE ORD CTLR READ BACK A DIFFERENT CALL SIGN AND THE CLBING ACFT WAS NOT STOPPED.

Narrative: I WAS WORKING THE EON LOW SECTOR AT ZAU WHEN I CALLED ORD TRACON TO STOP ACFT Y AT FL210 FOR TFC AT FL220. THE CTLR I WAS TALKING TO AT ORD SAID THAT HE WAS NOT WORKING THE DEPS BUT WOULD RELAY THE MESSAGE. UNFORTUNATELY, HE HAD PICKED THE WRONG ACFT AND I HAD NOT NOTICED THAT HE HAD READ BACK THE WRONG CALL SIGN ALTHOUGH I REPEATED THE CALL SIGN. ACFT Y WAS A LEAR JET AND IT WAS TURBULENT SO HE WAS CLBING AT A HIGH RATE SO I LOST THE MODE C READOUT AT 16000 FT AND DID NOT GET IT BACK TILL HE WAS AT FL224 AND ABOUT 1.4 MI FROM THE TFC AT FL220. I LATER FOUND OUT THAT WHEN THE ORD CTLR RELAYED THE MESSAGE, THE DEP CTLR SAID THAT HE HAD ALREADY SHIPPED THE ACFT. NO ONE INFORMED ME THAT THE ACFT DID NOT GET THE RESTR PLUS I STILL WAS NOT WORKING THE ACFT THAT WAS SUPPOSED TO BE STOPPED AT FL210.

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.