37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 881122 |
Time | |
Date | 201003 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZAN.ARTCC |
State Reference | AK |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
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 took over the sector and there was already a d-side trainee monitoring the sector; plugged in at the same position. The controller in charge notified me that the non-radar separation standard ZOA was using on a flex track affecting my sector had increased from 25 miles either side of center line to 50 miles. We began discussing the impact and how to determine where I needed to apply increased separation. The d-side trainee was asking a lot of questions about it as I was attempting to plot the flex track and protected airspace on the overhead map; and the controller in charge and I were discussing the difference between radar and non-radar traffic in my sector on airway B327. When I returned my attention to the radar display I saw that air carrier X had progressed to katch without a hand-off to vancouver center and air carrier Y was about to enter sector 69 without a hand-off as well. I immediately put air carrier Y into hand off mode and called over to the sector 69 controller who said 'radar contact' as air carrier Y crossed the sector boundary. I called vancouver on the shout line and gave them a hand off on air carrier X and another aircraft that was still in my sector. I apologized for the late hand-off and he said 'no problem.' I believe the primary cause of this error to be the combined distractions of the trainee and the controller in charge; and of course; my poor prioritizing of duties and inattention to my primary function; which is to watch the aircraft on the radar display and take action in a timely manner. Recommendation; when a controller in charge or flm has something like this to communicate; they should be more aware of the distraction they can cause. If the sector is one-armed; maybe the controller in charge/flm should do the plotting or whatever needs to be done instead of letting the controller do it. In any case; someone should be monitoring the traffic at all times; or at least scan to see what is coming up in the next couple of minutes and take care of things before addressing the distracting issue. If a trainee is monitoring a sector; they should take care to avoid distracting the controller; or assist in scanning the display for needed actions.
Original NASA ASRS Text
Title: ZAN Controller described probable multiple airspace incursion events resulting from several discussions taking place at the sector; all causing distractions.
Narrative: I took over the sector and there was already a D-Side trainee monitoring the sector; plugged in at the same position. The CIC notified me that the Non-RADAR separation standard ZOA was using on a flex track affecting my sector had increased from 25 miles either side of center line to 50 miles. We began discussing the impact and how to determine where I needed to apply increased separation. The D-Side trainee was asking a lot of questions about it as I was attempting to plot the flex track and protected airspace on the overhead map; and the CIC and I were discussing the difference between RADAR and Non-RADAR traffic in my sector on airway B327. When I returned my attention to the RADAR display I saw that Air Carrier X had progressed to KATCH without a hand-off to Vancouver Center and Air Carrier Y was about to enter Sector 69 without a hand-off as well. I immediately put Air Carrier Y into hand off mode and called over to the Sector 69 controller who said 'RADAR contact' as Air Carrier Y crossed the sector boundary. I called Vancouver on the shout line and gave them a hand off on Air Carrier X and another aircraft that was still in my sector. I apologized for the late hand-off and he said 'no problem.' I believe the primary cause of this error to be the combined distractions of the trainee and the CIC; and of course; my poor prioritizing of duties and inattention to my primary function; which is to watch the aircraft on the RADAR display and take action in a timely manner. Recommendation; when a CIC or FLM has something like this to communicate; they should be more aware of the distraction they can cause. If the sector is one-armed; maybe the CIC/FLM should do the plotting or whatever needs to be done instead of letting the Controller do it. In any case; someone should be monitoring the traffic at all times; or at least scan to see what is coming up in the next couple of minutes and take care of things before addressing the distracting issue. If a trainee is monitoring a sector; they should take care to avoid distracting the Controller; or assist in scanning the display for needed actions.
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.