Narrative:

At richmond international airport, I was taxiing out for departure on my daily freight run to ZZZ. I had received clearance to taxi to runway 20 (I was not given a specific taxi route). My point of origin on the airport was the FBO ramp which is at the south end of the field. Richmond international has 2 parallel txwys that run north/south along runways 2/20, txwys a and U. Normally when taxiing from FBO, I take a right on taxiway G and then left on taxiway U, when proceeding to runway 20 because taxiway a does not extend all the way south to taxiway G. On this particular day, taxiway G was closed, so I proceeded further north to taxiway F and took a right to get to the parallel txwys. Since I normally taxi northbound on taxiway U, and since I was not given instructions to taxi on taxiway a, I crossed taxiway a and made the left on taxiway U. At the next intersection (taxiway east) a jet (MD80?) was clearing runway 20 and was cleared by the ground controller to taxi to the gate without any warning to give way to me or for me to give way to him. By the time I realized there was going to be a conflict it was too late to stop. I passed approximately 50 ft in front of the jet. The pilot of the jet expressed his displeasure at the near miss to the ground controller, whose response leads me to believe that he was not aware of the potential conflict. Either the ground controller forgot about me or was expecting me to be on the other parallel taxiway when he cleared the jet to the gate. I think the major factors were the lack of specific instructions regarding which parallel taxiway I should have used and the ground controller's loss of awareness regarding my position as I taxied to runway 20. Also, (although not related or contributing to this event) the current airport diagram for ric in the northeast-3 terminal procedure charts does not accurately depict the taxiway layout with regards to txwys a and U.

Google
 

Original NASA ASRS Text

Title: NEAR GND COLLISION WHEN A TAXIING ATX CARGO ACFT PASSES 50 FT IN FRONT OF AN ACR JET JUST TURNING OFF RWY 20 ONTO TXWY E AT RIC, VA.

Narrative: AT RICHMOND INTL ARPT, I WAS TAXIING OUT FOR DEP ON MY DAILY FREIGHT RUN TO ZZZ. I HAD RECEIVED CLRNC TO TAXI TO RWY 20 (I WAS NOT GIVEN A SPECIFIC TAXI RTE). MY POINT OF ORIGIN ON THE ARPT WAS THE FBO RAMP WHICH IS AT THE S END OF THE FIELD. RICHMOND INTL HAS 2 PARALLEL TXWYS THAT RUN N/S ALONG RWYS 2/20, TXWYS A AND U. NORMALLY WHEN TAXIING FROM FBO, I TAKE A R ON TXWY G AND THEN L ON TXWY U, WHEN PROCEEDING TO RWY 20 BECAUSE TXWY A DOES NOT EXTEND ALL THE WAY S TO TXWY G. ON THIS PARTICULAR DAY, TXWY G WAS CLOSED, SO I PROCEEDED FURTHER N TO TXWY F AND TOOK A R TO GET TO THE PARALLEL TXWYS. SINCE I NORMALLY TAXI NBOUND ON TXWY U, AND SINCE I WAS NOT GIVEN INSTRUCTIONS TO TAXI ON TXWY A, I CROSSED TXWY A AND MADE THE L ON TXWY U. AT THE NEXT INTXN (TXWY E) A JET (MD80?) WAS CLRING RWY 20 AND WAS CLRED BY THE GND CTLR TO TAXI TO THE GATE WITHOUT ANY WARNING TO GIVE WAY TO ME OR FOR ME TO GIVE WAY TO HIM. BY THE TIME I REALIZED THERE WAS GOING TO BE A CONFLICT IT WAS TOO LATE TO STOP. I PASSED APPROX 50 FT IN FRONT OF THE JET. THE PLT OF THE JET EXPRESSED HIS DISPLEASURE AT THE NEAR MISS TO THE GND CTLR, WHOSE RESPONSE LEADS ME TO BELIEVE THAT HE WAS NOT AWARE OF THE POTENTIAL CONFLICT. EITHER THE GND CTLR FORGOT ABOUT ME OR WAS EXPECTING ME TO BE ON THE OTHER PARALLEL TXWY WHEN HE CLRED THE JET TO THE GATE. I THINK THE MAJOR FACTORS WERE THE LACK OF SPECIFIC INSTRUCTIONS REGARDING WHICH PARALLEL TXWY I SHOULD HAVE USED AND THE GND CTLR'S LOSS OF AWARENESS REGARDING MY POS AS I TAXIED TO RWY 20. ALSO, (ALTHOUGH NOT RELATED OR CONTRIBUTING TO THIS EVENT) THE CURRENT ARPT DIAGRAM FOR RIC IN THE NE-3 TERMINAL PROC CHARTS DOES NOT ACCURATELY DEPICT THE TXWY LAYOUT WITH REGARDS TO TXWYS A AND U.

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.