Date: 201809
Local time of day: 0601-1200
Location: IWA.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 7
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D IWA
ATC / advisory: Tower IWA
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Confusion
Second reporter function: Pilot Not Flying; Instructor
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I was on a takeoff and landing evaluation so we were flying in the pattern with full-stop taxi backs at [the] airfield. On our 6th cycle into the pattern we were given clearance to land on 12C; making right traffic. We acknowledged ATC with a read back for Runway 12C. After turning into our right base to final approach I noticed another aircraft coming in about 200 ft above us onto the same runway heading 12C. Being fairly new to aviation; I asked the evaluator if this was supposed to happen. He immediately called Tower to confirm our runway assignment and was told that we were given a runway assignment of 12R and that we were approaching the wrong runway and to alter course to perform a go-around over the correct runway. Following that; we were placed back in a right traffic pattern and after landing; we were grounded by Tower as they had closed the pattern. Upon listening to the ATC recording after the flight; I was able to confirm that ATC gave us a runway assignment of 12C; as we had originally believed. The traffic at the time of the event was less than I have seen in a few weeks; so I do not believe heavy traffic to be a contributing factor. A possible contributing factor is that prior to being given our runway clearance; tower had an interaction with another aircraft that didn't use the first available taxiway exit from the runway because their previous directions were to exit Charlie 3 to Charlie 1; back to 12L for next takeoff and they were expecting similar instructions. Tower had an audible frustration since they hadn't taken.


Second narrative: We were in the downwind on 12R setting up for full stop taxi backs. Tower told us follow [the aircraft]; traffic ahead of you is for different runway 12C clear to land. I repeated back 12C clear to land. Turning base we set up for 12C and continued on final for 12C then I heard tower make a call to another plane saying follow the Cessna number 2 12R clear to land. That's when I verified with Tower on final that we were cleared to land 12C; then Tower said negative you are for 12R go around; offset to the right; you were cleared for 12R. Then [another] plane flew about 200 feet above us. This event was caused by Tower's error in my opinion believing he cleared us for 12R when he clearly said 12C. The airport I fly out of can be extremely busy at times; but on this particular morning there were only a few of us in the pattern. The Tower also has trainees; but in this particular instance it was the overseer who was working the Tower. He gave us a little attitude after this event and told us make right traffic for 12R really emphasizing his word choice. There was no apology on his part and we were told to make a full stop terminate because the pattern is closed. The Tower Manager reviewed the recordings and called my manager to inform him that the overseer was in the wrong and we had done exactly what we were instructed to do.


Synopsis: C172 Student and Instructor reported a NMAC airborne conflict in the traffic pattern.