Narrative:

On lga approach, flight was on right base vectors for runway 22, speed 180 KTS. As we were near the turn to final we got a TA at 11 O'clock position, same altitude, and could not see the traffic. While we were very concerned about not seeing close traffic, approach said something and we got an RA with the traffic overhead with 200 ft separation. A supervisor took over when we reported TCASII RA and turned us to final. I called the facility, and their response basically was that this incident was not serious. I disagree. The baron was supposedly being squeezed into the sequence behind us, and adequate separation was lost. This was a blur of desperate events, especially when we never saw the baron.

Google
 

Original NASA ASRS Text

Title: FLC OF MD80 ON 10 MI FINAL HAS TCASII TA THEN RA. THE SECOND ACFT WAS ONLY 200 FT BELOW THE MD80.

Narrative: ON LGA APCH, FLT WAS ON R BASE VECTORS FOR RWY 22, SPD 180 KTS. AS WE WERE NEAR THE TURN TO FINAL WE GOT A TA AT 11 O'CLOCK POS, SAME ALT, AND COULD NOT SEE THE TFC. WHILE WE WERE VERY CONCERNED ABOUT NOT SEEING CLOSE TFC, APCH SAID SOMETHING AND WE GOT AN RA WITH THE TFC OVERHEAD WITH 200 FT SEPARATION. A SUPVR TOOK OVER WHEN WE RPTED TCASII RA AND TURNED US TO FINAL. I CALLED THE FACILITY, AND THEIR RESPONSE BASICALLY WAS THAT THIS INCIDENT WAS NOT SERIOUS. I DISAGREE. THE BARON WAS SUPPOSEDLY BEING SQUEEZED INTO THE SEQUENCE BEHIND US, AND ADEQUATE SEPARATION WAS LOST. THIS WAS A BLUR OF DESPERATE EVENTS, ESPECIALLY WHEN WE NEVER SAW THE BARON.

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.