General aviation pilot reported saturation of air-to-air radio communications at 52F due to multiple airports using the same CTAF frequency.

Narrative

This report does not relate to a single incident; but rather a concern that has developed over several months. I flew Aircraft X out of 30F in the North Texas area and frequently make scenic VFR flights in the north and northwest areas of the D10 TRACON area. Nearly all of the small non-towered airports in this general area use the same CTAF frequency - 122.9. There are up to a couple dozen small airports that use this frequency. Most of these airports are not so busy that traffic at that airport dominates the frequency … with one; dangerous exception. Aero Valley (52F) is too busy to be using this frequency and needs its own frequency. During busy times of the day; CTAF transmissions from 52F on 122.9 account for 75% - 90% of the radio calls; thereby crowding out other airports. During peak times; radio calls at 52F are nonstop and leave no room for calls at other airports. 52F needs its own frequency; similar to what the FAA did for TRL a few years ago. I also note that T67 Hicks has its own CTAF frequency. The overall characteristics of 52F much more aligns with these two airports; as opposed to all the other small grass strips in this sector that use 122.9.This situation creates several safety concerns. When 122.9 is jam packed with 52F traffic; it discourages pilots at other airports from making appropriate radio calls. When 122.9 is jam packed with 52F radio calls; it creates a dramatically higher workload environment for pilots at other airports who are genuinely trying to keep up and pick out non-52F radio calls. Over time; when I'm monitoring 122.9 when radio calls are dominated by 52F; I've caught myself falling into the expectation bias trap where I've tended to tune out the uninterrupted stream of radio calls that 'don't pertain to where I'm going.' I realize that changing a CTAF frequency at an airport has its own risks. It takes time to disseminate information on a frequency change and pilots may use the wrong frequency until the new frequency is widely known. Mitigating against this risk is a well-developed 'community' at 52F that can help get the word out.Also; moving 52F off 122.9 will mean that pilots operating at nearby airports will not be aware of 52F traffic. In my opinion; this isn't really a meaningful risk; as any local pilot knows that there is ALWAYS traffic in and out of 52F. Pilots familiar with this area of the Metroplex know to generally avoid the 52F area unless you're specifically going there. I would request that the FAA examine this situation and consider changing 52F to a different CTAF frequency.