Narrative:

Air carrier X taxiing for takeoff runway 8R was requested and assigned and then changed to runway 4. Our clearance was to taxi into position and hold runway 4 via the ramp and taxiway B. We notified tower that we had not received our final numbers and was advised to hold on the runway and call ready. We instead held on the beginning portion of taxiway B approximately 1000 ft from runway 4, but on runway 4's centerline. When we called ready, we were advised to hold short for traffic landing runway 22. We advised tower that we were on taxiway B which tower advised as being 'ok.' a B-737 land on runway 22 and exited at taxiway H and complained our presence. Upon the complaint, we re- established our clearance as to hold on B and the tower then notified us that we were not visible from the tower. We later noticed taxiway B designated as a stopway, unlike taxiway east, which I had examined after our initial clearance to runway 8R. So, why am I writing this? We strictly adhered to our clrncs and clarified our position when the hold short was given after 'into position and hold' was given. Clearly, any taxiway which could be used as a stopway, whether designated as such or not, should be protected. In my opinion, the B-737's complaint was warranted. It would also be nice if a note could be added on the airport depiction page which referenced areas not visible from the tower. Callback conversation with reporter revealed the following information: facility quats stated they could not have an aircraft holding on taxiway B and land or depart on runway 22. He stated he would brief with facility personnel. He also stated taxiway B is no longer designated as a stopway. NOAA charts have been updated. Other charts have not.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR Y LANDED ON OCCUPIED RWY HAD LTSS FROM ACR X HOLDING ON END TXWY. SYS ERROR.

Narrative: ACR X TAXIING FOR TKOF RWY 8R WAS REQUESTED AND ASSIGNED AND THEN CHANGED TO RWY 4. OUR CLRNC WAS TO TAXI INTO POS AND HOLD RWY 4 VIA THE RAMP AND TXWY B. WE NOTIFIED TWR THAT WE HAD NOT RECEIVED OUR FINAL NUMBERS AND WAS ADVISED TO HOLD ON THE RWY AND CALL READY. WE INSTEAD HELD ON THE BEGINNING PORTION OF TXWY B APPROX 1000 FT FROM RWY 4, BUT ON RWY 4'S CTRLINE. WHEN WE CALLED READY, WE WERE ADVISED TO HOLD SHORT FOR TFC LNDG RWY 22. WE ADVISED TWR THAT WE WERE ON TXWY B WHICH TWR ADVISED AS BEING 'OK.' A B-737 LAND ON RWY 22 AND EXITED AT TXWY H AND COMPLAINED OUR PRESENCE. UPON THE COMPLAINT, WE RE- ESTABLISHED OUR CLRNC AS TO HOLD ON B AND THE TWR THEN NOTIFIED US THAT WE WERE NOT VISIBLE FROM THE TWR. WE LATER NOTICED TXWY B DESIGNATED AS A STOPWAY, UNLIKE TXWY E, WHICH I HAD EXAMINED AFTER OUR INITIAL CLRNC TO RWY 8R. SO, WHY AM I WRITING THIS? WE STRICTLY ADHERED TO OUR CLRNCS AND CLARIFIED OUR POS WHEN THE HOLD SHORT WAS GIVEN AFTER 'INTO POS AND HOLD' WAS GIVEN. CLRLY, ANY TXWY WHICH COULD BE USED AS A STOPWAY, WHETHER DESIGNATED AS SUCH OR NOT, SHOULD BE PROTECTED. IN MY OPINION, THE B-737'S COMPLAINT WAS WARRANTED. IT WOULD ALSO BE NICE IF A NOTE COULD BE ADDED ON THE ARPT DEPICTION PAGE WHICH REFED AREAS NOT VISIBLE FROM THE TWR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: FACILITY QUATS STATED THEY COULD NOT HAVE AN ACFT HOLDING ON TXWY B AND LAND OR DEPART ON RWY 22. HE STATED HE WOULD BRIEF WITH FACILITY PERSONNEL. HE ALSO STATED TXWY B IS NO LONGER DESIGNATED AS A STOPWAY. NOAA CHARTS HAVE BEEN UPDATED. OTHER CHARTS HAVE NOT.

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.