 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Cleveland center controller reported an airspace deviation associated with a crossing restriction that the pilot busted.
| Attributes | |
| ACN | 1612876 |
| Time | |
| Date | 201901 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Aircraft 1 | |
| Make Model Name | Regional Jet 900 (CRJ900) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
Aircraft X checked on descending to FL240 from the high sector. I cleared him to descend via the TRYBE1 arrival which has them crossing their next waypoint; upprr; at or above FL240 (keeping them above the adjacent low sector which owns up to FL230). The workload was low and I watched their descent rate. I remember thinking to myself as they approached leveling at FL240 that the last hit had too high of a descent rate for them to stop at FL240. So still several miles from upprr; they descended through FL240. At FL238 I inquired what they were doing and they said descending via. I stopped them at FL230 and pvd'd [plan view display] a datablock up on the airspace that was just violated to my east; clarion sector. After calling and explaining; I went back to aircraft X and explained that they were to cross upprr at or above FL240. They apologized. I cleared them to cross upprr at FL230 then descend via. There were no other issues. I have seen several aircraft do this since metroplex rolled out. Pilots just aren't paying attention. They are anticipating; displaying expectation bias and not listening/understanding the clearance. So far I haven't seen a loss of separation or near midair collision; but it's only a matter of time. The issues I've seen are at the regional airline level.
Original NASA ASRS Text
Title: Cleveland Center Controller reported an airspace deviation associated with a crossing restriction that the pilot busted.
Narrative: Aircraft X checked on descending to FL240 from the high sector. I cleared him to descend via the TRYBE1 Arrival which has them crossing their next waypoint; UPPRR; at or above FL240 (keeping them above the adjacent low sector which owns up to FL230). The workload was low and I watched their descent rate. I remember thinking to myself as they approached leveling at FL240 that the last hit had too high of a descent rate for them to stop at FL240. So still several miles from UPPRR; they descended through FL240. At FL238 I inquired what they were doing and they said descending via. I stopped them at FL230 and PVD'd [Plan View Display] a datablock up on the airspace that was just violated to my east; Clarion Sector. After calling and explaining; I went back to Aircraft X and explained that they were to cross UPPRR at or above FL240. They apologized. I cleared them to cross UPPRR at FL230 then descend via. There were no other issues. I have seen several aircraft do this since Metroplex rolled out. Pilots just aren't paying attention. They are anticipating; displaying expectation bias and not listening/understanding the clearance. So far I haven't seen a loss of separation or NMAC; but it's only a matter of time. The issues I've seen are at the regional airline level.
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.