Weird flight path for BA714 - Sep 13, 2018

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite
1












just noticed this weird flight path and the altitude gain graph. What could be the possible reason?



https://www.flightstats.com/v2/flight-tracker/BA/714?year=2018&month=09&date=13&flightId=973124366










share|improve this question







New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



















  • Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
    – Thorsten S.
    5 hours ago







  • 4




    It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
    – Giacomo Catenazzi
    5 hours ago











  • @GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
    – Thorsten S.
    5 hours ago






  • 3




    I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
    – Giorgio
    4 hours ago






  • 2




    @ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
    – Henning Makholm
    3 hours ago
















up vote
1
down vote

favorite
1












just noticed this weird flight path and the altitude gain graph. What could be the possible reason?



https://www.flightstats.com/v2/flight-tracker/BA/714?year=2018&month=09&date=13&flightId=973124366










share|improve this question







New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



















  • Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
    – Thorsten S.
    5 hours ago







  • 4




    It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
    – Giacomo Catenazzi
    5 hours ago











  • @GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
    – Thorsten S.
    5 hours ago






  • 3




    I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
    – Giorgio
    4 hours ago






  • 2




    @ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
    – Henning Makholm
    3 hours ago












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





just noticed this weird flight path and the altitude gain graph. What could be the possible reason?



https://www.flightstats.com/v2/flight-tracker/BA/714?year=2018&month=09&date=13&flightId=973124366










share|improve this question







New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











just noticed this weird flight path and the altitude gain graph. What could be the possible reason?



https://www.flightstats.com/v2/flight-tracker/BA/714?year=2018&month=09&date=13&flightId=973124366







air-travel






share|improve this question







New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 5 hours ago









Dibyajit Majumder

91




91




New contributor




Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Dibyajit Majumder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











  • Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
    – Thorsten S.
    5 hours ago







  • 4




    It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
    – Giacomo Catenazzi
    5 hours ago











  • @GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
    – Thorsten S.
    5 hours ago






  • 3




    I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
    – Giorgio
    4 hours ago






  • 2




    @ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
    – Henning Makholm
    3 hours ago
















  • Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
    – Thorsten S.
    5 hours ago







  • 4




    It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
    – Giacomo Catenazzi
    5 hours ago











  • @GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
    – Thorsten S.
    5 hours ago






  • 3




    I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
    – Giorgio
    4 hours ago






  • 2




    @ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
    – Henning Makholm
    3 hours ago















Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
– Thorsten S.
5 hours ago





Educated guess: The flight crew experienced a problem with the plane and decided to return to London. Then they found the problem or it disappeared, so they continue the flight, but now they use a route over airports (see the jumps in orientation) so if it happens again they can go down as soon as possible.
– Thorsten S.
5 hours ago





4




4




It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
– Giacomo Catenazzi
5 hours ago





It is just an error. flightradar24.com/BAW714T/1dd99aed does not have such change. Do no trust automatic sources. Often there are error in the incoming data, or just an error in transmission/database
– Giacomo Catenazzi
5 hours ago













@GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
– Thorsten S.
5 hours ago




@GiacomoCatenazzi Is it? Strangely flight BA8765 (shown as CFE54K) with the same airline, source and destination almost perfectly follows the former predicted flight path, BAW714T flies definitely wrong in both maps.
– Thorsten S.
5 hours ago




3




3




I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
– Giorgio
4 hours ago




I'm voting to close this question as off-topic because it's not about travel, per se, and might be better asked on Aviation
– Giorgio
4 hours ago




2




2




@ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
– Henning Makholm
3 hours ago




@ThorstenS.: I don' think the grey line is a "predicted flight path" -- just a great-circle line between the scheduled origin and destination.
– Henning Makholm
3 hours ago










1 Answer
1






active

oldest

votes

















up vote
5
down vote













If you zoom in on the Flightstats map, you will see that the apparent initial excursion into Kent is made up of straight lines and impossibly sharp turns. Combined with the fact that Flightradar24 doesn't show any such thing, I conclude that it is a data error; the plane didn't actually fly to Kent and back to London.



The Flightradar replay shows that the flight left its Terminal 5A gate at 11:18 UTC, taxied to the runway and took off at 11:36 UTC, and then followed the path via Paris that Flightstats also shows. But Flightstat claims the "actual" departure time as 11:10 UTC. It seems to have invented 20 minutes of teleporting around Kent and Surrey out of thin air.



Possibly Flightstats started by guessing where the plane would be, based on its scheduled departure time of 11:10 UTC, and then, when actual position data started coming in, scrambled to connects its initial guess to reality somehow.






share|improve this answer






















  • Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
    – Michael Seifert
    1 hour ago










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "273"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






