Narrative:

I was just sitting down at local assist. [The] local controller (local control) was moderately busy. Aircraft X was on a visual approach to runway 15. Aircraft Y departed from whp runway 12 on a southeast heading; so she was in conflict with aircraft X the moment her wheels lifted from the ground at whp. As I was sitting down; local control was trying to coordinate with whp to turn aircraft Y south to get her out of the way of aircraft X. Whp advised local control that she was not responding to him on frequency. We reached out for her and she wasn't on our frequency. I called back to whp to tell them to get aircraft Y out of the way; but whp did not have her on frequency and she continued climbing toward aircraft X (now on about a 3-mile final to runway 15). Local control and I discussed telling aircraft X to pull up and go around; but there was additional traffic over the numbers of runway 15 going northwest to whp that we were keeping high (2;200) so that the arriving aircraft X could land. Additionally; aircraft Y was showing 100 ft. Above aircraft X on the radar. Local control issued a traffic alert to aircraft X; and aircraft X reported the cessna in sight. The targets merged at either the same altitude or 100 feet apart. It was close. Aircraft Y continued to fly through our airspace without talking to us and finally checked on about 4 miles later. Whp airspace is right next to bur [airspace]; so more often than not VFR planes departing southeast off whp are a few miles into our airspace before they check in. This situation is not new and I've had problems with it before; but this is by far the closest call I've had with it. This will likely be treated as an near midair collision. Our culture at bur over the years has evolved into being lackadaisical about allowing whp departures to violate our airspace to the north since it is something that is so astoundingly common. Since whp departures only have something like 2 miles from the runway to the edge of bur airspace; we've traditionally been lax about planes checking on when they're already a few miles into our airspace. This is something that's driven me crazy for a long time and I've complained to management about numerous times.

Google
 

Original NASA ASRS Text

Title: Burbank Local Controller reported C172 departed WHP not talking to ATC and had a NMAC with a CRJ9 arrival.

Narrative: I was just sitting down at Local Assist. [The] Local Controller (LC) was moderately busy. Aircraft X was on a Visual Approach to RWY 15. Aircraft Y departed from WHP RWY 12 on a southeast heading; so she was in conflict with Aircraft X the moment her wheels lifted from the ground at WHP. As I was sitting down; LC was trying to coordinate with WHP to turn Aircraft Y south to get her out of the way of Aircraft X. WHP advised LC that she was not responding to him on frequency. We reached out for her and she wasn't on our frequency. I called back to WHP to tell them to get Aircraft Y out of the way; but WHP did not have her on frequency and she continued climbing toward Aircraft X (now on about a 3-mile final to RWY 15). LC and I discussed telling Aircraft X to pull up and go around; but there was additional traffic over the numbers of RWY 15 going northwest to WHP that we were keeping high (2;200) so that the arriving Aircraft X could land. Additionally; Aircraft Y was showing 100 ft. above Aircraft X on the radar. LC issued a traffic alert to Aircraft X; and Aircraft X reported the Cessna in sight. The targets merged at either the same altitude or 100 feet apart. It was close. Aircraft Y continued to fly through our airspace without talking to us and finally checked on about 4 miles later. WHP airspace is right next to BUR [airspace]; so more often than not VFR planes departing southeast off WHP are a few miles into our airspace before they check in. This situation is not new and I've had problems with it before; but this is by far the closest call I've had with it. This will likely be treated as an NMAC. Our culture at BUR over the years has evolved into being lackadaisical about allowing WHP departures to violate our airspace to the north since it is something that is so astoundingly common. Since WHP departures only have something like 2 miles from the runway to the edge of BUR airspace; we've traditionally been lax about planes checking on when they're already a few miles into our airspace. This is something that's driven me crazy for a long time and I've complained to management about numerous times.

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.