Narrative:

I landed on runway 14 after a visual approach; following a C-172.there were two departures waiting to take off and several others in the pattern waiting to land. Upon touchdown the local controller told me to 'keep it rolling' down the runway to exit at taxiway alpha; and then in the same transmission cleared a waiting plane to depart before I fully cleared the runway. (Anticipating separation)I pulled just beyond the taxiway a hold line heading towards the GA ramp and stopped. I immediately contacted ground. The ground controller's first words were 'you just cut off that cessna 172 to your left'. I looked up and there was a 172 fifty ft away entering the same intersection; headed south on the taxiway. I did not expect to see him there because I was busy clearing the runway.this was the same 172 I had followed in on the approach. He had made an earlier turn off and was south bound on taxiway bravo; headed also for the GA ramp.as you can see from a google earth photo; there is no way an aircraft can clear runway 14 at taxiway a without intruding into taxiway bravo.the local controller did not appear to communicate with the ground controller because there should have been some coordination as to who had the right of way at this intersection before we both got there at the same time.the aircraft I 'cut off' was the 172 that landed prior to me. They took an earlier turn-off and followed me to the GA ramp and shut down next to me. In the plane were two FAA examiners. As a result of this possible conflict I was ramp checked. (The process was very pleasant and took no more than a minute or two.) there was no mention of the intersection incident.I spoke to the FAA pilots/examiners in the FBO and apologized that I did not see them and was simply trying to get clear of runway 14; and that the placement of the hold line caused me to taxi well into taxiway bravo. Fortunately they had seen me exiting the runway and stopped in time to avoid bending metal. I believe there was improper coordination between the ground and local controllers. I was not told to hold short of taxiway bravo so my obligation was to fully clear the runway. Ground control should have held southbound traffic into the ramp to allow landing aircraft to clear runway 14. The confluence of taxiways alpha and bravo at the intersection of runway 14/32 and runway 5/23 and the GA ramp is congested. The hold short lines are very close to active taxiways. If not already; this area should be designated a hot spot for taxi incidents.I recommend more training for ground and local controllers in coordinating landing traffic with taxiing aircraft in this area.

Related reports:

Google
 

Original NASA ASRS Text

Title: As he cleared his landing runway as directed; a BE-36 pilot experienced a ground conflict with a C-172 that had landed prior to him; exited on an earlier taxiway; and was taxiing as cleared down the parallel taxiway.

Narrative: I landed on Runway 14 after a visual approach; following a C-172.There were two departures waiting to take off and several others in the pattern waiting to land. Upon touchdown the Local Controller told me to 'keep it rolling' down the runway to exit at Taxiway Alpha; and then in the same transmission cleared a waiting plane to depart before I fully cleared the runway. (Anticipating separation)I pulled just beyond the Taxiway A hold line heading towards the GA ramp and stopped. I immediately contacted ground. The Ground Controller's first words were 'you just cut off that Cessna 172 to your left'. I looked up and there was a 172 fifty FT away entering the same intersection; headed south on the taxiway. I did not expect to see him there because I was busy clearing the runway.This was the same 172 I had followed in on the approach. He had made an earlier turn off and was south bound on Taxiway Bravo; headed also for the GA ramp.As you can see from a Google Earth photo; there is no way an aircraft can clear Runway 14 at Taxiway A without intruding into Taxiway Bravo.The Local Controller did not appear to communicate with the Ground Controller because there should have been some coordination as to who had the right of way at this intersection before we both got there at the same time.The aircraft I 'cut off' was the 172 that landed prior to me. They took an earlier turn-off and followed me to the GA ramp and shut down next to me. In the plane were two FAA examiners. As a result of this possible conflict I was ramp checked. (The process was very pleasant and took no more than a minute or two.) There was no mention of the intersection incident.I spoke to the FAA pilots/examiners in the FBO and apologized that I did not see them and was simply trying to get clear of Runway 14; and that the placement of the hold line caused me to taxi well into Taxiway Bravo. Fortunately they had seen me exiting the runway and stopped in time to avoid bending metal. I believe there was improper coordination between the Ground and Local Controllers. I was not told to hold short of Taxiway Bravo so my obligation was to fully clear the runway. Ground Control should have held southbound traffic into the ramp to allow landing aircraft to clear Runway 14. The confluence of Taxiways Alpha and Bravo at the intersection of Runway 14/32 and Runway 5/23 and the GA ramp is congested. The hold short lines are very close to active taxiways. If not already; this area should be designated a Hot Spot for taxi incidents.I recommend more training for Ground and Local Controllers in coordinating landing traffic with taxiing aircraft in this area.

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