 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZKC controller reported that he issued a crossing restriction but it was not what the receiving controllers were expecting. Separation was not lost due to turning of the aircraft to avoid each other. Reporter wanted to change the fix where the restriction was to a new one to avoid this error in the future.
| Attributes | |
| ACN | 1297612 |
| Time | |
| Date | 201509 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZKC.ARTCC |
| State Reference | KS |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR KOLTS1 |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Medium Large Transport |
| Operating Under FAR Part | Part 129 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.75 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X ZZZ.spi.kolts.KOLTS1.ind entered my sector at FL350. I issued clearance to descend to FL330 and subsequently to cross kolts at FL240 assuming the RNAV route with kolts was constructed to comply with our ZID letter of agreement. Approximately 20 miles from the ZID/ZKC boundary I initiated a radar handoff to ZID I75 sector for aircraft X; and transferred radio communications to ZID I35 sector (per left.O.a. Instructions; 'flash through' I75 sector) after acceptance of the radar handoff. Later I noticed a conflict alert with aircraft Y at FL250 in ZID I75 sector that seemed odd to me (as of I75 may not be aware of the impending conflict). I called I35 and I75 sector(s) to make sure they indeed were aware of the crossing restriction issued to aircraft X at kolts; which apparently was not what they expected. Both aircraft were turned; I don't believe separation was lost. After reviewing our left.O.a. Agreement with ZID I discovered the 'cross the boundary at or below FL240' wording which was an obvious conflict to my expectation that the previously issued routing (spi.kolts.KOLTS1.ind) included a crossing fix 'kolts' as an acceptable crossing restriction for ZID. Kolts is approximately 2 miles on the wrong side of the boundary line. I will no longer use 'kolts' as a crossing fix for ind arrivals; and must issue new clearances to each ind arrival that is given the erroneous routing.I will no longer use kolts as a crossing fix for ind arrivals; and must issue revised clearances to each ind arrival that is given the erroneous routing or short cut. Perhaps we could move kolts 2 miles west and rename it craig; and further revise the automated preferential routing (and associated ZKC facility SOP's / mci SOP's/RNAV STAR) to indicate spi.craig.CRAIG1.ind. This new routing goes a long way to remind me of the mistake and never to make it again.
Original NASA ASRS Text
Title: ZKC Controller reported that he issued a crossing restriction but it was not what the receiving controllers were expecting. Separation was not lost due to turning of the aircraft to avoid each other. Reporter wanted to change the fix where the restriction was to a new one to avoid this error in the future.
Narrative: Aircraft X ZZZ.SPI.KOLTS.KOLTS1.IND entered my sector at FL350. I issued clearance to descend to FL330 and subsequently to cross KOLTS at FL240 assuming the RNAV route with KOLTS was constructed to comply with our ZID letter of agreement. Approximately 20 miles from the ZID/ZKC boundary I initiated a radar handoff to ZID I75 sector for Aircraft X; and transferred radio communications to ZID I35 sector (per L.O.A. instructions; 'flash through' I75 sector) after acceptance of the radar handoff. Later I noticed a conflict alert with Aircraft Y at FL250 in ZID I75 sector that seemed odd to me (as of I75 may not be aware of the impending conflict). I called I35 and I75 sector(s) to make sure they indeed were aware of the crossing restriction issued to Aircraft X at KOLTS; which apparently was not what they expected. Both aircraft were turned; I don't believe separation was lost. After reviewing our L.O.A. agreement with ZID I discovered the 'cross the boundary at or below FL240' wording which was an obvious conflict to my expectation that the previously issued routing (SPI.KOLTS.KOLTS1.IND) included a crossing fix 'KOLTS' as an acceptable crossing restriction for ZID. KOLTS is approximately 2 miles on the wrong side of the boundary line. I will no longer use 'KOLTS' as a crossing fix for IND arrivals; and must issue new clearances to each IND arrival that is given the erroneous routing.I will no longer use KOLTS as a crossing fix for IND arrivals; and must issue revised clearances to each IND arrival that is given the erroneous routing or short cut. Perhaps we could move KOLTS 2 miles west and rename it CRAIG; and further revise the automated preferential routing (and associated ZKC facility SOP's / MCI SOP's/RNAV STAR) to indicate SPI.CRAIG.CRAIG1.IND. This new routing goes a long way to remind me of the mistake and never to make it again.
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.