During approach the boeing 737-700 crew was vectored by ATC on a course that conflicted with a tethe...

Narrative:

While being vectored by approach control on an easterly heading approximately 12 miles northeast of destination we received a GPWS alert of 'caution; obstacle' followed by a warning 'obstacle; obstacle; pull up.' the alert was generated by a tethered balloon in restricted airspace. I have flown into this airport numerous times and this event did not take us by surprise. We had briefed this restricted area earlier in the flight and both had terrain displayed on our nds. As we arrived in the terminal area; I pointed out the obstacle on the nd and explained how we would most likely be vectored into the airport. The first officer and I were both well aware that we needed a turn and conveyed that to approach control; who was vectoring another aircraft on a left base. Immediately thereafter; we received the caution and prior to receiving a vector we received the warning. It was obvious the terrain avoidance maneuver would not be appropriate in this situation. The autopilot and autothrottles were disconnected and a hard right turn at approximately 40-degree angle of bank was used. During the turn; ATC told us to fly heading 150. I had already overshot that heading by 20 degrees and immediately corrected back to the 150 degree heading. I can't say whether or not we had entered the restricted area. We were then vectored to an uneventful visual approach and landing.on the ground; I contacted approach control by telephone and we discussed the situation. The controller said he had the tethered balloon displayed on his screen but was delaying the vector because of spacing with the aircraft on left base but was just about to turn us. He stated adding to his predicament was the fact that we were co altitude with the other aircraft. We were assigned that altitude by the controller he had just relieved after asking for lower to get out of the bumpy cumulus clouds. I explained our warning system to him and we discussed steps that may be taken in the future to prevent a situation such as this. We could have notified the controller sooner for our need for a turn.

Original NASA ASRS Text

Title: During approach the Boeing 737-700 crew was vectored by ATC on a course that conflicted with a tethered balloon restricted area. The EGPWS activated and the crew took immediate evasive action.

Narrative: While being vectored by Approach Control on an easterly heading approximately 12 miles northeast of destination we received a GPWS alert of 'Caution; Obstacle' followed by a warning 'Obstacle; Obstacle; Pull Up.' The alert was generated by a tethered balloon in Restricted Airspace. I have flown into this airport numerous times and this event did not take us by surprise. We had briefed this restricted area earlier in the flight and both had terrain displayed on our NDs. As we arrived in the terminal area; I pointed out the obstacle on the ND and explained how we would most likely be vectored into the airport. The First Officer and I were both well aware that we needed a turn and conveyed that to Approach Control; who was vectoring another aircraft on a left base. Immediately thereafter; we received the caution and prior to receiving a vector we received the warning. It was obvious the terrain avoidance maneuver would not be appropriate in this situation. The autopilot and autothrottles were disconnected and a hard right turn at approximately 40-degree angle of bank was used. During the turn; ATC told us to fly heading 150. I had already overshot that heading by 20 degrees and immediately corrected back to the 150 degree heading. I can't say whether or not we had entered the restricted area. We were then vectored to an uneventful visual approach and landing.On the ground; I contacted Approach Control by telephone and we discussed the situation. The Controller said he had the tethered balloon displayed on his screen but was delaying the vector because of spacing with the aircraft on left base but was just about to turn us. He stated adding to his predicament was the fact that we were co altitude with the other aircraft. We were assigned that altitude by the Controller he had just relieved after asking for lower to get out of the bumpy cumulus clouds. I explained our warning system to him and we discussed steps that may be taken in the future to prevent a situation such as this. We could have notified the Controller sooner for our need for a turn.

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

Attributes
ACN	1093311
Time
Date	201306
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 13 Flight Crew Type 13000
Person 2
Function	First Officer
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT

During approach the boeing 737-700 crew was vectored by ATC on a course that conflicted with a tethered balloon restricted area. The egpws activated and the crew took immediate evasive action.