Date: 201305
Local time of day: 1201-1800
Location: ACT.Airport, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Taxi
ATC / advisory: Tower ACT
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Flight Instructor
Human factors: Distraction; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Airport; Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Upon landing at Waco airport on Runway 14; we proceeded to roll out on the full length of the runway. As we approached Taxiway B3; we were instructed by the Tower Controller to exit on Taxiway B2. At the moment; approaching B3 we assumed that B2 was the next taxiway turnoff. As we rolled off the end of Runway 14; we found ourselves on the overrun to Runway 14 (chevron taxiway marking). At this point we were approaching Runway 19 and slowed to stop to query the Tower Controller regarding our taxi instructions which did not include crossing Runway 19. Before we were able to question the Tower Controller; a second Controller instructed us to do a 180 turn on the runway and exit on Taxiway B3. As instructed; we complied with those instructions and proceeded to exit the Runway at B3. Approximately 1 minute later; the Tower instructed us to contact the Approach/Tower phone number to discuss a possible pilot deviation. We learned during that phone conversation; that the overrun for Runway 14 is a non-movement area. Further; because we had rolled out in this non-movement area; we were in violation of a runway incursion; even though we never moved on to the adjacent Runway 19 at any point. Subsequent to our phone discussion with the Tower Supervisor; we are still rather confused as to what we did wrong other then taxing on to the overrun portion of Runway 14. It should be noted there are no airport signs; directions or notes on the airport surface or more importantly; on our airport runway charts that identify this area as a non-movement area.

Callback: The reporter stated that he is still unclear what the runway incursion event was which the Controller referenced. His concentration was on the short field landing and at the time he was traveling at no more than 5 miles per hour and missed the taxiway sign so thought what turned out to be the overrun was Taxiway B-3. The reporter stated that the Controller whom he spoke with stated that they were having 'all kinds of problems with aircraft in that area.' What the reporter believes is that the signage on Runway 14 approaching the runway end should state that area is a non-movement area because it is not possible to see the overrun chevrons in a short aircraft.



Synopsis: A pilot landed on ACT Runway 14 and after missing Taxiway B-3 entered the area beyond the runway's end where he was given a 180 degree turn to Taxiway B-3 and advised of a runway incursion in the non-movement area.