A D21 Controller described an airspace incursion after a developmental failed to provide the necessary point outs to adjacent sector/s. The reporter noted the difficulty of monitoring a controller from another operational position.
Synopsis
A D21 Controller described an airspace incursion after a developmental failed to provide the necessary point outs to adjacent sector/s. The reporter noted the difficulty of monitoring a controller from another operational position.
Narrative
Aircraft X was a GLF4 off PTK. The developmental initially assigned 5000; which we own. There was conflicting traffic opposite direction descending to 4000. The developmental affected an automated point out to the West Jet controller; this enabled the developmental to run the aircraft out DUNKS. I observed an automated point out as I was using an adjacent scope. When the developmental climbed to 13000; I began to question if he/she pointed out to the 'S' controller or only to 'W'; the Departure Controller. When I asked; the developmental said he/she only pointed out to 'W'; and that he/she had 'prearranged coordination there'. I immediately told her to effect a point out to 'S'. They were a bit busy and slow to approve it. By the time they did; the aircraft was out of 5800. If utilizing an adjacent scope I would recommend the developmental provide a verbal confirmation of any automated point outs to the OJTI. As in; 'I'm pointing Aircraft X out to W.' This would avoid the confusion. Option B would be to force OJTI's to utilize the same scope as the developmental. This is a poor option. Stars preferential settings are always an issue when forced to 'share' a scope.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.