37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 176320 |
Time | |
Date | 199104 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : gsh |
State Reference | IN |
Altitude | msl bound lower : 14000 msl bound upper : 14000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau artcc : zjx |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | cruise other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar oversight : supervisor |
Qualification | controller : radar |
Experience | controller supervisory : 4 |
ASRS Report | 196320 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller non radar : 8 controller radar : 6 |
ASRS Report | 175698 |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Operational Deviation Intra Facility Coordination Failure |
Narrative:
I was the radar controller working the gsh sector. I accepted a handoff from cleveland center on air carrier X at 14000' proceeding direct fwa. Fwa VOR was off the air which caused X to be east of course on handoff. X was issued a heading to keep him tracking on his present course. I then handed off X to the next sector and coordination the heading. In addition, approval was given to descend air carrier X. When the olk sector radar controller called cleveland to advise that X would be descending, the reply was they were not watching X. After hearing this, I talked to the cleveland center controller and questioned him about the situation considering the location of air carrier X on handoff. The reply I received was that he had been watching X all along. I considered the situation to be a non-occurrence. Just after the termination of my phone call with cleveland, the plant sector called and asked if an air carrier Y flight was a surprise. When I looked at the data block, all appeared normal. My reply was that I didn't know what he was talking about and I would discuss the matter once off position. We later had a discussion in which the plant controller said he received a late handoff. I asked if there was a problem of a confliction, and if it needed to be pursued. His reply was no. Given the fact this was in the same area, and in the thought of team spirit and area cooperation, I considered the matter closed. Supplemental information from acn 175698. I was receiving controller for aircraft X. I needed to change his altitude and called sector controller in whose airspace X was. He gave me control, but I needed control from adjacent center, as X was on boundary. When I called adjacent center they had no knowledge of aircraft; had received no point out. I told this controller I would check into situation. I notified the controller who had xferred X to me. As this controller is my supervisor, I felt I had done my duty.
Original NASA ASRS Text
Title: INTERFAC COORD PROBLEM BETWEEN ZAU AND ZOB REFERENCE POSITION AND ALT ASSIGNMENT FOR ACR. OPERATIONAL DEVIATION.
Narrative: I WAS THE RADAR CTLR WORKING THE GSH SECTOR. I ACCEPTED A HDOF FROM CLEVELAND CTR ON ACR X AT 14000' PROCEEDING DIRECT FWA. FWA VOR WAS OFF THE AIR WHICH CAUSED X TO BE EAST OF COURSE ON HDOF. X WAS ISSUED A HDG TO KEEP HIM TRACKING ON HIS PRESENT COURSE. I THEN HANDED OFF X TO THE NEXT SECTOR AND COORD THE HDG. IN ADDITION, APPROVAL WAS GIVEN TO DSND ACR X. WHEN THE OLK SECTOR RADAR CTLR CALLED CLEVELAND TO ADVISE THAT X WOULD BE DSNDING, THE REPLY WAS THEY WERE NOT WATCHING X. AFTER HEARING THIS, I TALKED TO THE CLEVELAND CTR CTLR AND QUESTIONED HIM ABOUT THE SITUATION CONSIDERING THE LOCATION OF ACR X ON HDOF. THE REPLY I RECEIVED WAS THAT HE HAD BEEN WATCHING X ALL ALONG. I CONSIDERED THE SITUATION TO BE A NON-OCCURRENCE. JUST AFTER THE TERMINATION OF MY PHONE CALL WITH CLEVELAND, THE PLANT SECTOR CALLED AND ASKED IF AN ACR Y FLT WAS A SURPRISE. WHEN I LOOKED AT THE DATA BLOCK, ALL APPEARED NORMAL. MY REPLY WAS THAT I DIDN'T KNOW WHAT HE WAS TALKING ABOUT AND I WOULD DISCUSS THE MATTER ONCE OFF POS. WE LATER HAD A DISCUSSION IN WHICH THE PLANT CTLR SAID HE RECEIVED A LATE HDOF. I ASKED IF THERE WAS A PROB OF A CONFLICTION, AND IF IT NEEDED TO BE PURSUED. HIS REPLY WAS NO. GIVEN THE FACT THIS WAS IN THE SAME AREA, AND IN THE THOUGHT OF TEAM SPIRIT AND AREA COOPERATION, I CONSIDERED THE MATTER CLOSED. SUPPLEMENTAL INFO FROM ACN 175698. I WAS RECEIVING CTLR FOR ACFT X. I NEEDED TO CHANGE HIS ALT AND CALLED SECTOR CTLR IN WHOSE AIRSPACE X WAS. HE GAVE ME CTL, BUT I NEEDED CTL FROM ADJACENT CTR, AS X WAS ON BOUNDARY. WHEN I CALLED ADJACENT CTR THEY HAD NO KNOWLEDGE OF ACFT; HAD RECEIVED NO POINT OUT. I TOLD THIS CTLR I WOULD CHK INTO SITUATION. I NOTIFIED THE CTLR WHO HAD XFERRED X TO ME. AS THIS CTLR IS MY SUPVR, I FELT I HAD DONE MY DUTY.
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.