 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A ZDV controller reported of a lack of coordination from the overlying sector. Aircraft descended with a hand off into his airspace. Other than data block information the controller reported the other sector should have coordinated something verbally. The reporter stated there was no clear direction in any documents as to what should happen.
| Attributes | |
| ACN | 1315112 |
| Time | |
| Date | 201512 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZDV.ARTCC |
| State Reference | CO |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| 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) 1 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was working the radar on sectors 6 and 26. I received a hand-off from high altitude sector and the assigned altitude was FL260; which was below the stratum of the high altitude sector and the top altitude of my airspace. The aircraft checked in with the altitude FL260 and was descending into my airspace. Prior to this there was no coordination done from the previous controller that the aircraft would be descending into my airspace other than what was in the data block. I did protect for the possibility that the aircraft was actually descending as well as if it was assigned FL270 as I would normally expect.there needs to be clear guidance as to when the assigned altitude in the data block can be accepted as coordination. If this scenario were to happen during a very busy ski country day I would have no time to reach out to stop that aircraft and there will be a real safety issue if this practice is allowed to continue. Most controllers wouldn't do this; but there are a few who are continuing to do this because there is no clear direction in any documents.
Original NASA ASRS Text
Title: A ZDV Controller reported of a lack of coordination from the overlying sector. Aircraft descended with a hand off into his airspace. Other than data block information the Controller reported the other sector should have coordinated something verbally. The reporter stated there was no clear direction in any documents as to what should happen.
Narrative: I was working the Radar on sectors 6 and 26. I received a hand-off from high altitude sector and the assigned altitude was FL260; which was below the stratum of the high altitude sector and the top altitude of my airspace. The aircraft checked in with the altitude FL260 and was descending into my airspace. Prior to this there was no coordination done from the previous controller that the aircraft would be descending into my airspace other than what was in the data block. I did protect for the possibility that the aircraft was actually descending as well as if it was assigned FL270 as I would normally expect.There needs to be clear guidance as to when the assigned altitude in the data block can be accepted as coordination. If this scenario were to happen during a very busy ski country day I would have no time to reach out to stop that aircraft and there will be a real safety issue if this practice is allowed to continue. Most controllers wouldn't do this; but there are a few who are continuing to do this because there is no clear direction in any documents.
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.