Dab TRACON controller reported doing an automated point out to another sector. The other sector took...

Attributes
ACN	1380993
Time
Date	201608
Local Time Of Day	0601-1200
Place
Locale Reference	DAB.TRACON
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Climb
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Climb
Flight Plan	VFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6
Events
Anomaly	Airspace Violation All Types Deviation - Procedural Published Material / Policy

Narrative:

I had two aircraft depart dab requesting 045 but my airspace only extends to 035. These events happened separately and approximately five minutes apart. I initiated an automated point out with [the sector]. When I looked back at each aircraft neither were flashing po (point out) any longer so I assumed the point out had been accepted. I climbed both to 045 and terminated radar service with them at their request. [They] later said he had taken the handoff for both aircraft (**; slew; enter) instead of accepting the point out.when automated point outs are taken as handoffs by the '** slew enter' function; stars doesn't make it obvious that a handoff was taken other than a normal flashing (which you have to see before it disappears) and the position symbol change. In this case; I was north and [they were] M which look very similar. I suggest changing stars so that accepted point outs flash po until acknowledged and handoffs flash ho until acknowledged in the same way declined point outs flash un until acknowledged.

Original NASA ASRS Text

Title: DAB TRACON Controller reported doing an automated point out to another sector. The other sector took radar on the aircraft and the DAB Controller did not recognize the handoff and assumed the point out was good.

Narrative: I had two aircraft depart DAB requesting 045 but my airspace only extends to 035. These events happened separately and approximately five minutes apart. I initiated an automated point out with [the sector]. When I looked back at each aircraft neither were flashing PO (Point Out) any longer so I assumed the point out had been accepted. I climbed both to 045 and terminated radar service with them at their request. [They] later said he had taken the handoff for both aircraft (**; SLEW; ENTER) instead of accepting the point out.When automated point outs are taken as handoffs by the '** SLEW ENTER' function; STARS doesn't make it obvious that a handoff was taken other than a normal flashing (which you have to see before it disappears) and the position symbol change. In this case; I was N and [they were] M which look very similar. I suggest changing STARS so that accepted point outs flash PO until acknowledged and handoffs flash HO until acknowledged in the same way declined point outs flash UN until acknowledged.

Data retrieved from NASA's ASRS site 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.

Dab TRACON controller reported doing an automated point out to another sector. The other sector took radar on the aircraft and the dab controller did not recognize the handoff and assumed the point out was good.