hi everyone, 
I still use the default ATC. I used to have “turn next taxiway” and then “contact ground” when exiting the runway. But this does not occur anymore. I simply have contact ground when the main wheels touch the ground. And before I even finish the landing sequence. 
 

does anyone know where to look? Is this AFCAD related ? Traffic addons (AIG in my case ) perhaps edit voice pack ? 

Thanks 

Chris 

It isn't EditVoicePak -- I use EVP and don't have this issue. Don't know about AIG, I don't use it.

Edited February 21, 20224 yr by pgde

I have this issue too. It seems to occur at certain airports and runways only. 

Curious to see if anyone knows the culprit. I also have EVP installed. 

I think it's AFCAD related that default ATC thinks you landed outside of given runway.

I posted the same question on FSdeveloper forum. Here is what the guy said;
 

« « It usually means:

1. You landed on the wrong runway.
2. The runway is somehow corrupt, and is not registering to FS as a valid runway.
3. The runway surface is too narrow (although a GP runway may be wider).
4. The runway is too short, but the visible runway (GP) is longer.« « 

I mainly use addons airport, just recently happened to me in LFPG and LLBG.

but honestly I don’t think these addons have a too narrow runway surface or the runway is too short. I checked the afcad and they seem totally fine.

then come the runway is corrupt? What could it be?

 

chris

Edited February 22, 20224 yr by cmdn

It also happens if you have not requested landing clearance from the tower.

Noticed this as well 

I noticed it happens for me on 28R at KSFO and on 19C at KIAD, among others. All happening after receiving landing clearance. What's funny is that this seems to "lock" the runway I was cleared to land on. All the AI behind me are ordered to go-around long after I have cleared the runway and am sitting at the gate. 

I'll double check the ADE files to see if I can find anything strange. 

Can anyone confirm they are seeing this issue without the use of EditVoicePack?

Also, it may be worth it to do a quick search on FSDeveloper. 

I am using aiground and aiflow as well. Not sure if they could be causing this? 
but honestly I think this has to do with customized Afcads. I am going to try on a default airport as well. 

13 hours ago, Christopher Low said:

It also happens if you have not requested landing clearance from the tower.

That seems the wrong way around. Tower should give you clearance to land at the appropriate distance if the program is monitoring you. Around 2 miles out I reckon.

No such problems with Radar Contact for those who have yet to try it. 😉

Do you guys experience this contact ground at touchdown with or without ATCAPI, 

been using this and it Interferes with runway and taxiway, I thought that might be also a reason