Dibyajit Majumder is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftravel.stackexchange.com%2fquestions%2f122271%2fweird-flight-path-for-ba714-sep-13-2018%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
5
down vote













If you zoom in on the Flightstats map, you will see that the apparent initial excursion into Kent is made up of straight lines and impossibly sharp turns. Combined with the fact that Flightradar24 doesn't show any such thing, I conclude that it is a data error; the plane didn't actually fly to Kent and back to London.



The Flightradar replay shows that the flight left its Terminal 5A gate at 11:18 UTC, taxied to the runway and took off at 11:36 UTC, and then followed the path via Paris that Flightstats also shows. But Flightstat claims the "actual" departure time as 11:10 UTC. It seems to have invented 20 minutes of teleporting around Kent and Surrey out of thin air.



Possibly Flightstats started by guessing where the plane would be, based on its scheduled departure time of 11:10 UTC, and then, when actual position data started coming in, scrambled to connects its initial guess to reality somehow.






share|improve this answer






















  • Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
    – Michael Seifert
    1 hour ago














up vote
5
down vote













If you zoom in on the Flightstats map, you will see that the apparent initial excursion into Kent is made up of straight lines and impossibly sharp turns. Combined with the fact that Flightradar24 doesn't show any such thing, I conclude that it is a data error; the plane didn't actually fly to Kent and back to London.



The Flightradar replay shows that the flight left its Terminal 5A gate at 11:18 UTC, taxied to the runway and took off at 11:36 UTC, and then followed the path via Paris that Flightstats also shows. But Flightstat claims the "actual" departure time as 11:10 UTC. It seems to have invented 20 minutes of teleporting around Kent and Surrey out of thin air.



Possibly Flightstats started by guessing where the plane would be, based on its scheduled departure time of 11:10 UTC, and then, when actual position data started coming in, scrambled to connects its initial guess to reality somehow.






share|improve this answer






















  • Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
    – Michael Seifert
    1 hour ago












up vote
5
down vote










up vote
5
down vote









If you zoom in on the Flightstats map, you will see that the apparent initial excursion into Kent is made up of straight lines and impossibly sharp turns. Combined with the fact that Flightradar24 doesn't show any such thing, I conclude that it is a data error; the plane didn't actually fly to Kent and back to London.



The Flightradar replay shows that the flight left its Terminal 5A gate at 11:18 UTC, taxied to the runway and took off at 11:36 UTC, and then followed the path via Paris that Flightstats also shows. But Flightstat claims the "actual" departure time as 11:10 UTC. It seems to have invented 20 minutes of teleporting around Kent and Surrey out of thin air.



Possibly Flightstats started by guessing where the plane would be, based on its scheduled departure time of 11:10 UTC, and then, when actual position data started coming in, scrambled to connects its initial guess to reality somehow.






share|improve this answer














If you zoom in on the Flightstats map, you will see that the apparent initial excursion into Kent is made up of straight lines and impossibly sharp turns. Combined with the fact that Flightradar24 doesn't show any such thing, I conclude that it is a data error; the plane didn't actually fly to Kent and back to London.



The Flightradar replay shows that the flight left its Terminal 5A gate at 11:18 UTC, taxied to the runway and took off at 11:36 UTC, and then followed the path via Paris that Flightstats also shows. But Flightstat claims the "actual" departure time as 11:10 UTC. It seems to have invented 20 minutes of teleporting around Kent and Surrey out of thin air.



Possibly Flightstats started by guessing where the plane would be, based on its scheduled departure time of 11:10 UTC, and then, when actual position data started coming in, scrambled to connects its initial guess to reality somehow.







share|improve this answer














share|improve this answer



share|improve this answer








edited 3 hours ago

























answered 4 hours ago









Henning Makholm

36.4k685141




36.4k685141











  • Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
    – Michael Seifert
    1 hour ago
















  • Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
    – Michael Seifert
    1 hour ago















Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
– Michael Seifert
1 hour ago




Flightaware doesn't show any odd jogs either, other than the long turn to the southeast after takeoff.
– Michael Seifert
1 hour ago










Dibyajit Majumder is a new contributor. Be nice, and check out our Code of Conduct.









 

draft saved


draft discarded


















Dibyajit Majumder is a new contributor. Be nice, and check out our Code of Conduct.












Dibyajit Majumder is a new contributor. Be nice, and check out our Code of Conduct.











Dibyajit Majumder is a new contributor. Be nice, and check out our Code of Conduct.













 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftravel.stackexchange.com%2fquestions%2f122271%2fweird-flight-path-for-ba714-sep-13-2018%23new-answer', 'question_page');

);

Post as a guest













































































Comments

Popular posts from this blog

Long meetings (6-7 hours a day): Being “babysat” by supervisor

What does second last employer means? [closed]

One-line joke