Narrative:

I was on an IFR flight to ZZZ at 4000 feet. Approach assigned a heading of 235 degrees over zzzzz with the direction to expect a straight in visual approach to runway xx. I announced my position over unicom 10 miles out; later turning base to final and again 2 mile final. ZZZ has a part time tower that was closed. I was navigating with a new upgrade to my garmin 1000. I looked up the CTAF 100 miles out and set the frequency identified in the chart for unicom. This was third flight with the new charts feature and I misread the unicom as the CTAF when in fact it should have been the closed tower frequency. The controller cleared me for the approach but did not advise of any traffic in the area. I did not receive any aircraft proximity warnings on TCAS or adsb. I descended from 3000 feet about 4 miles out and did not see any traffic in area. The approach and landing were uneventful. Upon landing; I was approached by a pilot who said he was turning base and saw that we were too close and he did a 180 before landing without incident.TCAS did not report a proximity warning. I have reported it to maintenance. Adsb did not report a proximity warning. Not sure why.I should have double checked the CTAF against my efb and would have discovered I was transmitting on the wrong frequency.I did not see the other aircraft. He said he was doing touch and go operations. I was scanning a wide area but it was near dusk. When he taxied near me; to tell me about the incident; he did not have on any lights except rotating beacon. This is reported due to the other pilot's notice to me that we had a close encounter. He indicated that he was a low time VFR pilot. The chart he showed me was 10 years old. I am not sure that an actual close encounter by practical standards occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: TBM pilot reported an NMAC in the pattern; citing use of the incorrect CTAF frequency as contributing.

Narrative: I was on an IFR flight to ZZZ at 4000 feet. Approach assigned a heading of 235 degrees over ZZZZZ with the direction to expect a straight in visual approach to Runway XX. I announced my position over Unicom 10 miles out; later turning base to final and again 2 mile final. ZZZ has a part time Tower that was closed. I was navigating with a new upgrade to my Garmin 1000. I looked up the CTAF 100 miles out and set the frequency identified in the chart for Unicom. This was third flight with the new charts feature and I misread the Unicom as the CTAF when in fact it should have been the closed Tower frequency. The Controller cleared me for the approach but did not advise of any traffic in the area. I did not receive any aircraft proximity warnings on TCAS or ADSB. I descended from 3000 feet about 4 miles out and did not see any traffic in area. The approach and landing were uneventful. Upon landing; I was approached by a pilot who said he was turning base and saw that we were too close and he did a 180 before landing without incident.TCAS did not report a proximity warning. I have reported it to Maintenance. ADSB did not report a proximity warning. Not sure why.I should have double checked the CTAF against my EFB and would have discovered I was transmitting on the wrong frequency.I did not see the other aircraft. He said he was doing touch and go operations. I was scanning a wide area but it was near dusk. When he taxied near me; to tell me about the incident; he did not have on any lights except rotating beacon. This is reported due to the other pilot's notice to me that we had a close encounter. He indicated that he was a low time VFR pilot. The chart he showed me was 10 years old. I am not sure that an actual close encounter by practical standards occurred.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.