Narrative:

After I landed on runway 27 at boston, we were not given any instructions by the tower to turn off the runway, so the captain slowed to taxi speed and continued to taxi on runway 27 since our ramp is located adjacent to the end of runway 27. As we approached the area where the overrun of runway 27 intersects the overrun of runway 22R the tower instructed us to 'stop,' which we did. We remained holding short of the overrun of runway 22R until the aircraft on that runway turned off. We were then cleared across the runway 22R overrun and changed to ground control. The ground controller told us to call the tower after we could get to the phone (land line). The only reference to the use of these runway overrun areas is on 10-9 airport diagram in small letters stating that it is not available for rollout after landing. We did not see this note. We were not in rollout but were simply taxiing on this area. If no taxi is allowed in this area it should be stated clearly on both the airport diagram and on the approach plate. Also, if there was a potential for traffic conflict in this area, the tower controller should advise us and instruct us to clear the runway prior to reaching this area. Supplemental information from acn 394150: prior to this point, I was not asked to hold short of any intersection or turn off at any taxiway before the end of the runway. Supplemental information from acn 394144: during takeoff roll on runway 22R at a speed of 95 KTS, bos tower informed us of a cargo B727 landing on runway 27 that was going to cross the end of runway 22R. We aborted our takeoff at 105 KTS, because we felt we would be too close to the B727. The abort was normal and we reconfigured for another takeoff.

Google
 

Original NASA ASRS Text

Title: A POTENTIAL CONFLICT OCCURRED AS A LNDG B727 ROLLED OUT ONTO THE RWY 27 OVERRUN AS AN MD80 WAS ON THE TKOF ROLL ON RWY 22R. BOTH TWR CTLRS INTERVENED, RWY 27 CTLR STOPPED THE B727, RWY 22R CTLR ADVISING MD80 OF POTENTIAL XING TFC. CTLRS WERE ON SEPARATE FREQS.

Narrative: AFTER I LANDED ON RWY 27 AT BOSTON, WE WERE NOT GIVEN ANY INSTRUCTIONS BY THE TWR TO TURN OFF THE RWY, SO THE CAPT SLOWED TO TAXI SPD AND CONTINUED TO TAXI ON RWY 27 SINCE OUR RAMP IS LOCATED ADJACENT TO THE END OF RWY 27. AS WE APCHED THE AREA WHERE THE OVERRUN OF RWY 27 INTERSECTS THE OVERRUN OF RWY 22R THE TWR INSTRUCTED US TO 'STOP,' WHICH WE DID. WE REMAINED HOLDING SHORT OF THE OVERRUN OF RWY 22R UNTIL THE ACFT ON THAT RWY TURNED OFF. WE WERE THEN CLRED ACROSS THE RWY 22R OVERRUN AND CHANGED TO GND CTL. THE GND CTLR TOLD US TO CALL THE TWR AFTER WE COULD GET TO THE PHONE (LAND LINE). THE ONLY REF TO THE USE OF THESE RWY OVERRUN AREAS IS ON 10-9 ARPT DIAGRAM IN SMALL LETTERS STATING THAT IT IS NOT AVAILABLE FOR ROLLOUT AFTER LNDG. WE DID NOT SEE THIS NOTE. WE WERE NOT IN ROLLOUT BUT WERE SIMPLY TAXIING ON THIS AREA. IF NO TAXI IS ALLOWED IN THIS AREA IT SHOULD BE STATED CLRLY ON BOTH THE ARPT DIAGRAM AND ON THE APCH PLATE. ALSO, IF THERE WAS A POTENTIAL FOR TFC CONFLICT IN THIS AREA, THE TWR CTLR SHOULD ADVISE US AND INSTRUCT US TO CLR THE RWY PRIOR TO REACHING THIS AREA. SUPPLEMENTAL INFO FROM ACN 394150: PRIOR TO THIS POINT, I WAS NOT ASKED TO HOLD SHORT OF ANY INTXN OR TURN OFF AT ANY TXWY BEFORE THE END OF THE RWY. SUPPLEMENTAL INFO FROM ACN 394144: DURING TKOF ROLL ON RWY 22R AT A SPD OF 95 KTS, BOS TWR INFORMED US OF A CARGO B727 LNDG ON RWY 27 THAT WAS GOING TO CROSS THE END OF RWY 22R. WE ABORTED OUR TKOF AT 105 KTS, BECAUSE WE FELT WE WOULD BE TOO CLOSE TO THE B727. THE ABORT WAS NORMAL AND WE RECONFIGURED FOR ANOTHER TKOF.

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.