Announcement

Collapse
No announcement yet.

CALL SIGN ERROR or DATABASE ERROR

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • KyleG
    replied
    Because ATC identify aircraft with squawk codes, generally not the callsign entered into the FMS.

    Leave a comment:


  • DemonLee
    replied
    Originally posted by Mike View Post
    Callsign, this case MAC373, has nothing to do with aircraft type, but it shows it's a flight operated by Royal Air Maroc.
    Hex code 0200FB is Boeing 737-8B6
    In that case, both are wrong, FR24 is showing it as an Airbus A320-214 and according to the data, the Registration CN-NMF matches to that aircraft in Morocco, in VirtualRadar it is showing as a Beech B200 - Reg Number CN-TPH (Mode S is 02007B) also registered in Morocco as a 1982 Beech... how can it be so easy for pilots to input the incorrect Call Signs as surely an ATC will assume he is dealing with one particular aircraft and get a completely different one land...!

    Leave a comment:


  • Mike
    replied
    Callsign, this case MAC373, has nothing to do with aircraft type, but it shows it's a flight operated by Royal Air Maroc.
    Hex code 0200FB is Boeing 737-8B6

    Leave a comment:


  • DemonLee
    started a topic CALL SIGN ERROR or DATABASE ERROR

    CALL SIGN ERROR or DATABASE ERROR

    A short while ago I noticed that FR24 and Virtual Radar are tracking the same aircraft, same position on map but according to the data, two completely different aircraft....?

    MAC373.jpgMAC373-2.jpg
Working...
X