Narrative:

I was working D67 combined up with 68; states sector; during the event. The event started developing when air carrier X was a point out from sector 66 deviating south of chs level at FL290. I approved the point out from 66 on the air carrier X deviating with sector 47 taking radar on the aircraft. The aircraft never entered 47's airspace. Sector 47 called the r-side after air carrier X was in our airspace for about 5-7 minutes stating that he would need to stay on that heading; about a 130; for another 30 miles. At which time my r-side stated radar contact and asked for communications with the aircraft. As soon as air carrier X came over; the r-side controller advised him of the active warning area airspace (W157A) he was about to enter and to fly heading 090 to remain clear. Air carrier X advised that he was unable because that would put him right in the middle of a thunderstorm. I then tried to point out the aircraft to sea lord control deviating on that heading and turning on course when able. Sea lord said unable. The radar controller then advised the aircraft that since he was unable to comply with an ATC clearance to squawk 7700 and say intentions. The aircraft then squawked 7700 and remained on that heading until he was clear of the weather. Things of this nature continue to happen at ZJX. Weather is blocking much of our airspace and we are still expected to operate as normal. In this case the aircraft was never able to make it back over chs and sea lord wouldn't accept a point out on him so his only option to remain clear of the weather was to squawk 7700 and fly into active military airspace with fighter jets. This lack of safety is becoming all too familiar at ZJX. We get aircraft departures and arrivals head on many times because everyone is trying to squeeze through one hole of weather and we have a lot of airspace off the coast that goes active just because one aircraft is using it. I think it is over kill to make all the warning areas active; when only a portion of the area is going to be used by the military. It hampers our ability to do our job safely because of lack of airspace and accommodating aircraft wishing to deviate around weather. Recommendation; some recommendations to prevent this from continuing to happen are: requesting in trail separation for over flights and landing aircraft and to take back airspace and to shut down certain routes that we know aren't working due to weather.

Google
 

Original NASA ASRS Text

Title: ZJX Controller described a complex/unsafe traffic period when an aircraft refused to alter routing because of weather; entering military airspace; the reporter suggesting acquiring additional military airspace; improved in-trail procedures and to simply shut down routes that are unusable due to weather/airspace.

Narrative: I was working D67 combined up with 68; States Sector; during the event. The event started developing when Air Carrier X was a point out from Sector 66 deviating south of CHS level at FL290. I approved the point out from 66 on the Air Carrier X deviating with Sector 47 taking RADAR on the aircraft. The aircraft never entered 47's airspace. Sector 47 called the R-Side after Air Carrier X was in our airspace for about 5-7 minutes stating that he would need to stay on that heading; about a 130; for another 30 miles. At which time my R-Side stated RADAR contact and asked for communications with the aircraft. As soon as Air Carrier X came over; the R-Side Controller advised him of the active warning area airspace (W157A) he was about to enter and to fly heading 090 to remain clear. Air Carrier X advised that he was unable because that would put him right in the middle of a thunderstorm. I then tried to point out the aircraft to Sea Lord Control deviating on that heading and turning on course when able. Sea Lord said unable. The RADAR Controller then advised the aircraft that since he was unable to comply with an ATC clearance to squawk 7700 and say intentions. The aircraft then squawked 7700 and remained on that heading until he was clear of the weather. Things of this nature continue to happen at ZJX. Weather is blocking much of our airspace and we are still expected to operate as normal. In this case the aircraft was never able to make it back over CHS and Sea Lord wouldn't accept a point out on him so his only option to remain clear of the weather was to squawk 7700 and fly into active military airspace with fighter jets. This lack of safety is becoming all too familiar at ZJX. We get aircraft departures and arrivals head on many times because everyone is trying to squeeze through one hole of weather and we have a lot of airspace off the coast that goes active just because one aircraft is using it. I think it is over kill to make all the warning areas active; when only a portion of the area is going to be used by the military. It hampers our ability to do our job safely because of lack of airspace and accommodating aircraft wishing to deviate around weather. Recommendation; some recommendations to prevent this from continuing to happen are: requesting in trail separation for over flights and landing aircraft and to take back airspace and to shut down certain routes that we know aren't working due to weather.

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.