37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1088665 |
Time | |
Date | 201305 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
The aircraft was experiencing a bad ride at FL320 and requested a climb to FL340. I climbed the aircraft to FL340. A minute or so later; I noticed a limited data block the looked like traffic at FL340; still around 8 minutes or so out. The traffic was inside the next sectors' airspace; sector xx (different area). Right at the same time that I noticed the traffic; the sector xx controller called and told me to take the aircraft back down to FL320. I tried to tell the controller that he was getting a bad ride and need to stay higher. The xx controller talked over me and told me FL320. I then told the aircraft that the next sector wanted them to descend back down to FL320; or I could give him a vector to the right. They said they wanted the vector; to avoid going back to the bad rides. I gave the vector; put it in the 4th line and kept the aircraft at FL340. I flashed the aircraft early so the xx controller could see what I had done. A minute or so later I called the xx controller to coordinate the aircraft's request to be vector instead of descending back to the bad ride. The controller would not talk to me about it; even with subsequent coordination calls. Ultimately the aircraft penetrated the xx airspace without a hand off. Recommendation; the xx controller needs to take handoffs; especially when I was the one trying to accommodate the pilot and provide the best service I could for him. The xx controller didn't take the hand-off out of spite; which is a dangerous way of working with lives at stake.
Original NASA ASRS Text
Title: Two different points of view involving a refused handoff event; both Center controllers believing their actions were appropriate.
Narrative: The aircraft was experiencing a bad ride at FL320 and requested a climb to FL340. I climbed the aircraft to FL340. A minute or so later; I noticed a limited data block the looked like traffic at FL340; still around 8 minutes or so out. The traffic was inside the next sectors' airspace; Sector XX (different area). Right at the same time that I noticed the traffic; the Sector XX Controller called and told me to take the aircraft back down to FL320. I tried to tell the Controller that he was getting a bad ride and need to stay higher. The XX Controller talked over me and told me FL320. I then told the aircraft that the next sector wanted them to descend back down to FL320; or I could give him a vector to the right. They said they wanted the vector; to avoid going back to the bad rides. I gave the vector; put it in the 4th line and kept the aircraft at FL340. I flashed the aircraft early so the XX Controller could see what I had done. A minute or so later I called the XX Controller to coordinate the aircraft's request to be vector instead of descending back to the bad ride. The Controller would not talk to me about it; even with subsequent coordination calls. Ultimately the aircraft penetrated the XX airspace without a hand off. Recommendation; the XX Controller needs to take handoffs; especially when I was the one trying to accommodate the pilot and provide the best service I could for him. The XX Controller didn't take the hand-off out of spite; which is a dangerous way of working with lives at stake.
Data retrieved from NASA's ASRS site as of July 2013 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.