37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 841366 |
Time | |
Date | 200906 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
I took over sector a and while setting up the user request evaluation tool (uret) and taking care of traffic entering the sector. Sector B called to coordinate air carrier X descending due to air conditioner problem. Air carrier X was eastbound. I approved down to FL250; took the hand-off removed the interim altitude and flashed air carrier X to C sector. I continued to setup sector and took care of more hand-offs and answered aircraft check-ins. When I scanned back to air carrier X I saw that he had turned southeast bound into the path of air carrier Y. I stopped air carrier Y altitude at FL290 (he already was through FL277) and called C sector to stop air carrier X at FL300. C sector knew nothing about air carrier X because my keyboard entry failed on the hand-off. I went back to air carrier Y and turned him for more space (the targets were not going to merge but I wanted more space). I called traffic to air carrier Y and initiated a call to B sector. Separation was lost.
Original NASA ASRS Text
Title: Enroute Controller experienced loss of separation shortly after assuming the operational position; listing sector take over duties and coordination requirements as causal factors.
Narrative: I took over Sector A and while setting up the user request evaluation tool (URET) and taking care of traffic entering the sector. Sector B called to coordinate ACR X descending due to air conditioner problem. ACR X was eastbound. I approved down to FL250; took the hand-off removed the interim altitude and flashed ACR X to C sector. I continued to setup sector and took care of more hand-offs and answered aircraft check-ins. When I scanned back to ACR X I saw that he had turned southeast bound into the path of ACR Y. I stopped ACR Y altitude at FL290 (he already was through FL277) and called C sector to stop ACR X at FL300. C sector knew nothing about ACR X because my keyboard entry failed on the hand-off. I went back to ACR Y and turned him for more space (the targets were not going to merge but I wanted more space). I called traffic to ACR Y and initiated a Call to B sector. Separation was lost.
Data retrieved from NASA's ASRS site as of April 2012 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.