{ "id": 3515, "title": "\"Time Adjustment\" after \"STATUS-Landed\" in flighthistoryevents.csv", "url": "/competitions/flight/discussion/3515", "author_name": "", "post_date": "2013-01-01T08:12:17.470Z", "votes": null, "comment_count": 2, "views": 2565, "content": "

When I checked flighthistoryevents.csv, I found that some "Time Adjustment" events come after "STATUS-Landed" event.

\r\n

My understanding is that an "STATUS-Landed" means AGA is known, so there should be no more "Time Adjustment" of ERA/EGA/ARA/AGA. Is my understanding wrong?

\r\n

Thanks.

", "messages": [ { "id": "18860", "postDate": "01/01/2013 08:12:17", "content": "

When I checked flighthistoryevents.csv, I found that some "Time Adjustment" events come after "STATUS-Landed" event.

\r\n

My understanding is that an "STATUS-Landed" means AGA is known, so there should be no more "Time Adjustment" of ERA/EGA/ARA/AGA. Is my understanding wrong?

\r\n

Thanks.

", "rawMarkdown": "", "votes": null }, { "id": "18893", "postDate": "01/02/2013 13:34:43", "content": "

I'm just speculating here. Could the "Time Adjustment" after "Status-Landed" be data corrections?

", "rawMarkdown": "", "votes": null }, { "id": "18962", "postDate": "01/04/2013 12:57:11", "content": "

Unlikely ... let us take flight-number 281189436 (from the 2012_11_23 folder of the trainign set)

\r\n

Every data provided by the flightHistory-data seems to indicate that this is a regular flight. (There is not even an "Redirected" or "Diverted" message in the history).

\r\n

For this flight every predictor whould indicate this one will arrive somehow arround 18:11 - 18:13 local time. In fact at 18:17 and 18:18 local time the status is "landed" and the ARA and AGA are set to 18:14 and  18:18, so everyting seems to be fine (it\r\n was a little late but withing common time bounds). 3 hours later - for an unknown reason - ARA and AGA are re-setted to a time nearly 3 hoers later ... and this are the times printed into the flight-history, so if this flight is to be scored it will add more\r\n than 120 minutes (to the square (!) ) malus to the score - I don't know why this has happend, but it can't be the intention of the quest-host to let people win who are best in predicting which flight will have a post-landing time change ;)

\r\n

 

\r\n

 

\r\n

 

\r\n

An other example: 281355519 (2012_11_25) a very short flight, indeed... but after landing ARA and ERA are still corrected - by more than 4 hours away from the actual landing time. In the last entry the wrong ARA time is set back to the realistic value, but\r\n in total data for this flight is a mess...

\r\n

 

", "rawMarkdown": "", "votes": null } ], "comments": [ { "id": 18893, "author_name": "jimthompson", "author_url": "", "post_date": "01/02/2013 13:34:43", "content": "

I'm just speculating here. Could the "Time Adjustment" after "Status-Landed" be data corrections?

", "votes": null, "replies": [] }, { "id": 18962, "author_name": "lolliedieb", "author_url": "", "post_date": "01/04/2013 12:57:11", "content": "

Unlikely ... let us take flight-number 281189436 (from the 2012_11_23 folder of the trainign set)

\r\n

Every data provided by the flightHistory-data seems to indicate that this is a regular flight. (There is not even an "Redirected" or "Diverted" message in the history).

\r\n

For this flight every predictor whould indicate this one will arrive somehow arround 18:11 - 18:13 local time. In fact at 18:17 and 18:18 local time the status is "landed" and the ARA and AGA are set to 18:14 and  18:18, so everyting seems to be fine (it\r\n was a little late but withing common time bounds). 3 hours later - for an unknown reason - ARA and AGA are re-setted to a time nearly 3 hoers later ... and this are the times printed into the flight-history, so if this flight is to be scored it will add more\r\n than 120 minutes (to the square (!) ) malus to the score - I don't know why this has happend, but it can't be the intention of the quest-host to let people win who are best in predicting which flight will have a post-landing time change ;)

\r\n

 

\r\n

 

\r\n

 

\r\n

An other example: 281355519 (2012_11_25) a very short flight, indeed... but after landing ARA and ERA are still corrected - by more than 4 hours away from the actual landing time. In the last entry the wrong ARA time is set back to the realistic value, but\r\n in total data for this flight is a mess...

\r\n

 

", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "18860": "", "18893": "", "18962": "" }, "source": "meta" }