Date: 201605
Local time of day: 0001-0600
Location: JCF.TRACON, CA
Aircraft: Military Transport
Operator: Military
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E JCF
ATC / advisory: TRACON JCF
Second aircraft: Military Transport
Reporter organization: Government
Reporter function: Approach; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness; Distraction; Communication Breakdown; Confusion
Second reporter function: Approach; Trainee
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: MAFFS [Modular Airborne Fire Fighting System] aircraft had been entering IFR for their special mission regularly; canceling IFR and going VFR to their respective work areas. Aircraft X had called us up for an IFR pick-up clearance. Training was in progress at this time and we were in the process of getting a handoff (assist) at the same time. We entered in a flight plan manually and saw a tag that popped up. My trainee didn't issue the code; and I didn't catch that he didn't issue a code because of multiple things going on at the same time. We never noticed that the tag had popped on an aircraft performing VFR maneuvers neither talking to BUR area of SCT or ANT sectors.Watching the replay; that aircraft had come from BUR area and continued to use the old code. [The developmental] had thought he issued the code; called radar contact from the position the tag was at along with the clearance. The pilot read back the clearance and never question the contact position correlating with what [the developmental] had said. After a few minutes had passed; Aircraft X asked us if he should be squawking something different around the time we noticed the tag wasn't doing anything it was supposed to. Aircraft X was squawking 1200 still this whole time. By the time we had caught the issue and were trying to correct it; Aircraft X was already on the boundary to Valley sector of SCT. Coordination was accomplished and Aircraft X never had a separation issue with any other aircraft.For any special mission where the aircraft are going to work without talking to ATC in designated areas; it would be helpful if they all squawked VFR to reduce confusion and new codes being tagged up on the aircraft squawking codes that are no longer valid. I should have been a little more vigilant about what was going on with the clearance; even if there was a lot going on. Not sure what else aside from more vigilance all around because it was a build-up of a lot of little problems from both pilot and ATC side that lead to the airspace violation.


Second narrative: I was working the Antelope/Palmdale radar position. Multiple MAFFS [Modular Airborne Fire Fighting System] aircraft had been coming in and out of the airspace. Two MAFFS aircraft had recently entered IFR and cancelled to VFR. They were told 'IFR cancellation received; maintain VFR.' Then; almost immediately; both of those aircraft switched frequencies on their own. A MAFFS aircraft called later and asked for and IFR pickup. I gave him a new beacon code and issued the clearance. Shortly after Aircraft X called and said he would also like to pick up IFR and follow his company traffic.I input all the information and a new beacon code was established in the system. While dealing with other aircraft; including a traffic alert and vectoring to and clearing an approach; Aircraft X tagged up on his beacon code. I told Aircraft X he was radar contact and gave his position and a clearance to [destination airport]. The aircraft did not dispute the positioning and read back the clearance. Because the aircraft tagged up I thought that I must have already issued Aircraft X his beacon code; but had not. Shortly after I realized that Aircraft X was not turning as expected to a 250 heading to which he was assigned. I then told him to turn right to 270. The aircraft continued a gradual left turn and so I confirmed to the pilot that he was turning right to 270. The aircraft responded that he was turning to 270; but did not say it was a right turn. Then Aircraft X asked if he needed a different code and I said that the code he was on; [Beacon Code]; was correct. At this time myself; my trainer and handoff were trying to figure out if this was actually the correct aircraft when a limited tag squawked up on the code that I had just read back.We then realized that the aircraft that had previously tagged up was on an old code that had not been removed from the system. I believe this is because the MAFFS aircraft from before switched frequencies without being told to and remained on his old code. We quickly recognized where Aircraft X actually was and track repositioned the tag and started manual handoff coordination with SoCal. I then asked the other aircraft that was squawking [beacon code] what his call sign was and to squawk VFR. He said his call sign was Aircraft Y. Very bizarre situation including the fact that the actual Aircraft X never descended to 80.I would recommend that all aircraft that are routed in to our airspace be removed from the system unless they are landing immediately. All aircraft that cancel IFR and are told IFR cancellation received; maintain VFR should also remain on frequency until told to switch. If the aircraft had requested a cancellation of radar service he would have been told to squawk VFR.


Synopsis: JCF TRACON (Edwards Approach Control) Instructor and Developmental reported of issues with aircraft that are not squawking VFR (1200) when instructed to. Later in the shift when trying to identify other aircraft there is confusion because the aircraft tag up incorrectly.