Traffic pattern calls at non-towered airports are incorrect - career mode

Bug Reporting Hub ATC, Traffic & NAVAIDs
, ,
1

ISSUE DESCRIPTION

Description of the issue:

Applied to US airports (at minimum), traffic pattern radio calls on CTAF at non-towered airports are incorrect and incomplete, missing several key elements and adding others that are unnecessary.

First, all CTAF communications should begin with the airport name (not identifier) “traffic”, aircraft type, callsign (poss. abbreviated), the content of the call (where & what as necessary), and end with the airport name again.

Currently career mode judges us on several mandatory radio calls:

  • Taxiing out
  • Takeoff, including departure plan
  • 5 mile inbound
  • Final
  • Taxiing in

In reality, these are the standard CTAF calls that should be made in the non-towered airport environment:

  • Taxi out (this is recommended by the AIM, but arguably unnecessary at many airports, especially when busy). “Auburn traffic, Skyhawk four Charlie Foxtrot taxiing to runway two-five via alpha, Auburn.”
  • Takeoff (including pattern departure plan). Ex: “Auburn traffic, Skyhawk six-zero-four Charlie Foxtrot taking off runway 25, departing to the southwest, Auburn”
  • 10-mile inbound (arguably up to 15 miles if you’re moving fast) Ex: “Auburn traffic, Skyhawk six-zero-four Charlie Foxtrot one-zero miles south, four thousand five hundred, inbound to land, Auburn”
  • (optional) 5-mile inbound (including pattern entry plan) - Ex: “Auburn traffic, Skyhawk four Charlie Foxtrot, 5 mile forty-five to left downwind, runway two-five, Auburn”
  • Joining the pattern (include leg, like downwind) - Ex: “Auburn traffic, Skyhawk four Charlie Foxtrot joining left downwind, two-five, full-stop, Auburn.”
  • Base - Ex: “Auburn traffic, Skyhawk four Charlie Foxtrot, left base, two-five, Auburn”
  • Final - Ex: “Auburn traffic, Skyhawk four Charlie Foxtrot, one mile final, two-five, full stop, Auburn.”
  • Clear of runway - Ex: “ Auburn traffic, Skyhawk four Charlie Foxtrot, clear runway two-five, Auburn.”

There are also obviously other pattern calls that can be made, especially if staying in the pattern and/or using parts of it for a departure (like “departing the pattern to the south from the crosswind”). Some of that is outside the scope of career mode.

Keep in mind this is trying to hit center-mass. I guarantee there will be nits to pick on some details - remember, there are recommendations for a lot of this in the AIM, but that includes some variation due to local procedure and/or frequency congestion. And different schools/instructors teach slightly different variations.

If applicable, which aircraft is experiencing this issue:

All

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

No mods

FREQUENCY OF ISSUE

During any flight into a non-towered (uncontrolled) airport.

REPRODUCTION STEPS

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

  1. Fly a career flight
  2. Take notes
  3. Compare to the AIM and standard practices

YOUR SETTINGS

N/A

MEDIA

N/A

[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:
•