Narrative:

Facility has initiated a new requirement to have a visual indicator that each aircraft is either on/off frequency. We are to use one of four methods. One such method advised was to change one's radar settings to a default setting of /0 for the data block length. What was not made clear was that if you sign in with such a default setting and the controller you are relieving has his set to a /1 setting; aircraft that are in the /1 position changes to a /0. In our area we are used to seeing aircraft in a /0 position as being shipped to another frequency/facility. In this case I had an aircraft going to phx and he was level FL290 but not flashed to abq 43. When I relieved the controller I signed in and didn't notice that the aircraft was not handed off. The aircraft crossed the phx boundary without a hand off. I noticed it 2 or 3 miles into their airspace and flashed the data block and called the sector. They took the hand off prior to answering the line. I asked if the aircraft was on their frequency and was told negative. I advised that I would try him again. There were no other aircraft nearby. Recommendation; this quick fix for the no radio contact stuff was too hastily done. People are required to use 1 of 4 methods to meet these new rules. Other methods are not allowed due to a desire to be 'standardized'. If there are 4 choices; then it's not standardized. This quick fix also increases the workload of the controller significantly. Only one method given is available to both right and D sides to do; however if the previous controller is not using this method then data blocks are changed; thereby causing confusion and increasing the possibility of an aircraft not being handed off and violating another sector/facility's airspace. Require pilots to monitor guard.

Related reports:

Google
 

Original NASA ASRS Text

Title: An allegedly hastily activated procedure to note an aircraft's availability on a frequency is reported as causing confusion for controllers as well as airspace incursions.

Narrative: Facility has initiated a new requirement to have a visual indicator that each aircraft is either on/off frequency. We are to use one of four methods. One such method advised was to change one's RADAR settings to a default setting of /0 for the data block length. What was not made clear was that if you sign in with such a default setting and the controller you are relieving has his set to a /1 setting; aircraft that are in the /1 position changes to a /0. In our area we are used to seeing aircraft in a /0 position as being shipped to another frequency/facility. In this case I had an aircraft going to PHX and he was level FL290 but not flashed to ABQ 43. When I relieved the controller I signed in and didn't notice that the aircraft was NOT handed off. The aircraft crossed the PHX boundary without a hand off. I noticed it 2 or 3 miles into their airspace and flashed the data block and called the sector. They took the hand off prior to answering the line. I asked if the aircraft was on their frequency and was told negative. I advised that I would try him again. There were no other aircraft nearby. Recommendation; this quick fix for the no radio contact stuff was too hastily done. People are required to use 1 of 4 methods to meet these new rules. Other methods are not allowed due to a desire to be 'Standardized'. If there are 4 choices; then it's NOT standardized. This quick fix also increases the workload of the controller significantly. Only one method given is available to both R and D sides to do; however if the previous controller is NOT using this method then data blocks are changed; thereby causing confusion and increasing the possibility of an aircraft not being handed off and violating another sector/facility's airspace. Require pilots to monitor Guard.

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.