Narrative:

The aircraft I was working was deviating east of course and was told to proceed direct to omn when able. The aircraft was approaching what I thought to be daytona approach controls airspace. When I called daytona; the controller told me that isn't his airspace. I asked him whose airspace it was and he was unable to give me a specific response but gave me three possibilities. Of the three I first called the barin/stoop sector of miama center and was informed that wasn't their airspace. I then called the st. Augustine sector of jax center and was informed that wasn't their airspace either. I asked them whose airspace it was and they said sealord and also advised me that the aircraft was in an active warning area. I asked them to point the aircraft to sealord as I didn't have a direct line to them. They then informed me that sealord received the point out on the aircraft but after the aircraft was already about 10 miles in their airspace. The aircraft then began his turn west bound towards omn into daytona approach. I then was relieved from position perplexed because; I feel if we boarder sealord's airspace we should have a direct line to them and know more about them. That was the first time I even knew the airspace existed! I informed the supervisor and he told me where I could find there dial code. It is located in the ids system on a page that is very hard to find and to be quite frank; the supervisor who was on the phone didn't know where to find it either because he also asked jax center to point the aircraft out under the assumption that we didn't have a means to communicate with them. I recommend that the facility acquire information about sealord; boundary lines; hours of operations; etc.; as none of this info was present to me at the time. Very little is know about this sector. I also recommend we install a direct dial line to be able to communicate with this sector as it boarders our airspace here at F11. It was a frustrating position for me to be in as I knew something was developing; and had to find the solution and information through two other facilities.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLL Controller described an airspace incursion event into an adjacent military controlled area; the reporter noting a lack of knowledge regarding the adjacent airspace and difficulty communicating with same.

Narrative: The aircraft I was working was deviating East of course and was told to proceed direct to OMN when able. The aircraft was approaching what I thought to be Daytona Approach Controls airspace. When I called Daytona; the Controller told me that isn't his airspace. I asked him whose airspace it was and he was unable to give me a specific response but gave me three possibilities. Of the three I first called the Barin/Stoop Sector of Miama Center and was informed that wasn't their airspace. I then called the St. Augustine Sector of Jax Center and was informed that wasn't their airspace either. I asked them whose airspace it was and they said SEALORD and also advised me that the aircraft was in an active Warning Area. I asked them to point the aircraft to SEALORD as I didn't have a direct line to them. They then informed me that SEALORD received the point out on the aircraft but after the aircraft was already about 10 miles in their airspace. The aircraft then began his turn West bound towards OMN into Daytona Approach. I then was relieved from position perplexed because; I feel if we boarder SEALORD's airspace we should have a direct line to them and know more about them. That was the first time I even knew the airspace existed! I informed the supervisor and he told me where I could find there dial code. It is located in the IDS system on a page that is very hard to find and to be quite frank; the supervisor who was on the phone didn't know where to find it either because he also asked Jax Center to point the aircraft out under the assumption that we didn't have a means to communicate with them. I recommend that the facility acquire information about SEALORD; boundary lines; hours of operations; etc.; as none of this info was present to me at the time. Very little is know about this sector. I also recommend we install a direct dial line to be able to communicate with this sector as it boarders our airspace here at F11. It was a frustrating position for me to be in as I knew something was developing; and had to find the solution and information through two other facilities.

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