An A319 crew refused the approach to runway 22 at lga due to a tailwind, a go around ensued.

Attributes
ACN	517604
Time
Date	200107
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lga.airport
State Reference	NY
Altitude	msl bound lower : 2700 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : lga.tower artcc : zhu.artcc
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach landing : go around
Route In Use	approach other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 23000 flight time type : 1600
ASRS Report	517604
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	altitude deviation : overshoot inflight encounter : weather non adherence : clearance non adherence : published procedure other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued advisory controller : issued new clearance flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Weather Environmental Factor ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

ATIS for lga was advertising winds of about 320 degrees 12 KTS and we were on an RNAV approach for runway 22. When we got over to tower. He announced winds of about 350 degrees 14 KTS which was borderline limiting and totally stupid. I asked him again. And now it ws 340 degrees 13 KTS, but I'm thinking pretty strong quartering tailwind and a bad idea. We said no to the approach, but were still about 2000 ft. To get out of the approach mode and get go around logic, you have to advance the throttles to toga and quickly snap them back to 'cl' detent. While the first officer did this, we think the controller cleared us to 2000 ft in the middle of the throttle up. The missed approach altitude was 2700 ft, but we still had 3000 ft set in the window as that was our initial point of the approach. We, with that throttle burst, shut up to 2700 ft and eventually leveled at 3000 ft -- which I asked if that was ok. The tower fellow said yes, and there was no conflict that we know of. 5 mins later, they had the airport turned around, and we landed on runway 31. There was obvious confusion caused mostly by trying to get us to land with a serious tailwind.

Original NASA ASRS Text

Title: AN A319 CREW REFUSED THE APCH TO RWY 22 AT LGA DUE TO A TAILWIND, A GAR ENSUED.

Narrative: ATIS FOR LGA WAS ADVERTISING WINDS OF ABOUT 320 DEGS 12 KTS AND WE WERE ON AN RNAV APCH FOR RWY 22. WHEN WE GOT OVER TO TWR. HE ANNOUNCED WINDS OF ABOUT 350 DEGS 14 KTS WHICH WAS BORDERLINE LIMITING AND TOTALLY STUPID. I ASKED HIM AGAIN. AND NOW IT WS 340 DEGS 13 KTS, BUT I'M THINKING PRETTY STRONG QUARTERING TAILWIND AND A BAD IDEA. WE SAID NO TO THE APCH, BUT WERE STILL ABOUT 2000 FT. TO GET OUT OF THE APCH MODE AND GET GAR LOGIC, YOU HAVE TO ADVANCE THE THROTTLES TO TOGA AND QUICKLY SNAP THEM BACK TO 'CL' DETENT. WHILE THE FO DID THIS, WE THINK THE CTLR CLRED US TO 2000 FT IN THE MIDDLE OF THE THROTTLE UP. THE MISSED APCH ALT WAS 2700 FT, BUT WE STILL HAD 3000 FT SET IN THE WINDOW AS THAT WAS OUR INITIAL POINT OF THE APCH. WE, WITH THAT THROTTLE BURST, SHUT UP TO 2700 FT AND EVENTUALLY LEVELED AT 3000 FT -- WHICH I ASKED IF THAT WAS OK. THE TWR FELLOW SAID YES, AND THERE WAS NO CONFLICT THAT WE KNOW OF. 5 MINS LATER, THEY HAD THE ARPT TURNED AROUND, AND WE LANDED ON RWY 31. THERE WAS OBVIOUS CONFUSION CAUSED MOSTLY BY TRYING TO GET US TO LAND WITH A SERIOUS TAILWIND.

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.