Narrative:

Approximately 17 mi out from our destination of sny, northeast, ZDV cleared me to descend at pilot's discretion from 9000 ft to 6000 ft. We expected a visual approach. About 13 mi out of our destination, I began the descent to 6000 ft and at 12 mi I notified center I had the airport in sight and was canceling IFR. Center acknowledged. At 10 mi out and descending, I broadcast on sny CTAF my position and intentions to land at sny. At 5 mi out, I again broadcast my position and intention to land on runway 12. At 3 mi out, I made yet another broadcast of my position and intentions to land on runway 12 and began the approach to landing checklist (this included turning on the landing lights at this time, tail and wingtip strobes were already on). At 1 mi out, final checklist was completed. During final descent and less than 1/2 mi from the approach end of runway 12, a swearingen merlin iv metroliner pulled onto runway 12 and began to back-taxi. It wasn't until after the merlin pilot had completed the turn onto the active runway 12 and began the back-taxi that he announced his intentions and asked if there was any other traffic in the area, to please advise. While the merlin pilot was still broadcasting I had already aborted the landing and initiated go around procedures. I advised the merlin pilot of the fact I was on a short final for runway 12 and had to abort because of him. He initially accused me of failure to announce my position and intentions but after assuring him I had made at least 3 such announcements, he no longer took issue with me. It was very obvious to me that the merlin pilot had made 3 very serious errors: he did not take the time to look and see if anyone might have been landing, nor did he announce his intentions prior to puling out onto an active runway. He also failed to monitor his radio as to where other traffic might be in the area.

Google
 

Original NASA ASRS Text

Title: WHILE ON VFR APCH TO SNY SHORT FINAL (UNCTLED FIELD), A PA28 PLT IS FORCED TO GO AROUND WHEN AN SW4 ENTERED THE RWY AND BEGAN TO BACK TAXI, CAUSING A RWY INCURSION.

Narrative: APPROX 17 MI OUT FROM OUR DEST OF SNY, NE, ZDV CLRED ME TO DSND AT PLT'S DISCRETION FROM 9000 FT TO 6000 FT. WE EXPECTED A VISUAL APCH. ABOUT 13 MI OUT OF OUR DEST, I BEGAN THE DSCNT TO 6000 FT AND AT 12 MI I NOTIFIED CTR I HAD THE ARPT IN SIGHT AND WAS CANCELING IFR. CTR ACKNOWLEDGED. AT 10 MI OUT AND DSNDING, I BROADCAST ON SNY CTAF MY POS AND INTENTIONS TO LAND AT SNY. AT 5 MI OUT, I AGAIN BROADCAST MY POS AND INTENTION TO LAND ON RWY 12. AT 3 MI OUT, I MADE YET ANOTHER BROADCAST OF MY POS AND INTENTIONS TO LAND ON RWY 12 AND BEGAN THE APCH TO LNDG CHKLIST (THIS INCLUDED TURNING ON THE LNDG LIGHTS AT THIS TIME, TAIL AND WINGTIP STROBES WERE ALREADY ON). AT 1 MI OUT, FINAL CHKLIST WAS COMPLETED. DURING FINAL DSCNT AND LESS THAN 1/2 MI FROM THE APCH END OF RWY 12, A SWEARINGEN MERLIN IV METROLINER PULLED ONTO RWY 12 AND BEGAN TO BACK-TAXI. IT WASN'T UNTIL AFTER THE MERLIN PLT HAD COMPLETED THE TURN ONTO THE ACTIVE RWY 12 AND BEGAN THE BACK-TAXI THAT HE ANNOUNCED HIS INTENTIONS AND ASKED IF THERE WAS ANY OTHER TFC IN THE AREA, TO PLEASE ADVISE. WHILE THE MERLIN PLT WAS STILL BROADCASTING I HAD ALREADY ABORTED THE LNDG AND INITIATED GAR PROCS. I ADVISED THE MERLIN PLT OF THE FACT I WAS ON A SHORT FINAL FOR RWY 12 AND HAD TO ABORT BECAUSE OF HIM. HE INITIALLY ACCUSED ME OF FAILURE TO ANNOUNCE MY POS AND INTENTIONS BUT AFTER ASSURING HIM I HAD MADE AT LEAST 3 SUCH ANNOUNCEMENTS, HE NO LONGER TOOK ISSUE WITH ME. IT WAS VERY OBVIOUS TO ME THAT THE MERLIN PLT HAD MADE 3 VERY SERIOUS ERRORS: HE DID NOT TAKE THE TIME TO LOOK AND SEE IF ANYONE MIGHT HAVE BEEN LNDG, NOR DID HE ANNOUNCE HIS INTENTIONS PRIOR TO PULING OUT ONTO AN ACTIVE RWY. HE ALSO FAILED TO MONITOR HIS RADIO AS TO WHERE OTHER TFC MIGHT BE IN THE AREA.

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.