Missing Flight CV2612/05NOV

FlightAware AeroAPI
1

Hi Flightaware staff,

Can you tell me why you didn’t detect this flight that occurred yesterday?
The last flight detected from your site with this identification (CLX2612) has landed over 2 weeks ago.

Screenshot%20from%202019-11-06%2009-44-59
Screenshot%20from%202019-11-06%2009-44-59954×341 30.6 KB

The only information FlightInfoStatus (from FlightXml3) is returning for 5th November is this:

   {
        "ident": "CLX2612",
        "faFlightID": "CLX2612-1572759928-airline-0219",
        "airline": "CLX",
        "airline_iata": "CV",
        "flightnumber": "2612",
        "type": "Form_Airline",
        "blocked": false,
        "diverted": false,
        "cancelled": true,
        "origin": {
            "code": "LEZG",
            "city": "Zaragoza / Aragon",
            "alternate_ident": "ZAZ",
            "airport_name": "Zaragoza"
        },
        "destination": {
            "code": "ELLX",
            "city": "Luxembourg",
            "alternate_ident": "LUX",
            "airport_name": "Luxembourg Int'l"
        },
        "filed_ete": 6000,
        "filed_airspeed_kts": 340,
        "distance_filed": 652,
        "filed_departure_time": {
            "epoch": 1572959400,
            "tz": "CET",
            "dow": "Tuesday",
            "time": "14:10",
            "date": "11/05/2019",
            "localtime": 1572963000
        },
        "estimated_departure_time": {
            "epoch": 1572959400,
            "tz": "CET",
            "dow": "Tuesday",
            "time": "14:10",
            "date": "11/05/2019",
            "localtime": 1572963000
        },
        "actual_departure_time": {
            "epoch": -1,
            "tz": "CET",
            "dow": "Thursday",
            "time": "00:59",
            "date": "01/01/1970",
            "localtime": 3599
        },
        "departure_delay": -1572959401,
        "filed_arrival_time": {
            "epoch": 1572965400,
            "tz": "CET",
            "dow": "Tuesday",
            "time": "15:50",
            "date": "11/05/2019",
            "localtime": 1572969000
        },
        "estimated_arrival_time": {
            "epoch": -1,
            "tz": "CET",
            "dow": "Thursday",
            "time": "00:59",
            "date": "01/01/1970",
            "localtime": 3599
        },
        "actual_arrival_time": {
            "epoch": -1,
            "tz": "CET",
            "dow": "Thursday",
            "time": "00:59",
            "date": "01/01/1970",
            "localtime": 3599
        },
        "arrival_delay": -1572965401,
        "status": "result unknown",
        "progress_percent": 100,
        "aircrafttype": "B744",
        "full_aircrafttype": "B744",
        "adhoc": false
    }

and, as you can see… the result is unknown, and the actual time of departure and actual time of arrival epochs have the same (erroneous) values, making that data useless to be treated.

Other flighttrackers detect that flight correctly:

Screenshot%20from%202019-11-06%2009-53-54
Screenshot%20from%202019-11-06%2009-53-54977×139 9.33 KB

Hope this case help you improve the service provided.

2

This appears to be the result of a CSD failure. The aircraft normally operates with the transponder set to CLX67Y. This appears to have been erroneously decoded to and tracked as CLX2602, which is the opposite (LUX to ZAZ) route. A bug has been opened to correct this behavior.

3

Thank you detected the problem.
Will this case help you to correct other flights with similar problems? Or you can only fix this flight (every CV2612) in particular?
Waiting for updates on this.

Thank you

4

I’m unable to give an indication for how many CSD instances would be modified or when a fix would be visible. In the very least this case should be resolved.

5

Hello @dogrock,

I dont know what CSD means, can you clarify?
Yesterday another CV2612 flight occurred, and the problem persisted.

API response:

         {
            "ident": "CLX2612",
            "faFlightID": "CLX2612-1573364728-airline-0068",
            "airline": "CLX",
            "airline_iata": "CV",
            "flightnumber": "2612",
            "tailnumber": "LX-FCL",
            "type": "Form_Airline",
            "blocked": false,
            "diverted": false,
            "cancelled": true,
            "origin": {
                "code": "LEZG",
                "city": "Zaragoza / Aragon",
                "alternate_ident": "ZAZ",
                "airport_name": "Zaragoza"
            },
            "destination": {
                "code": "ELLX",
                "city": "Luxembourg",
                "alternate_ident": "LUX",
                "airport_name": "Luxembourg Int'l"
            },
            "filed_ete": 6300,
            "filed_airspeed_kts": 324,
            "distance_filed": 652,
            "filed_departure_time": {
                "epoch": 1573560600,
                "tz": "CET",
                "dow": "Tuesday",
                "time": "13:10",
                "date": "11/12/2019",
                "localtime": 1573564200
            },
            "estimated_departure_time": {
                "epoch": 1573560600,
                "tz": "CET",
                "dow": "Tuesday",
                "time": "13:10",
                "date": "11/12/2019",
                "localtime": 1573564200
            },
            "actual_departure_time": {
                "epoch": -1,
                "tz": "CET",
                "dow": "Thursday",
                "time": "00:59",
                "date": "01/01/1970",
                "localtime": 3599
            },
            "departure_delay": -1573560601,
            "filed_arrival_time": {
                "epoch": 1573566900,
                "tz": "CET",
                "dow": "Tuesday",
                "time": "14:55",
                "date": "11/12/2019",
                "localtime": 1573570500
            },
            "estimated_arrival_time": {
                "epoch": -1,
                "tz": "CET",
                "dow": "Thursday",
                "time": "00:59",
                "date": "01/01/1970",
                "localtime": 3599
            },
            "actual_arrival_time": {
                "epoch": -1,
                "tz": "CET",
                "dow": "Thursday",
                "time": "00:59",
                "date": "01/01/1970",
                "localtime": 3599
            },
            "arrival_delay": -1573566901,
            "status": "result unknown",
            "progress_percent": 100,
            "aircrafttype": "B744",
            "full_aircrafttype": "B744",
            "inbound_faFlightID": "CLX2602-1573364728-airline-0222",
            "adhoc": false
        }

Screenshot%20from%202019-11-13%2009-54-17
Screenshot%20from%202019-11-13%2009-54-17919×125 11.8 KB

Please, take a look on this, because we are relying on your service to track this specific flight. But the problem may occurr on others aswell.

Thanks.

6

Hello @dogrock,

The problem is persisting with this CLX2612.
Will you do something regarding this?
And by the way, what CSD means( An acronym of mentioned before)

Thanks.

7

CSD stands for Call Sign Disambiguation. It is the mapping of the ticketing flight number to the identifier value actually programmed in the transponder when an operator using call sing similarity tools.

I have no additional update for when this case will be resolved. The bug ticket is prioritized for development with the team that handles this system.

8

Thank you for your response.
Good to know you prioritized this ticket.
Please let me know when you’ll have an update on this.

Best regards