I know it goes without explanation, but it should be stated again:
CTAF is NOT UNICOM; additionally, not every airport has UNICOM. Now, that needs some explaining.
At a given towered field (I’ll use KLAS and PANC for my examples), they do not have a CTAF, because they are always open; however, in the cases where they have closed (for example, when KLAS had to close during a COVID outbreak, or when an earthquake closed PANC), the CTAF was the combined tower frequency. In KLAS’ case, it was 119.9; in PANC’s case, it was 118.3.
For both of those airports, the UNICOM frequency is 122.95. See how that varies?
I’ll use another example: KSMO and KLAX.
KSMO closest at 9pm LT. At that point, the CTAF is the Tower frequency, 120.1. LAX doesn’t close; if it ever had to, it will use the combined tower frequency at that time (which would be depicted in the ATIS or given by the TRACON).
Both airports use 122.95 as their UNICOM.
So as one can see, remaining on a single UNICOM frequency and using that as CTAF would be a problem, especially if both airports are within range of each other. SMO is 5nm north of LAX.
Also, if need be, for a given airport that may or may not be closed, a controller can post the ATIS for that field (if the field has ATIS capability) and note what the CTAF is there. For example, when KVGT closes at 9pm LT, their ATIS states:
Common Traffic Advisory Frequency and pilot-controlled field lighting frequency is 125.7. For further information, contact Las Vegas approach control on xxx.xx in the air or on xxx.xx if on the ground.
125.7 is the tower frequency at KVGT.
So we can definitely see the need of using CTAF, but it requires the pilot knowing and reading the charts for the airports in question to know what that CTAF is. We should be all for that, as it brings in the realism we need for this on the network.
BL.