Narrative:

I was on final vector to runway 28 at ord. I had reviewed NOTAMS for the runway. I or the first officer did not see the NOTAM that reported the first 3700 ft of runway 28 was closed and the ATIS I pulled up from the airport did not state the first 3700 ft of runway 28 was closed. The controller informed me that the localizer will be temporary out of service. I was then given instructions to follow a 737 on final and to call the field in sight. I reported the field but could not make out the 737. On final we were behind a 737 so I called the aircraft in sight. We were told his speed was 170 KTS. I visually followed him down to his landing; noticing that his aircraft blocked the view of the landing area in my windshield. At 500 ft; the first officer called out our speed; sink 700 -- PAPI good. After the 737 landing; he and the tower were talking about which exit to take. I was getting closer to the runway; however; I keep my eyes on him watching to see that he exited the runway. I then shifted my eyesight down the runway for landing. At 150 ft the first officer stated 'go-around/barriers.' in my mind I processed the call out he made then began the go-around procedure that resulted in the main tires touching down in the over run area. We returned to the field; landing on runway 27L. No damage resulted to the aircraft or property. I have learned that a very close attention to the landing area is required even in VFR weather. I also fully understand that a closer review of all NOTAMS and airport pages is paramount. Undated information like this should be placed on ever ATIS broadcast or report for backup safety information.

Related reports:

Google
 

Original NASA ASRS Text

Title: An air carrier executed a go-around on the ORD Runway 28 short final after realizing the first 3;700 FT of the runway were closed. During the go-around the aircraft's main gear touched down in the closed portion of the runway.

Narrative: I was on final vector to Runway 28 at ORD. I had reviewed NOTAMS for the runway. I or the First Officer did not see the NOTAM that reported the first 3700 FT of Runway 28 was closed and the ATIS I pulled up from the airport did not state the first 3700 FT of Runway 28 was closed. The Controller informed me that the localizer will be temporary out of service. I was then given instructions to follow a 737 on final and to call the field in sight. I reported the field but could not make out the 737. On final we were behind a 737 so I called the aircraft in sight. We were told his speed was 170 KTS. I visually followed him down to his landing; noticing that his aircraft blocked the view of the landing area in my windshield. At 500 FT; the First Officer called out our speed; sink 700 -- PAPI good. After the 737 landing; he and the Tower were talking about which exit to take. I was getting closer to the runway; however; I keep my eyes on him watching to see that he exited the runway. I then shifted my eyesight down the runway for landing. At 150 FT the First Officer stated 'go-around/barriers.' In my mind I processed the call out he made then began the go-around procedure that resulted in the main tires touching down in the over run area. We returned to the field; landing on Runway 27L. No damage resulted to the aircraft or property. I have learned that a very close attention to the landing area is required even in VFR weather. I also fully understand that a closer review of all NOTAMS and airport pages is paramount. Undated information like this should be placed on ever ATIS broadcast or report for backup safety information.

Data retrieved from NASA's ASRS site as of April 2012 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.