Flight executed go around because of traffic on landing runway and too close to airport to change to...

Attributes
ACN	113698
Time
Date	198906
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dtw
State Reference	MI
Altitude	msl bound lower : 850 msl bound upper : 850
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : dtw tower : 214
Operator	common carrier : air taxi
Make Model Name	Small Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent : approach landing : go around other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : takeoff ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : cfi pilot : atp pilot : commercial
Experience	flight time last 90 days : 80 flight time total : 5500 flight time type : 800
ASRS Report	113698
Person 2
Affiliation	company : air taxi
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance none taken : unable other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Detroit approach cleared us for ILS 3R approach at dtw. When crossing the outer marker for 3R, we contacted the tower and he cleared us to land 3C. When 1/4 mi away from end of 3C an air carrier airliner was taxiing onto 3C. We told the tower and he told us to land 3R. We told him we were 1/4 mi final and he told us to remain closed traffic for 3R and if we could maintain VFR. We said we could, and downwind cleared us to land 3C. I believe the problem arose when the tower cleared us to land on 3C at the outer marker. Because our company is based on the field and they know we prefer the center runways if the tower can accommodate us. It was busy at the time because of thunderstorms in the area with delays etc. I don't believe the tower saw us even though we had our landing and recognizer lights on. The air carrier airliner taxied onto the active runway without looking on final approach or he would have queried the tower. We didn't hear the tower clear the air carrier onto 3C or we could have caught the mistake also.

Original NASA ASRS Text

Title: FLT EXECUTED GO AROUND BECAUSE OF TRAFFIC ON LNDG RWY AND TOO CLOSE TO ARPT TO CHANGE TO ANOTHER RWY.

Narrative: DETROIT APCH CLRED US FOR ILS 3R APCH AT DTW. WHEN XING THE OUTER MARKER FOR 3R, WE CONTACTED THE TWR AND HE CLRED US TO LAND 3C. WHEN 1/4 MI AWAY FROM END OF 3C AN ACR AIRLINER WAS TAXIING ONTO 3C. WE TOLD THE TWR AND HE TOLD US TO LAND 3R. WE TOLD HIM WE WERE 1/4 MI FINAL AND HE TOLD US TO REMAIN CLOSED TFC FOR 3R AND IF WE COULD MAINTAIN VFR. WE SAID WE COULD, AND DOWNWIND CLRED US TO LAND 3C. I BELIEVE THE PROBLEM AROSE WHEN THE TWR CLRED US TO LAND ON 3C AT THE OUTER MARKER. BECAUSE OUR COMPANY IS BASED ON THE FIELD AND THEY KNOW WE PREFER THE CENTER RWYS IF THE TWR CAN ACCOMMODATE US. IT WAS BUSY AT THE TIME BECAUSE OF TSTMS IN THE AREA WITH DELAYS ETC. I DON'T BELIEVE THE TWR SAW US EVEN THOUGH WE HAD OUR LNDG AND RECOGNIZER LIGHTS ON. THE ACR AIRLINER TAXIED ONTO THE ACTIVE RWY WITHOUT LOOKING ON FINAL APCH OR HE WOULD HAVE QUERIED THE TWR. WE DIDN'T HEAR THE TWR CLEAR THE ACR ONTO 3C OR WE COULD HAVE CAUGHT THE MISTAKE ALSO.

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

Flight executed go around because of traffic on landing runway and too close to airport to change to another runway.