Turbojet pilot reported executing a go-around on the szt runway 02 final because a crane protruded i...

Attributes
ACN	1474439
Time
Date	201707
Local Time Of Day	1201-1800
Place
Locale Reference	SZT.Airport
State Reference	ID
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach Direct
Flight Plan	IFR
Person 1
Function	Pilot Flying Single Pilot
Qualification	Flight Crew Rotorcraft Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 35 Flight Crew Total 11000 Flight Crew Type 2000
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

Flying into szt saw NOTAM and ASOS saying a crane was off the north end of runway 02 and 90 ft off centerline. Didn't pay too much attention; but on final; flying the PAPI lights; I had to go-around the top of the crane; which protruded some 60 ft into the PAPI glidepath. I took a photo looking north on runway 02 and the crane was dead center in the runway centerline. The solution was to turn off the PAPI lights so it did not guide aircraft into the crane; which moved east and west during the day; but often within the runway width and extending into the PAPI glidepath. Seems that simple solution would have been to find some other way to do work on a bridge north of szt; but FAA decided ok; which baffles me from a safety standpoint. Call 208-263-3074 and listen to the current ASOS; which is better; but what if a transient pilot doesn't listen; or pay attention. Same risk on takeoff with low-performance aircraft hitting the crane.

Original NASA ASRS Text

Title: Turbojet pilot reported executing a go-around on the SZT Runway 02 final because a crane protruded into the runway's visual descent path. The crane is mobile and NOTAMed; but a danger to transient pilots and others.

Narrative: Flying into SZT saw NOTAM and ASOS saying a crane was off the north end of RWY 02 and 90 ft off centerline. Didn't pay too much attention; but on final; flying the PAPI lights; I had to go-around the top of the crane; which protruded some 60 ft into the PAPI glidepath. I took a photo looking north on RWY 02 and the crane was dead center in the runway centerline. The solution was to turn off the PAPI lights so it did not guide aircraft into the crane; which moved east and west during the day; but often within the runway width and extending into the PAPI glidepath. Seems that simple solution would have been to find some other way to do work on a bridge north of SZT; but FAA decided OK; which baffles me from a safety standpoint. Call 208-263-3074 and listen to the current ASOS; which is better; but what if a transient pilot doesn't listen; or pay attention. Same risk on takeoff with low-performance aircraft hitting the crane.

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.

Turbojet pilot reported executing a go-around on the szt runway 02 final because a crane protruded into the runway's visual descent path. The crane is mobile and notamed; but a danger to transient pilots and others.