Skyhawk 172/Cutlass 172
Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
General None Reported / Taken
Human Factors; Procedure
I was working Cab Coordinator at PDK Tower; Runway 34 and Runway 3R where in use. Local 1 was busy and had Cessna X cleared number 1 to land on Runway 34. Cessna Y was on the right downwind and was cleared to land number behind Cessna X number 2 for Runway 34. Cessna Y turned from the downwind quickly and on a much tighter base leg than the Local Controller had planned. I advised the Local Controller that it was not going to work and to send Cessna Y around; but he did not. I advised the Local Controller again; a second time; to send Cessna Y around but he did not. Cessna X landed and almost came to a complete stop even though Local 1 was advising Cessna X to exit the runway to the left. Cessna Y questioned Local 1 about possibly going around; but Local 1 did not send Cessna Y around. I believe Local 1 thought it was too late in the landing to safely send the aircraft around. Cessna Y landed with Cessna X exiting but still on Runway 34 ahead of it. The required separation did not exist. The Ground Controllers a PDK block the exit points of the active runways on a routine basis; even though our SOP states that they shall keep the exit points open to allow landing aircraft to exit the runway. This is not enforced by local management. Enforce the local procedure and require the Ground Controller to keep the exit points open/unblocked.
PDK Controller described a less than standard runway separation event when a second aircraft landed with the prior arrival still on the runway; the reporter listed non compliance with local SOP requirements as a causal factor.