CPT connection non-interline tickets.
#1
Original Poster
Join Date: Jul 2017
Location: Outside of Cleveland Ohio
Programs: UA *G. DL ̶G̶O̶L̶D̶ Member, Hilton/SPG Gold, Hertz PC
Posts: 362
CPT connection non-interline tickets.
Hi all,
We're going to be flying out of CPT on KL which is a late evening departure. Will be booking a separate OW flight JNB-CPT to connect. there are loads of options for JNB-CPT.
How long should I allow to collect baggage, clear immigration and security? Thanks.
We're going to be flying out of CPT on KL which is a late evening departure. Will be booking a separate OW flight JNB-CPT to connect. there are loads of options for JNB-CPT.
How long should I allow to collect baggage, clear immigration and security? Thanks.
#3
Original Poster
Join Date: Jul 2017
Location: Outside of Cleveland Ohio
Programs: UA *G. DL ̶G̶O̶L̶D̶ Member, Hilton/SPG Gold, Hertz PC
Posts: 362
#4
Suspended
Join Date: Aug 2010
Location: DCA
Programs: UA US CO AA DL FL
Posts: 50,261
You are not connecting at CPT. If you are on separate tickers, you are transferring between entirely separate journeys. The question is not how long you need under ordinary circumstances, but your willingness to take the risk of being a no show for your onwards flight and having to possibly purchase a new ticket at walk up prices back to AMS.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
#5
Join Date: Mar 2016
Location: CPT,AMS
Posts: 4,425
You are not connecting at CPT. If you are on separate tickers, you are transferring between entirely separate journeys. The question is not how long you need under ordinary circumstances, but your willingness to take the risk of being a no show for your onwards flight and having to possibly purchase a new ticket at walk up prices back to AMS.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
That being said, JNB-CPT (and v.v.) flights are very rarely cancelled or have major delays, I'd be comfortable with a 3hrs window in such cases, when I take the KL flight from CPT I usually arrive at the airport 80-90 min before if I have a bag to drop, and less than that if I don't.
#6
Original Poster
Join Date: Jul 2017
Location: Outside of Cleveland Ohio
Programs: UA *G. DL ̶G̶O̶L̶D̶ Member, Hilton/SPG Gold, Hertz PC
Posts: 362
You are not connecting at CPT. If you are on separate tickers, you are transferring between entirely separate journeys. The question is not how long you need under ordinary circumstances, but your willingness to take the risk of being a no show for your onwards flight and having to possibly purchase a new ticket at walk up prices back to AMS.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
Thus, if there is bad weather or a technical issue on your flight into CPT, you are truly stuck. Only you can determine your own risk tolerance.
#7
Join Date: Mar 2004
Location: CPT
Programs: BA BD SA
Posts: 4,467
So although I agree with Ditto that 2.5 to 3 hours should be ample, the bottom line still is it depends on your risk appetite regarding events that are admittedly infrequent but could be extremely disruptive if one of them eventuates.
#8
Ambassador: World of Hyatt
Join Date: Mar 2002
Location: UK - the nearest airport is named after a motorway !
Posts: 4,253
Well, much as you disparage that input, I think it is very valid. There is a very real risk of delays. My Comair flight on Sunday (the last of the day) was delayed by 30 minutes. I have had BA flights cancelled on that route too - though they did call ahead and offer to move my flight. For some reason Mango seems to be going through a spate of delays recently and colleagues are avoiding them for that reason. Also if there are major thunderstorms around JNB (typically in high summer) it can throw out the schedules very badly - and the later flights bear the brunt of it as the delays cascade.
So although I agree with Ditto that 2.5 to 3 hours should be ample, the bottom line still is it depends on your risk appetite regarding events that are admittedly infrequent but could be extremely disruptive if one of them eventuates.
So although I agree with Ditto that 2.5 to 3 hours should be ample, the bottom line still is it depends on your risk appetite regarding events that are admittedly infrequent but could be extremely disruptive if one of them eventuates.
It should be ample, but be aware that there is a real risk...
Of course, Ditto below is right as well. That's my horror story, but I have made many many domestic flights without issue, and I would still book that 'connection' that went wrong - but be aware that it *might* go wrong, and understand that there is no 'flat tire' rule with most European carriers...
Last edited by Stewie Mac; Apr 17, 2019 at 9:41 am Reason: to agree with Ditto that likely all will be well
#9
Join Date: Mar 2016
Location: CPT,AMS
Posts: 4,425
Maybe to balance a bit the horror stories shared above, I'll add some experience from the last year (between me and Mrs. Ditto)
- A total of about 50 flights, mostly Mon/Tue morning CPT-JNB and Thu/Fri evening JNB-CPT
- About equal split between Mango and Kulula with the odd SAA/BA
- One flight delayed on arrival by about 30 minutes due to thunder storms in JHB
- One flight delayed by about 1HR due to cascading delays earlier in the day
- One flight almost diverted to GRJ due to winds at CPT, a bit of a rough landing but nonetheless on time
- All other flights landing within +-15 min of schedule time
- 0 Flights cancelled
- Some 20 additional flights CPT/JNB to other domestic airports also with no major issues
So yes, the risk is definitely there, but better to put things in proportion...
- A total of about 50 flights, mostly Mon/Tue morning CPT-JNB and Thu/Fri evening JNB-CPT
- About equal split between Mango and Kulula with the odd SAA/BA
- One flight delayed on arrival by about 30 minutes due to thunder storms in JHB
- One flight delayed by about 1HR due to cascading delays earlier in the day
- One flight almost diverted to GRJ due to winds at CPT, a bit of a rough landing but nonetheless on time
- All other flights landing within +-15 min of schedule time
- 0 Flights cancelled
- Some 20 additional flights CPT/JNB to other domestic airports also with no major issues
So yes, the risk is definitely there, but better to put things in proportion...
#10
Original Poster
Join Date: Jul 2017
Location: Outside of Cleveland Ohio
Programs: UA *G. DL ̶G̶O̶L̶D̶ Member, Hilton/SPG Gold, Hertz PC
Posts: 362
Well, much as you disparage that input, I think it is very valid. There is a very real risk of delays. My Comair flight on Sunday (the last of the day) was delayed by 30 minutes. I have had BA flights cancelled on that route too - though they did call ahead and offer to move my flight. For some reason Mango seems to be going through a spate of delays recently and colleagues are avoiding them for that reason. Also if there are major thunderstorms around JNB (typically in high summer) it can throw out the schedules very badly - and the later flights bear the brunt of it as the delays cascade.
So although I agree with Ditto that 2.5 to 3 hours should be ample, the bottom line still is it depends on your risk appetite regarding events that are admittedly infrequent but could be extremely disruptive if one of them eventuates.
So although I agree with Ditto that 2.5 to 3 hours should be ample, the bottom line still is it depends on your risk appetite regarding events that are admittedly infrequent but could be extremely disruptive if one of them eventuates.
As far as Mango goes do you feel better or worse about them than SA or Kulua?
Maybe to balance a bit the horror stories shared above, I'll add some experience from the last year (between me and Mrs. Ditto)
- A total of about 50 flights, mostly Mon/Tue morning CPT-JNB and Thu/Fri evening JNB-CPT
- About equal split between Mango and Kulula with the odd SAA/BA
- One flight delayed on arrival by about 30 minutes due to thunder storms in JHB
- One flight delayed by about 1HR due to cascading delays earlier in the day
- One flight almost diverted to GRJ due to winds at CPT, a bit of a rough landing but nonetheless on time
- All other flights landing within +-15 min of schedule time
- 0 Flights cancelled
- Some 20 additional flights CPT/JNB to other domestic airports also with no major issues
So yes, the risk is definitely there, but better to put things in proportion...
- A total of about 50 flights, mostly Mon/Tue morning CPT-JNB and Thu/Fri evening JNB-CPT
- About equal split between Mango and Kulula with the odd SAA/BA
- One flight delayed on arrival by about 30 minutes due to thunder storms in JHB
- One flight delayed by about 1HR due to cascading delays earlier in the day
- One flight almost diverted to GRJ due to winds at CPT, a bit of a rough landing but nonetheless on time
- All other flights landing within +-15 min of schedule time
- 0 Flights cancelled
- Some 20 additional flights CPT/JNB to other domestic airports also with no major issues
So yes, the risk is definitely there, but better to put things in proportion...
#11
Join Date: Apr 2007
Location: Australia
Posts: 6,349
I think you are being way too hard on others. YOU are the one who used the word "connect" in your OP. Noone else can read your mind and know in what sense you meant that. We get MANY folks on FT who ask similar questions about separate tickets who clearly think (initially) that they ARE "connecting" (in the Airline sense of the word). They are - very appropriately - disabused of that notion. You know the difference and didn't mean it that way. Great. Others clearly do not always have that knowledge and it is a VERY important point to understand.
#12
Join Date: Mar 2004
Location: CPT
Programs: BA BD SA
Posts: 4,467
Since my observation on Mango punctuality was based on anecdote, it is difficult for me to say with certainty whether there is a genuine pattern of delays and, if there is, how long that pattern will persist.
One can get some idea of recent on time performance here. I can’t find the more complete stats that give average length of delay and longest delay. Didn’t it used to be given on flighstats.com?
One can get some idea of recent on time performance here. I can’t find the more complete stats that give average length of delay and longest delay. Didn’t it used to be given on flighstats.com?