Narrative:

I was on arrival radar and had [aircraft X] on a heading of 090 VFR at 3;000 feet. The aircraft was being vectored for a practice ILS approach to runway 24. I was taking him on the south side of the airport since we were advertising the visual approach to runway 31. When [aircraft X] was about 10 west of abe; I noticed [aircraft Y] was departing runway 31 on runway heading landing phl. I heard the departure controller issue the pilot 5;000 feet and a left turn direct ptw. This action put him in conflict with [aircraft X] and standard VFR separation could not be ensured. This action also violated our local procedures. Departure is not allowed to turn aircraft outside the departure corridor without coordination which he failed to do. Luckily; the required separation existed by the time the targets overlapped. I don't know if the other controller saw the potential conflict when he attempted the look and go operation. I did notify [aircraft X] of the traffic conflict and eventually he did see [aircraft Y]. I also expressed my concern to the departure controller that he had violated my airspace and in doing so; caused this event to occurhad the departure controller followed proper procedures this event would have never of occurred. His actions introduced unnecessary risk into the NAS. We must to a better job at producing controllers that have pride in what they do and follow procedures that exist for a reason. If we keep certifying lazy controllers this event or events similar to it are certainly going to occur again.

Related reports:

Google
 

Original NASA ASRS Text

Title: ABE Approach Controller reported of an airspace deviation caused by the Departure Controller that led to a loss of separation with an arrival.

Narrative: I was on arrival radar and had [Aircraft X] on a heading of 090 VFR at 3;000 feet. The aircraft was being vectored for a practice ILS approach to runway 24. I was taking him on the south side of the airport since we were advertising the visual approach to runway 31. When [Aircraft X] was about 10 west of ABE; I noticed [Aircraft Y] was departing runway 31 on runway heading landing PHL. I heard the departure controller issue the pilot 5;000 feet and a left turn direct PTW. This action put him in conflict with [Aircraft X] and standard VFR separation could not be ensured. This action also violated our local procedures. Departure is not allowed to turn aircraft outside the departure corridor without coordination which he failed to do. Luckily; the required separation existed by the time the targets overlapped. I don't know if the other controller saw the potential conflict when he attempted the look and go operation. I did notify [Aircraft X] of the traffic conflict and eventually he did see [Aircraft Y]. I also expressed my concern to the departure controller that he had violated my airspace and in doing so; caused this event to occurHad the departure controller followed proper procedures this event would have never of occurred. His actions introduced unnecessary risk into the NAS. We must to a better job at producing controllers that have pride in what they do and follow procedures that exist for a reason. If we keep certifying lazy controllers this event or events similar to it are certainly going to occur again.

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.