ZLA controller describes situation where yuma approach controller violates his airspace with three d...

Narrative:

I was working a few san arrivals westbound over ipl. The ekane MOA was active. I noticed a limited [data block] at FL220 about 5 miles outside of ekane in my airspace. At that time yuma range initiated a handoff and called me. I accepted radar. Then a few seconds later another limited [data block] at FL220 was 5 miles in my airspace. They again initiated a flash and called. I told them I would not take a stack and they needed to give me 10 miles in trail of the first one. Then a few minutes later I yuma range called and said hand off unable flash. They gave me the code and I noticed it was another limited [data block] 5 miles into my airspace; this time on the west side of ekane. I asked 'is he VFR?' they responded 'no.' I told them unable and I had to call them back because I was unable to start a track on the code and find the flight plan. They said they would keep him in ekane although he was already in my airspace. However; the airplane checked in with me anyway. I asked the pilot if he was VFR and he stated; 'no;' he received the clearance from yuma. At that time the supervisor came over and helped me get a track started while I worked the other traffic. After that I asked him to call them to see why they allowed 3 IFR aircraft in my airspace without hand offs and the one I said no to.train them that you can't enter someone else's airspace without a hand off and what unable means.

Original NASA ASRS Text

Title: ZLA Controller describes situation where Yuma Approach Controller violates his airspace with three different aircraft. This is considered an airspace deviation and leads to an increased workload for the receiving Controller.

Narrative: I was working a few SAN arrivals westbound over IPL. The EKANE MOA was active. I noticed a limited [data block] at FL220 about 5 miles outside of EKANE in my airspace. At that time Yuma Range initiated a handoff and called me. I accepted radar. Then a few seconds later another limited [data block] at FL220 was 5 miles in my airspace. They again initiated a flash and called. I told them I would not take a stack and they needed to give me 10 miles in trail of the first one. Then a few minutes later I Yuma Range called and said hand off unable flash. They gave me the code and I noticed it was another limited [data block] 5 miles into my airspace; this time on the west side of EKANE. I asked 'Is he VFR?' they responded 'No.' I told them unable and I had to call them back because I was unable to start a track on the code and find the flight plan. They said they would keep him in EKANE although he was already in my airspace. However; the airplane checked in with me anyway. I asked the pilot if he was VFR and he stated; 'No;' he received the clearance from YUMA. At that time the Supervisor came over and helped me get a track started while I worked the other traffic. After that I asked him to call them to see why they allowed 3 IFR aircraft in my airspace without hand offs and the one I said no to.Train them that you can't enter someone else's airspace without a hand off and what unable means.

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.

Attributes
ACN	1193812
Time
Date	201408
Local Time Of Day	0001-0600
Place
Locale Reference	ZLA.ARTCC
State Reference	CA
Environment
Light	Night
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Fighter
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 9
Events
Anomaly	Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

ZLA controller describes situation where yuma approach controller violates his airspace with three different aircraft. This is considered an airspace deviation and leads to an increased workload for the receiving controller.