B737 initiated go around at mdpp after observing aircraft on assigned landing runway

Attributes
ACN	643124
Time
Date	200501
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mdpp.airport
State Reference	FO
Altitude	agl single value : 400
Environment
Flight Conditions	VMC
Weather Elements	Rain
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mdpp.tower
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : missed approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : mdpp.tower
Operator	general aviation : corporate
Make Model Name	Commercial Fixed Wing
Flight Phase	landing : roll
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 240 flight time total : 25000 flight time type : 7000
ASRS Report	643124
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	flight crew : executed go around flight crew : took evasive action
Miss Distance	vertical : 400
Supplementary
Problem Areas	Weather ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Mdpp tower acknowledged and advised to report left base. Turned close in left base due to rainshowers and reported left base and told to continue by tower. After descending on final; I thought I saw something on the approach end of runway 8. I asked my first officer if he saw an aircraft on the runway. He responded that he didn't see anything (at this point visibility was somewhat diminished due to rain on the wind screen). I started to level off and discontinue the descent. Asked tower if there was an aircraft on the runway. Tower responded yes. Initiated missed approach and due to the fuel state and the tower confusion; diverted to mdst. At no time were we advised of traffic on the runway at mdpp. Aircraft on runway appeared to be a small bizjet and he was surprised; as we were; by the event. Due to the size of the small jet and its position on the runway markings; it was very hard to see. At the time we executed the missed approach; we were only about 400 ft AGL. I feel lack of communication; use of nonstandard ATC procedures by tower; and language barrier contributed to this event.

Original NASA ASRS Text

Title: B737 INITIATED GAR AT MDPP AFTER OBSERVING ACFT ON ASSIGNED LNDG RWY

Narrative: MDPP TWR ACKNOWLEDGED AND ADVISED TO RPT L BASE. TURNED CLOSE IN L BASE DUE TO RAINSHOWERS AND RPTED L BASE AND TOLD TO CONTINUE BY TWR. AFTER DSNDING ON FINAL; I THOUGHT I SAW SOMETHING ON THE APCH END OF RWY 8. I ASKED MY FO IF HE SAW AN ACFT ON THE RWY. HE RESPONDED THAT HE DIDN'T SEE ANYTHING (AT THIS POINT VISIBILITY WAS SOMEWHAT DIMINISHED DUE TO RAIN ON THE WIND SCREEN). I STARTED TO LEVEL OFF AND DISCONTINUE THE DSCNT. ASKED TWR IF THERE WAS AN ACFT ON THE RWY. TWR RESPONDED YES. INITIATED MISSED APCH AND DUE TO THE FUEL STATE AND THE TWR CONFUSION; DIVERTED TO MDST. AT NO TIME WERE WE ADVISED OF TFC ON THE RWY AT MDPP. ACFT ON RWY APPEARED TO BE A SMALL BIZJET AND HE WAS SURPRISED; AS WE WERE; BY THE EVENT. DUE TO THE SIZE OF THE SMALL JET AND ITS POS ON THE RWY MARKINGS; IT WAS VERY HARD TO SEE. AT THE TIME WE EXECUTED THE MISSED APCH; WE WERE ONLY ABOUT 400 FT AGL. I FEEL LACK OF COM; USE OF NONSTANDARD ATC PROCS BY TWR; AND LANGUAGE BARRIER CONTRIBUTED TO THIS EVENT.

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