![]() |
DL263?
What's going on with delays on DL263, CDG-JFK? When I booked the flight some months ago, it seemed generally fine, but the past few days it's been delayed by a couple of hours. If this is going to continue I can plan to spend lots of time at the airport or cut things closer than usual.
|
Originally Posted by richarddd
(Post 35803320)
What's going on with delays on DL263, CDG-JFK? When I booked the flight some months ago, it seemed generally fine, but the past few days it's been delayed by a couple of hours. If this is going to continue I can plan to spend lots of time at the airport or cut things closer than usual.
|
Originally Posted by xliioper
(Post 35803354)
As typical, these things really have nothing to do with the route itself. N421DX is flying the route today and came in from SLC where it spent 4.5 hours on the ground yesterday when it was only supposed to be in SLC for around 2 hours. The delay in SLC for SLC-CDG inbound flight naturally cascaded into the delay on today's CDG-JFK flight.
|
Originally Posted by xliioper
(Post 35803354)
As typical, these things really have nothing to do with the route itself. N421DX is flying the route today and came in from SLC where it spent 4.5 hours on the ground yesterday when it was only supposed to be in SLC for around 2 hours. The delay in SLC for SLC-CDG inbound flight naturally cascaded into the delay on today's CDG-JFK flight.
|
Originally Posted by Weekend Away
(Post 35803429)
Looks like it departed Amsterdam a half hour late en route to SLC where it landed 2.5 hours late. I would bet the jet stream was particularly strong on this flight (DL220 on 12/06/23) and that's why it landed 2.5 hours late. But that's just an assumption. Looks like the speed slowed down a bit: https://www.flightaware.com/live/fli.../LFPG/tracklog
The Tuesday CDG-JFK flight was delayed because the inbound from JFK on Monday was taxing at JFK for 4 hours before it took off according to Flightaware (although I suspect tarmac rule would have come into play if it was really taxiing for that long) -- https://www.flightaware.com/live/fli...035Z/KJFK/LFPG |
DL switched from a reliable 764 to an A339 (A300-900neo) at the beginning of the month and Tuesday's DL262 JFK-CDG, the incoming for yesterdays DL263, took a mechanical and was subbed by an A333 along with a scheduled 2 hour delay which turned out to be 2.5+ hours. DL263 was rescheduled with a 2 hour delay at CDG and did make it of the gate 11 minutes late and landed a few minutes early.
The 300-900neo appears to have lots of reliability issues and the J seating on the 764 resolves many of the seatig gripes. It still dumped us into rush hour traffic getting away from JFK. You'll probably still have to re-clear security at CDG which can be a miserable experience. |
Originally Posted by SuperG1955
(Post 35803603)
DL switched from a reliable 764 to an A339 (A300-900neo) at the beginning of the month and Tuesday's DL262 JFK-CDG, the incoming for yesterdays DL263, took a mechanical and was subbed by an A333 along with a scheduled 2 hour delay which turned out to be 2.5+ hours. DL263 was rescheduled with a 2 hour delay at CDG and did make it of the gate 11 minutes late and landed a few minutes early.
The 300-900neo appears to have lots of reliability issues and the J seating on the 764 resolves many of the seatig gripes. It still dumped us into rush hour traffic getting away from JFK. You'll probably still have to re-clear security at CDG which can be a miserable experience. Re-clear? We're originating at CDG, not transiting. |
Originally Posted by richarddd
(Post 35803748)
Does the new less reliable equipment suggest problems will continue? I'm trying to get a feel for our Sunday flight.
|
Originally Posted by xliioper
(Post 35803602)
It only landed 29 minutes late in SLC, not 2.5 hours. It was on the ground for around 4 hours when it was only scheduled for 2 hours before departing for CDG.
The Tuesday CDG-JFK flight was delayed because the inbound from JFK on Monday was taxing at JFK for 4 hours before it took off according to Flightaware (although I suspect tarmac rule would have come into play if it was really taxiing for that long) -- https://www.flightaware.com/live/fli...035Z/KJFK/LFPG |
Originally Posted by Mountain Explorer
(Post 35803899)
No one can predict what will happen on Sunday until your inbound is airborne. And even then, DL could always make a last minute plane reassignment.
|
Originally Posted by richarddd
(Post 35803748)
Does the new less reliable equipment suggest problems will continue? I'm trying to get a feel for our Sunday flight.
Re-clear? We're originating at CDG, not transiting. Here's the schedule right now. According to Flightradar24 your aircraft, a 339, flew JFK-AMS yesterday afternoon to this morning and landed a few minutes early. I write this, It's airborne as DL47 AMS-JFK and scheduled for an on-tine arrival. It's then scheduled to fly JFK-CDG on Saturday (tomorrow) as DL262 and return CDG-JFK as DL263 on Sunday. A relatively long layover at JFK from arrival today to departure tomorrow. Probably scheduled MX. Very likely on-time, |
Originally Posted by SuperG1955
(Post 35805203)
Very likely on-time, Thanks for the helpful information. |
Originally Posted by SuperG1955
(Post 35805203)
Sorrry, I was responding to another post about PRG-CDG-ATL-HSV and confused them.
Here's the schedule right now. According to Flightradar24 your aircraft, a 339, flew JFK-AMS yesterday afternoon to this morning and landed a few minutes early. I write this, It's airborne as DL47 AMS-JFK and scheduled for an on-tine arrival. It's then scheduled to fly JFK-CDG on Saturday (tomorrow) as DL262 and return CDG-JFK as DL263 on Sunday. A relatively long layover at JFK from arrival today to departure tomorrow. Probably scheduled MX. Very likely on-time, |
Is flightaware the best way to track incoming equipment, etc?
|
Originally Posted by xliioper
(Post 35803602)
It only landed 29 minutes late in SLC, not 2.5 hours. It was on the ground for around 4 hours when it was only scheduled for 2 hours before departing for CDG.
The Tuesday CDG-JFK flight was delayed because the inbound from JFK on Monday was taxing at JFK for 4 hours before it took off according to Flightaware (although I suspect tarmac rule would have come into play if it was really taxiing for that long) -- https://www.flightaware.com/live/fli...035Z/KJFK/LFPG |
| All times are GMT -6. The time now is 1:36 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.