Date: 201207
Local time of day: 1201-1800
Location: APA.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: Tower APA
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness; Confusion
Second reporter function: Local
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew; Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Aircraft; Chart Or Publication; Human Factors
Primary problem: Ambiguous

Narrative: Aircraft was directed to move up and hold short at A16 for a planned departure on 35R. The hold bar is located at the intersection of Alpha and A16 where the aircraft would block other taxi traffic on Alpha from passing behind to the end for 35R departures. This hold bar location seemed to be extremely far away from the runway surface. The aircraft was moved passed the hold bar to clear the taxiway anticipating the correct hold to be ahead closer to the runway. The aircraft was immediately stopped just passed the hold bar when a hold bar closer to the runway was not seen. Tower advised the aircraft of the error and requested a call by phone which was accomplished later. Aircraft was cleared for takeoff and departed. The aircraft and the pilot were at APA for their first time and this departure was the first takeoff from APA. The lack of local surface operational experience was a factor associated with the occurrence. The airport diagram could be improved by showing the location of the hold short lines on the diagram to assist pilots with preflight understanding of the airport's configuration.


Second narrative: I was working Local and I had cleared a corporate jet to land Runway 35R. Ground Control had taxied a small aircraft to the South Run up area; an area that is not published or marked on the airport and sits on the east side of Taxiway A near Runway 35R. As you know; APA does not issue a runway assignment to an aircraft who needs a runup until they have completed their runup. The A16 pad; otherwise known to management as the South Run up area; is about 50 FT away from the hold lines for Runway 35R at A16. They were struggling to get the small aircraft to correctly respond to the clearance because the initial instruction to Runway 35R at A16 was read back as full length. The procedure sucks. As he was leaving the pad; they shipped him to me. I was checking the winds when the FLM who was giving a skills check to the GC yelled out 'watch the Bonanza;' in which case I observed him cross the hold line with his entire aircraft and then stop and I sent the corporate jet around. I hesitated slightly because I was trying to determine if the corporate jet could sidestep to Runway 35L; but he was too close so I sent him around. The small aircraft acknowledged his error on frequency. I spoke with the pilot on the phone today and he stated he was not familiar to APA and he didn't exact to be at the hold bars to soon and expected them closer to the runway.


Synopsis: A pilot crossed the APA Runway 34R hold short line on Taxiway A16 because it is so far from the runway and aircraft stopped there would block Taxiway A.