Light aircraft pilot reported an NMAC on approach to GON airport.

Date: 2022-08 · Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear · Phase: approach

Anomalies: atc-issue-all-types|conflict-nmac

Synopsis

Light aircraft pilot reported an NMAC on approach to GON airport.

Narrative

After an IFR flight I transitioned from Providence Approach to the Groton New London Tower. I was cleared for the visual Runway 33; descending from the northwest out of 3000 ft. The aircraft was oriented inline with a downwind entry to Runway 33 without any maneuvering. I reported to Groton Tower NW descending cleared for the visual 33. I was told to report mid field Runway 33. I was told there was an aircraft near the shoreline heading toward Long Island Sound. As I descended; I was given another report that the aircraft was to my right (not sure if he announced below) I had the aircraft on ADS-B screen location and altitude but no visual. (I did not report anything to the Tower). I continued to monitor the location of the traffic and began to adjust my flight path using ADS-B location. As I arrived mid field the other aircraft reported mid field. I then announced also. The Tower asked or told me about the other aircraft. (Evidently the other aircraft was doing pattern work.) Through this entire scenario the other aircraft was to my right and below; not visible from my seat. (Low wing and left seat). The other aircraft never made any verbal contact with the Tower while I was on frequency; other than mid field.After some thought and review; from my perspective I was conditioned to have ATC provide some clear statement about what I should do with the reported traffic. (Follow traffic; go ahead of traffic; do a 360 turn; etc.) I do not recall any clear defined action until I was cleared to land and the other was cleared behind me. I took immediate action to turn left away from the adjacent aircraft. ADS-B suggested 100 to 200 vertical separation. Horizontal unknown. I was busy flying the plane. I've been in the aviation business all my life and have been a safety technical fellow. If I did something wrong I want to hear it and I want to assure safety practices are working for everyone.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.