 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLC controller described an airspace incursion event immediately after assuming the position. Reporter noted that the previous controller had unintentionally dropped a data tag causing the incident.
| Attributes | |
| ACN | 1023897 |
| Time | |
| Date | 201207 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| 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 received a position relief briefing from the previous controller. He had accidentally dropped the track of aircraft X instead of the intended arrival; but didn't realize it. At the time I signed in to take the sector; the limited data block of aircraft X was at the boundary leaving my airspace and I didn't notice it. I remember aircraft X calling me later to ask for a higher altitude. I did not remember working him; so I pulled up his flight plan and ran a route line to see where he was. The route line came up in the middle of the adjacent sector's airspace; and I saw the call sign in the limited data block next to the route line; so I sent him to that sector's frequency (sector 16). Since dropping a data block is so easy to do and can cause such an unsafe condition; it might help to make dropping data blocks have the same procedure as removing a flight plan; where a /ok entry is required. Perhaps many people just /ok without really double-checking; but it might save some people from making a mistake.
Original NASA ASRS Text
Title: ZLC Controller described an airspace incursion event immediately after assuming the position. Reporter noted that the previous Controller had unintentionally dropped a data tag causing the incident.
Narrative: I received a position relief briefing from the previous Controller. He had accidentally dropped the track of Aircraft X instead of the intended arrival; but didn't realize it. At the time I signed in to take the sector; the limited Data Block of Aircraft X was at the boundary leaving my airspace and I didn't notice it. I remember Aircraft X calling me later to ask for a higher altitude. I did not remember working him; so I pulled up his Flight Plan and ran a route line to see where he was. The route line came up in the middle of the adjacent sector's airspace; and I saw the call sign in the limited Data Block next to the route line; so I sent him to that sector's frequency (Sector 16). Since dropping a Data Block is so easy to do and can cause such an unsafe condition; it might help to make dropping Data Blocks have the same procedure as removing a flight plan; where a /OK entry is required. Perhaps many people just /OK without really double-checking; but it might save some people from making a mistake.
Data retrieved from NASA's ASRS site as of July 2013 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.