Narrative:

An aircraft entered the cno airspace from the west at 1;800 ft MSL. He continued towards the airport for about 2 miles; then turned southbound and appeared to land at ajo airport. The aircraft conflicted with aircraft in the pattern for runway 26L. The closest proximity was less than 1/2 mile laterally at the same altitude. At the time; training was in progress and traffic was busy. The ojti on local control issued traffic advisories to aircraft that were on frequency and ensured separation; but it was definitely an unnecessary distraction and disturbed the smooth traffic flow. Cno airspace is violated from aircraft either inbound or outbound from ajo on a daily basis; usually more than once a day. It has been a problem for years. Usually; the violations are not reported because communication with the aircraft is not established; and filing the paperwork for a pilot deviation on an unknown pilot never seems to produce a result. Since the new qa/qc (quality assurance/quality control) procedures have been established; 21 mor's have been filed for airspace violations off of ajo. Sometimes the aircraft do not conflict with anyone; sometimes local control is left scrambling to separate his/her traffic from an airplane they are not in communication with. Ajo is an uncontrolled airport. It is only a matter of time before we have a safety related incident with one of these aircraft. Some sort of training must be accomplished. Our manager has reached out to the airport administration at ajo; who has agreed to hang signs around the airport at ajo; but I do not believe this will solve the problem. I would like to see some sort of mailer sent to everyone on the ajo tenant list. At least the combination of the two would help mitigate the problem; though I assume the pilots who fly out of ajo everyday are aware of our airspace. I am not sure how to reach the itinerant pilots inbound and outbound from ajo.

Related reports:

Google
 

Original NASA ASRS Text

Title: CNO Controller voiced concern regarding the continued CNO airspace violations by aircraft operating to/from AJO airport.

Narrative: An aircraft entered the CNO airspace from the west at 1;800 FT MSL. He continued towards the airport for about 2 miles; then turned southbound and appeared to land at AJO Airport. The aircraft conflicted with aircraft in the pattern for Runway 26L. The closest proximity was less than 1/2 mile laterally at the same altitude. At the time; training was in progress and traffic was busy. The OJTI on LC issued traffic advisories to aircraft that were on frequency and ensured separation; but it was definitely an unnecessary distraction and disturbed the smooth traffic flow. CNO airspace is violated from aircraft either inbound or outbound from AJO on a daily basis; usually more than once a day. It has been a problem for years. Usually; the violations are not reported because communication with the aircraft is not established; and filing the paperwork for a pilot deviation on an unknown pilot never seems to produce a result. Since the new QA/QC (Quality Assurance/Quality Control) procedures have been established; 21 MOR's have been filed for airspace violations off of AJO. Sometimes the aircraft do not conflict with anyone; sometimes Local Control is left scrambling to separate his/her traffic from an airplane they are not in communication with. AJO is an uncontrolled airport. It is only a matter of time before we have a safety related incident with one of these aircraft. Some sort of training must be accomplished. Our Manager has reached out to the airport administration at AJO; who has agreed to hang signs around the airport at AJO; but I do not believe this will solve the problem. I would like to see some sort of mailer sent to everyone on the AJO tenant list. At least the combination of the two would help mitigate the problem; though I assume the pilots who fly out of AJO everyday are aware of our airspace. I am not sure how to reach the itinerant pilots inbound and outbound from AJO.

Data retrieved from NASA's ASRS site as of July 2013 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.