Narrative:

On feb/xa/99, a BE55 baron departed vps. IFR clearance received from eglin clearance delivery control prior to taxi was 'cleared as filed to wrb, maintain runway heading, climb to 3000 ft, expect 9000 ft 10 mins after departure, departure control frequency is 125.1, squawk XXXX. Eglin tower clearance to depart runway 30 was 'fly runway heading, climb to 2000 ft.' after takeoff, climb was accomplished to 2000 ft MSL on runway heading. No further communications from the tower were received until the pilot called 5 mins after takeoff and informed the tower that the aircraft was still at 2000 ft on runway heading. Eglin tower replied 'we show you 12 mi west.' pilot reported again 'I'm still at 2000 ft on runway heading.' eglin tower then replied 'we show you 15 mi west, contact eglin departure on 125.1.' pilot reported to eglin tower 'switching to 125.1.' there was a small delay, perhaps 30 seconds before communications were established with eglin departure control due to other traffic on the frequency. Pilot reported to eglin departure control that he was 'level at 2000 ft, runway heading.' eglin departure control gave instructions to climb to 3000 ft, heading 090 degrees, and repeatedly questioned the pilot as to what distance he was at when tower advised the pilot to change to departure control frequency. Eglin departure control gave further vectors, and climb to 9000 ft, and again questioned the pilot as to what distance he was when eglin tower gave instructions to contact departure control. Subsequent climb to altitude, and interception of assigned route was without incident. Reference to united states government flight information publication, IFR en route low altitude -- united states, navigation chart L18, indicates aircraft penetrated sua R2915A prior to receiving instructions from eglin tower to contact eglin departure control. Callback conversation with reporter revealed the following information: reporter called back and stated that he had not received any other calls from either the FAA or the military regarding this incident. He thinks that the military is undergoing a lot of training and that this controller forgot about his aircraft. He is concerned about the level of proficiency exhibited by the military controllers that he contacts in his course of business flying. No explanation offered as to why he waited so long to call the tower.

Google
 

Original NASA ASRS Text

Title: A BE55 DEPARTING EGLIN FIELD FLIES INTO THE RESTR AREA 6 MI NW OF THE DEP ARPT.

Narrative: ON FEB/XA/99, A BE55 BARON DEPARTED VPS. IFR CLRNC RECEIVED FROM EGLIN CLRNC DELIVERY CTL PRIOR TO TAXI WAS 'CLRED AS FILED TO WRB, MAINTAIN RWY HDG, CLB TO 3000 FT, EXPECT 9000 FT 10 MINS AFTER DEP, DEP CTL FREQ IS 125.1, SQUAWK XXXX. EGLIN TWR CLRNC TO DEPART RWY 30 WAS 'FLY RWY HDG, CLB TO 2000 FT.' AFTER TKOF, CLB WAS ACCOMPLISHED TO 2000 FT MSL ON RWY HDG. NO FURTHER COMS FROM THE TWR WERE RECEIVED UNTIL THE PLT CALLED 5 MINS AFTER TKOF AND INFORMED THE TWR THAT THE ACFT WAS STILL AT 2000 FT ON RWY HDG. EGLIN TWR REPLIED 'WE SHOW YOU 12 MI W.' PLT RPTED AGAIN 'I'M STILL AT 2000 FT ON RWY HDG.' EGLIN TWR THEN REPLIED 'WE SHOW YOU 15 MI W, CONTACT EGLIN DEP ON 125.1.' PLT RPTED TO EGLIN TWR 'SWITCHING TO 125.1.' THERE WAS A SMALL DELAY, PERHAPS 30 SECONDS BEFORE COMS WERE ESTABLISHED WITH EGLIN DEP CTL DUE TO OTHER TFC ON THE FREQ. PLT RPTED TO EGLIN DEP CTL THAT HE WAS 'LEVEL AT 2000 FT, RWY HDG.' EGLIN DEP CTL GAVE INSTRUCTIONS TO CLB TO 3000 FT, HDG 090 DEGS, AND REPEATEDLY QUESTIONED THE PLT AS TO WHAT DISTANCE HE WAS AT WHEN TWR ADVISED THE PLT TO CHANGE TO DEP CTL FREQ. EGLIN DEP CTL GAVE FURTHER VECTORS, AND CLB TO 9000 FT, AND AGAIN QUESTIONED THE PLT AS TO WHAT DISTANCE HE WAS WHEN EGLIN TWR GAVE INSTRUCTIONS TO CONTACT DEP CTL. SUBSEQUENT CLB TO ALT, AND INTERCEPTION OF ASSIGNED RTE WAS WITHOUT INCIDENT. REF TO UNITED STATES GOV FLT INFO PUB, IFR ENRTE LOW ALT -- UNITED STATES, NAV CHART L18, INDICATES ACFT PENETRATED SUA R2915A PRIOR TO RECEIVING INSTRUCTIONS FROM EGLIN TWR TO CONTACT EGLIN DEP CTL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR CALLED BACK AND STATED THAT HE HAD NOT RECEIVED ANY OTHER CALLS FROM EITHER THE FAA OR THE MIL REGARDING THIS INCIDENT. HE THINKS THAT THE MIL IS UNDERGOING A LOT OF TRAINING AND THAT THIS CTLR FORGOT ABOUT HIS ACFT. HE IS CONCERNED ABOUT THE LEVEL OF PROFICIENCY EXHIBITED BY THE MIL CTLRS THAT HE CONTACTS IN HIS COURSE OF BUSINESS FLYING. NO EXPLANATION OFFERED AS TO WHY HE WAITED SO LONG TO CALL THE TWR.

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