After landing GA small aircraft turned onto an active runway without clearance.

Attributes
ACN	161768
Time
Date	199011
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : ues
State Reference	WI
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : fpr
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	ground other : taxi landing other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 50 flight time total : 410 flight time type : 410
ASRS Report	161768
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	incursion : runway non adherence : far
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Traffic was heavy for this airport which is my home base. Traffic was departing on runway 18 and landing on 28, an unusual situation. The controller was busy. I was making a normal left pattern for 28. It was necessary for me to announce that I was on base leg to get clearance to land. I made a normal landing. At this point I would have expected a tower advisory to 'turn off when able,' or 'continue across 18.' west/O an advisory, I erroneously turned right onto 17, marked 1 on the diagram. The controller started to stop me, commenting that 18 was active, then directed me to continue on 18 for about 200' to the next taxiway, marked 2, where I turned off. Controller advised me of the correct procedure which was that I was cleared to cross 18, not turn onto it. I do not believe that there was an aircraft holding in position on 18 at that time, therefore was no potential conflict. Both runways active at the same time is unusual. The fact that the tower operator did not give me a timely advisory to continue across 18 led me to turn off onto 18 which I have done many times (when 28 was the only active runway) at the advisory, 'turn off when able.'

Original NASA ASRS Text

Title: AFTER LNDG GA SMA TURNED ONTO AN ACTIVE RWY WITHOUT CLRNC.

Narrative: TFC WAS HVY FOR THIS ARPT WHICH IS MY HOME BASE. TFC WAS DEPARTING ON RWY 18 AND LNDG ON 28, AN UNUSUAL SITUATION. THE CTLR WAS BUSY. I WAS MAKING A NORMAL LEFT PATTERN FOR 28. IT WAS NECESSARY FOR ME TO ANNOUNCE THAT I WAS ON BASE LEG TO GET CLRNC TO LAND. I MADE A NORMAL LNDG. AT THIS POINT I WOULD HAVE EXPECTED A TWR ADVISORY TO 'TURN OFF WHEN ABLE,' OR 'CONTINUE ACROSS 18.' W/O AN ADVISORY, I ERRONEOUSLY TURNED RIGHT ONTO 17, MARKED 1 ON THE DIAGRAM. THE CTLR STARTED TO STOP ME, COMMENTING THAT 18 WAS ACTIVE, THEN DIRECTED ME TO CONTINUE ON 18 FOR ABOUT 200' TO THE NEXT TXWY, MARKED 2, WHERE I TURNED OFF. CTLR ADVISED ME OF THE CORRECT PROC WHICH WAS THAT I WAS CLRED TO CROSS 18, NOT TURN ONTO IT. I DO NOT BELIEVE THAT THERE WAS AN ACFT HOLDING IN POS ON 18 AT THAT TIME, THEREFORE WAS NO POTENTIAL CONFLICT. BOTH RWYS ACTIVE AT THE SAME TIME IS UNUSUAL. THE FACT THAT THE TWR OPERATOR DID NOT GIVE ME A TIMELY ADVISORY TO CONTINUE ACROSS 18 LED ME TO TURN OFF ONTO 18 WHICH I HAVE DONE MANY TIMES (WHEN 28 WAS THE ONLY ACTIVE RWY) AT THE ADVISORY, 'TURN OFF WHEN ABLE.'

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.