Date: 201706
Local time of day: 1201-1800
Location: HIO.Airport, OR
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Initial Climb
Airspace: Class D HIO
ATC / advisory: Tower HIO
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Communication Breakdown; Workload
Second reporter function: Local
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: This incident happened during a check ride. I took off Runway 31L at HIO Airport. Upon turning crosswind for a left pattern for Runway 31L; Tower issued to turn base for Runway 2. We were cleared to land on Runway 2 at HIO Airport. The examiner called for a go around. I executed the go around and reported to Tower that I was doing so. Tower responded by saying to stay to the right of an aircraft that was approaching towards us; to our left; opposite direction. They issued the resulting aircraft the same order. Essentially insuring that we avoid each other. At this point; I heard Tower contact an aircraft and tell them to turn left. Now; I don't know if the Tower issued that order to the traffic in front and to the left of us; or another one; but the traffic ended up turning to their left in front of our flight path. To avoid them; we turned to our left; out of their flight path. We made left crosswind for a left pattern for Runway 2 afterward. Upon landing and clearing the runway; the examiner contacted ground in order to get a better idea of what happened. He ended up requesting a number and calling that number to get to the bottom of it. He followed up by saying that wasn't my fault and that he was going to call them after we were done.As far as why I think it happened; I believe it was a mixture of ATC changing runways; miscommunication on their part; and workload. There seemed to be a good amount of aircraft and helicopter traffic. Some of the error could have come from the aircraft mishearing their tail number and executing the turn regardless. I can't say for sure; all I know is a plane began turning into my flight path and I avoided it. Also; I'm not really sure why that aircraft was flying towards the Runway environment; opposite landing and departing aircraft; at such a low altitude.


Second narrative: I was training on Local Control. The wind was favoring Runway 2 so we changed from Runway 31L/31R. There were two [aircraft] in the pattern for Runway 31R and they were instructed to enter a right downwind for Runway 2. Aircraft X was in left traffic for Runway 31L and was instructed to enter left base for Runway 2. After established on base; I cleared aircraft X for a touch and go. Aircraft X advised that they were unable to accept Runway 2 for touch and go's and requested a full stop. I responded with 'roger' and continued on with clearing the next aircraft for landing. Thinking that aircraft X was a full stop; I didn't advise him of the aircraft off the departure end entering the right downwind for Runway 2.Aircraft X advised that he was on a go around. I checked the upwind to ensure that aircraft Y was not a factor. It was then that I saw aircraft Y had turned final for Runway 20 and was now opposite direction with aircraft X. I told aircraft X about aircraft Y and told him to turn left. Aircraft X initially turned right so I told aircraft Y to turn right as well; but when aircraft X turned back to the left I told aircraft Y to turn left. The two aircraft missed by a few hundred feet at most.I assumed that when aircraft X said he was unable to make a touch and go; that he would make a full stop. Also; aircraft need to ensure that when they line up with the runway the runway numbers match the clearance that they were given. Even if aircraft X had made a full stop; aircraft Y was still going to land opposite direction on Runway 2.


Synopsis: GA pilot on a check ride and Local Controller reported an airborne conflict with another aircraft after departing Runway 31L and being cleared to enter left traffic for Runway 2.