 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller reported after accepting a point out; another sector changed the data block information without coordination.
| Attributes | |
| ACN | 1546216 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | PC-12 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
My d-side accepted an automated point out on aircraft X. The aircraft was at FL230; level. He informed me he'd accepted the point out; we continued going about our business. Later I noticed aircraft X was descending; FL210 was in the data block. I asked my d-side if eon sector had called to coordinate (I did not see the distracting P above the data block; I looked at bearz mdm (main display monitor) and bearz did not have the wifi symbol). The d-side said no; no call. But they'd amended the altitude then put a new distracting P over the data block; tried to make a new (illegal) unsafe automated point out. I explained to him that this represents a new abuse of the unsafe automated point out procedure. They change the data block; they're required to call. But it's like jurassic park; we will evolve new ways to misuse the unsafe automated point out procedure.[my suggestion is to] terminate the unsafe automated point out procedure until adequate training can be completed.
Original NASA ASRS Text
Title: ZAU Controller reported after accepting a point out; another sector changed the data block information without coordination.
Narrative: My d-side accepted an automated point out on Aircraft X. The aircraft was at FL230; level. He informed me he'd accepted the point out; we continued going about our business. Later I noticed Aircraft X was descending; FL210 was in the data block. I asked my d-side if EON sector had called to coordinate (I did not see the distracting P above the data block; I looked at BEARZ MDM (Main Display Monitor) and BEARZ did not have the wifi symbol). The d-side said no; no call. But they'd amended the altitude then put a new distracting P over the data block; tried to make a new (illegal) unsafe automated point out. I explained to him that this represents a new abuse of the unsafe automated point out procedure. They change the data block; they're required to call. But it's like Jurassic Park; we will evolve new ways to misuse the unsafe automated point out procedure.[My suggestion is to] terminate the unsafe automated point out procedure until adequate training can be completed.
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.