CTAF transmissions should not say the word "traffic" at the end

ISSUE DESCRIPTION

Description of the issue:
It’s great that in Sim Update 2, we’re finally getting the name (sort of…we’re getting an airport code…but that’s not the bug) of the airport at the end of a CTAF transmission. I logged a bug report about this four years ago, and in it, I copied examples from the FAA’s Aeronautical Information Manual (AIM) 4-1-9. In the AIM, you will see them use examples like this to describe how to transmit on the radio:

Strawn traffic Apache Two Two Five Zulu clear of runway one seven Strawn.

What you don’t see is the word “traffic” at the end of the example transmission. However, in the sim, that’s exactly what you get: They say the word “traffic.”

Please see the AIM:

AIM. Click to expand.
  1. Recommended self-announce broadcasts: It should be noted that aircraft operating to or from another nearby airport may be making self-announce broadcasts on the same UNICOM or MULTICOM frequency. To help identify one airport from another, the airport name should be spoken at the beginning and end of each self-announce transmission. When referring to a specific runway, pilots should use the runway number and not use the phrase “Active Runway.”

    (a) Inbound

    EXAMPLE-

    Strawn traffic, Apache Two Two Five Zulu, (position), (altitude), (descending) or entering downwind/base/final (as appropriate) runway one seven full stop, touch-and-go, Strawn.
    Strawn traffic Apache Two Two Five Zulu clear of runway one seven Strawn.

    (b) Outbound

    EXAMPLE-

    Strawn traffic, Queen Air Seven One Five Five Bravo (location on airport) taxiing to runway two six Strawn.
    Strawn traffic, Queen Air Seven One Five Five Bravo departing runway two six. Departing the pattern to the (direction), climbing to (altitude) Strawn.

    (c) Practice Instrument Approach

    EXAMPLE-

    Strawn traffic, Cessna Two One Four Three Quebec (position from airport) inbound descending through (altitude) practice (name of approach) approach runway three five Strawn.
    Strawn traffic, Cessna Two One Four Three Quebec practice (type) approach completed or terminated runway three five Strawn.

Here are also five flight schools that I used constantly when I was studying ground school, not using the word “traffic” at the end of their CTAF transmissions. Each one of the people speaking is a CFI:

Did you experience this issue before you joined the Beta?
No…this change was introduced in the beta.

If applicable, which aircraft is experiencing this issue:
N/A

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes and yes. I wrote a phraseology mod to fix things like this, and it was turned off.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time I’m at an uncontrolled airport.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start a flight at an uncontrolled airport. I chose airport 0L7 in Nevada.
  2. Open your ATC menu.
  3. Take off and climb.
  4. At some altitude or distance from the field, you should be able to use the ATC window to tune back into your airport. Do it.
  5. In the ATC window, choose some ATC command. I chose to announce my crosswind leg.

Expected result (assuming using 07L airport and a crosswind leg):
The ATC window says, and you hear:
07L traffic, <callsign> is on crosswind, runway <runway>, 07L.

Observed result (assuming using 07L airport and a crosswind leg):
The ATC window says, and you hear:
07L traffic, <callsign> is on crosswind, runway <runway>, 07L traffic.

See the MEDIA section of this bug report for a video showing this in action.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
N/A

[PC Only] Are you using Developer Mode or have you made any changes to it?
I was using developer mode, but it’s irrelevant for this bug. I can tell you the exact .locPak entries that caused this issue, and developer mode being on or off does not affect which .locPak entries get used.

[PC Only] What GPU (Graphics Card) do you use?
N/A

[PC Only] What other relevant PC specs can you share?
N/A

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video: