Narrative:

At about 200' on final approach to runway 4R at ord, we heard the tower instruct, 'go around.' it wasn't our flight #, though. We were anticipating and starting a go around at that point anyway because the aircraft ahead of us was still on the runway. We advised, 'XXX going around,' after the other aircraft xyz responded to the tower that he was going around. (Last month the ord tower mistakenly told the aircraft behind us, at the OM, to go around under these same conditions. I assumed the same thing was happening again.) next we heard another aircraft complain that he had traffic right in front of him. We then saw that it was the aircraft from runway 9R, who was also going around for traffic still on runway, climbing right at us. I told him we'd stay low, and flew down our runway at about 250' until he passed over us and was well clear. A double go around on these intersecting runways is always going to cause this situation. This was our second go around. On the first approach we couldn't get down from our last assigned altitude and abandoned the approach at about 1500'. I think a runway change started the sequencing problems. Another problem though was the tower instructions to all of us on runway 4R to 'roll to the end of the runway and expedite.' not a smart thing to do at night, so most of us probably spent more time on the runway than an earlier turnoff would have required.

Google
 

Original NASA ASRS Text

Title: ATCT LCL CTLR SENT AN ACFT AROUND LNDG ON RWY 9R BECAUSE OF TRAFFIC ON RWY. AT THE SAME TIME, AN ACFT LNDG ON RWY 4R DECIDED TO GO AROUND BECAUSE OF TRAFFIC STILL ON RWY. THE FLT PATHS OF THE 2 ACFT CROSSED WITH 1000' OF SEPARATION.

Narrative: AT ABOUT 200' ON FINAL APCH TO RWY 4R AT ORD, WE HEARD THE TWR INSTRUCT, 'GO AROUND.' IT WASN'T OUR FLT #, THOUGH. WE WERE ANTICIPATING AND STARTING A GAR AT THAT POINT ANYWAY BECAUSE THE ACFT AHEAD OF US WAS STILL ON THE RWY. WE ADVISED, 'XXX GOING AROUND,' AFTER THE OTHER ACFT XYZ RESPONDED TO THE TWR THAT HE WAS GOING AROUND. (LAST MONTH THE ORD TWR MISTAKENLY TOLD THE ACFT BEHIND US, AT THE OM, TO GO AROUND UNDER THESE SAME CONDITIONS. I ASSUMED THE SAME THING WAS HAPPENING AGAIN.) NEXT WE HEARD ANOTHER ACFT COMPLAIN THAT HE HAD TFC RIGHT IN FRONT OF HIM. WE THEN SAW THAT IT WAS THE ACFT FROM RWY 9R, WHO WAS ALSO GOING AROUND FOR TFC STILL ON RWY, CLBING RIGHT AT US. I TOLD HIM WE'D STAY LOW, AND FLEW DOWN OUR RWY AT ABOUT 250' UNTIL HE PASSED OVER US AND WAS WELL CLR. A DOUBLE GAR ON THESE INTERSECTING RWYS IS ALWAYS GOING TO CAUSE THIS SITUATION. THIS WAS OUR SECOND GAR. ON THE FIRST APCH WE COULDN'T GET DOWN FROM OUR LAST ASSIGNED ALT AND ABANDONED THE APCH AT ABOUT 1500'. I THINK A RWY CHANGE STARTED THE SEQUENCING PROBS. ANOTHER PROB THOUGH WAS THE TWR INSTRUCTIONS TO ALL OF US ON RWY 4R TO 'ROLL TO THE END OF THE RWY AND EXPEDITE.' NOT A SMART THING TO DO AT NIGHT, SO MOST OF US PROBABLY SPENT MORE TIME ON THE RWY THAN AN EARLIER TURNOFF WOULD HAVE REQUIRED.

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.