A be-30 pilot reported that a high performance single engine aircraft taxied on to boi runway 28L wi...

Narrative:

Conducting a visual approach to boise gowan field (kboi) at the end of an IFR leg. We were cleared to land on 28L following a regional jet on final for 28R with a caution for wake turbulence. We acknowledged and proceeded. I was captain and my partner was at the controls. On short final aircraft Y; that was holding short; taxied onto the runway at the departure end. Being focused on reviewing the landing checklist; I don't recall the tower issuing a clearance to the aircraft Y to enter the runway. My partner asked if tower had cleared the aircraft onto the runway and transmitted the question on tower frequency. Tower hesitated; then told us to execute a left 360. Being fully configured and close to the ground; I gave the command to go-around; add power and accelerate straight ahead; then I selected flaps approach and we began a climb. We extended upwind in order to clear the new tower under construction; then tower cleared us to turn left downwind. As we flew downwind; tower cleared aircraft Y for takeoff. We were then cleared to land; turned final and executed a normal landing. Everything normal after that; nothing said by tower or ground to us.because of the sequence of events and the fact that our approach had been a long straight-in; we believe tower had forgotten us and had cleared aircraft Y to enter the runway; then was momentarily surprised by us. The obvious thing is that had we not taken action; we may have hit the aircraft on the runway. Aircraft Y did not clear the approach area before entering the runway and tower did not give either of us any commands until we spoke up. While it wasn't razor close; it was much closer than ever should have occurred.a classic runway incursion. Vigilance is the only way to avoid these events. Complacency is the enemy.

Original NASA ASRS Text

Title: A BE-30 pilot reported that a high performance single engine aircraft taxied on to BOI Runway 28L without clearance. The crew queried the aircraft's runway position where upon ATC issue a go-around and cleared the incurring aircraft for takeoff.

Narrative: Conducting a visual approach to Boise Gowan Field (KBOI) at the end of an IFR leg. We were cleared to land on 28L following a regional jet on final for 28R with a caution for wake turbulence. We acknowledged and proceeded. I was Captain and my partner was at the controls. On short final Aircraft Y; that was holding short; taxied onto the runway at the departure end. Being focused on reviewing the landing checklist; I don't recall the Tower issuing a clearance to the Aircraft Y to enter the runway. My partner asked if Tower had cleared the aircraft onto the runway and transmitted the question on tower frequency. Tower hesitated; then told us to execute a left 360. Being fully configured and close to the ground; I gave the command to go-around; add power and accelerate straight ahead; then I selected flaps approach and we began a climb. We extended upwind in order to clear the new tower under construction; then Tower cleared us to turn left downwind. As we flew downwind; Tower cleared Aircraft Y for takeoff. We were then cleared to land; turned final and executed a normal landing. Everything normal after that; nothing said by Tower or Ground to us.Because of the sequence of events and the fact that our approach had been a long straight-in; we believe Tower had forgotten us and had cleared Aircraft Y to enter the runway; then was momentarily surprised by us. The obvious thing is that had we not taken action; we may have hit the aircraft on the runway. Aircraft Y did not clear the approach area before entering the runway and tower did not give either of us any commands until we spoke up. While it wasn't razor close; it was much closer than ever should have occurred.A classic runway incursion. Vigilance is the only way to avoid these events. Complacency is the enemy.

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

Attributes
ACN	840502
Time
Date	200906
Local Time Of Day	1201-1800
Place
Locale Reference	BOI.Airport
State Reference	ID
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Super King Air 300
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 140 Flight Crew Total 9600 Flight Crew Type 425
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Clearance Ground Incursion Runway
Miss Distance	Horizontal 2500 Vertical 500

A be-30 pilot reported that a high performance single engine aircraft taxied on to boi runway 28L without clearance. The crew queried the aircraft's runway position where upon ATC issue a go-around and cleared the incurring aircraft for takeoff.