Narrative:

Airport was moderately busy. More than 5, less than 10 operations monitored during 10-15 mins prior to approach. Operations were using runway 35. Called in 'east over the lake, landing.' tower's response was 'cleared direct to runway 17.' called back for confirmation of runway 17. Response was, 'did I say runway 17? Cleared to land runway 35.' no request for another call-up on final. Descended 2500 ft to pattern altitude 1500 ft. Pwred back to begin base descent. Tower cleared a cessna for touch-and-go, no statement of '#2.' after tower cleared aircraft #2, I scanned to the right, looking for aircraft #2. Aircraft #2 appeared, overflying by 100 ft, appeared to be making base turn from downwind. I broke to south about same time tower called 'there are 2 of you out there.' I called that I had broken off to the south. Tower responded to the effect that 'I didn't anticipate you arriving so soon.' continued descending to assure clearance from aircraft #2. Began right turn back to base. Aircraft #2 below, turned to final. I announced I was doing a 360 degree turn to achieve spacing. Tower approved maneuver. Climbed back to pattern altitude during circle. Called in 'long final' before pulling power. Tower stated I was 'still cleared to land.' no calls from aircraft #2 through the incident. Aircraft #2 not in sight. No tower clearance for another touch-and-go during taxi to north end of airport. This incident appears to be caused by inattn in tower -- 2 mistakes on 1 approach: clearing me to runway 17, then clearing aircraft #2 for touch-and-go without sequencing. Tower did not notice conflict until I had already seen aircraft #2 appear over my right wing. I was not instructed to call in on base or final, but doing so probably would have alerted tower before the conflicting clrncs were issued.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 EXPERIENCES NMAC WITH ANOTHER C172 IN TFC PATTERN AT TKI.

Narrative: ARPT WAS MODERATELY BUSY. MORE THAN 5, LESS THAN 10 OPS MONITORED DURING 10-15 MINS PRIOR TO APCH. OPS WERE USING RWY 35. CALLED IN 'E OVER THE LAKE, LNDG.' TWR'S RESPONSE WAS 'CLRED DIRECT TO RWY 17.' CALLED BACK FOR CONFIRMATION OF RWY 17. RESPONSE WAS, 'DID I SAY RWY 17? CLRED TO LAND RWY 35.' NO REQUEST FOR ANOTHER CALL-UP ON FINAL. DSNDED 2500 FT TO PATTERN ALT 1500 FT. PWRED BACK TO BEGIN BASE DSCNT. TWR CLRED A CESSNA FOR TOUCH-AND-GO, NO STATEMENT OF '#2.' AFTER TWR CLRED ACFT #2, I SCANNED TO THE R, LOOKING FOR ACFT #2. ACFT #2 APPEARED, OVERFLYING BY 100 FT, APPEARED TO BE MAKING BASE TURN FROM DOWNWIND. I BROKE TO S ABOUT SAME TIME TWR CALLED 'THERE ARE 2 OF YOU OUT THERE.' I CALLED THAT I HAD BROKEN OFF TO THE S. TWR RESPONDED TO THE EFFECT THAT 'I DIDN'T ANTICIPATE YOU ARRIVING SO SOON.' CONTINUED DSNDING TO ASSURE CLRNC FROM ACFT #2. BEGAN R TURN BACK TO BASE. ACFT #2 BELOW, TURNED TO FINAL. I ANNOUNCED I WAS DOING A 360 DEG TURN TO ACHIEVE SPACING. TWR APPROVED MANEUVER. CLBED BACK TO PATTERN ALT DURING CIRCLE. CALLED IN 'LONG FINAL' BEFORE PULLING PWR. TWR STATED I WAS 'STILL CLRED TO LAND.' NO CALLS FROM ACFT #2 THROUGH THE INCIDENT. ACFT #2 NOT IN SIGHT. NO TWR CLRNC FOR ANOTHER TOUCH-AND-GO DURING TAXI TO N END OF ARPT. THIS INCIDENT APPEARS TO BE CAUSED BY INATTN IN TWR -- 2 MISTAKES ON 1 APCH: CLRING ME TO RWY 17, THEN CLRING ACFT #2 FOR TOUCH-AND-GO WITHOUT SEQUENCING. TWR DID NOT NOTICE CONFLICT UNTIL I HAD ALREADY SEEN ACFT #2 APPEAR OVER MY R WING. I WAS NOT INSTRUCTED TO CALL IN ON BASE OR FINAL, BUT DOING SO PROBABLY WOULD HAVE ALERTED TWR BEFORE THE CONFLICTING CLRNCS WERE ISSUED.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.