Narrative:

Training flight from columbus, ms, AFB consisting of 2 MTR's entered holly springs sector west/O prior handoff or coordination. I observed the transponder code of the flight approximately 15 mi in my airspace. Columbus AFB approach controller called to initiate handoff and advised the flight had not called airborne until just then. No evasive action was required. Contributing factors include the local procedure at columbus AFB for flts to call airborne to approach control rather than having tower advise. The instrument pilot of this flight should bear full responsibility for allowing the flight proceed 60 mi out a departure route west/O advising approach they were airborne. The lead aircraft did not have transponder activated. In essence, we had a flight of high performance aircraft at an IFR altitude non radar with no communications. This has happened to me, personally, 3 times before. It is imperative that the instrument ensure the proper contacts are made at the proper time. He is not riding a ferris wheel. The local procedure should be changed to have the tower advise departure control of active flts. Callback conversation with reporter revealed the following: reporter stated yrs of ATC experience. Reporter unable to get a straight answer from cbm tower controllers or atrep as to why the tower does not input departure times via fdep or call them via landline. As it stands now, many departures get airborne west/O transponders on or off times in computer to activate the flight plan, which not only results in unauthorized penetration of airspace, but could lead to a more serious incident.

Google
 

Original NASA ASRS Text

Title: MIL MTR FLT DEPARTED WITHOUT HIS DEP TIME BEING FORWARDED TO ATC BY MIL TWR OR MIL FLT CREW. ACFT PENETRATED ARTCC AIRSPACE BY 15 MILES WITHOUT COORD OR HANDOFF.

Narrative: TRNING FLT FROM COLUMBUS, MS, AFB CONSISTING OF 2 MTR'S ENTERED HOLLY SPRINGS SECTOR W/O PRIOR HDOF OR COORD. I OBSERVED THE TRANSPONDER CODE OF THE FLT APPROX 15 MI IN MY AIRSPACE. COLUMBUS AFB APCH CTLR CALLED TO INITIATE HDOF AND ADVISED THE FLT HAD NOT CALLED AIRBORNE UNTIL JUST THEN. NO EVASIVE ACTION WAS REQUIRED. CONTRIBUTING FACTORS INCLUDE THE LCL PROC AT COLUMBUS AFB FOR FLTS TO CALL AIRBORNE TO APCH CTL RATHER THAN HAVING TWR ADVISE. THE INSTR PLT OF THIS FLT SHOULD BEAR FULL RESPONSIBILITY FOR ALLOWING THE FLT PROCEED 60 MI OUT A DEP ROUTE W/O ADVISING APCH THEY WERE AIRBORNE. THE LEAD ACFT DID NOT HAVE TRANSPONDER ACTIVATED. IN ESSENCE, WE HAD A FLT OF HIGH PERFORMANCE ACFT AT AN IFR ALT NON RADAR WITH NO COMS. THIS HAS HAPPENED TO ME, PERSONALLY, 3 TIMES BEFORE. IT IS IMPERATIVE THAT THE INSTR ENSURE THE PROPER CONTACTS ARE MADE AT THE PROPER TIME. HE IS NOT RIDING A FERRIS WHEEL. THE LCL PROC SHOULD BE CHANGED TO HAVE THE TWR ADVISE DEP CTL OF ACTIVE FLTS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR STATED YRS OF ATC EXPERIENCE. RPTR UNABLE TO GET A STRAIGHT ANSWER FROM CBM TWR CTLRS OR ATREP AS TO WHY THE TWR DOES NOT INPUT DEP TIMES VIA FDEP OR CALL THEM VIA LANDLINE. AS IT STANDS NOW, MANY DEPS GET AIRBORNE W/O TRANSPONDERS ON OR OFF TIMES IN COMPUTER TO ACTIVATE THE FLT PLAN, WHICH NOT ONLY RESULTS IN UNAUTH PENETRATION OF AIRSPACE, BUT COULD LEAD TO A MORE SERIOUS INCIDENT.

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