Date: 201909
Local time of day: 0601-1200
Location: LVK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class D LVK
ATC / advisory: Tower LVK
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Distraction; Communication Breakdown
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: The incident occurred on a very busy afternoon at LVK with many aircraft in pattern for both parallel runways. Approaching from north; I was cleared to make right downwind for Runway 25R and follow traffic ahead turning downwind. I reported 'traffic in sight' and continued the approach. They were approximately 2 miles ahead of me at this point. As I approached the downwind; the Tower informed me about some other traffic that had just taken off from 25R. I misheard this communication and thought the aircraft is waiting for me to land. Hence I asked the Tower 'what do you want me to do'; expecting either 'extend downwind' or 'expedite'. The Tower replied 'I want you to come in and land'. This created a false sense of urgency in me; even though the Tower never used the word 'expedite'. Next; I heard an exchange between Tower and the #1 traffic ahead of me. They were initially told to extend their downwind; but then immediately told to disregard and turn base. They acknowledged; and confirmed starting their base turn. Next; as I flew downwind past the approach end of the runway; I momentarily switched my attention to pre-landing checks and lost sight of the #1 traffic in the process. After some time; I made an unsafe assumption that the #1 traffic had turned base long time ago; and hence must be already on final by now; and decided to make my base and then final turns. At this point Tower asked me if I still had the #1 traffic in sight. Since I did not; Tower asked me to initiate a go-around; and return back to downwind. I did so; and landed without any further event.After I initiated the go-around; the other aircraft mentioned on frequency that they had taken some evasive actions to keep away from us. After landing and evacuating the runway; ATC gave me a phone number to call. I was told that the ATC did not know exactly how close it was. However; it was a mistake for me to continue without knowing exactly where the #1 aircraft was. After returning back; I reviewed the communication on LiveATC and my ForeFlight track logs to reconstruct the scenario. I took the help of my CFI to understand how things went wrong and learned following lessons. 1. Use standard radio phraseology. Do not say 'roger' if unclear about some instruction. Ask the Tower to 'say again'. 2. Most importantly - if I am following someone and I lose sight of them for any reason; ask the Tower for help. Do not make assumptions about their position. 3. Do not get pressured to do anything I am not ready for.




Synopsis: C172 pilot reported conflicting with traffic the C172 was instructed to follow on final.