37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 873705 |
Time | |
Date | 201002 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZKC.ARTCC |
State Reference | KS |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
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:
I was working colie sector; providing assistance to an aircraft (negative rvsm) landing st louis. I was attempting get this aircraft into an arrival gate and down from FL430 to FL240 through traffic; when I noticed a limited data block (air carrier X) tracking some two minutes into my sector at FL340. I observed the sector next to mine; that owns FL240 to FL320; working a track control target at FL340. I told him that the aircraft was at FL340; my altitudes; and told him to ship the aircraft and that he was radar contact. I stole track control of the target. Recommendation; sector 92 and 32 have become a coordination challenge because of the fact that sector 32 is rarely opened. Traffic demand should allow the sector to open more often but because of staffing challenges sector 32 is rarely split from 92. The controller; which the aircraft came from; had been in the sector a very short period. During the relief change period big turn over of workforce causes briefings to take place every several minutes. Better staffing and management by the front line manager could have prevented the revolving door that played a part in the hand-off to the wrong sector.
Original NASA ASRS Text
Title: ZKC Controller described an airspace incursion event; listing multiple position changes during the subject shift relief time period as a causal factor.
Narrative: I was working Colie sector; providing assistance to an aircraft (negative RVSM) landing St Louis. I was attempting get this aircraft into an arrival gate and down from FL430 to FL240 through traffic; when I noticed a limited data block (Air Carrier X) tracking some two minutes into my sector at FL340. I observed the sector next to mine; that owns FL240 to FL320; working a track control target at FL340. I told him that the aircraft was at FL340; my altitudes; and told him to ship the aircraft and that he was RADAR contact. I stole track control of the target. Recommendation; Sector 92 and 32 have become a coordination challenge because of the fact that Sector 32 is rarely opened. Traffic demand should allow the sector to open more often but because of staffing challenges Sector 32 is rarely split from 92. The Controller; which the aircraft came from; had been in the sector a very short period. During the relief change period big turn over of workforce causes briefings to take place every several minutes. Better staffing and management by the Front Line Manager could have prevented the revolving door that played a part in the hand-off to the wrong sector.
Data retrieved from NASA's ASRS site as of April 2012 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.