Narrative:

I landed on runway 35 following a visual approach. Due to construction on taxiway K; the usual route to the FBO; I was instructed by the tower controller to taxi via Q; runway 32; and hold short of runway 35. I read back the instructions and proceeded to taxi. As I was approaching the end of runway 32; the tower controller verified that I was to hold short of runway 35; which I acknowledged. Upon reaching the end of [runway] 32; and crossing over the threshold line; I realized that there was no hold short line between me and the edge of runway 35. I stopped and queried the controller. At the same time a plane that was on short final for runway 35 was instructed to go-around. I was stopped on taxiway J; close to the edge of runway 35. In retrospect I did not notice the hold short markings placed before the runway 32 threshold markings. I was expecting to find those marking after exiting the runway and crossing the runway threshold; and was looking for them when I realized that I was already on taxiway J. This is my home airport and am aware that the area is a hot spot; but for departing on the wrong runway. I had never taxied back on runway 32. The construction on taxiway K and need for alternate taxi routes played a role in this incident. Regardless; I accidentally did not follow the ATC instruction to hold short of runway 35 and caused a runway incursion that required a go around of a landing aircraft.I spoke with the tower controller and discussed the situation. He acknowledged that the taxi instructions were non-standard; and in the future when faced with a similar situation he will route aircraft to taxi via taxiways instead of the runway; due to the proximity of the runway ends and confusion markings.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reported landing at home airport but due to construction and ATC clearance was confused causing a runway incursion and a go-around.

Narrative: I landed on Runway 35 following a visual approach. Due to construction on Taxiway K; the usual route to the FBO; I was instructed by the tower controller to taxi via Q; Runway 32; and hold short of Runway 35. I read back the instructions and proceeded to taxi. As I was approaching the end of Runway 32; the tower controller verified that I was to hold short of Runway 35; which I acknowledged. Upon reaching the end of [Runway] 32; and crossing over the threshold line; I realized that there was no hold short line between me and the edge of Runway 35. I stopped and queried the Controller. At the same time a plane that was on short final for Runway 35 was instructed to go-around. I was stopped on Taxiway J; close to the edge of Runway 35. In retrospect I did not notice the hold short markings placed before the Runway 32 threshold markings. I was expecting to find those marking after exiting the runway and crossing the runway threshold; and was looking for them when I realized that I was already on Taxiway J. This is my home airport and am aware that the area is a Hot Spot; but for departing on the wrong runway. I had never taxied back on Runway 32. The construction on Taxiway K and need for alternate taxi routes played a role in this incident. Regardless; I accidentally did not follow the ATC instruction to hold short of Runway 35 and caused a runway incursion that required a go around of a landing aircraft.I spoke with the Tower Controller and discussed the situation. He acknowledged that the taxi instructions were non-standard; and in the future when faced with a similar situation he will route aircraft to taxi via taxiways instead of the runway; due to the proximity of the runway ends and confusion markings.

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