Narrative:

During departure from lga airport tower instructed us to, 'turn to heading 350 degree now.' we initiated turn right over runway 22 - runway 31 intersection. Upon climbing out of 15000 ft MSL (after contacting departure and climbing to 12000 ft) we received an RA, descend command from TCASII. I initiated descent immediately and looked at TCASII to see 2 targets. The first target was at 2:00 O'clock at 2.5 mi and 300 ft above our altitude. The second was at 8-9 O'clock and at 3 mi at our altitude. The captain (PNF) told departure we received an RA and we descended to comply. Departure informed us we had 1 aircraft now behind us and 1 at 8-9 O'clock at 1000 ft coming up on the hudson, neither a factor, climb to 12000 ft. The captain nor I visually contacted any traffic, so I initiated climb to 12000 ft. Out of 1800 ft MSL, I received another RA to descend. I was hesitant. Upon receiving 'descend now' command. I descended again to approximately 1200 ft MSL. We were blow the clouds and perceived no immediate terrain or aircraft collision danger. After contacting departure again, he told us 'no traffic now, your TCASII, something must be wrong with it. Maybe you should turn it off.' captain and I concurred and immediately initiated aggressive climb to 12000 ft and cycled transponder and TCASII. After level off, I tried TCASII test and it tested ok. Conflict may have been with aircraft on visibility or lda-a to runway 22. Maybe new york should not issue turn to north until you're out of certain altitude and at end of runway 31. Also, before takeoff, radar stabilizer went inoperative and screen said flight 6. Question may be we had a short that caused stabilizer inoperative and TCASII to malfunction after first RA. I believe first RA was correct. With information we had, we did our best.

Google
 

Original NASA ASRS Text

Title: TCASII ALTDEV COMPLYING WITH TCASII COMMAND.

Narrative: DURING DEP FROM LGA ARPT TWR INSTRUCTED US TO, 'TURN TO HDG 350 DEG NOW.' WE INITIATED TURN R OVER RWY 22 - RWY 31 INTXN. UPON CLBING OUT OF 15000 FT MSL (AFTER CONTACTING DEP AND CLBING TO 12000 FT) WE RECEIVED AN RA, DSND COMMAND FROM TCASII. I INITIATED DSCNT IMMEDIATELY AND LOOKED AT TCASII TO SEE 2 TARGETS. THE FIRST TARGET WAS AT 2:00 O'CLOCK AT 2.5 MI AND 300 FT ABOVE OUR ALT. THE SECOND WAS AT 8-9 O'CLOCK AND AT 3 MI AT OUR ALT. THE CAPT (PNF) TOLD DEP WE RECEIVED AN RA AND WE DSNDED TO COMPLY. DEP INFORMED US WE HAD 1 ACFT NOW BEHIND US AND 1 AT 8-9 O'CLOCK AT 1000 FT COMING UP ON THE HUDSON, NEITHER A FACTOR, CLB TO 12000 FT. THE CAPT NOR I VISUALLY CONTACTED ANY TFC, SO I INITIATED CLB TO 12000 FT. OUT OF 1800 FT MSL, I RECEIVED ANOTHER RA TO DSND. I WAS HESITANT. UPON RECEIVING 'DSND NOW' COMMAND. I DSNDED AGAIN TO APPROX 1200 FT MSL. WE WERE BLOW THE CLOUDS AND PERCEIVED NO IMMEDIATE TERRAIN OR ACFT COLLISION DANGER. AFTER CONTACTING DEP AGAIN, HE TOLD US 'NO TFC NOW, YOUR TCASII, SOMETHING MUST BE WRONG WITH IT. MAYBE YOU SHOULD TURN IT OFF.' CAPT AND I CONCURRED AND IMMEDIATELY INITIATED AGGRESSIVE CLB TO 12000 FT AND CYCLED XPONDER AND TCASII. AFTER LEVEL OFF, I TRIED TCASII TEST AND IT TESTED OK. CONFLICT MAY HAVE BEEN WITH ACFT ON VISIBILITY OR LDA-A TO RWY 22. MAYBE NEW YORK SHOULD NOT ISSUE TURN TO N UNTIL YOU'RE OUT OF CERTAIN ALT AND AT END OF RWY 31. ALSO, BEFORE TKOF, RADAR STABILIZER WENT INOP AND SCREEN SAID FLT 6. QUESTION MAY BE WE HAD A SHORT THAT CAUSED STABILIZER INOP AND TCASII TO MALFUNCTION AFTER FIRST RA. I BELIEVE FIRST RA WAS CORRECT. WITH INFO WE HAD, WE DID OUR BEST.

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.