Narrative:

On final approach to ord runway 27L in visual conditions, tower cleared us to land behind another aircraft about 3.5 mi ahead of us. I was on course, glide path, and speed as I flew the ILS approach. We continued to monitor the other aircraft as it landed and exited the runway. At this point our attention was refocused to the approach. Then just prior to landing, tower instructed an aircraft to expedite his takeoff on runway 22L. I had just enough time to glance down, see the aircraft, and observe that he had started moving before we flew over the takeoff end of runway 22L. So, late in the landing phase, I chose to continue the approach, slow the descent rate slightly and land. The GPWS announced momentarily and then silenced as I returned to the glide path. The landing was in the normal touchdown zone without incident. There was no comment from the controller. I called the tower and discussed the situation with them and let them know that I was uncomfortable with the separation of our 2 aircraft. They seemed to be unaware of what had happened but would discuss it with the controller on duty to make sure he knew what his responsibilities were. I think all landing aircraft should be notified of aircraft either holding in position or cleared to take off if the takeoff zone of the runway is to be overflown while on final approach. That way, you'll have the time to monitor the movement of the other aircraft and have the time to make the decision to either go around or land. Supplemental information from acn 418995: cleared to land by ord tower at 2 NM from OM on runway 27L. On short final, tower cleared a B737 for takeoff on runway 22L. Aircraft did not move until we were approximately 1 NM final.

Related reports:

Google
 

Original NASA ASRS Text

Title: A LNDG MD88 ON A LESS THAN 1 MI SHORT FINAL TO RWY 27L ADJUSTS ITS FLT PATH TO PASS OVER A B737 ON THE TKOF ROLL ON RWY 22L. THE B737 HAD BEEN CLRED FOR AN IMMEDIATE TKOF WHEN THE MD88 WAS AT 3 MI BUT THE TKOF WAS DELAYED.

Narrative: ON FINAL APCH TO ORD RWY 27L IN VISUAL CONDITIONS, TWR CLRED US TO LAND BEHIND ANOTHER ACFT ABOUT 3.5 MI AHEAD OF US. I WAS ON COURSE, GLIDE PATH, AND SPD AS I FLEW THE ILS APCH. WE CONTINUED TO MONITOR THE OTHER ACFT AS IT LANDED AND EXITED THE RWY. AT THIS POINT OUR ATTN WAS REFOCUSED TO THE APCH. THEN JUST PRIOR TO LNDG, TWR INSTRUCTED AN ACFT TO EXPEDITE HIS TKOF ON RWY 22L. I HAD JUST ENOUGH TIME TO GLANCE DOWN, SEE THE ACFT, AND OBSERVE THAT HE HAD STARTED MOVING BEFORE WE FLEW OVER THE TKOF END OF RWY 22L. SO, LATE IN THE LNDG PHASE, I CHOSE TO CONTINUE THE APCH, SLOW THE DSCNT RATE SLIGHTLY AND LAND. THE GPWS ANNOUNCED MOMENTARILY AND THEN SILENCED AS I RETURNED TO THE GLIDE PATH. THE LNDG WAS IN THE NORMAL TOUCHDOWN ZONE WITHOUT INCIDENT. THERE WAS NO COMMENT FROM THE CTLR. I CALLED THE TWR AND DISCUSSED THE SIT WITH THEM AND LET THEM KNOW THAT I WAS UNCOMFORTABLE WITH THE SEPARATION OF OUR 2 ACFT. THEY SEEMED TO BE UNAWARE OF WHAT HAD HAPPENED BUT WOULD DISCUSS IT WITH THE CTLR ON DUTY TO MAKE SURE HE KNEW WHAT HIS RESPONSIBILITIES WERE. I THINK ALL LNDG ACFT SHOULD BE NOTIFIED OF ACFT EITHER HOLDING IN POS OR CLRED TO TAKE OFF IF THE TKOF ZONE OF THE RWY IS TO BE OVERFLOWN WHILE ON FINAL APCH. THAT WAY, YOU'LL HAVE THE TIME TO MONITOR THE MOVEMENT OF THE OTHER ACFT AND HAVE THE TIME TO MAKE THE DECISION TO EITHER GO AROUND OR LAND. SUPPLEMENTAL INFO FROM ACN 418995: CLRED TO LAND BY ORD TWR AT 2 NM FROM OM ON RWY 27L. ON SHORT FINAL, TWR CLRED A B737 FOR TKOF ON RWY 22L. ACFT DID NOT MOVE UNTIL WE WERE APPROX 1 NM FINAL.

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.