|  | 37000 Feet | Browse and search NASA's Aviation Safety Reporting System | 
| 
 | 
| Attributes | |
| ACN | 1188459 | 
| Time | |
| Date | 201407 | 
| Local Time Of Day | 1201-1800 | 
| Place | |
| Locale Reference | SNA.Tower | 
| State Reference | CA | 
| Environment | |
| Light | Daylight | 
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng | 
| Flight Phase | Final Approach | 
| Route In Use | Other Instrument Approach | 
| Flight Plan | IFR | 
| Aircraft 2 | |
| Make Model Name | Small Transport Low Wing 2 Turboprop Eng | 
| Operating Under FAR Part | Part 91 | 
| Flight Phase | Cruise | 
| Flight Plan | VFR | 
| Person 1 | |
| Function | Local | 
| Qualification | Air Traffic Control Fully Certified | 
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.9 | 
| Person 2 | |
| Function | Handoff / Assist Local | 
| Qualification | Air Traffic Control Fully Certified | 
| Experience | Air Traffic Control Time Certified In Pos 1 (mon) 1.5 | 
| Events | |
| Anomaly | Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy | 
Narrative:
I was working local 1 and aircraft X checked onto my frequency; I noticed that aircraft Y was 2-3 miles south west at 1;000 feet heading towards the final northeast bound. My assist had just accepted an automated point out less than a minute before aircraft X checked on my frequency. I then issued traffic to aircraft X and at the same time my assist was asking the sct sector controlling aircraft Y what he was doing. I then noticed that aircraft Y was still on course to cross the final at about 4 to 5 miles from the airport at 1;000 feet. Aircraft X was at 2;200 feet when I gave a traffic alert traffic call that I will admit I messed up a bit; however; I tried to correct my mistake as best as I could while keyed up. Aircraft X crossed over aircraft Y at 1;700 feet; while aircraft Y was at 1;000 feet.anytime an aircraft will be operating on a final at an altitude that may affect arriving aircraft; it should be verbally coordinated between controllers along with the positive control of the point out aircraft; ensuring that it does not affect any aircraft on the final.
Original NASA ASRS Text
Title: SNA Tower controllers report of a conflict on final due to a VFR aircraft coming in close proximity to IFR arrival into SNA.
Narrative: I was working Local 1 and Aircraft X checked onto my frequency; I noticed that Aircraft Y was 2-3 miles south west at 1;000 feet heading towards the final northeast bound. My Assist had just accepted an automated point out less than a minute before Aircraft X checked on my frequency. I then issued traffic to Aircraft X and at the same time my Assist was asking the SCT sector controlling Aircraft Y what he was doing. I then noticed that Aircraft Y was still on course to cross the final at about 4 to 5 miles from the airport at 1;000 feet. Aircraft X was at 2;200 feet when I gave a traffic alert traffic call that I will admit I messed up a bit; however; I tried to correct my mistake as best as I could while keyed up. Aircraft X crossed over Aircraft Y at 1;700 feet; while Aircraft Y was at 1;000 feet.Anytime an aircraft will be operating on a final at an altitude that may affect arriving aircraft; it should be verbally coordinated between controllers along with the positive control of the point out aircraft; ensuring that it does not affect any aircraft on the final.
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.