MIL FACILITY DEV.

Narrative

WHILE WORKING THE COMBINED RADAR APCH AND DEP CTL POS AT THE ABILENE FAA RAPCON LOCATED ON DYESS AFB; TX; I BECAME AWARE THAT DYESS TWR (USAF) HAD CALLED OUR FLT DATA POS TO INQUIRE IF WE HAD A FLT PROGRESS STRIP REFLECTING THE FLT PLAN DATA ON AN ACFT TO WHICH THEY HAD JUST ISSUED AN ATC CLRNC TO BARKSDALE AFB; LA. WE HAD NONE AND DETERMINED THAT THE NAS COMPUTER AT FORT WORTH ARTCC DID NOT HAVE ANY FLT PLAN FILED FOR THIS CROSS COUNTRY FLT WITH A CALL SIGN OF XXX. THERE WAS; HOWEVER; 1 FILED UNDER THAT CALL SIGN FROM SHREVEPORT REGIONAL ARPT TO BARKSDALE AFB SOME TIME LATER. WE ASKED DYESS TWR HOW THEY HAD ISSUED AN ATC CLRNC TO THE PLT WITHOUT A FLT PLAN FILED. THEY REPLIED THAT WHEN NO IFR FLT PLAN WAS FOUND OFF DYESS; THEY'D SIMPLY AMENDED THE PROPOSED DEP TIME FROM SHREVEPORT IN ORDER FOR THE COMPUTER TO GENERATE A XPONDER CODE AND THEN ISSUED THE PLT AN ATC CLRNC TO BARKSDALE AS 'CLRED AS FILED.' THEY MADE NO OTHER CHANGES OR INPUTS AND THE T38; WAS ABOUT TO DEPART ON AN INVALID ATC CLRNC BASED UPON A NON EXISTENT FLT PLAN. WE ADVISED DYESS TWR THAT WE COULD NOT ACCEPT THE FLT AND TO TELL THE PLT THAT HE WOULD HAVE TO FILE A FLT PLAN WITH BASOPS. OUR SUPVR THEN CALLED THEIR SUPVR TO FIND OUT HOW SUCH A THING COULD HAPPEN. HE WAS TOLD THAT THE PARTY RESPONSIBLE WAS IN FACT THE USAF SUPVR WHO WAS WORKING THE FLT DATA POS AND HE APPARENTLY JUST DOES NOT UNDERSTAND THE SYS. SINCE IT WAS SUPVR TO SUPVR; NO OTHER ACTION WAS TAKEN. TO MY CERTAIN KNOWLEDGE; THIS IS AT LEAST THE SECOND TIME THIS SAME THING HAS OCCURRED THIS YR. THE LAST ONE I WAS AWARE OF WE WERE NOT LUCKY ENOUGH TO CATCH THEM IN TIME AND THE ACFT ACTUALLY GOT AIRBORNE ON THE INVALID ATC CLRNC WITH NO FLT PLAN FILED. AGAIN NO ACTION WAS TAKEN AND THESE ARE JUST 2 EXAMPLES OF THE LAX ATTITUDES OF FAA SUPVRS TOWARDS DYESS TWR CTLR'S DEVS. THE STANDARD STATEMENT IS 'WELL IT WON'T DO ANY GOOD ANYWAY.' THAT IN TURN; LEADS TO THE SAME ATTITUDE AMONG OUR OWN CTLRS WHO FEEL IT'S NO USE TO EVEN RPT THEM.