 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
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.
| Attributes | |
| ACN | 928876 |
| Time | |
| Date | 201101 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SNA.Tower |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Flight Plan | VFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Coordinator |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
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.
Original NASA ASRS Text
Title: 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.
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.