Date: 201206
Local time of day: 1201-1800
Location: CID.Airport, IA
Light: Daylight
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower CID
Second aircraft: SR20
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Airport; Procedure
Primary problem: Airport

Narrative: Aircraft X had taxied to Runway 9 for departure.  Aircraft Y; SR20; called from the east tee hangars for VFR departure. Due to construction closing Taxiway C; the only route from the east tee hangars to active runways involved a back taxi on Runway 13/31. Aircraft Y was given departure instructions and taxied to Runway 13; holding short and expecting back taxi on Tower frequency. Meanwhile; Aircraft X was issued takeoff instructions on Runway 9. Immediately afterward; Aircraft Y was issued back taxi instructions on Runway 13; and instructed to hold short of Runway 9. The pilot read back; 'Back taxi Runway 13 and stay south of Runway 9.' Aircraft Y began taxi northwest on Runway 31 as Aircraft X was rolling on Runway 9. Aircraft Y taxied at a fairly high rate of speed nearing the intersection with Runway 9; making me pay close attention as Aircraft X was also nearing the intersection on Runway 9 takeoff roll. Aircraft Y did slow before reaching the intersection; actually making a 180 to prepare for takeoff from south of the Runway 13/Runway 9 intersection. However; the aircraft did go across the painted LAHSO [land and hold short] hold lines on Runway 31 while making the 180.My particular concern is; why does the CID airport have LAHSO hold lines painted on Runway 31? There is no local procedure for LAHSO on Runway 31. We cannot perform LAHSO operations on Runway 31. There are no such hold lines painted on any of our other runway intersections; with the one obvious exception being on Runway 9 where we actually have LAHSO procedures in place (Runway 9 hold short of Runway 13/31). In my opinion; these additional unnecessary hold lines only create confusion among controllers and pilots. As stated above; the introduction of LAHSO-type hold short markings on a runway where we do not and cannot perform LAHSO only creates confusion. An aircraft instructed to taxi on Runway 13 (north of Runway 9) and told to hold short of Runway 9 can judge their hold short point on their own; given proximity to the runway edge markings. There are no LAHSO-type markings on that side of Runway 9. On the south side; though; a pilot who might judge their hold short spot by the runway edge markings could cross the LAHSO painted lines; but this can create confusion and concern for the controller; as well as pilots using Runway 9/27. Either we need these hold short lines on all the runways; or we only need them for approved LAHSO runways. This extraneous marking on Runway 31 is confusing and unnecessary




Synopsis: CID Controller reported LAHSO markings on Runway 31 create confusion as LAHSO is not permitted on Runway 31.