Narrative:

Slowing down, descending, and trying to keep PA34-220T turbochargers from cooling too quickly, while looking for conflicting traffic. At 2 mi from runway 17 threshold, tower cleared waiting aircraft at taxiway B to 'depart or wait, your choice.' we were still traveling 130 KTS and thought that would be close. The aircraft operator said he thought he would go. Tower said, 'on second thought, you had better wait.' we had already been cleared to land runway 17. Came in hot, landed fast and used heavy braking to make taxiway D due to following traffic and waiting aircraft. Turned onto taxiway D. Tower cleared waiting aircraft for immediate departure. And I taxied to the ramp along taxiway D and taxiway C. Tower called on tower frequency and asked that I call ground on 121.90. I called ground and was instructed to call tower on telephone once inside at FBO. Controller scolded me for not contacting ground control prior to movement on taxiway. I admitted that I had not done so and accepted responsibility for my error. I had allowed myself to become distraction by chain of events. Don't really know if tower ever instructed me to switch to ground or not. Have flown into pns often lately and usually hear 'taxi to ramp this frequency' from tower. So, I suppose I simply assumed I should do so this time as well. Bad decision. I should have queried the controller and not have assumed. No accident occurred, no near miss. Outbound student aircraft had to wait for me to taxi, but one of us would have had to wait anyway. Still, my fault for not being sure. Contributing factors, I believe, were compliance with approach controller's request. Hesitant tower controller, and knowledge of past pattern and practice at this field.

Related reports:

Google
 

Original NASA ASRS Text

Title: PLT OF A PIPER PA34-200 FAILED TO CONTACT GND CTL AFTER TURNING OFF RWY AND TAXIED TO PARKING WITHOUT CLRNC.

Narrative: SLOWING DOWN, DSNDING, AND TRYING TO KEEP PA34-220T TURBOCHARGERS FROM COOLING TOO QUICKLY, WHILE LOOKING FOR CONFLICTING TFC. AT 2 MI FROM RWY 17 THRESHOLD, TWR CLRED WAITING ACFT AT TXWY B TO 'DEPART OR WAIT, YOUR CHOICE.' WE WERE STILL TRAVELING 130 KTS AND THOUGHT THAT WOULD BE CLOSE. THE ACFT OPERATOR SAID HE THOUGHT HE WOULD GO. TWR SAID, 'ON SECOND THOUGHT, YOU HAD BETTER WAIT.' WE HAD ALREADY BEEN CLRED TO LAND RWY 17. CAME IN HOT, LANDED FAST AND USED HVY BRAKING TO MAKE TXWY D DUE TO FOLLOWING TFC AND WAITING ACFT. TURNED ONTO TXWY D. TWR CLRED WAITING ACFT FOR IMMEDIATE DEP. AND I TAXIED TO THE RAMP ALONG TXWY D AND TXWY C. TWR CALLED ON TWR FREQ AND ASKED THAT I CALL GND ON 121.90. I CALLED GND AND WAS INSTRUCTED TO CALL TWR ON TELEPHONE ONCE INSIDE AT FBO. CTLR SCOLDED ME FOR NOT CONTACTING GND CTL PRIOR TO MOVEMENT ON TXWY. I ADMITTED THAT I HAD NOT DONE SO AND ACCEPTED RESPONSIBILITY FOR MY ERROR. I HAD ALLOWED MYSELF TO BECOME DISTR BY CHAIN OF EVENTS. DON'T REALLY KNOW IF TWR EVER INSTRUCTED ME TO SWITCH TO GND OR NOT. HAVE FLOWN INTO PNS OFTEN LATELY AND USUALLY HEAR 'TAXI TO RAMP THIS FREQ' FROM TWR. SO, I SUPPOSE I SIMPLY ASSUMED I SHOULD DO SO THIS TIME AS WELL. BAD DECISION. I SHOULD HAVE QUERIED THE CTLR AND NOT HAVE ASSUMED. NO ACCIDENT OCCURRED, NO NEAR MISS. OUTBOUND STUDENT ACFT HAD TO WAIT FOR ME TO TAXI, BUT ONE OF US WOULD HAVE HAD TO WAIT ANYWAY. STILL, MY FAULT FOR NOT BEING SURE. CONTRIBUTING FACTORS, I BELIEVE, WERE COMPLIANCE WITH APCH CTLR'S REQUEST. HESITANT TWR CTLR, AND KNOWLEDGE OF PAST PATTERN AND PRACTICE AT THIS FIELD.

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.