Narrative:

We were inbound to the tanks on the expressway visual runway 31 to lga descending to 2500 ft. ATC attempted several times to point out the traffic that we were to follow. We couldn't find him in the sea of lights, so ATC took us out of the pattern and vectored us back to the tanks. ATC pointed out our traffic to follow over tanks and we called the traffic in sight. We followed the aircraft over the tanks and turned to 085 degrees to follow the expressway and our traffic. We configured for landing and were at about 130 KTS as we started to turn around shea stadium to pick up the VASI. We were both looking to the left to make the turn around shea when the TCASII displayed an RA. TCASII indicated a red target at approximately 1-2 O'clock and 100 ft below our altitude. I looked out as I began to go around to see this jet which appeared to be flying a straight-in to runway 31. ATC told us to turn to 100 degrees and climb to 2000 ft. As we were turning to 100 degrees, ATC asked us our heading. We were passing 070 degrees and ATC said turn to 040 degrees. Next they gave us 270 degrees and 4000 ft. We were given a series of heading changes very quickly including a command to follow the hudson river which was 12 O'clock and approximately 5 mi. In the meantime, we received a TCASII advisory which turned to an RA to climb. We began climb and RA quickly was resolved. ATC pointed this traffic out to us and we did have him in sight. We were once again vectored around for the expressway visual and landed. We noticed several aircraft were having trouble picking up their traffic to follow. This approach is much easier during the day because you can look away from your traffic to scan your instruments and then look back out and easily re-identify your traffic. At night this is a real challenge. It's much harder to find your traffic in the sea of lights. This approach is an accident waiting to happen, particularly at night. Callback conversation with reporter revealed the following information: the reporter flies the B757-200. The reporter's aircraft was very slow over 'dials,' then immediately slowed to approach speed. The reporter does not know where the intruding MD88 came from, but it may have been on a straight-in approach. When on the ground, the reporter noticed that other aircraft seemed to be coming straight in, mixing with aircraft on the expressway approach. The captain has followed through with his air carrier and its new york chief pilot. He has found that the controller that allowed the conflict after the missed approach has been decertified and sent back to school. Nothing has been found out about the conflict on approach. The reporter suspects a cover up. The reporter's air carrier does not encourage turning off RA's when in close to the airport, but TCASII does not 'speak' below 1000 ft AGL, this is handled automatically. The reporter pointed out that there is no missed approach procedure for the expressway approach, it is all radar vectors. Supplemental information from acn 362543: although flying the approach visually, we had the FMS expressway visual displayed on our map screens. I would stay outside watching the traffic so we would not lose him in the lights. I followed the aircraft as we began our turn over flushing meadow. Everything lined up perfectly. TCASII showed a TA. The first officer sighted the traffic at about 2 O'clock low, tower called and gave us a climb and vectors. As we taxied to the gate it appeared that an aircraft was on a straight-in approach to runway 31. ATIS at the time was calling the winds 310 degrees at 11 KTS. I feel that a night visual expressway runway 31 approach should not be dependent on pilot visual contact with preceding traffic due to extremely heavy cockpit workload at this point and attendant distracting ground lighting.

Google
 

Original NASA ASRS Text

Title: AN ACR B757-200 HAD TO MAKE 3 TRIES TO GET INTO LGA ON THE EXPRESSWAY VISUAL APCH TO RWY 31. NIGHT OP. WX FACTORS 11 KTS RIGHT DOWN THE RWY. NMAC IN THE EYES OF THE RPTRS. FLC DISTR GND LIGHTS, COCKPIT DUTIES.

