AA5 taxiing for departure crossed runway without ATC clearance.

Attributes
ACN	581630
Time
Date	200305
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : frg.airport
State Reference	NY
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 58 flight time total : 1125 flight time type : 1125
ASRS Report	581630
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Frg has 2 intersecting runways, runway 14/32 (the active at the time of the event) and runway 1/19. I was at the ramp, south end of runway 1/19, and was cleared to taxi to runway 14, which should have been via a n-s taxiway on the west side of runway 1/19 to a taxiway paralleling runway 14/32 without crossing any runways. I confused runway 14 and runway 32 in my mind, and so taxied across runway 1/19 (remembering that a clearance to taxi to a runway includes clearance to cross any intervening runways) to a n-s taxiway on the east side of runway 1/19. I know that the FAA is particularly concerned about runway incursions, and I thought this would never happen to me. I guess it just did. Ground told me to either make a left turn on the taxiway paralleling runway 14/32, or to taxi northwest on that taxiway ahead of a lear jet that had exited runway 14/32 (after landing on runway 14) ahead and to my right, which made me realize my mistake at that point. Fortunately, there was no traffic to runway 1/19 at the time of the incident.

Original NASA ASRS Text

Title: AA5 TAXIING FOR DEP CROSSED RWY WITHOUT ATC CLRNC.

Narrative: FRG HAS 2 INTERSECTING RWYS, RWY 14/32 (THE ACTIVE AT THE TIME OF THE EVENT) AND RWY 1/19. I WAS AT THE RAMP, S END OF RWY 1/19, AND WAS CLRED TO TAXI TO RWY 14, WHICH SHOULD HAVE BEEN VIA A N-S TXWY ON THE W SIDE OF RWY 1/19 TO A TXWY PARALLELING RWY 14/32 WITHOUT XING ANY RWYS. I CONFUSED RWY 14 AND RWY 32 IN MY MIND, AND SO TAXIED ACROSS RWY 1/19 (REMEMBERING THAT A CLRNC TO TAXI TO A RWY INCLUDES CLRNC TO CROSS ANY INTERVENING RWYS) TO A N-S TXWY ON THE E SIDE OF RWY 1/19. I KNOW THAT THE FAA IS PARTICULARLY CONCERNED ABOUT RWY INCURSIONS, AND I THOUGHT THIS WOULD NEVER HAPPEN TO ME. I GUESS IT JUST DID. GND TOLD ME TO EITHER MAKE A L TURN ON THE TXWY PARALLELING RWY 14/32, OR TO TAXI NW ON THAT TXWY AHEAD OF A LEAR JET THAT HAD EXITED RWY 14/32 (AFTER LNDG ON RWY 14) AHEAD AND TO MY R, WHICH MADE ME REALIZE MY MISTAKE AT THAT POINT. FORTUNATELY, THERE WAS NO TFC TO RWY 1/19 AT THE TIME OF THE INCIDENT.

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.