Narrative:

On jan/mon/01, I was the captain on flight X from sea to stl. During taxi out to runway 16L, it became obvious that the local control and ground control position were combined. Holding short of runway 16L we advised the control tower that we were ready for takeoff. ATC cleared flight X into position and hold runway 16L for traffic 1 mi final landing runway 16R. After the aircraft landed on runway 16R, ATC cleared flight X for takeoff on runway 16L. During the takeoff roll, there was conversation on the tower frequency between ATC and some aircraft or tugs on the ground frequency and between ATC and the flight Y that had landed on runway 16R. My first officer and I heard ATC issue hold short instructions to flight Y, but neither of us caught the readback of the Y flight as we had commenced our takeoff roll and were in the process of making procedural checks and callouts. Just after rotation and gear up, flight Y transmitted to ATC that an aircraft had just taken off over the top of them. ATC then told flight Y that he had issued instructions for them to turn left and hold short of runway 16L. Flight Y replied that he was cleared to cross runway 16L to the ramp. Next, ATC instructed us to contact departure control. My first officer and I did not see flight Y on the runway due to low visibility at the time. I believe it was around 1200 ft RVR. We proceeded to stl. Contributing factors: 1) combined ground control and local tower position leading to controller focusing on problem on ground control and not hearing flight Y's non complying readback to hold short of runway 16L. 2) crew not hearing correctly instructions to hold short of runway 16L. 3) low visibility. 4) my failure to recognize these contributing factors and the potential for a disaster by not being aware of flight Y's readback. But then, I would have to question if an aborted takeoff would have stopped my aircraft prior to flight Y aircraft crossing at taxiway north.

Google
 

Original NASA ASRS Text

Title: MD83 WENT OVER THE TOP OF ANOTHER ACFT THAT WAS JUST XING THEIR RWY DURING TAXI AFTER LNDG ON THE PARALLEL RWY.

Narrative: ON JAN/MON/01, I WAS THE CAPT ON FLT X FROM SEA TO STL. DURING TAXI OUT TO RWY 16L, IT BECAME OBVIOUS THAT THE LCL CTL AND GND CTL POS WERE COMBINED. HOLDING SHORT OF RWY 16L WE ADVISED THE CTL TWR THAT WE WERE READY FOR TKOF. ATC CLRED FLT X INTO POS AND HOLD RWY 16L FOR TFC 1 MI FINAL LNDG RWY 16R. AFTER THE ACFT LANDED ON RWY 16R, ATC CLRED FLT X FOR TKOF ON RWY 16L. DURING THE TKOF ROLL, THERE WAS CONVERSATION ON THE TWR FREQ BTWN ATC AND SOME ACFT OR TUGS ON THE GND FREQ AND BTWN ATC AND THE FLT Y THAT HAD LANDED ON RWY 16R. MY FO AND I HEARD ATC ISSUE HOLD SHORT INSTRUCTIONS TO FLT Y, BUT NEITHER OF US CAUGHT THE READBACK OF THE Y FLT AS WE HAD COMMENCED OUR TKOF ROLL AND WERE IN THE PROCESS OF MAKING PROCEDURAL CHKS AND CALLOUTS. JUST AFTER ROTATION AND GEAR UP, FLT Y XMITTED TO ATC THAT AN ACFT HAD JUST TAKEN OFF OVER THE TOP OF THEM. ATC THEN TOLD FLT Y THAT HE HAD ISSUED INSTRUCTIONS FOR THEM TO TURN L AND HOLD SHORT OF RWY 16L. FLT Y REPLIED THAT HE WAS CLRED TO CROSS RWY 16L TO THE RAMP. NEXT, ATC INSTRUCTED US TO CONTACT DEP CTL. MY FO AND I DID NOT SEE FLT Y ON THE RWY DUE TO LOW VISIBILITY AT THE TIME. I BELIEVE IT WAS AROUND 1200 FT RVR. WE PROCEEDED TO STL. CONTRIBUTING FACTORS: 1) COMBINED GND CTL AND LCL TWR POS LEADING TO CTLR FOCUSING ON PROB ON GND CTL AND NOT HEARING FLT Y'S NON COMPLYING READBACK TO HOLD SHORT OF RWY 16L. 2) CREW NOT HEARING CORRECTLY INSTRUCTIONS TO HOLD SHORT OF RWY 16L. 3) LOW VISIBILITY. 4) MY FAILURE TO RECOGNIZE THESE CONTRIBUTING FACTORS AND THE POTENTIAL FOR A DISASTER BY NOT BEING AWARE OF FLT Y'S READBACK. BUT THEN, I WOULD HAVE TO QUESTION IF AN ABORTED TKOF WOULD HAVE STOPPED MY ACFT PRIOR TO FLT Y ACFT XING AT TXWY N.

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.