Narrative:

We flew an ILS approach to runway 22 at lga with flaps 30 degrees; vref of about 135 KIAS and manual brakes. We were cleared to land by laguardia tower. When we were starting the flare a regional jet looked like it was starting to move left to right to cross runway 22 on taxiway east. First officer called this out. As we touched down we realized that the regional jet was not going to stop short and continued to cross runway 22 in front of us. First officer called brakes and we both immediately applied maximum manual braking and I applied full reverse thrust. We slowed very quickly reaching taxi speed prior to taxiway east. About the time aircraft Y was clearing the runway laguardia tower made a radio call saying that there was an aircraft exiting at midfield. We cleared the runway at taxiway D and taxied to gate. While taxiing to the ramp we accomplished the after landing checklist. While stopped on taxiway a for taxiing traffic we referenced the brake cooling following landing chart in the odm. We saw that we were not in the caution or fuse plug zone so we continued to the ramp when cleared in. After blocking in we accomplished the shutdown checklist. We then referenced the odm to come up with a more refined brake cooling time of about 24 mins; well less than the turn time of the aircraft. As a precaution maintenance inspected our brakes and landing gear and all was normal. Supplemental information from acn 744729: on taxi out we were instructed to hold short of runway 4 in lga on taxiway F. We complied and held short. As we were #1 for crossing the runway somebody advised ground that there was a vehicle on fire on the other side of the airport near the 5 towers parking area. The controller said he was aware that there was a fire. Shortly thereafter he cleared us across the runway at taxiway F. I read back the crossing clearance and glanced out the right side of the aircraft and observed no traffic. It is noteworthy that taxiway F is a high speed taxiway and when utilized the aircraft faces towards the opposite side of the runway at a 45 degree angle. This makes it very difficult to see down the entire length of the runway or see the final approach end. As we started moving we were told to expedite which we did and I responded. As we entered the runway and the aircraft was perpendicular to the runway I took another look and saw a B737 on the runway approaching us rapidly and he appeared to be using maximum brakes. I told the captain that there was an aircraft approaching and to move it. He complied immediately by adding full thrust to the engine. We cleared with maybe 400 ft to spare. I also noticed there was indeed a dash 8 on a 1 mi final; I think the ground controller must have lost track of the B737; possibly because of the fire situation. Possible ways to avoid this incurrence are as follows: 1) we should have never been issued the crossing. 2) controller was distraction and should have slowed down instead of trying to rush us across. 3) taxiway F or any other reverse high speed should not be utilized for crossing as it is very difficult for the flight crew to see down the runway. 4) runway xings should be made with the tower controller as he or she knows first hand the status of their runway.

Google
 

Original NASA ASRS Text

Title: B737-800 ON LNDG ROLLOUT AND CARJ CLEARED TO CROSS AT TAXIWAY F EXPERIENCE NEAR COLLISION ON RWY 22 AT LGA.

