Narrative:

The situation was caused by the changing of the unicom frequency at 33N. It is an airport I have visited several times and has been 123.000 for as long as I can remember so I simply checked the weather; checked notams; reviewed the charts (including frequencies); etc. What I didn't do like I would have if I was visiting an airport I either never or recently visited is check the a/FD.the situation is probably obvious at this point. Ultimately; I flew into the airport announcing on the incorrect frequency. Thankfully; due to the benefits of adsb; I was aware that another aircraft approaching was 'not communicating'. I even tried hailing them on the radio. So I gave way to him and visually checked for other aircraft. At this point I considered if my radio was possibly inoperative. I requested a radio check and received a response. I dropped off my passengers and departed the airport announcing on the deprecated frequency. After landing at my home airport my passengers called me telling me that there was a bulletin up in the FBO calling out the frequency change for the airport. Upon checking the a/FD; I verified the frequency had changed.I recognized from this flight that my preflight should always include an airport details and a/FD scan. Being a low hour pilot I am constantly tuning my preflight. I am always trying to learn. I believe I handled the flight safely given my transmissions on the incorrect frequency. Tools like adsb I do believe are making flying safer offering better situational awareness. But knowing that every aircraft doesn't have it I am always keeping my eyes out the windows as well. I also take advantage of having passengers keeping their eyes out as well which I definitely did in this flight.I do think there was an opportunity for the airport to coincide their frequency change with the release of the regions charts to help ensure all sources were correct. The error was on my part being that I only referenced the chart. But if the frequency change coincided with the february release of the chart; I would have caught it.

Related reports:

Google
 

Original NASA ASRS Text

Title: GA pilot reported using the incorrect CTAF frequency due to a recent airport frequency revision.

Narrative: The situation was caused by the changing of the UNICOM frequency at 33N. It is an airport I have visited several times and has been 123.000 for as long as I can remember so I simply checked the weather; checked NOTAMs; reviewed the charts (including frequencies); etc. What I didn't do like I would have if I was visiting an airport I either never or recently visited is check the A/FD.The situation is probably obvious at this point. Ultimately; I flew into the airport announcing on the incorrect frequency. Thankfully; due to the benefits of ADSB; I was aware that another aircraft approaching was 'not communicating'. I even tried hailing them on the radio. So I gave way to him and visually checked for other aircraft. At this point I considered if my radio was possibly inoperative. I requested a radio check and received a response. I dropped off my passengers and departed the airport announcing on the deprecated frequency. After landing at my home airport my passengers called me telling me that there was a bulletin up in the FBO calling out the frequency change for the airport. Upon checking the A/FD; I verified the frequency had changed.I recognized from this flight that my preflight should always include an airport details and A/FD scan. Being a low hour pilot I am constantly tuning my preflight. I am always trying to learn. I believe I handled the flight safely given my transmissions on the incorrect frequency. Tools like ADSB I do believe are making flying safer offering better situational awareness. But knowing that every aircraft doesn't have it I am always keeping my eyes out the windows as well. I also take advantage of having passengers keeping their eyes out as well which I definitely did in this flight.I do think there was an opportunity for the airport to coincide their frequency change with the release of the regions charts to help ensure all sources were correct. The error was on my part being that I only referenced the chart. But if the frequency change coincided with the February release of the chart; I would have caught it.

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.