Orf TRACON controller reported a conflict between an orf arrival and an ntu departure. Reporter stat...

Narrative:

I was working a CRJ2 inbound to orf from the south for a left downwind visual approach. I called ntu approach and gave them a point-out on the CRJ2 descending for orf. A couple of minutes later I hear ntu yelling over the landline for a point-out and I saw a target in a right turn out off of ntu runway 32 climbing. I called traffic to the CRJ2 and he reported the aircraft in sight; and I instructed him to maintain visual separation. The ntu airport is about 3.64 miles from our airspace boundary with ntu approach. We have conditional use airspace that goes active when ntu is on runway 32 but this doesn't seem to be the solution. When their fighters depart runway 32 I believe they are instructed to turn right off the deck; but many times they end up busting our airspace. The problem is compounded greatly when we have aircraft in that vicinity or when we have been given approval to ride the boundary with inbounds to orf. Recommendations that might be considered are airspace redesign or ntu calling orf for release when they are on runway 32.

Original NASA ASRS Text

Title: ORF TRACON Controller reported a conflict between an ORF arrival and an NTU departure. Reporter stated it is a recurring problem and existing procedures do not seem to work.

Narrative: I was working a CRJ2 inbound to ORF from the south for a left downwind visual approach. I called NTU approach and gave them a point-out on the CRJ2 descending for ORF. A couple of minutes later I hear NTU yelling over the landline for a point-out and I saw a target in a right turn out off of NTU Runway 32 climbing. I called traffic to the CRJ2 and he reported the aircraft in sight; and I instructed him to maintain visual separation. The NTU airport is about 3.64 miles from our airspace boundary with NTU approach. We have conditional use airspace that goes active when NTU is on Runway 32 but this doesn't seem to be the solution. When their fighters depart Runway 32 I believe they are instructed to turn right off the deck; but many times they end up busting our airspace. The problem is compounded greatly when we have aircraft in that vicinity or when we have been given approval to ride the boundary with inbounds to ORF. Recommendations that might be considered are airspace redesign or NTU calling ORF for release when they are on Runway 32.

Data retrieved from NASA's ASRS site as of April 2012 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	912760
Time
Date	201010
Local Time Of Day	1201-1800
Place
Locale Reference	ORF.TRACON
State Reference	VA
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict

Orf TRACON controller reported a conflict between an orf arrival and an ntu departure. Reporter stated it is a recurring problem and existing procedures do not seem to work.