Narrative:

We were vectored for a CAT ii approach and landing on runway 14R. The reported RVR was fluctuating between 1400 ft and 2000 ft. We conducted a CAT ii monitored approach per SOP after a thorough briefing. The first officer flew the approach. At approximately 150- 200 ft RA, some discussion ensued on the tower frequency between an airport vehicle and the ord tower. The vehicle first reported to be short of runway 14L and then changed his mind and claimed short of runway 14R and was witnessing debris on the runway. There was a query by ord tower as to if he (the vehicle) was clear of the runway. After the vehicle answered in the affirmative, the tower acknowledged the debris report and issued us a clearance to go around. By this point, I already had the runway environment in sight, had displaced the first officer from the controls per the monitored approach SOP, had determined the requirements of far 121.651(C) had been met and had announced 'runway in sight, landing.' my impression was that this was the first time that the tower was advised of any FOD or abnormal situation taking place on runway 14R. Our go around was initiated in the landing flare at approximately AB58Z. Due to the go around being initiated at such a low altitude, incidental main gear contact with the runway resulted. A normal published missed approach procedure followed. During the missed approach, the passenger on the right side of the aircraft were able to look down through the obscuration and witness a B727 that had diverted off runway 14R on landing and had come to rest on its belly about 1500 ft off the side of the runway. Question remains, why did an airplane land after that emergency and evacuate/evacuation and why did ord tower not know of such emergency 6 mins after it had occurred, allowing us to conduct an approach to the runway?

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MLG PERFORMS A GAR AT TWR'S REQUEST AFTER GOING VISUAL AT 100 FT AGL AFTER A MONITORED APCH TO ORD'S RWY 14R. ARPT VEHICLE HAD RPTED DEBRIS ON THAT RWY, PROBABLY FROM AN ACR B727 THAT HAD SLID 1500 FT OFF RWY 14R ABOUT 6 MINS PRIOR TO RPTR'S GAR. RPTR WANTS TO KNOW WHY ATC DIDN'T KNOW OF THIS SOONER SO AS TO PRECLUDE ANY ACFT, PARTICULARLY THEIRS, FROM MAKING AN APCH AND LNDG TO A DEBRIS CLUTTERED RWY.

Narrative: WE WERE VECTORED FOR A CAT II APCH AND LNDG ON RWY 14R. THE RPTED RVR WAS FLUCTUATING BTWN 1400 FT AND 2000 FT. WE CONDUCTED A CAT II MONITORED APCH PER SOP AFTER A THOROUGH BRIEFING. THE FO FLEW THE APCH. AT APPROX 150- 200 FT RA, SOME DISCUSSION ENSUED ON THE TWR FREQ BTWN AN ARPT VEHICLE AND THE ORD TWR. THE VEHICLE FIRST RPTED TO BE SHORT OF RWY 14L AND THEN CHANGED HIS MIND AND CLAIMED SHORT OF RWY 14R AND WAS WITNESSING DEBRIS ON THE RWY. THERE WAS A QUERY BY ORD TWR AS TO IF HE (THE VEHICLE) WAS CLR OF THE RWY. AFTER THE VEHICLE ANSWERED IN THE AFFIRMATIVE, THE TWR ACKNOWLEDGED THE DEBRIS RPT AND ISSUED US A CLRNC TO GAR. BY THIS POINT, I ALREADY HAD THE RWY ENVIRONMENT IN SIGHT, HAD DISPLACED THE FO FROM THE CTLS PER THE MONITORED APCH SOP, HAD DETERMINED THE REQUIREMENTS OF FAR 121.651(C) HAD BEEN MET AND HAD ANNOUNCED 'RWY IN SIGHT, LNDG.' MY IMPRESSION WAS THAT THIS WAS THE FIRST TIME THAT THE TWR WAS ADVISED OF ANY FOD OR ABNORMAL SIT TAKING PLACE ON RWY 14R. OUR GAR WAS INITIATED IN THE LNDG FLARE AT APPROX AB58Z. DUE TO THE GAR BEING INITIATED AT SUCH A LOW ALT, INCIDENTAL MAIN GEAR CONTACT WITH THE RWY RESULTED. A NORMAL PUBLISHED MISSED APCH PROC FOLLOWED. DURING THE MISSED APCH, THE PAX ON THE R SIDE OF THE ACFT WERE ABLE TO LOOK DOWN THROUGH THE OBSCURATION AND WITNESS A B727 THAT HAD DIVERTED OFF RWY 14R ON LNDG AND HAD COME TO REST ON ITS BELLY ABOUT 1500 FT OFF THE SIDE OF THE RWY. QUESTION REMAINS, WHY DID AN AIRPLANE LAND AFTER THAT EMER AND EVAC AND WHY DID ORD TWR NOT KNOW OF SUCH EMER 6 MINS AFTER IT HAD OCCURRED, ALLOWING US TO CONDUCT AN APCH TO THE RWY?

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.