Narrative:

Instructed by tower to cross runway 30. Approaching runway 30 on taxiway Y, overheard transmission on tower frequency of aircraft going around. Initially saw no traffic on runway 30 or runway 12. Then saw aircraft approaching on runway 30. We stopped our aircraft on taxiway Y and the edge of runway 30 just as a DC6 passed in front of us on the go at 10-20 ft. Informed tower of the near miss and verified that we were cleared to cross runway 30. Discussion later revealed that tower thought we had already crossed runway 30, due in part to tower's visibility restr by blast deflector fence. Due to 360 degree heading on taxiway Y our visibility was restr for seeing the approach end of runway 30. Fogged rear side window also restr visibility.

Google
 

Original NASA ASRS Text

Title: MD80S ACFT WITH CLRNC TO CROSS RWY SAW ACFT ON FINAL APCH AND STOPPED, BUT OVER HOLD LINE. APCHING ACFT DID GAR. RPTR SAYS TWR VISIBILITY WAS RESTR BY BLAST FENCE.

Narrative: INSTRUCTED BY TWR TO CROSS RWY 30. APCHING RWY 30 ON TXWY Y, OVERHEARD XMISSION ON TWR FREQ OF ACFT GOING AROUND. INITIALLY SAW NO TFC ON RWY 30 OR RWY 12. THEN SAW ACFT APCHING ON RWY 30. WE STOPPED OUR ACFT ON TXWY Y AND THE EDGE OF RWY 30 JUST AS A DC6 PASSED IN FRONT OF US ON THE GO AT 10-20 FT. INFORMED TWR OF THE NEAR MISS AND VERIFIED THAT WE WERE CLRED TO CROSS RWY 30. DISCUSSION LATER REVEALED THAT TWR THOUGHT WE HAD ALREADY CROSSED RWY 30, DUE IN PART TO TWR'S VISIBILITY RESTR BY BLAST DEFLECTOR FENCE. DUE TO 360 DEG HDG ON TXWY Y OUR VISIBILITY WAS RESTR FOR SEEING THE APCH END OF RWY 30. FOGGED REAR SIDE WINDOW ALSO RESTR VISIBILITY.

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.