Why is there not an option to change the ATC Phraseology to FAA standards or at least enable it in FAA airspace.
Van you be more precise what is incorrect? Because with latest update msfs atc was updated to be in par with FAA terminology
1 Like
Sorry for stepping on your question to OP, but for one the phraseology “ N1234 continue to assigned” should instead be “N1234 radar contact” after contacting ATC.
Well “Continue to xyz as planned” and “turning and following heading xyz” aren’t FAA standard. They are still in the sim.
1 Like
The latest feedback snapshot shows ATC phraseology is still “under investigation” with expected date of 2021-2022. Still going to see a lot of things to be fixed for quite a while.
Regards
3 Likes
I see some improvements in the latest update. However, the following are still open items:
-
“Keep speed not above…” should be “Keep speed below…”
-
“Contact Tower when inbound on the approach” should be “Contact tower when established.”
-
Missing “Cancel speed restrictions”
(Think of departing IFR on a SID… ATC does not usually assign 250 KTAS speed restriction below 10,000 ft / FL100 (for intl aviators), even if it’s printed on the SID.) -
It’s “nice to have” when ATC gives you a wind check when issuing a runway clearance (“cleared for takeoff / cleared to land / line up and wait”). However in real life, this is not all the time. How about a random number generator that ATC will sometimes provide it, and sometimes not?
-
Approach clearance coming WAYYYYY too late. ATC seems to be issuing step clearances when it should just be assigning me the approach. Good example is ILS into Chicago O’Hare (KORD). I’ve run 3/4 of the approach, then BOOM - cleared for the approach when i’m approaching Final Approach Fix (FAF) and then 2 seconds later cleared for landing.
-
Why is TRACON not clearing me for the approach? This should not be a function handled by Tower. I’m expecting:
- TRACON: [Callsign], you are 57 mi east of O’Hare, [GUIDANCE - descend via the STAR, turn left 260, descend & maintain etc], expect ILS Runway 28C approach
- TRACON: [Callsign], turn right heading 270, cleared for the ILS Runway 28C approach"
- TRACON (after established on the approach): [Callsign], Contact Tower now on 118.25, Good day."
- TRACON (Fix-based handoff): [Callsign] continue to GRABL, Tower at GRABL, 118.25."
- TRACON (if not yet established): [Callsign], Tower on 118.25 when established."
- ORD TOWER: [Callsign] Continue Runway 28C, Number 2 behind a 737 on final."
- ORD TOWER: [Callsign] Cleared to land, Runway 28C, [optional wind check]
On the whole, however, good improvements. If we can get the approach clearance handled properly, that would be a major update.
(Aero Engineer & Pilot - Instrument Airplane)
1 Like
For example; FAA Phraseology when giving a radio frequency is said like this
*ATC: (Callsign) contact departure on 121.85 said ONE TWO ONE POINT EIGHT FIVE.
The current phraseology is said in the ICOA speak DECIMAL instead of POINT. This is the most emersion braking thing in the sim for me. Also I know that THREE is supposed to be said like TREE but no one in North America really says that.
1 Like
Additionally, ATC would not use the type codes when providing guidance. Instead they would use generic fleet families, like A320 instead of A20N or A319. 737 instead of 738 or 7M8 (737-800, 737 Max 8).
Also, when previous traffic is heavy or super (747, 757, 767, 777, 787, A330, A340, A380: super), ATC should caution wake turbulence. I came back to note this because I just got a departure behind an AI Super and was not cautioned of wake turbulence.
EX: Southwest 877, traffic is at your nine o’clock FL380, A20N. Report them in sight.
should be:
[Callsign], traffic is at your nine o’clock, FL380, A320. Report them in sight.
…then…
[Callsign], Airbus traffic is no factor. proceed on course.
EX: American 3221, Runway 28C, cleared to land number 2 behind an Embraer.
EX: “American 3221, Runway 28C, cleared to land. Traffic ahead is 747 on short final. Caution wake turbulence.”
1 Like
OH! This is genuinely a problem, which made me get quite frequently lost / confused when I first strapped in to FS2020 flight deck. Now I’ve learned to ignore the instruction, which is also decidedly NOT correct.
Imagine that you are following your flight plan, then ATC tells you:
ATC: “[CALLSIGN]: maintain present heading and altitude.”
This reads as an instruction to proceed straight and level, regardless of what your flight plan, clearance or previous ATC instruction said.
In real life if I get this instruction, mid turn, i stop turning, level off descent and readback:
ME: Stop the turn, maintain present heading 265 and leveling off at 10,600. King Air 1234
I think what the simulator ATC really means is “Proceed on course to [FIX]” when the instruction it’s actually issuing is “Fly straight ahead.”
While I’m on this topic, a similar confusion shows up with transition fix from the enroute structure to the approach. Usually I get:
TRACON: “King Air 1234, you are 87 mi north of Lafayette. Maintain present heading and altitude. Expect ILS Runway 10 Approach, VAGES Transition. Cleared to VAGES.”
Now note that this instruction is very confusing. On one hand ATC is telling me to flight straight & level. Then “Cleared to VAGES” is telling me to fly direct VAGES.
I would replace this with:
TRACON: “King Air 1234, you are 87 mi north of Lafayette. Expect ILS Runway 10 Approach, VAGES Transition. Cleared direct to VAGES.”