PA32 pilot turned off his landing runway onto another runway at sgj.

Attributes
ACN	576579
Time
Date	200303
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sgj.airport
State Reference	FL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	PA-32 Cherokee Six/Lance/Saratoga
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 25 flight time total : 2800 flight time type : 1100
ASRS Report	576579
Person 2
Function	flight crew : single pilot
Events
Anomaly	conflict : ground critical incursion : runway non adherence : far non adherence : published procedure
Independent Detector	other controllera other other : 2
Resolutory Action	controller : issued new clearance flight crew : executed go around flight crew : took precautionary avoidance action
Miss Distance	horizontal : 1000 vertical : 100
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Was IFR sgj in VMC. Original ATIS information specified visual approach to runway 31. New ATIS changed some items including adding ILS approach to runway 31. However, recording still used old identifier. Runway 31 still was only runway declared to be in use. Following tower instructions, I entered downwind, was cleared to land and landed on runway 31. After roll-out, I exited runway 31 by turning southwest onto intersecting runway 2/20. I had not been advised that lahso's were in effect. Nor was I given any specific instructions where to exit runway 31. Upon leaving runway 31, I contacted ground control with no response. Then saw plane on close approach to runway 2 (head-on to me). I called ground control again to advise of other plane, which was now executing a go around. Advised I was on an active runway, but to continue taxiing to a particular intersection then to FBO. There was no further conflict. I feel that sgj tower was remiss in advising me and other aircraft of the use of 2 intersecting runways either by ATIS or direct radio transmission.

Original NASA ASRS Text

Title: PA32 PLT TURNED OFF HIS LNDG RWY ONTO ANOTHER RWY AT SGJ.

Narrative: WAS IFR SGJ IN VMC. ORIGINAL ATIS INFO SPECIFIED VISUAL APCH TO RWY 31. NEW ATIS CHANGED SOME ITEMS INCLUDING ADDING ILS APCH TO RWY 31. HOWEVER, RECORDING STILL USED OLD IDENTIFIER. RWY 31 STILL WAS ONLY RWY DECLARED TO BE IN USE. FOLLOWING TWR INSTRUCTIONS, I ENTERED DOWNWIND, WAS CLRED TO LAND AND LANDED ON RWY 31. AFTER ROLL-OUT, I EXITED RWY 31 BY TURNING SW ONTO INTERSECTING RWY 2/20. I HAD NOT BEEN ADVISED THAT LAHSO'S WERE IN EFFECT. NOR WAS I GIVEN ANY SPECIFIC INSTRUCTIONS WHERE TO EXIT RWY 31. UPON LEAVING RWY 31, I CONTACTED GND CTL WITH NO RESPONSE. THEN SAW PLANE ON CLOSE APCH TO RWY 2 (HEAD-ON TO ME). I CALLED GND CTL AGAIN TO ADVISE OF OTHER PLANE, WHICH WAS NOW EXECUTING A GAR. ADVISED I WAS ON AN ACTIVE RWY, BUT TO CONTINUE TAXIING TO A PARTICULAR INTXN THEN TO FBO. THERE WAS NO FURTHER CONFLICT. I FEEL THAT SGJ TWR WAS REMISS IN ADVISING ME AND OTHER ACFT OF THE USE OF 2 INTERSECTING RWYS EITHER BY ATIS OR DIRECT RADIO XMISSION.

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.