Narrative: WE WERE INBOUND TO THE TANKS ON THE EXPRESSWAY VISUAL RWY 31 TO LGA DSNDING TO 2500 FT. ATC ATTEMPTED SEVERAL TIMES TO POINT OUT THE TFC THAT WE WERE TO FOLLOW. WE COULDN'T FIND HIM IN THE SEA OF LIGHTS, SO ATC TOOK US OUT OF THE PATTERN AND VECTORED US BACK TO THE TANKS. ATC POINTED OUT OUR TFC TO FOLLOW OVER TANKS AND WE CALLED THE TFC IN SIGHT. WE FOLLOWED THE ACFT OVER THE TANKS AND TURNED TO 085 DEGS TO FOLLOW THE EXPRESSWAY AND OUR TFC. WE CONFIGURED FOR LNDG AND WERE AT ABOUT 130 KTS AS WE STARTED TO TURN AROUND SHEA STADIUM TO PICK UP THE VASI. WE WERE BOTH LOOKING TO THE L TO MAKE THE TURN AROUND SHEA WHEN THE TCASII DISPLAYED AN RA. TCASII INDICATED A RED TARGET AT APPROX 1-2 O'CLOCK AND 100 FT BELOW OUR ALT. I LOOKED OUT AS I BEGAN TO GAR TO SEE THIS JET WHICH APPEARED TO BE FLYING A STRAIGHT-IN TO RWY 31. ATC TOLD US TO TURN TO 100 DEGS AND CLB TO 2000 FT. AS WE WERE TURNING TO 100 DEGS, ATC ASKED US OUR HDG. WE WERE PASSING 070 DEGS AND ATC SAID TURN TO 040 DEGS. NEXT THEY GAVE US 270 DEGS AND 4000 FT. WE WERE GIVEN A SERIES OF HDG CHANGES VERY QUICKLY INCLUDING A COMMAND TO FOLLOW THE HUDSON RIVER WHICH WAS 12 O'CLOCK AND APPROX 5 MI. IN THE MEANTIME, WE RECEIVED A TCASII ADVISORY WHICH TURNED TO AN RA TO CLB. WE BEGAN CLB AND RA QUICKLY WAS RESOLVED. ATC POINTED THIS TFC OUT TO US AND WE DID HAVE HIM IN SIGHT. WE WERE ONCE AGAIN VECTORED AROUND FOR THE EXPRESSWAY VISUAL AND LANDED. WE NOTICED SEVERAL ACFT WERE HAVING TROUBLE PICKING UP THEIR TFC TO FOLLOW. THIS APCH IS MUCH EASIER DURING THE DAY BECAUSE YOU CAN LOOK AWAY FROM YOUR TFC TO SCAN YOUR INSTS AND THEN LOOK BACK OUT AND EASILY RE-IDENT YOUR TFC. AT NIGHT THIS IS A REAL CHALLENGE. IT'S MUCH HARDER TO FIND YOUR TFC IN THE SEA OF LIGHTS. THIS APCH IS AN ACCIDENT WAITING TO HAPPEN, PARTICULARLY AT NIGHT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR FLIES THE B757-200. THE RPTR'S ACFT WAS VERY SLOW OVER 'DIALS,' THEN IMMEDIATELY SLOWED TO APCH SPD. THE RPTR DOES NOT KNOW WHERE THE INTRUDING MD88 CAME FROM, BUT IT MAY HAVE BEEN ON A STRAIGHT-IN APCH. WHEN ON THE GND, THE RPTR NOTICED THAT OTHER ACFT SEEMED TO BE COMING STRAIGHT IN, MIXING WITH ACFT ON THE EXPRESSWAY APCH. THE CAPT HAS FOLLOWED THROUGH WITH HIS ACR AND ITS NEW YORK CHIEF PLT. HE HAS FOUND THAT THE CTLR THAT ALLOWED THE CONFLICT AFTER THE MISSED APCH HAS BEEN DECERTIFIED AND SENT BACK TO SCHOOL. NOTHING HAS BEEN FOUND OUT ABOUT THE CONFLICT ON APCH. THE RPTR SUSPECTS A COVER UP. THE RPTR'S ACR DOES NOT ENCOURAGE TURNING OFF RA'S WHEN IN CLOSE TO THE ARPT, BUT TCASII DOES NOT 'SPEAK' BELOW 1000 FT AGL, THIS IS HANDLED AUTOMATICALLY. THE RPTR POINTED OUT THAT THERE IS NO MISSED APCH PROC FOR THE EXPRESSWAY APCH, IT IS ALL RADAR VECTORS. SUPPLEMENTAL INFO FROM ACN 362543: ALTHOUGH FLYING THE APCH VISUALLY, WE HAD THE FMS EXPRESSWAY VISUAL DISPLAYED ON OUR MAP SCREENS. I WOULD STAY OUTSIDE WATCHING THE TFC SO WE WOULD NOT LOSE HIM IN THE LIGHTS. I FOLLOWED THE ACFT AS WE BEGAN OUR TURN OVER FLUSHING MEADOW. EVERYTHING LINED UP PERFECTLY. TCASII SHOWED A TA. THE FO SIGHTED THE TFC AT ABOUT 2 O'CLOCK LOW, TWR CALLED AND GAVE US A CLB AND VECTORS. AS WE TAXIED TO THE GATE IT APPEARED THAT AN ACFT WAS ON A STRAIGHT-IN APCH TO RWY 31. ATIS AT THE TIME WAS CALLING THE WINDS 310 DEGS AT 11 KTS. I FEEL THAT A NIGHT VISUAL EXPRESSWAY RWY 31 APCH SHOULD NOT BE DEPENDENT ON PLT VISUAL CONTACT WITH PRECEDING TFC DUE TO EXTREMELY HVY COCKPIT WORKLOAD AT THIS POINT AND ATTENDANT DISTRACTING GND LIGHTING.

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.