37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 679868 |
Time | |
Date | 200512 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : iiu.vortac |
State Reference | KY |
Altitude | msl bound lower : 34000 msl bound upper : 35000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zid.artcc |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 135 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zid.artcc |
Operator | common carrier : air carrier |
Make Model Name | MD-81 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller limited radar : 15 controller non radar : 16 controller radar : 14 controller time certified in position1 : 14 controller time certified in position2 : 5 |
ASRS Report | 679868 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : airborne less severe non adherence : required legal separation |
Independent Detector | atc equipment : conflict alert other controllera |
Resolutory Action | controller : issued alert controller : issued new clearance |
Consequence | faa : investigated |
Miss Distance | horizontal : 10440 vertical : 400 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
While working mystic radar (R92); I was controling air carrier X; an inbound to ord; at FL370. The limited data block of air carrier Y at FL340 was illustrated underneath the data block of air carrier X. My intentions were to descend air carrier X to FL350 and initiate a handoff to louisville radar (R82). I asked the louisville radar controller if he wanted me to turn air carrier X for air carrier Y underneath him. I cleared air carrier X to FL340 and the pilot read back my clearance correctly. I input FL350 into the data block of air carrier X. Corrective action was not taken until I noticed air carrier X descending to FL347. I cleared air carrier X to maintain FL350. Air carrier X descended to FL343 and I issued an immediate climb to FL350 and issued traffic.
Original NASA ASRS Text
Title: ZID CTLR EXPERIENCED OPERROR AT FL340 WHEN ENTERING AN ALT IN THE DATA BLOCK THAT DIFFERED FROM THE VERBAL CLRNC ISSUED.
Narrative: WHILE WORKING MYSTIC RADAR (R92); I WAS CTLING ACR X; AN INBOUND TO ORD; AT FL370. THE LIMITED DATA BLOCK OF ACR Y AT FL340 WAS ILLUSTRATED UNDERNEATH THE DATA BLOCK OF ACR X. MY INTENTIONS WERE TO DSND ACR X TO FL350 AND INITIATE A HDOF TO LOUISVILLE RADAR (R82). I ASKED THE LOUISVILLE RADAR CTLR IF HE WANTED ME TO TURN ACR X FOR ACR Y UNDERNEATH HIM. I CLRED ACR X TO FL340 AND THE PLT READ BACK MY CLRNC CORRECTLY. I INPUT FL350 INTO THE DATA BLOCK OF ACR X. CORRECTIVE ACTION WAS NOT TAKEN UNTIL I NOTICED ACR X DSNDING TO FL347. I CLRED ACR X TO MAINTAIN FL350. ACR X DSNDED TO FL343 AND I ISSUED AN IMMEDIATE CLB TO FL350 AND ISSUED TFC.
Data retrieved from NASA's ASRS site as of January 2009 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.