Narrative:

I was instructed to hold short of runway 28R for landing traffic. I was the only aircraft at the approach end of runway 28R. We heard instructions to taxi into position and hold on runway 28R. As we entered the runway, we saw another aircraft entering the runway (28R) from the opposite that we entered. The other aircraft entered the runway from an intersection about a half mile down the runway and took off. Aircraft Y was on final and asked for confirmation of landing clearance. I spoke up and announced that we were holding as instructed or runway 28R. Tower ordered aircraft Y to go around. I was given clearance to take off and proceed on course. Callback conversation with reporter revealed the following information: reporter stated that the tower never corrected their readback.

Google
 

Original NASA ASRS Text

Title: SA226 MISTAKENLY TAXIES ON TO RWY 28R AT BOI, RESULTING IN ARRIVING F28 TFC EXECUTING A GAR.

Narrative: I WAS INSTRUCTED TO HOLD SHORT OF RWY 28R FOR LNDG TFC. I WAS THE ONLY ACFT AT THE APCH END OF RWY 28R. WE HEARD INSTRUCTIONS TO TAXI INTO POS AND HOLD ON RWY 28R. AS WE ENTERED THE RWY, WE SAW ANOTHER ACFT ENTERING THE RWY (28R) FROM THE OPPOSITE THAT WE ENTERED. THE OTHER ACFT ENTERED THE RWY FROM AN INTERSECTION ABOUT A HALF MILE DOWN THE RWY AND TOOK OFF. ACFT Y WAS ON FINAL AND ASKED FOR CONFIRMATION OF LNDG CLRNC. I SPOKE UP AND ANNOUNCED THAT WE WERE HOLDING AS INSTRUCTED OR RWY 28R. TWR ORDERED ACFT Y TO GAR. I WAS GIVEN CLRNC TO TAKE OFF AND PROCEED ON COURSE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE TWR NEVER CORRECTED THEIR READBACK.

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.