Narrative: WE FLEW AN ILS APCH TO RWY 22 AT LGA WITH FLAPS 30 DEGS; VREF OF ABOUT 135 KIAS AND MANUAL BRAKES. WE WERE CLRED TO LAND BY LAGUARDIA TWR. WHEN WE WERE STARTING THE FLARE A REGIONAL JET LOOKED LIKE IT WAS STARTING TO MOVE L TO R TO CROSS RWY 22 ON TXWY E. FO CALLED THIS OUT. AS WE TOUCHED DOWN WE REALIZED THAT THE REGIONAL JET WAS NOT GOING TO STOP SHORT AND CONTINUED TO CROSS RWY 22 IN FRONT OF US. FO CALLED BRAKES AND WE BOTH IMMEDIATELY APPLIED MAX MANUAL BRAKING AND I APPLIED FULL REVERSE THRUST. WE SLOWED VERY QUICKLY REACHING TAXI SPD PRIOR TO TXWY E. ABOUT THE TIME ACFT Y WAS CLRING THE RWY LAGUARDIA TWR MADE A RADIO CALL SAYING THAT THERE WAS AN ACFT EXITING AT MIDFIELD. WE CLRED THE RWY AT TXWY D AND TAXIED TO GATE. WHILE TAXIING TO THE RAMP WE ACCOMPLISHED THE AFTER LNDG CHKLIST. WHILE STOPPED ON TXWY A FOR TAXIING TFC WE REFED THE BRAKE COOLING FOLLOWING LNDG CHART IN THE ODM. WE SAW THAT WE WERE NOT IN THE CAUTION OR FUSE PLUG ZONE SO WE CONTINUED TO THE RAMP WHEN CLRED IN. AFTER BLOCKING IN WE ACCOMPLISHED THE SHUTDOWN CHKLIST. WE THEN REFED THE ODM TO COME UP WITH A MORE REFINED BRAKE COOLING TIME OF ABOUT 24 MINS; WELL LESS THAN THE TURN TIME OF THE ACFT. AS A PRECAUTION MAINT INSPECTED OUR BRAKES AND LNDG GEAR AND ALL WAS NORMAL. SUPPLEMENTAL INFO FROM ACN 744729: ON TAXI OUT WE WERE INSTRUCTED TO HOLD SHORT OF RWY 4 IN LGA ON TXWY F. WE COMPLIED AND HELD SHORT. AS WE WERE #1 FOR XING THE RWY SOMEBODY ADVISED GND THAT THERE WAS A VEHICLE ON FIRE ON THE OTHER SIDE OF THE ARPT NEAR THE 5 TWRS PARKING AREA. THE CTLR SAID HE WAS AWARE THAT THERE WAS A FIRE. SHORTLY THEREAFTER HE CLRED US ACROSS THE RWY AT TXWY F. I READ BACK THE XING CLRNC AND GLANCED OUT THE R SIDE OF THE ACFT AND OBSERVED NO TFC. IT IS NOTEWORTHY THAT TXWY F IS A HIGH SPD TXWY AND WHEN UTILIZED THE ACFT FACES TOWARDS THE OPPOSITE SIDE OF THE RWY AT A 45 DEG ANGLE. THIS MAKES IT VERY DIFFICULT TO SEE DOWN THE ENTIRE LENGTH OF THE RWY OR SEE THE FINAL APCH END. AS WE STARTED MOVING WE WERE TOLD TO EXPEDITE WHICH WE DID AND I RESPONDED. AS WE ENTERED THE RWY AND THE ACFT WAS PERPENDICULAR TO THE RWY I TOOK ANOTHER LOOK AND SAW A B737 ON THE RWY APCHING US RAPIDLY AND HE APPEARED TO BE USING MAX BRAKES. I TOLD THE CAPT THAT THERE WAS AN ACFT APCHING AND TO MOVE IT. HE COMPLIED IMMEDIATELY BY ADDING FULL THRUST TO THE ENG. WE CLRED WITH MAYBE 400 FT TO SPARE. I ALSO NOTICED THERE WAS INDEED A DASH 8 ON A 1 MI FINAL; I THINK THE GND CTLR MUST HAVE LOST TRACK OF THE B737; POSSIBLY BECAUSE OF THE FIRE SITUATION. POSSIBLE WAYS TO AVOID THIS INCURRENCE ARE AS FOLLOWS: 1) WE SHOULD HAVE NEVER BEEN ISSUED THE XING. 2) CTLR WAS DISTR AND SHOULD HAVE SLOWED DOWN INSTEAD OF TRYING TO RUSH US ACROSS. 3) TXWY F OR ANY OTHER REVERSE HIGH SPD SHOULD NOT BE UTILIZED FOR XING AS IT IS VERY DIFFICULT FOR THE FLT CREW TO SEE DOWN THE RWY. 4) RWY XINGS SHOULD BE MADE WITH THE TWR CTLR AS HE OR SHE KNOWS FIRST HAND THE STATUS OF THEIR RWY.

Data retrieved from NASA's ASRS site as of January 2009 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.