Narrative:

Help! This is a serious and ongoing issue. I've seen multiple issues because of the unmonitored unicom frequency (122.95) is being mistaken for the CTAF. I was taxing on taxiway F at and. A student pilot with an instructor were on short final 23 in aircraft Y. The pilot was a newer student from what I could tell and was landing very long where 2/3 runway appeared to be aiming point. They had flown typical downwind; base; final and made all the calls. Suddenly as they crossed the threshold aircraft Z took off without announcement from 35 and they would have collided. The pilot turned aggressively up/left and went around missing aircraft Z less than 50 ft. I chimed in on the radio and told them good job on go around and the instructor asked if the aircraft Z pilot was making radio calls. A few seconds later the aircraft Z pilot chimed in and was on 122.95 and did not hear the pilot in aircraft Y. Another incident; we were taking off one evening from runway 5 and the sun was very bright. We made all of our calls and looked for traffic. None was seen and we announced and took off. About 30 seconds later; aircraft a pilot chimes in and apologized for being on the wrong frequency (122.95) and explained he was on 1.5 mile final and aborted his landing. I later spoke to him on the ground and he said he glanced at the chart and saw the last number and used it. I've spoken to numerous pilots and now monitor 122.95 and it happens several times a week. All of my students now monitor 122.95 as a backup. A few months back a friend and I were departing 23 and a pilot practicing an approach into 5 on a sunny day. We were climbing out in my [aircraft] which has a poor sight picture on climb but we were meandering left and right and looking for traffic as best we could. A friend was circling the VOR and heard us on the radio and mentioned they saw a plane on final 5 (I think ILS 5). Thank god they keyed up and told me. We lowered the nose and looked and he was on top of us within 500 ft. We tuned 122.95 and sure enough; he was on the wrong frequency...122.95. Another student who had not flown in 20 years came and did his biannual and renewed his medical. He was soloing after many years of not flying. An aircraft cut him off and he saw him and went around him on the downwind; extended out and gave him time to land. I happened to tune my handheld to 122.95 and [aircraft pilot] was on the wrong frequency. I understand this is an untowered field; and people do not even need radios. The problem is these pilots are keying up on the radio and have an expectation that radio communication is happening and I believe people are taking extra risk because they believe they are talking on the radio. The 122.95 needs to be removed from the chart before the next printing. I also asked the airport manager to see if he could add a message onto the ASOS recording (I know some have this option) for pilots to please use 123.6. He did not think this was possible. He did send a letter to tenants but the problem is transient traffic. This is a serious issue. Help us out before someone gets killed here.

Related reports:

Google
 

Original NASA ASRS Text

Title: A general aviation pilot reported many pilots are confused by the charted frequency depiction for Anderson Regional Airport.

Narrative: HELP! This is a serious and ongoing issue. I've seen multiple issues because of the unmonitored Unicom frequency (122.95) is being mistaken for the CTAF. I was taxing on taxiway F at AND. A student pilot with an instructor were on short final 23 in Aircraft Y. The pilot was a newer student from what I could tell and was landing very long where 2/3 runway appeared to be aiming point. They had flown typical downwind; base; final and made all the calls. Suddenly as they crossed the threshold Aircraft Z took off without announcement from 35 and they would have collided. The pilot turned aggressively up/left and went around missing Aircraft Z less than 50 ft. I chimed in on the radio and told them good job on go around and the instructor asked if the Aircraft Z pilot was making radio calls. A few seconds later the Aircraft Z pilot chimed in and was on 122.95 and did not hear the pilot in Aircraft Y. Another incident; we were taking off one evening from runway 5 and the sun was very bright. We made all of our calls and looked for traffic. None was seen and we announced and took off. About 30 seconds later; Aircraft A pilot chimes in and apologized for being on the wrong frequency (122.95) and explained he was on 1.5 mile final and aborted his landing. I later spoke to him on the ground and he said he glanced at the chart and saw the last number and used it. I've spoken to numerous pilots and now monitor 122.95 and it happens several times a week. All of my students now monitor 122.95 as a backup. A few months back a friend and I were departing 23 and a pilot practicing an approach into 5 on a sunny day. We were climbing out in my [aircraft] which has a poor sight picture on climb but we were meandering left and right and looking for traffic as best we could. A friend was circling the VOR and heard us on the radio and mentioned they saw a plane on final 5 (I think ILS 5). Thank God they keyed up and told me. We lowered the nose and looked and he was on top of us within 500 ft. We tuned 122.95 and sure enough; he was on the wrong frequency...122.95. Another student who had not flown in 20 years came and did his biannual and renewed his medical. He was soloing after many years of not flying. An aircraft cut him off and he saw him and went around him on the downwind; extended out and gave him time to land. I happened to tune my handheld to 122.95 and [aircraft pilot] was on the wrong frequency. I understand this is an untowered field; and people do not even need radios. The problem is these pilots are keying up on the radio and have an expectation that radio communication is happening and I believe people are taking extra risk because they believe they are talking on the radio. The 122.95 needs to be removed from the chart before the next printing. I also asked the airport manager to see if he could add a message onto the ASOS recording (I know some have this option) for pilots to please use 123.6. He did not think this was possible. He did send a letter to tenants but the problem is transient traffic. This is a serious issue. Help us out before someone gets killed here.

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.