ATC seems to read the lines without any regard for punctuation or pauses.
I understand that in real life, ATC is required to talk fast; somewhere between the wpm of a rapper and a cattle auctioneer. But this is ridiculous and makes listening to instructions very difficult when my callsign and the instruction are so blended together.
Does anyone else here feel the same way or did i just learn listening to ATC wrong from years of playing FSX where the ATC makes generous pauses between callsign and instructions?
Try landing at CDG and wait for taxi instructions:
Taxi to gate J37 using taxiway W3 WT T RT7 R TL7 TL6 GE10 E TJ3 P5 E10 P4
Ground said it so fast⊠Taxi to Gate Juliet Three Seven Whisky Three Whisky Tango Tango Romeo Tango Seven Romeo Tango Lima Six Golf Echo One Zero Echo Tango Juliet Three Papa Five Echo One Zero Papa Four.
Would need someone in the cockpit who knows shorthand.
Yes, I think youâve pointed out a good place for a simple improvement.
In the real world, its perfectly acceptable for a pilot to request the ATC to slow it down, something roughly like âSeattle Ground, Cessna 152 GHO, Say Again, Speak Slowerâ.
This is as much an accessibility issue as it is a realism one. There is an ATC log you can read, but engineering the option to have the azure ATC voice slow its cadence down when requested is something that should be available.
I know this is an old thread but I need to add that it isnât just the speed of delivery - the pauses are there, just in the wrong place - in Viscousâ post it would be âSeattleGroundCessna15 2GHOSayagainâŠâ And the other thing really bugging me is âO N Eâ for â1â as above âCessna O N E 52â but it doesnât seem consistent - sometimes âOneâ is pronounced correctly and sometimes it is spelt out in the same message.
Iâve noticed this, too. In big airports itâs really hard to receive taxi instructions without reading the text. âAlphaSixAlphaEchoFoxtrotLimaBravoFourCrossRunwayTwoFiveCharlieNovemberPapaâ.
Hahaha! That sounds exactly like my experience with ground!
Fortunately, I heard on the last Developer Q&A that they will be implementing some more natural-sounding voice(s) at some point, but who knows how long that will take.
Thatâs good advice. During my ground school there was a CFI that said the same. Thereâs too many pilots that ramble it.
I worked at an airport that wasnât controlled and pilots would call in. The commercial pilots were clear, the some of the private pilots I had to have them repeat it.
HI all. I had a look through the âincorrect phraseologyâ thread but that was a fairly technical debate on what ATC should or shouldnât be saying. My issue is a much simpler one. In these days of sophisticated Test to Speech software, why does the SIM ATC make such a mess of voicing a simple instruction? Iâm talking about when it says something like
âAirbus A5-EYF : Taxi to and hold {pause}
short of runway {pause}
23 via {pause}
taxiway cross runway {pause}
28 {pause}
A Airbus EYFâ.
OK Iâm maybe exaggerating there, but weird misplaced breaks in a sentence does nothing to enhance realism, and I donât understand why the ATC canât be as good as the TTS engine on my phone speaking a sentence itâs never seen before and yet getting the stress and phrasing right.
The TTS engine is actually doing quite well. But every time it has to process repeating letters or numbers the output sounds a little bit like a machine gun Is there a chance to add some âmodulationâ or variety to it?
BTW a (slight) local accent could probably contribute to realism too.
Is there a chance to add some âmodulationâ or variety to it?