Skylane 182/RG Turbo Skylane/RG
Air Traffic Control Fully Certified
Confusion; Situational Awareness; Communication Breakdown
ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance
Procedure; Human Factors
I taxied a C182 to the runway for an Intersection C departure. I marked the strip as required. A PA28 was in the touch and go pattern for the runway. Local Control cleared the C182 for take off after the PA28 crossed the landing threshold but not yet past Intersection C not realizing that the C182 was at the intersection instead of full length. Our SOP allows for written communication for intersection departures. I recommend all intersection departures require a verbal APREQ.
I was working Local Control. Ground Control taxied a C182 to the runway at Taxiway C Intersection. A PA28 was doing a touch and go on the runway. I thought the C182 was at the end of the runway and cleared him for take off. Ground Control caught the mistake and promptly told me. I stopped the C182 from takeoff roll in front of the PA28 but the C182 passed the hold short line. The PA28 also stopped on the runway. The C182 was told to make a 180 and hold short of the runway at C again. The PA28 exited the runway and taxied back to the runway to depart again. The C182 then departed the runway at C Intersection. The PA28 departed and completed more touch and go's. Neither pilot complained. I need to make sure I see where the aircraft is prior to clearing him for take off. I need to look at the strip marking in front of me to make sure where the aircraft is supposed to be.
Ground Controller described a go around event when the Local Controller failed to note the requested intersection departure on the strip; assumed traffic was at the end of the runway and cleared the aircraft for takeoff.