Small transport pilot told to turn right on taxi and taxies beyond hold line for runway.

Attributes
ACN	312700
Time
Date	199508
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : slc
State Reference	UT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : stl
Operator	general aviation : personal
Make Model Name	Cessna 310/T310C
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 1150 flight time type : 600
ASRS Report	312700
Person 2
Affiliation	government : faa
Function	controller : ground
Qualification	controller : non radar
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : became reoriented other other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing to FBO from runway 17 at slc on taxiway K, the ground controller told me I was taxiing into the air guard parking and to veer to the right. I turned right, then I realized that I was taxiing along a long high speed exit to runway 35 and I had just inadvertently crossed the hold bars. I immediately braked, called ground and turned around to exit the runway. Ground controller then told me in a very rude tone that I had taxied onto the runway and then told me to turn around (which I was doing) and to make the first right turn and to continue on taxiway K. The problem was that I was not going toward the guard ramp in the first place and the right turn he had me do, brought me back onto the runway. I believe the numerous construction going on at the ramp increased the controllers workload which caused a judgement error. At the FBO, I was told to call the tower and I told the controller my side of the story. Callback conversation with reporter revealed the following information: reporter states he was flying a C310. Another aircraft had taxied into the air guard area earlier that same day, and the controller was super cautious about that situation. Reporter indicated the controller was quite uptight with him initially until he told him his side of the story and indicated he was on the taxiway, not going into the air guard area. Controller then calmed down. No action was taken. Pilot did not have the airport diagram out for his use.

Original NASA ASRS Text

Title: SMT PLT TOLD TO TURN R ON TAXI AND TAXIES BEYOND HOLD LINE FOR RWY.

Narrative: WHILE TAXIING TO FBO FROM RWY 17 AT SLC ON TXWY K, THE GND CTLR TOLD ME I WAS TAXIING INTO THE AIR GUARD PARKING AND TO VEER TO THE R. I TURNED R, THEN I REALIZED THAT I WAS TAXIING ALONG A LONG HIGH SPD EXIT TO RWY 35 AND I HAD JUST INADVERTENTLY CROSSED THE HOLD BARS. I IMMEDIATELY BRAKED, CALLED GND AND TURNED AROUND TO EXIT THE RWY. GND CTLR THEN TOLD ME IN A VERY RUDE TONE THAT I HAD TAXIED ONTO THE RWY AND THEN TOLD ME TO TURN AROUND (WHICH I WAS DOING) AND TO MAKE THE FIRST R TURN AND TO CONTINUE ON TXWY K. THE PROB WAS THAT I WAS NOT GOING TOWARD THE GUARD RAMP IN THE FIRST PLACE AND THE R TURN HE HAD ME DO, BROUGHT ME BACK ONTO THE RWY. I BELIEVE THE NUMEROUS CONSTRUCTION GOING ON AT THE RAMP INCREASED THE CTLRS WORKLOAD WHICH CAUSED A JUDGEMENT ERROR. AT THE FBO, I WAS TOLD TO CALL THE TWR AND I TOLD THE CTLR MY SIDE OF THE STORY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES HE WAS FLYING A C310. ANOTHER ACFT HAD TAXIED INTO THE AIR GUARD AREA EARLIER THAT SAME DAY, AND THE CTLR WAS SUPER CAUTIOUS ABOUT THAT SIT. RPTR INDICATED THE CTLR WAS QUITE UPTIGHT WITH HIM INITIALLY UNTIL HE TOLD HIM HIS SIDE OF THE STORY AND INDICATED HE WAS ON THE TXWY, NOT GOING INTO THE AIR GUARD AREA. CTLR THEN CALMED DOWN. NO ACTION WAS TAKEN. PLT DID NOT HAVE THE ARPT DIAGRAM OUT FOR HIS USE.

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.