Narrative:

Upon initial contact with pdk ground control, I was cleared to taxi to runway 34. As I approached the intersection of taxiway B and runway 2R, I checked in both directions for traffic. My passenger (a private pilot) and I both observed a jet on final for runway 2R and listened for instructions from ATC. Not hearing any, and perceiving no safety hazard, I proceeded to cross the runway and continued to the run-up area for runway 34. After completing my before takeoff checklist, I switched to tower frequency and reported that I was ready for takeoff. Tower responded by telling me that ground control had attempted to contact me to tell me to hold short of runway 2R for landing traffic. They then cleared me for takeoff. The rest of the flight proceeded uneventfully and concluded west/O incident. During normal debriefing of the flight, my passenger and I discussed possible reasons for not receiving ground control's hold short instructions. We came to no real conclusions, aside from possible intermittent radio problems. However, it had come to my attention that is fairly common for controller's xmissions to be 'cut-off' or 'stepped on' due to frequency congestion at pdk. Perhaps this caused the lack of communication. It seems to me that the situation might have been averted if the ground controller had issued the hold short instructions along with his first taxi clearance. Presumably, he was aware of the approaching jet traffic. In my experience at other airports, this is a common procedure. Then, if the traffic is no longer a factor, the controller removes the hold short restriction. In this case, radio failure or other communication problems would raise the possibility of a safety hazard.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA CLEARED TO TAXI TO RWY WITH NO RESTRICTIONS. CROSSED ACTIVE, LATER TOLD GND CTLR TRIED TO ISSUE HOLD SHORT CLRNC.

Narrative: UPON INITIAL CONTACT WITH PDK GND CTL, I WAS CLRED TO TAXI TO RWY 34. AS I APCHED THE INTXN OF TXWY B AND RWY 2R, I CHKED IN BOTH DIRECTIONS FOR TFC. MY PAX (A PVT PLT) AND I BOTH OBSERVED A JET ON FINAL FOR RWY 2R AND LISTENED FOR INSTRUCTIONS FROM ATC. NOT HEARING ANY, AND PERCEIVING NO SAFETY HAZARD, I PROCEEDED TO CROSS THE RWY AND CONTINUED TO THE RUN-UP AREA FOR RWY 34. AFTER COMPLETING MY BEFORE TKOF CHKLIST, I SWITCHED TO TWR FREQ AND RPTED THAT I WAS READY FOR TKOF. TWR RESPONDED BY TELLING ME THAT GND CTL HAD ATTEMPTED TO CONTACT ME TO TELL ME TO HOLD SHORT OF RWY 2R FOR LNDG TFC. THEY THEN CLRED ME FOR TKOF. THE REST OF THE FLT PROCEEDED UNEVENTFULLY AND CONCLUDED W/O INCIDENT. DURING NORMAL DEBRIEFING OF THE FLT, MY PAX AND I DISCUSSED POSSIBLE REASONS FOR NOT RECEIVING GND CTL'S HOLD SHORT INSTRUCTIONS. WE CAME TO NO REAL CONCLUSIONS, ASIDE FROM POSSIBLE INTERMITTENT RADIO PROBS. HOWEVER, IT HAD COME TO MY ATTN THAT IS FAIRLY COMMON FOR CTLR'S XMISSIONS TO BE 'CUT-OFF' OR 'STEPPED ON' DUE TO FREQ CONGESTION AT PDK. PERHAPS THIS CAUSED THE LACK OF COM. IT SEEMS TO ME THAT THE SITUATION MIGHT HAVE BEEN AVERTED IF THE GND CTLR HAD ISSUED THE HOLD SHORT INSTRUCTIONS ALONG WITH HIS FIRST TAXI CLRNC. PRESUMABLY, HE WAS AWARE OF THE APCHING JET TFC. IN MY EXPERIENCE AT OTHER ARPTS, THIS IS A COMMON PROC. THEN, IF THE TFC IS NO LONGER A FACTOR, THE CTLR REMOVES THE HOLD SHORT RESTRICTION. IN THIS CASE, RADIO FAILURE OR OTHER COM PROBS WOULD RAISE THE POSSIBILITY OF A SAFETY HAZARD.

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.