Announcement

Collapse
No announcement yet.

Data errors in Flightradar24 aircraft database

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Originally posted by Coxy View Post
    Miscode as in it should be 9A or 8A as my tracker picked it up as 9A..
    The transponder is miscoded.
    Don't know the ICAO type code? Look it up here.

    Comment


    • A5B785
      N468C
      P68
      Partenavia P-68C

      Comment


      • Aircraft DMWYK, Hex 3FF67E is only shown as ULAC with track on the map.
        The callsign is not displayed and so no history is available.
        The aircrafttype is shown correctly in the left colum, also altitude, speed and position (ADS-B).

        Comment


        • Originally posted by Eagletrike View Post
          Aircraft DMWYK, Hex 3FF67E is only shown as ULAC with track on the map.
          The callsign is not displayed and so no history is available.
          The aircrafttype is shown correctly in the left colum, also altitude, speed and position (ADS-B).
          If the callsign is not displayed, it's because the transponder is not transmitting it.
          Don't know the ICAO type code? Look it up here.

          Comment


          • 7C175C
            VH-EWE
            T18
            Thorp T-18S
            N30
            Private owner

            Year:2019

            Comment


            • I will check settings at the transponder. Last year the callsign was displayed on the map.
              Is the hex Code and a transpondercode also not transmitted? (not displayed on the left aircraftdetails)
              Normaly FIS informs if there are data missing. I fly with radio/transponder-contact to FIS.

              Comment


              • Albastar EC-MUB data is ok in Flight data history but remains wrong when the flgiht is selected
                can you try to fix it
                Thank you in advance

                Comment


                • Originally posted by occ@albastar.es View Post
                  Albastar EC-MUB data is ok in Flight data history but remains wrong when the flgiht is selected
                  can you try to fix it
                  Thank you in advance
                  It's been like that Since Feb 2018. Sending the wrong code.

                  And posted many many many times - it needs to be reprogrammed.

                  https://forum.flightradar24.com/thre...l=1#post121861

                  https://forum.flightradar24.com/thre...l=1#post115758

                  Only when it sends valid code "345618" Will it show up here
                  https://www.flightradar24.com/data/aircraft/ec-mubecmub.JPG


                  https://www.planespotters.net/airfra...-Star/LZAltYpP

                  Correct Mode S should be: 345618
                  leased from (hidden) Dec 2017 - Dec 2018
                  leased from (hidden) Dec 2018
                  ecmub.JPG



                  https://www.icao.int/Meetings/AMC/MA...ccdca3wp05.pdf

                  Spain * 0 0 1 1 0 1 – – – – – – – –

                  NOT 1 1 0 0 1 0 ... LIKE IT IS PROGRAMMED NOW - 110010111010100111100111

                  Anyone who is fluent in spanish. Feel free to chime in here. Because it won't get fixed until the point is across.
                  Last edited by Oblivian; 2019-06-19, 10:30.
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • @albastar

                    La gente de aviónica de Albastar necesita recodificar el transpondedor. (with thanks to Google )

                    Binary 00110100 01010110 00011000

                    Comment


                    • 7C309A
                      VH-JVW
                      R22
                      Robinson R22 Beta
                      4134
                      Corsaire Flight School
                      2007-00-00

                      Comment


                      • A33A30
                        N307JW
                        CL30
                        Bombardier BD-100-1A10 Challenger 300
                        20093
                        Private owner
                        2006-00-00

                        Comment


                        • A5EF60
                          N4815J
                          BE33
                          Beech C33A Debonair
                          CE-114
                          Private owner

                          Comment


                          • Originally posted by 40612 View Post
                            If the callsign is not displayed, it's because the transponder is not transmitting it.
                            Aircraft DMWYK, Hex 3FF67E is only shown as ULAC with track on the map.
                            The callsign is not displayed and so no history is available.
                            The aircrafttype is shown correctly in the left colum, also altitude, speed and position (ADS-B).

                            I have an other flight yesterday. I checked the settings of the transponder and ask FIS if the ADS-B data are correctly transmitted including callsign and hex. That was positiv.
                            The track was on the map without callsign/hex, but with model ULAC higthech composite Eagle (see trackplot 20.Jun.2019 12:20UTC 51.5221 13.2034 ADS-B position).
                            What esle can be done, that I can see the tracks with callsign. Last year the callsign was displayed, only the history for the callsign was not activated.

                            Comment


                            • There is an error in the following plane:

                              ModeS/Hex-code: DDC152 (FLARM-ID)
                              Registration: D-KSIN NOT D-KHHT!!!!
                              Type: SF-25C
                              Airline / Owner: SFG Singen-Hilzingen e.V.

                              D-KHHT is not more existing (plane is sold to Poland and deleted in German register)

                              Thank you for correcting
                              Last edited by leporelo; 2019-06-21, 10:27.

                              Comment


                              • Originally posted by Eagletrike View Post
                                Aircraft DMWYK, Hex 3FF67E is only shown as ULAC with track on the map.
                                The callsign is not displayed and so no history is available.
                                The aircrafttype is shown correctly in the left colum, also altitude, speed and position (ADS-B).

                                I have an other flight yesterday. I checked the settings of the transponder and ask FIS if the ADS-B data are correctly transmitted including callsign and hex. That was positiv.
                                The track was on the map without callsign/hex, but with model ULAC higthech composite Eagle (see trackplot 20.Jun.2019 12:20UTC 51.5221 13.2034 ADS-B position).
                                What esle can be done, that I can see the tracks with callsign. Last year the callsign was displayed, only the history for the callsign was not activated.
                                The problem is that D-MWYK is not in the FR24 database, that's why there is no flight history. If you add the details in the other thread (Aircraft to be added) it should then appear.

                                Comment

                                Working...
                                X