Date: 201902
Local time of day: 1201-1800
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G CVC
ATC / advisory: CTAF CVC
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Confusion; Communication Breakdown; Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Procedure; Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: Due to the bad weather on the north of the zone; we decided to change our planned destination and aim for another airport to the east before the departure from our base. We checked NOTAMs and rapidly prepared the navigation log.Once arriving in the vicinity of the destination airport; we heard one airplane landing on Runway 28. We decided to enter the traffic pattern in downwind directly. Thus we positioned our airplane in the left traffic pattern for Runway 28. We did 2 touch and go using left traffic pattern. On the third left downwind; we departed to the south for some maneuver practice because one IFR arrival was on a 5 mile final and we didn't want to turn in final just in front of him. After 5 minutes; we came back to the airfield and entered in a left midfield traffic pattern. We were doing our radio calls and monitoring the CTAF/UNICOM frequency. At this point we thought we were alone and that no other airplane was in the traffic pattern. We announced our self in base and then on final for Runway 28. At this point; a Piper Cherokee who was on final in front of us did a go around and said it on the CTAF/UNICOM frequency. There were no risk of collision as the Piper was approximately 1 km in front of us but we didn't expected to see any airplane on the final because we heard nobody on the radio. We continued our approach and did a full stop landing.In the end what we understood/ Contributing factors:The Cherokee pilot did his message with 'Cherokee X; downwind/base/final runway 28; Covington' Because there is another airport named Cherokee (CNI) 30 nm North West of the field with a similar TAF/UNICOM frequency I thought this airplane was actually doing traffic pattern at the Cherokee airport and not at Covington. Thus I didn't paid much attention to the messages starting with Cherokee and missed that the Piper was not operating from Cherokee but at Covington.Because we were flying the left traffic pattern (due to the convention in most airport and lack of preparation of our navigation/destination airport); the Piper Cherokee flying the traffic pattern wasn't able to locate us visually despite our radio called (I didn't say 'left downwind/base' but just 'downwind/base'). The situation was not dangerous because:-We always kept our eyes outside; and once on final we identified the airplane in front of us just before he made the radio call after we announced ourselves in final and I totally understand his decision because we were not able to see us since the beginning. In fact we were 1km behind him but he couldn't know.-We got lucky and didn't arrived in front of each other; me in base and the Piper on final. Corrective actions: -I will prepare better my navigation and especially the arrival on an unknown airport. I will especially look for the little sign for an unconventional (right) traffic pattern.-I will pay attention to the radio calls even if they don't start with the same location I am operating from.-I will try to incorporate 'left/right' before saying down-wind/base in my radio calls.




Synopsis: GA pilot reported an airborne conflict with an aircraft on final in the pattern after missing the other aircraft's position calls.