Narrative:

When I assumed sector R18; I noticed that the sector sia indicated 'show and go's with sector 47. A 'show and go' is an unapproved procedure where sector a forces a data block unto sectors B's mdm and then clears the aircraft to enter sector B's airspace without completing the required verbal coordination (i.e. Point out ). For the hour or so I was working this sector; there were 15-20 aircraft that entered my sector without proper point outs from sector 47. This is not the first time that I have seen this coordinated agreement being used. While efficient; a 'show and go' requires a waiver to the 7110.65; which our facility does not posses. There is a fair amount of risk involved because an errant computer entry can preclude a data block appearing on 'sector B's' mdm. The redundancy of the verbal follow up to the forcing of a data block on another sector's mdm is meant to close the loop and ensure controllers are watching and separating all traffic in their airspace. The resurgence of this 'procedure' seems to be related to the recent change to the kbos departure routes. Aircraft are routinely delivered to ZBW departure sectors in a manner where they will level at the top of A90's airspace well inside of a sector other than the departure sector who will work the aircraft. In retrospect; I should have called sector 47 and rescinded this 'agreement' instead of waiting until it was scheduled to time out. Recommendation; there should be strict guidance prohibiting this procedure. Alternately; a procedure could be developed that allows sectors to climb kbos departures in adjacent sector's airspace. It would need to be subjected srm process; documented in the SOP and taught to the affected controllers.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW Controller voiced concern regarding the use of 'Show and Go' procedures claiming same is not in compliance with FAA Orders.

Narrative: When I assumed Sector R18; I noticed that the sector SIA indicated 'Show and Go's with Sector 47. A 'Show and Go' is an unapproved procedure where Sector A forces a data block unto Sectors B's MDM and then clears the aircraft to enter Sector B's airspace without completing the required verbal coordination (I.E. point out ). For the hour or so I was working this sector; there were 15-20 aircraft that entered my sector without proper point outs from Sector 47. This is not the first time that I have seen this coordinated agreement being used. While efficient; a 'Show and Go' requires a waiver to the 7110.65; which our facility does not posses. There is a fair amount of risk involved because an errant computer entry can preclude a data block appearing on 'Sector B's' MDM. The redundancy of the verbal follow up to the forcing of a data block on another sector's MDM is meant to close the loop and ensure controllers are watching and separating all traffic in their airspace. The resurgence of this 'procedure' seems to be related to the recent change to the KBOS departure routes. Aircraft are routinely delivered to ZBW departure sectors in a manner where they will level at the top of A90's airspace well inside of a sector other than the departure sector who will work the aircraft. In retrospect; I should have called sector 47 and rescinded this 'agreement' instead of waiting until it was scheduled to time out. Recommendation; There should be strict guidance prohibiting this procedure. Alternately; a procedure could be developed that allows sectors to climb KBOS departures in adjacent sector's airspace. It would need to be subjected SRM process; documented in the SOP and taught to the affected controllers.

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.