A D21 controller described an airspace incursion after a developmental failed to provide the necessa...

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 'south' controller or only to 'west'; the departure controller. When I asked; the developmental said he/she only pointed out to 'west'; and that he/she had 'prearranged coordination there'. I immediately told her to effect a point out to 'south'. 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 west.' 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.

Original NASA ASRS Text

Title: 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.

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.

Attributes
ACN	923820
Time
Date	201012
Local Time Of Day	0001-0600
Place
Locale Reference	PTK.Airport
State Reference	MI
Aircraft 1
Make Model Name	Gulfstream IV / G350 / G450
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Events
Anomaly	ATC Issue All Types

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.