Narrative:

On may/mon/04, when taxiing for departure from sna for our trip to clm, we had a runway incursion. There was no evasive action required and a description of the event is described below. We were parked at an FBO south of taxiway D. Taxi instructions were to taxi via taxiway a, hold short of taxiway D. After the crossing aircraft passed, we were instructed to continue taxi to runway 19R, hold short of taxiway left. Prior to reaching taxiway J, we were instructed to turn left on taxiway J then right on taxiway C and hold short of taxiway left. There was an air carrier flight holding on taxiway a short of taxiway left. There was another air carrier back taxiing on runway 19L. We made the left turn on taxiway J and assumed that air carrier Z aircraft was taxiing on taxiway C. It was not until we started the right turn that we realized our mistake. The txwys were marked properly, but when we looked at the airport diagram it appears that there is grass between txwys a and C, which does not exist. Taxiway C is narrow and we mistook it for a vehicle access road. The fact that air carrier Z was taxiing on runway 19L also caused us to mistake it for taxiway C. We acknowledged our mistake with ground control and apologized for our error. They instructed us to continue the back taxi on runway 19L, turn left on taxiway K, hold short of runway 19R and contact tower. No further action was taken. Sna airport is a very busy airport with a lot of mixed operations, commercial, light and heavy GA aircraft. Upon further review of the airport diagram, it would seem that aircraft parked on the far south side of the airport would have less congestion and confusion if aircraft were instructed to taxi across runway 19L at taxiway D, then taxi to runway 19L via taxiway B. This would cause us to have to wait to cross an active runway, but this area of the airport is less congested.

Google
 

Original NASA ASRS Text

Title: RWY INCURSION BY AN FA20 CPR JET ONTO RWY 19L AT SNA, CA.

Narrative: ON MAY/MON/04, WHEN TAXIING FOR DEP FROM SNA FOR OUR TRIP TO CLM, WE HAD A RWY INCURSION. THERE WAS NO EVASIVE ACTION REQUIRED AND A DESCRIPTION OF THE EVENT IS DESCRIBED BELOW. WE WERE PARKED AT AN FBO S OF TXWY D. TAXI INSTRUCTIONS WERE TO TAXI VIA TXWY A, HOLD SHORT OF TXWY D. AFTER THE XING ACFT PASSED, WE WERE INSTRUCTED TO CONTINUE TAXI TO RWY 19R, HOLD SHORT OF TXWY L. PRIOR TO REACHING TXWY J, WE WERE INSTRUCTED TO TURN L ON TXWY J THEN R ON TXWY C AND HOLD SHORT OF TXWY L. THERE WAS AN ACR FLT HOLDING ON TXWY A SHORT OF TXWY L. THERE WAS ANOTHER ACR BACK TAXIING ON RWY 19L. WE MADE THE L TURN ON TXWY J AND ASSUMED THAT ACR Z ACFT WAS TAXIING ON TXWY C. IT WAS NOT UNTIL WE STARTED THE R TURN THAT WE REALIZED OUR MISTAKE. THE TXWYS WERE MARKED PROPERLY, BUT WHEN WE LOOKED AT THE ARPT DIAGRAM IT APPEARS THAT THERE IS GRASS BTWN TXWYS A AND C, WHICH DOES NOT EXIST. TXWY C IS NARROW AND WE MISTOOK IT FOR A VEHICLE ACCESS ROAD. THE FACT THAT ACR Z WAS TAXIING ON RWY 19L ALSO CAUSED US TO MISTAKE IT FOR TXWY C. WE ACKNOWLEDGED OUR MISTAKE WITH GND CTL AND APOLOGIZED FOR OUR ERROR. THEY INSTRUCTED US TO CONTINUE THE BACK TAXI ON RWY 19L, TURN L ON TXWY K, HOLD SHORT OF RWY 19R AND CONTACT TWR. NO FURTHER ACTION WAS TAKEN. SNA ARPT IS A VERY BUSY ARPT WITH A LOT OF MIXED OPS, COMMERCIAL, LIGHT AND HVY GA ACFT. UPON FURTHER REVIEW OF THE ARPT DIAGRAM, IT WOULD SEEM THAT ACFT PARKED ON THE FAR S SIDE OF THE ARPT WOULD HAVE LESS CONGESTION AND CONFUSION IF ACFT WERE INSTRUCTED TO TAXI ACROSS RWY 19L AT TXWY D, THEN TAXI TO RWY 19L VIA TXWY B. THIS WOULD CAUSE US TO HAVE TO WAIT TO CROSS AN ACTIVE RWY, BUT THIS AREA OF THE ARPT IS LESS CONGESTED.

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.