Narrative:

Crg was operating under VFR conditions. The ATIS indicated winds were 230 deg at 5 kts and the active runway being used was runway 23. Note that I filed and received an instrument flight plan clearance before taxiing. Before taxiing from the FBO; I called crg ground and was directed to taxi to runway 32 (vs 23) via taxiway alpha due to my planned route of flight (which was to the north). During taxi; ground noted that the winds had shifted to 180 deg at 9 knots. Given that would result in a 7 kt tailwind at takeoff; I called ground and requested to be shifted to runway 23 (note that runways 23 and 32 cross at the departure end). Ground cleared me to runway 23 via alpha; echo and runway 32. As I pulled up to the intersection of taxiways alpha; bravo; charlie; echo and foxtrot there were at least two other aircraft waiting to depart runway 23. My parking position blocked me from seeing the hold short for runway 32 although I could see the hold short markings on runway 32 for runway 23. Once the taxi traffic cleared; I proceeded to roll from taxiway echo onto runway 32. As I rolled onto runway 32; ground notified me that I had rolled onto the runway and wasn't cleared to do so (note that runway 32 was not in active use from what I could ascertain visually or on the radio). Ground asked me to do a 180 deg turn and return to the taxiway. I immediately complied and told ground I believed I had been cleared to runway 23 via runway 32. I was then handed to tower and departed runway 23 without incident. I believe several things contributed to the inadvertent runway 32 incursion: 1) apparent miscommunication with ground on being cleared to runway 23 via runway 32; 2) the wind shift and change from runway 32 to 23 during taxi; 3) the fact that runways 23 and 32 cross at the departure end with several taxiways feeding these runways; 4) significant ground traffic backed up at runway 23 and the close proximity of taxiway's alpha; bravo; charlie; echo and foxtrot coming together in a small space which caused 5) me not to be able to see the hold short markings for runway 32; and 6) the fact that runways 23 and 32 could easily be confused due to common numeral usage. I would suggest that 1) the intersection of runways 23 and 32 be noted as a 'hot spot' and 2) one of the runways be renumbered to move them up or down by one numeral (e.g.; 23 to 24).

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reported a runway incursion due to communication issue between Ground Control and Pilot in addition to intersecting departure ends of two runways.

Narrative: CRG was operating under VFR conditions. The ATIS indicated winds were 230 deg at 5 kts and the active runway being used was Runway 23. Note that I filed and received an instrument flight plan clearance before taxiing. Before taxiing from the FBO; I called CRG ground and was directed to taxi to Runway 32 (vs 23) via Taxiway Alpha due to my planned route of flight (which was to the north). During taxi; ground noted that the winds had shifted to 180 deg at 9 knots. Given that would result in a 7 kt tailwind at takeoff; I called ground and requested to be shifted to Runway 23 (note that Runways 23 and 32 cross at the departure end). Ground cleared me to Runway 23 via Alpha; Echo and Runway 32. As I pulled up to the intersection of taxiways Alpha; Bravo; Charlie; Echo and Foxtrot there were at least two other aircraft waiting to depart Runway 23. My parking position blocked me from seeing the hold short for Runway 32 although I could see the hold short markings on Runway 32 for Runway 23. Once the taxi traffic cleared; I proceeded to roll from taxiway Echo onto runway 32. As I rolled onto Runway 32; ground notified me that I had rolled onto the runway and wasn't cleared to do so (note that Runway 32 was not in active use from what I could ascertain visually or on the radio). Ground asked me to do a 180 deg turn and return to the taxiway. I immediately complied and told ground I believed I had been cleared to Runway 23 via Runway 32. I was then handed to tower and departed Runway 23 without incident. I believe several things contributed to the inadvertent Runway 32 incursion: 1) apparent miscommunication with ground on being cleared to Runway 23 via Runway 32; 2) the wind shift and change from Runway 32 to 23 during taxi; 3) the fact that Runways 23 and 32 cross at the departure end with several taxiways feeding these runways; 4) significant ground traffic backed up at Runway 23 and the close proximity of taxiway's Alpha; Bravo; Charlie; Echo and Foxtrot coming together in a small space which caused 5) me not to be able to see the hold short markings for Runway 32; and 6) the fact that Runways 23 and 32 could easily be confused due to common numeral usage. I would suggest that 1) the intersection of Runways 23 and 32 be noted as a 'hot spot' and 2) one of the runways be renumbered to move them up or down by one numeral (e.g.; 23 to 24).

Data retrieved from NASA's ASRS site 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.