Phl TRACON controller reported that a controller failed to make a radar point out to the reporter's ...

Attributes
ACN	1329304
Time
Date	201602
Local Time Of Day	1201-1800
Place
Locale Reference	PHL.TRACON
State Reference	PA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 5
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

I was just assuming the sector after receiving a briefing from the controller I was relieving. Aircraft X was westbound level at 5000 feet IFR. The pilot of aircraft X said 'we've finally got that dash in sight'. I looked at the scope; thinking that he had gotten a DH8A in sight that was still at his 2 o'clock and about 9 miles but was caught off guard when I realized that he probably wasn't talking about that DH8A because it would have been difficult for him to see him at that point. I asked him to repeat and he did. I then noticed a limited data block descending through the altitude of aircraft X southeast bound. I realized that the final controller had descended aircraft Y into my airspace without a point out and had not seen aircraft X. I believe separation was lost between these two IFR aircraft.by the time I noticed aircraft Y in my airspace he was already no factor for aircraft X. He was descending below him and turning southbound away from aircraft X. I did not need to issue evasive action. This was caused by the final controller allowing aircraft Y to enter my airspace without approval and not recognizing the conflict with aircraft X. The final controller should not enter another controller's airspace without coordination.

Original NASA ASRS Text

Title: PHL TRACON Controller reported that a Controller failed to make a radar point out to the reporter's adjacent sector.

Narrative: I was just assuming the sector after receiving a briefing from the controller I was relieving. Aircraft X was westbound level at 5000 feet IFR. The pilot of Aircraft X said 'We've finally got that Dash in sight'. I looked at the scope; thinking that he had gotten a DH8A in sight that was still at his 2 o'clock and about 9 miles but was caught off guard when I realized that he probably wasn't talking about that DH8A because it would have been difficult for him to see him at that point. I asked him to repeat and he did. I then noticed a limited data block descending through the altitude of Aircraft X southeast bound. I realized that the Final controller had descended Aircraft Y into my airspace without a point out and had not seen Aircraft X. I believe separation was lost between these two IFR aircraft.By the time I noticed Aircraft Y in my airspace he was already no factor for Aircraft X. He was descending below him and turning southbound away from Aircraft X. I did not need to issue evasive action. This was caused by the Final Controller allowing Aircraft Y to enter my airspace without approval and not recognizing the conflict with Aircraft X. The Final Controller should not enter another controller's airspace without coordination.

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.

Phl TRACON controller reported that a controller failed to make a radar point out to the reporter's adjacent sector.