Narrative:

I took off at the destin airport at about XA30Z on feb/xa/99. I departed runway 14 and after crossing to coast line (1 mi south of runway), I turned west heading 270 degrees. I departed VFR (WX was good). I initially called eglin after turning west and there was no reply. He was apparently busy with something else. I finally got a response when I was nearing the town of ft walton (7 mi west of destin airport). Upon requesting a clearance to my destination (crx) bearing about 345 degrees, he told me to remain clear of the eglin airspace. I replied, 'roger, remain clear of eglin controled airspace.' I also told him I was over ft walton and turning north. I knew I was heading toward the north. My ignorance and not having the map handy, I entered the corridor not knowing I was. At the time, I was not clear on the rules and classification of the north/south corridor that GA aircraft use to access the destin airport from the north and departing to the north. I have flown through this area many times, always in direct communication with eglin approach. I have never had any trouble here. I had the appropriate maps with me but not open or immediately handy. I think that this contributed to the airspace violation being addressed. It was after I entered the corridor that he asked me to identify myself via radio and present position in relation to eglin AFB. I idented myself and he informed me that I was in the corridor illegally. I continued north and leveled at 8000 ft as I had filed. It was about this time that I received an IFR clearance to my destination. In my opinion the contributing factors to this violation were: 1) pilot error and misunderstanding of the north/south corridor. 2) not having map open and in hand. 3) temporary overload on the ATC operator. To correct this and prevent this from happening again, I have studied the airspace around eglin AFB and the north/south corridor. I should not anticipate getting an IFR clearance in the air for the controllers could get busy at any time. I am sorry that this happened and feel fortunate that there were no 'near misses' involved. I will do everything in my power to prevent this from happening again.

Related reports:

Google
 

Original NASA ASRS Text

Title: A DEPARTING, CLBING GA ACFT ENTERS THE EGLIN AFB N-S CORRIDOR PRIOR TO RECEIVING ANY CLRNC TO DO SO. THE PLT HAD NOT FILED AN IFR CLRNC PRIOR TO DEP AND WAS WAITING FOR EGLIN APCH CTLR TO ANSWER HIS REQUEST FOR AN IFR CLRNC TO CRX, MS.

Narrative: I TOOK OFF AT THE DESTIN ARPT AT ABOUT XA30Z ON FEB/XA/99. I DEPARTED RWY 14 AND AFTER XING TO COAST LINE (1 MI S OF RWY), I TURNED W HDG 270 DEGS. I DEPARTED VFR (WX WAS GOOD). I INITIALLY CALLED EGLIN AFTER TURNING W AND THERE WAS NO REPLY. HE WAS APPARENTLY BUSY WITH SOMETHING ELSE. I FINALLY GOT A RESPONSE WHEN I WAS NEARING THE TOWN OF FT WALTON (7 MI W OF DESTIN ARPT). UPON REQUESTING A CLRNC TO MY DEST (CRX) BEARING ABOUT 345 DEGS, HE TOLD ME TO REMAIN CLR OF THE EGLIN AIRSPACE. I REPLIED, 'ROGER, REMAIN CLR OF EGLIN CTLED AIRSPACE.' I ALSO TOLD HIM I WAS OVER FT WALTON AND TURNING N. I KNEW I WAS HDG TOWARD THE N. MY IGNORANCE AND NOT HAVING THE MAP HANDY, I ENTERED THE CORRIDOR NOT KNOWING I WAS. AT THE TIME, I WAS NOT CLR ON THE RULES AND CLASSIFICATION OF THE N/S CORRIDOR THAT GA ACFT USE TO ACCESS THE DESTIN ARPT FROM THE N AND DEPARTING TO THE N. I HAVE FLOWN THROUGH THIS AREA MANY TIMES, ALWAYS IN DIRECT COM WITH EGLIN APCH. I HAVE NEVER HAD ANY TROUBLE HERE. I HAD THE APPROPRIATE MAPS WITH ME BUT NOT OPEN OR IMMEDIATELY HANDY. I THINK THAT THIS CONTRIBUTED TO THE AIRSPACE VIOLATION BEING ADDRESSED. IT WAS AFTER I ENTERED THE CORRIDOR THAT HE ASKED ME TO IDENT MYSELF VIA RADIO AND PRESENT POS IN RELATION TO EGLIN AFB. I IDENTED MYSELF AND HE INFORMED ME THAT I WAS IN THE CORRIDOR ILLEGALLY. I CONTINUED N AND LEVELED AT 8000 FT AS I HAD FILED. IT WAS ABOUT THIS TIME THAT I RECEIVED AN IFR CLRNC TO MY DEST. IN MY OPINION THE CONTRIBUTING FACTORS TO THIS VIOLATION WERE: 1) PLT ERROR AND MISUNDERSTANDING OF THE N/S CORRIDOR. 2) NOT HAVING MAP OPEN AND IN HAND. 3) TEMPORARY OVERLOAD ON THE ATC OPERATOR. TO CORRECT THIS AND PREVENT THIS FROM HAPPENING AGAIN, I HAVE STUDIED THE AIRSPACE AROUND EGLIN AFB AND THE N/S CORRIDOR. I SHOULD NOT ANTICIPATE GETTING AN IFR CLRNC IN THE AIR FOR THE CTLRS COULD GET BUSY AT ANY TIME. I AM SORRY THAT THIS HAPPENED AND FEEL FORTUNATE THAT THERE WERE NO 'NEAR MISSES' INVOLVED. I WILL DO EVERYTHING IN MY PWR TO PREVENT THIS FROM HAPPENING AGAIN.

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.