Narrative:

I was working combined arrival/departure sectors for north whiting. Traffic was busy and the session was made more difficult by numerous student pilots not answering radio calls and/or answering for the wrong aircraft. Nse called for a release on a VFR F18. I told them to release him on a standard departure heading (340 degrees) and assign him 3000 ft. They acknowledged this and hung up. In the meantime; I was working on IFR T34 on departure. I assigned him 1700 ft (MVA) and turned him to heading 270 degrees; and then heading 230 degrees. He was approximately 4 mi northwest of nse heading 230 degrees. I observed F18 depart nse. He appeared to be heading nwbound and his altitude indicated 1000 ft. I began calling traffic to the T34. I did not climb the T34 because I was expecting the F18 to climb. He didn't. The targets merged-- the F18 flew under the T34 at approximately 1000 ft. I finally got the F18 on frequency and asked him what heading nse assigned him. He said no heading (and apparently no altitude) were assigned by nse. Earlier in the same session; I had to stop departures at nse because of traffic saturation. Approximately 2 mins after I stopped departures; nse launched a T34; without a release. I called the P31 supervisor on duty down to the sector and reported both of these events. I specifically stated that nse had committed an operational deviation when they launched the T34. No action was taken; to my knowledge; other than the supervisor and area manager making a couple of phone calls to nse. This is typical of the FAA's attitude regarding the navy. Little if any action is ever taken even when nse violates the LOA's; 7110.65; etc.

Related reports:

Google
 

Original NASA ASRS Text

Title: P31 CTLR DESCRIBED CONFLICT BTWN IFR T34 DEP AND A VFR F18 DEP WHEN NSE LCL CTLR FAILED TO ISSUED RESTRS AS GIVEN BY THE RPTR.

Narrative: I WAS WORKING COMBINED ARR/DEP SECTORS FOR NORTH WHITING. TFC WAS BUSY AND THE SESSION WAS MADE MORE DIFFICULT BY NUMEROUS STUDENT PLTS NOT ANSWERING RADIO CALLS AND/OR ANSWERING FOR THE WRONG ACFT. NSE CALLED FOR A RELEASE ON A VFR F18. I TOLD THEM TO RELEASE HIM ON A STANDARD DEP HDG (340 DEGS) AND ASSIGN HIM 3000 FT. THEY ACKNOWLEDGED THIS AND HUNG UP. IN THE MEANTIME; I WAS WORKING ON IFR T34 ON DEP. I ASSIGNED HIM 1700 FT (MVA) AND TURNED HIM TO HDG 270 DEGS; AND THEN HDG 230 DEGS. HE WAS APPROX 4 MI NW OF NSE HDG 230 DEGS. I OBSERVED F18 DEPART NSE. HE APPEARED TO BE HDG NWBOUND AND HIS ALT INDICATED 1000 FT. I BEGAN CALLING TFC TO THE T34. I DID NOT CLB THE T34 BECAUSE I WAS EXPECTING THE F18 TO CLB. HE DIDN'T. THE TARGETS MERGED-- THE F18 FLEW UNDER THE T34 AT APPROX 1000 FT. I FINALLY GOT THE F18 ON FREQ AND ASKED HIM WHAT HDG NSE ASSIGNED HIM. HE SAID NO HDG (AND APPARENTLY NO ALT) WERE ASSIGNED BY NSE. EARLIER IN THE SAME SESSION; I HAD TO STOP DEPS AT NSE BECAUSE OF TFC SATURATION. APPROX 2 MINS AFTER I STOPPED DEPS; NSE LAUNCHED A T34; WITHOUT A RELEASE. I CALLED THE P31 SUPVR ON DUTY DOWN TO THE SECTOR AND RPTED BOTH OF THESE EVENTS. I SPECIFICALLY STATED THAT NSE HAD COMMITTED AN OPDEV WHEN THEY LAUNCHED THE T34. NO ACTION WAS TAKEN; TO MY KNOWLEDGE; OTHER THAN THE SUPVR AND AREA MGR MAKING A COUPLE OF PHONE CALLS TO NSE. THIS IS TYPICAL OF THE FAA'S ATTITUDE REGARDING THE NAVY. LITTLE IF ANY ACTION IS EVER TAKEN EVEN WHEN NSE VIOLATES THE LOA'S; 7110.65; ETC.

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