DL787932ER From United States of America, joined Dec 2005, 597 posts, RR: 1 Posted (4 years 1 month 1 week 1 day 10 hours ago) and read 5925 times:
I have a relative on DL22 ATL-CDG tonight. It's been delayed for several hours, and I originally thought it was because the inbound aircraft was late. Looking at the Flightaware track it appears that DL 29 made it almost halfway across the Atlantic before turning around and going back to Paris. I would think if it were a mechanical problem or a medical issue they would have gone to Shannon. What gives?
Also, it looks like 29 was on a 763 and 22 is on a 333, so that's not what delayed 22. Anyone know what's going on with it?
mayor From United States of America, joined Mar 2008, 10922 posts, RR: 14
Reply 3, posted (4 years 1 month 1 week 20 hours ago) and read 5316 times:
Looks to me that 22/27Jan was about 2+ hours late into CDG......hardly "several" hours, but still late enough to be annoying. Also looks like 29/27Jan was about 1 hr 41 min late departing....don't see any indication that it took off and came back to CDG.
"A committee is a group of the unprepared, appointed by the unwilling, to do the unnecessary"----Fred Allen
DL787932ER From United States of America, joined Dec 2005, 597 posts, RR: 1
Reply 4, posted (4 years 1 month 1 week 19 hours ago) and read 5165 times:
22 yesterday departed and arrived about 3 hours late. I'll be interested to hear what the "security sweep" entailed. As for 29, the FlightAware track yesterday clearly showed it leaving CDG, reaching almost the middle of the Atlantic, returning to (or near) CDG, and then going back to ATL. That part's been erased and just the second half of the trip over Atlantic and US airspace is shown now, but it still shows a total distance covered of over 8600NM, twice the direct distance. Of course it was delayed only 2 hours, so it couldn't have traveled that far.