A potential conflict occurred between a VFR and IFR departure at SNA. The SCT controller turned the IFR aircraft unexpectedly toward the VFR aircraft without regard for LOA procedures.

Date: 2011-01 · Aircraft: B737 Undifferentiated or Other Model · Phase: initial_climb

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

A potential conflict occurred between a VFR and IFR departure at SNA. The SCT controller turned the IFR aircraft unexpectedly toward the VFR aircraft without regard for LOA procedures.

Narrative

Aircraft Y departed SNA on a VFR flight plan eastbound off Runway 01L. Aircraft Y was RADAR identified by the Tower and then switched to SOCAL approach. Aircraft X departed Runway 01L. While Aircraft X was departing; I notice that the Shore Sector at SOCAL had turned Aircraft Y Westbound one mile west of the airport at 2;200 feet. Targets merged one mile north of SNA. Aircraft X was indicating 1;500 feet and Aircraft Y was indicating 2;500 feet. It should be noted that Aircraft Y was turned while still in Tower airspace. No coordination was accomplished or requested to take control of Aircraft Y. It should further be noted that Aircraft Y destination was MHV which is east of SNA. There is no reasonable reason for Tower personnel to expect that Aircraft Y would make a 180 degree turn and fly through the departure corridor. At the time of the incident SNA was on Runway 01; which is an unusual configuration. I believe this event occurred due to inexperience and lack of training at SOCAL Approach. Personnel at SOCAL routinely indicate they are unfamiliar with requirements of the LOA; including supervisors. Better training is needed.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.