Sct controller described a conflict between a lgb IFR departure and unknown VFR traffic transitionin...

Narrative:

I was the radar controller on position. I received an automated notification of an A320 departing lgb climbing to 3;000. There was an unidentified target maneuvering towards the departure corridor at 3;000. The A320 departed and I radar identified the aircraft; then immediately gave traffic and told to expedite climb through 3;000 to 4;000. The A320 responded that he was searching and expediting. I again issued traffic prior to the A320 reaching 3;000. The A320 then responded that they had the aircraft in sight. The A320's departure procedure (SCENIC1) required the aircraft to turn left heading 180 immediately after take off for airspace configuration. This vector turned the aircraft directly into the path of the unidentified target. The A320 then asked to maneuver to miss the aircraft at which I responded 'approved'. After the incident; the A320 was vectored back on course. Recommendation; lgb needs to become a class C surface area. Unidentified targets maneuvering around the departure and arrival corridor are unsafe to IFR operations in and out of lgb. Controllers become powerless to control aircraft at times when unidentified targets are maneuvering and changing altitudes frequently; especially in the initial stage of departure and final stage of their approach.

Original NASA ASRS Text

Title: SCT Controller described a conflict between a LGB IFR departure and unknown VFR traffic transitioning near the departure runway; the reporter suggesting LGB be authorized Class C airspace.

Narrative: I was the RADAR Controller on position. I received an automated notification of an A320 departing LGB climbing to 3;000. There was an unidentified target maneuvering towards the departure corridor at 3;000. The A320 departed and I RADAR identified the aircraft; then immediately gave traffic and told to expedite climb through 3;000 to 4;000. The A320 responded that he was searching and expediting. I again issued traffic prior to the A320 reaching 3;000. The A320 then responded that they had the aircraft in sight. The A320's departure procedure (SCENIC1) required the aircraft to turn left heading 180 immediately after take off for airspace configuration. This vector turned the aircraft directly into the path of the unidentified target. The A320 then asked to maneuver to miss the aircraft at which I responded 'approved'. After the incident; the A320 was vectored back on course. Recommendation; LGB needs to become a Class C surface area. Unidentified targets maneuvering around the departure and arrival corridor are unsafe to IFR operations in and out of LGB. Controllers become powerless to control aircraft at times when unidentified targets are maneuvering and changing altitudes frequently; especially in the initial stage of departure and final stage of their approach.

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	977769
Time
Date	201111
Local Time Of Day	1201-1800
Place
Locale Reference	SCT.TRACON
State Reference	CA
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Conflict Airborne Conflict

Sct controller described a conflict between a lgb IFR departure and unknown VFR traffic transitioning near the departure runway; the reporter suggesting lgb be authorized class C airspace.