Date: 201304
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Hercules (C-130)/L100/382
Operator: Military
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: B1 Lancer
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was working Approach/Departure and had been on position approximately 11 minutes; first day back from break. We work all the aircraft going into and out of the Air Force Base outside the Class C. Today we were on a south flow both airports; Runway 16 at [Air Force Base]. I had one H/B1/B on an approximate 2 mile final [Air Force Base Runway] 16 (talking to the Air Force Base Tower) coming back to me after his touch and go heading 180 climbing to 040 (standard climb out). [The Air Force Base] had a couple aircraft in their VFR pattern. When [Air Force Base] has their Class C and automatic releases; they are required by LOA to give a rolling call on all departures and 5 miles between departures; runway heading to 040. [The Air Force Base] called me on the shout line and called H/B1/B rolling; IFR first fix ZZZ. A C130 checked in with me; I scanned; and I had no C130 tagged anywhere (no rolling call was given). He said he was off [the Air Force Base] on local departure procedures. I looked in my proposal bay and saw two local IFR strips for the C130; one for an ILS at [the Air Force Base] and one for an established departure procedure. I then saw a splat approximately 2 miles off the departure end of [the Air Force Base] flashing a wrong beacon code; by this time the B1 was airborne and at the departure end; he was not talking to me. I immediately called [the Air Force Base] and told them to turn the B1 to a heading of 270 right now; they called back and said they did not have him. As I was talking to [the Air Force Base]; the B1 checked in on my frequency; I issued a turn to 270 and asked if he had the C130 in sight ahead of him; he said he did; requested to climb to 060 and he continued runway heading; the B1 was instructed to maintain visual separation from the C130. It appeared the B1 passed to the east of the C130 and I issued a climb to 060. I called [the Air Force Base] back and told them to never; ever do that again and told the CIC to advise our supervisor who is getting ready to go home of what just took place. [The Air Force Base] controllers to receive additional classroom training on our joint LOA with explanations of why things are done the way they are. Have a meeting between the two facilities management teams identifying on going issues [TRACON] is having with [the Air Force Base] controllers. I know we cannot dictate how they work but if all else fails; take away automatic releases permanently.




Synopsis: TRACON Controller described an unsafe event when a local military controller failed to adhere to LOA requirements and released an aircraft into a conflict environment.