Narrative:

Upon checking on with jan approach; we were told to expect vectors for the visual approach runway 16L. Shortly after that; we were placed on a vector that would take us outside the final approach fix for the ILS 16L and traffic was called out to us as a 'aircraft Y on a 6 mile final'. We were still approximately 20 miles from the airport. About 10 miles from the airport we were told to proceed directly to the final approach fix on the ILS 16L. About 2 miles from this fix; the airport direction and distance was called out by ATC and we informed that we had it in sight. Subsequently they cleared us for the visual 16L and asked us to switch to tower frequency. We checked in with tower and were cleared to land runway 16L. As we approached the airport; fully configured and stabilized; I noticed that an aircraft was on the runway approximately 1500 ft down from the approach end. I immediately pointed this out to the captain/pilot flying and keyed the mike to query ATC about the aircraft. I said; 'is the runway clear?' he informed me it was not and to be prepared for a go around. Seconds after that and upon conferring with the captain; we executed a go around at approximately 400 ft AGL. As we passed over the runway on the go around the aircraft was still attempting to taxi off. We entered left traffic for runway 16L and landed uneventfully. Failure on the part of ATC to inform us of an aircraft still on the runway on initial check in. We had landing data for runway 16R and could have side stepped to that runway. Failure of the landing aircraft ahead to clear the runway in a reasonable amount of time. The pilot of that aircraft was confused and disoriented made apparent by his radio communications to tower.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot observes aircraft on runway when on short final. Pilot executes go-around and advises ATC reason for go-around. ATC did not advise pilot of landing traffic that aircraft was on the runway.

Narrative: Upon checking on with JAN approach; we were told to expect vectors for the visual approach runway 16L. Shortly after that; we were placed on a vector that would take us outside the final approach fix for the ILS 16L and traffic was called out to us as a 'Aircraft Y on a 6 mile final'. We were still approximately 20 miles from the airport. About 10 miles from the airport we were told to proceed directly to the final approach fix on the ILS 16L. About 2 miles from this fix; the airport direction and distance was called out by ATC and we informed that we had it in sight. Subsequently they cleared us for the visual 16L and asked us to switch to tower frequency. We checked in with tower and were cleared to land runway 16L. As we approached the airport; fully configured and stabilized; I noticed that an aircraft was on the runway approximately 1500 ft down from the approach end. I immediately pointed this out to the Captain/Pilot Flying and keyed the mike to query ATC about the aircraft. I said; 'Is the runway clear?' He informed me it was not and to be prepared for a go around. Seconds after that and upon conferring with the captain; we executed a go around at approximately 400 ft AGL. As we passed over the runway on the go around the aircraft was still attempting to taxi off. We entered left traffic for runway 16L and landed uneventfully. Failure on the part of ATC to inform us of an aircraft still on the runway on initial check in. We had landing data for runway 16R and could have side stepped to that runway. Failure of the landing aircraft ahead to clear the runway in a reasonable amount of time. The pilot of that aircraft was confused and disoriented made apparent by his radio communications to tower.

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