Narrative:

We were departing runway 04 in lga. I received position and hold, then we were cleared for immediate take off. Just before vr, we hear air carrier Y go around. They were landing runway 31. I looked to our right, there was a MD80 about 3000 ft off our right and about 200 ft AGL. We were between 20 and 200 ft AGL. We turned to a 360 degree heading at 400 ft. I believe the contributing factor for lga and the controller are takeoff and landing too many airplanes too close together. I don't know if the go around was issued due to another aircraft on runway 31 or a conflict with us on runway 04. Supplemental information from acn 571559: potential for midair at lga. My aircraft on takeoff roll. MD80 flight given go around instructions on crossing runway. 1) controller pushing the limit on separation. 2) slow spooling engines, poor judgement on controllers part traffic congestion. Callback conversation with reporter revealed the following information: the departing aircraft had been in a long line up for departure. They were cleared into position and hold for an estimated one min before being issued an 'immediate' takeoff clearance. There was no delay in beginning the takeoff roll other than the normal time it takes for the engines to spool up. The MD80 traffic was not mentioned in the takeoff clearance. The local controller was handling both arrs and departures. Arrs were being cleared for visual approachs to runway 31. The approach end of runway 31 is not visible from the 'position and hold' position on runway 04 because of the terminal location. The full complement of approaching landing lights on the MD80 were quite startling as we were above V1 and committed for take off. The turn that was made at 400 ft was normal and not an evasive maneuver.

Related reports:

Google
 

Original NASA ASRS Text

Title: AFTER BEING ISSUED AN IMMEDIATE TKOF CLRNC ON LGA, RWY 04, AN A319 FLC OBSERVES A MD80, MIDFIELD RWY 31 AT APPROX 200 FT, ON A GAR.

Narrative: WE WERE DEPARTING RWY 04 IN LGA. I RECEIVED POSITION AND HOLD, THEN WE WERE CLRED FOR IMMEDIATE TAKE OFF. JUST BEFORE VR, WE HEAR ACR Y GAR. THEY WERE LNDG RWY 31. I LOOKED TO OUR R, THERE WAS A MD80 ABOUT 3000 FT OFF OUR R AND ABOUT 200 FT AGL. WE WERE BETWEEN 20 AND 200 FT AGL. WE TURNED TO A 360 DEG HEADING AT 400 FT. I BELIEVE THE CONTRIBUTING FACTOR FOR LGA AND THE CTLR ARE TKOF AND LNDG TOO MANY AIRPLANES TOO CLOSE TOGETHER. I DON'T KNOW IF THE GAR WAS ISSUED DUE TO ANOTHER ACFT ON RWY 31 OR A CONFLICT WITH US ON RWY 04. SUPPLEMENTAL INFO FROM ACN 571559: POTENTIAL FOR MIDAIR AT LGA. MY ACFT ON TKOF ROLL. MD80 FLT GIVEN GAR INSTRUCTIONS ON CROSSING RWY. 1) CTLR PUSHING THE LIMIT ON SEPARATION. 2) SLOW SPOOLING ENGINES, POOR JUDGEMENT ON CTLRS PART TFC CONGESTION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE DEPARTING ACFT HAD BEEN IN A LONG LINE UP FOR DEP. THEY WERE CLRED INTO POSITION AND HOLD FOR AN ESTIMATED ONE MIN BEFORE BEING ISSUED AN 'IMMEDIATE' TKOF CLRNC. THERE WAS NO DELAY IN BEGINNING THE TKOF ROLL OTHER THAN THE NORMAL TIME IT TAKES FOR THE ENGINES TO SPOOL UP. THE MD80 TFC WAS NOT MENTIONED IN THE TKOF CLRNC. THE LCL CTLR WAS HANDLING BOTH ARRS AND DEPS. ARRS WERE BEING CLRED FOR VISUAL APCHS TO RWY 31. THE APCH END OF RWY 31 IS NOT VISIBLE FROM THE 'POSITION AND HOLD' POSITION ON RWY 04 BECAUSE OF THE TERMINAL LOCATION. THE FULL COMPLEMENT OF APCHING LNDG LIGHTS ON THE MD80 WERE QUITE STARTLING AS WE WERE ABOVE V1 AND COMMITTED FOR TAKE OFF. THE TURN THAT WAS MADE AT 400 FT WAS NORMAL AND NOT AN EVASIVE MANEUVER.

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.