 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZBW center controller reported an airspace violation that may have been either human or equipment failure.
| Attributes | |
| ACN | 1630876 |
| Time | |
| Date | 201903 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZBW.ARTCC |
| State Reference | NH |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| 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) 9.5 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Had just relieved another controller. Aircraft X was descending via JFUND2 STAR and (I think) flashing to approach control. I signed in with my settings and went on to help an aircraft at a different airport up north with a practice approach and subsequent missed into another. This may have distracted me enough so that I didn't become aware that approach hadn't taken the hand off on aircraft X. However; when I looked back down; aircraft X was around 3NM into approach airspace and I still had track control. I could've sworn approach already had the hand off but when I looked back it wasn't even flashing to them anymore.I accept I may be in error. Fatigue was definitely a factor and it was the end of my week. That being said; when I called my supervisor over; I noted to him that the auto-hand off function was still active on the data block. At a minimum; this means that even if I'd forgotten aircraft X; the function should have activated and worked as designed to initiate a hand off to approach when I hadn't done it myself in a timely manner.I'm uncertain; but believe that when I signed in with my settings the hand off that the previous controller had already initiated for aircraft X ceased. I am certain that the auto hand off function was not suppressed when I noticed aircraft X was 3NM into approach airspace. Look into the auto-hand off function behavior.
Original NASA ASRS Text
Title: ZBW Center Controller reported an airspace violation that may have been either human or equipment failure.
Narrative: Had just relieved another controller. Aircraft X was descending via JFUND2 STAR and (I think) flashing to Approach Control. I signed in with my settings and went on to help an aircraft at a different airport up north with a practice approach and subsequent missed into another. This may have distracted me enough so that I didn't become aware that approach hadn't taken the hand off on Aircraft X. However; when I looked back down; Aircraft X was around 3NM into Approach airspace and I still had track control. I could've sworn Approach already had the hand off but when I looked back it wasn't even flashing to them anymore.I accept I may be in error. Fatigue was definitely a factor and it was the end of my week. That being said; when I called my Supervisor over; I noted to him that the auto-hand off function was still active on the data block. At a minimum; this means that even if I'd forgotten Aircraft X; the function should have activated and worked as designed to initiate a hand off to approach when I hadn't done it myself in a timely manner.I'm uncertain; but believe that when I signed in with my settings the hand off that the previous controller had already initiated for Aircraft X ceased. I am certain that the auto hand off function was not suppressed when I noticed Aircraft X was 3NM into approach airspace. Look into the auto-hand off function behavior.
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.