ATC on live traffic: aircraft type and tail number used instead of airline and flight number on IFR flights

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

Even if new data is provided using flight aware (like the tail number of the aircraft) ATC seems not to use the airline information (name and flight number) anymore, instead the aircraft type/manufacturer and the tail number is always picked for IFR flights.

An United Airlines flight 123 which is operated with an A320, reg N700UA is called “Airbus N700UA” instead of “United 123”. It seems like theflight number is in general missing on IFR flights.

Provide Screenshot(s)/video(s) of the issue encountered:

atc as used on TTS:

Little Nav Map information shows no flight number but the airline:
image

Detailed steps to reproduce the issue encountered:

Fly in busy airspace with ATC and live traffic enabled, at best dialed to some approach frequency.

PC specs and/or peripheral set up if relevant:


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

All my online traffic is called Generic by ATC, instead of by their airline names.

5 Likes

Yes in SU11 for some reason the ATC has regressed to not using the Airline Callsign and instead is using Generic or the Aircraft type followed by their registration number for all aircraft.

7 Likes

As I cannot see any flight number withing LNV that might be the reason for the wrong handling:

If there is no flight number in place ATC seems to handle the flights as VFR instead of IFR. VFR flights are called by aircraft type and tail number correctly (e.g. Cessna N22AS). IFR flights instead are called by airline callsign and flight number.

As Asobo now integrated the real tail number into the information used from FlightAware this change may have lead to the flight number being inop :wink:

1 Like

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

yes

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

exactly as OP has said

If relevant, provide additional screenshots/video:

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

Yes

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

If relevant, provide additional screenshots/video:

1 Like

Interesting this may also be why the model matching is way out of whack.

1 Like

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

Yes

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

If relevant, provide additional screenshots/video:

1 Like

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

Yes

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

Could be why flights are not taking off, ATC has no IFR flight

If relevant, provide additional screenshots/video:

1 Like

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

Yes

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

I have been flying in the London area, and I normally hear “Speedbird” but now, I only hear the tail number.

If relevant, provide additional screenshots/video:

2 Likes

No because it’s also out of wack in SU10 which doesn’t have these live traffic changes. It’s been happening in SU10 since at least the week of October 4th.

Aircraft in SU11 are also only showing their tail number in LittleNavMap. So they did change something with reporting. LittleNavMap only showed the Airline Code + Number before SU11.

I’ve seen some aircraft spawn with Airline code instead of flight number, mostly in Asia. I wonder if those are planes that Flightaware doesn’t know the tail number for.

Oh I realise that. I was commenting it’s significantly worse in SU11 and this may be the reason.

2 Likes

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

Same issue on Xbox SX; AI live traffic is no longer called like Lufthansa 123. Traffic instead called based on tailgate number

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

If relevant, provide additional screenshots/video:

1 Like

I was sitting at KATL this morning, got up to 85 aircraft before I departed with no mismatching. I wonder if it’s fixed.

edit: nope, once I got toe KDTW it started mismatching again

Same thing for me. Also if you use the FSLTL injector, then atc simply doesn’t even communicate with the AI at all…

2 Likes

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

Yes

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

If relevant, provide additional screenshots/video:

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

Yes

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

If relevant, provide additional screenshots/video:

This seems to be fixed in today’s beta release. I am now getting airline/flight calls.

Still not fixed on my end really frustrating bug, still get thing like “Airbus HAV” instead of “FRENCHWEST 510”, also still a lot of generic aircraft, before live traffic was using AIG and FSLTL aircraft that matches

1 Like

For me, this is still not fixed with latest beta update. AI live traffic called by tail number instead of callsign

1 Like