 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOB ARTCC controller reported a violation of a point out; when another controller descended an aircraft without permission.
| Attributes | |
| ACN | 1604114 |
| Time | |
| Date | 201812 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
The sector to the south of me was coming out of the hold for ZZZ. ZZZ1 sector pointed out an aircraft in a right hand turn out of the holding stack back on course at FL370. I accepted the point out via automated means. No further coordination was accomplished and ZZZ1 sector descended the aircraft to FL310 while still in my airspace. No further call was made. This is a growing problem and has been ever since automated point outs where introduced. Controller(s) take accepting an automated pointout as blanket control.I've filed numerous reports on this issue and still nothing has been done. The definition of a pointout has not changed. If I accept an automated point out; I'm accepting what the data block and route of flight is showing. I am not giving away control of that plane. Further education or briefings need to take place before an accident occurs. This happens on a daily basis.
Original NASA ASRS Text
Title: ZOB ARTCC Controller reported a violation of a point out; when another Controller descended an aircraft without permission.
Narrative: The sector to the south of me was coming out of the hold for ZZZ. ZZZ1 sector pointed out an aircraft in a right hand turn out of the holding stack back on course at FL370. I accepted the point out via automated means. No further coordination was accomplished and ZZZ1 sector descended the aircraft to FL310 while still in my airspace. No further call was made. This is a growing problem and has been ever since automated point outs where introduced. Controller(s) take accepting an automated pointout as blanket control.I've filed numerous reports on this issue and still nothing has been done. The definition of a pointout has not changed. If I accept an automated point out; I'm accepting what the data block and route of flight is showing. I am not giving away control of that plane. Further education or briefings need to take place before an accident occurs. This happens on a daily basis.
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.