 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID center controller reported observing that the next sector changed the assigned altitude in the aircraft data block to a different altitude than the aircraft was cleared to climb.
| Attributes | |
| ACN | 1389039 |
| Time | |
| Date | 201609 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZID.ARTCC |
| State Reference | IN |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 21 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
This is another example of controllers 'pre-loading' the data block and changing the data block before they are actually working the aircraft! Aircraft X was requesting 32000 feet so I climbed him to 29000 feet (my top altitude) and handed the aircraft off to sector 89. That controller ended up taking the handoff while I was paying attention to another portion of my sector and the sector 89 controller changed the data block to show aircraft X climbing to 32000 feet and flashed it on the ZAU sector 47. When my attention went back to the aircraft X I saw that the data block was changed but I still hadn't switched the aircraft to sector 89. I began to question whether or not I had switched the aircraft yet; but realized that particular controller always does this. I ended up just switching the aircraft to sector 89 when that controller neglected to call me with information. Don't know what to recommend as I seem to be one of the few controllers in my area that follows procedures and doesn't pre-load data blocks without coordination.
Original NASA ASRS Text
Title: ZID Center Controller reported observing that the next sector changed the assigned altitude in the aircraft data block to a different altitude than the aircraft was cleared to climb.
Narrative: This is another example of controllers 'pre-loading' the data block and changing the data block before they are actually working the aircraft! Aircraft X was requesting 32000 feet so I climbed him to 29000 feet (my top altitude) and handed the aircraft off to Sector 89. That controller ended up taking the handoff while I was paying attention to another portion of my sector and the Sector 89 controller changed the data block to show Aircraft X climbing to 32000 feet and flashed it on the ZAU Sector 47. When my attention went back to the Aircraft X I saw that the data block was changed but I still hadn't switched the aircraft to sector 89. I began to question whether or not I had switched the aircraft yet; but realized that particular controller always does this. I ended up just switching the aircraft to sector 89 when that controller neglected to call me with information. Don't know what to recommend as I seem to be one of the few controllers in my area that follows procedures and doesn't pre-load data blocks without coordination.
Data retrieved from NASA's ASRS site 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.