PA-28 pilot taxied onto runway without clearance.

Attributes
ACN	548502
Time
Date	200205
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : jxn.airport
State Reference	MI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	PA-28 Cherokee/Archer II/Dakota/Pillan/Warrior
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	None
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 30 flight time total : 2000 flight time type : 1000
ASRS Report	548502
Person 2
Affiliation	government : faa
Function	controller : local
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Runways 6/24 and 14/32 intersect at taxiway 'echo'. Jxn however was busy with VFR arrivals on runway 24. On landing jxn tower instructed me to remain on tower frequency for ground directions. I was told to exit on 'echo' for terminal building and FBO. I exited on what I though was 'echo' but turned too tight and exited on the inactive runway 14/32. Tower called and informed me and told me to continue on runway 14 and then exit on 'charlie' and continue to terminal ramp. No further contact was made by tower. I feel that the unusual intersection was the prime contribution, along with high-density traffic and my desire to expedite clearing the active runway. I suggest that ground control or tower alert landing traffic runway 24 or traffic about to exit runway 24 for this unusual intersection of 6/24, 14/32 and taxiway 'echo'. The alternative would be to close the short section of 'echo' where it intersects and then exit landing traffic for runway 24 onto 'delta' and then 'echo'. Jxn tower is understaffed on weekends and still does an excellent job, but the manpower shortage shows. I should have been better prepared and not so eager to expedite clearing runway 24.

Original NASA ASRS Text

Title: PA-28 PLT TAXIED ONTO RWY WITHOUT CLRNC.

Narrative: RWYS 6/24 AND 14/32 INTERSECT AT TXWY 'ECHO'. JXN HOWEVER WAS BUSY WITH VFR ARRIVALS ON RWY 24. ON LNDG JXN TWR INSTRUCTED ME TO REMAIN ON TWR FREQ FOR GND DIRECTIONS. I WAS TOLD TO EXIT ON 'ECHO' FOR TERMINAL BUILDING AND FBO. I EXITED ON WHAT I THOUGH WAS 'ECHO' BUT TURNED TOO TIGHT AND EXITED ON THE INACTIVE RWY 14/32. TWR CALLED AND INFORMED ME AND TOLD ME TO CONTINUE ON RWY 14 AND THEN EXIT ON 'CHARLIE' AND CONTINUE TO TERMINAL RAMP. NO FURTHER CONTACT WAS MADE BY TWR. I FEEL THAT THE UNUSUAL INTXN WAS THE PRIME CONTRIBUTION, ALONG WITH HIGH-DENSITY TFC AND MY DESIRE TO EXPEDITE CLEARING THE ACTIVE RWY. I SUGGEST THAT GND CTL OR TWR ALERT LNDG TFC RWY 24 OR TFC ABOUT TO EXIT RWY 24 FOR THIS UNUSUAL INTXN OF 6/24, 14/32 AND TXWY 'ECHO'. THE ALTERNATIVE WOULD BE TO CLOSE THE SHORT SECTION OF 'ECHO' WHERE IT INTERSECTS AND THEN EXIT LNDG TFC FOR RWY 24 ONTO 'DELTA' AND THEN 'ECHO'. JXN TWR IS UNDERSTAFFED ON WEEKENDS AND STILL DOES AN EXCELLENT JOB, BUT THE MANPOWER SHORTAGE SHOWS. I SHOULD HAVE BEEN BETTER PREPARED AND NOT SO EAGER TO EXPEDITE CLEARING RWY 24.

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.