JNBCPT
Johannesburg to Cape Town
Direct and one-stop flights from O. R. Tambo International (JNB) to Cape Town International (CPT), ranked by how reliably they actually get you there.
Our recommendation
Not enough flight history yet to recommend a journey
We don't have enough flight history yet to recommend a way to fly from Johannesburg to Cape Town.
Flexible on dates?
Pick a range of up to 14 days and we'll tell you the best day to fly, and the most reliable journey that actually operates on each date.
Every way to fly Johannesburg to Cape Town
Past year. Direct flights and one-stop journeys, ranked by how reliably they actually got passengers there. A journey is on time if it reached Cape Town within 15 minutes of schedule; a missed connection counts as late.
Live prices aren't connected in this preview yet. When they are, each journey shows its lowest current fare for the date you pick. Prices never affect our recommendation.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 55m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 2h 00m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 00m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 58m on average.
- Journey
- 2h 25m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 1h 56m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 2h 06m on average.
- Journey
- 2h 06m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 57m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 58m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 52m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 56m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 57m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 11m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 06m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 20m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 05m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 04m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 15m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 59m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 59m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 09m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 1h 54m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 18m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 12m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 02m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 05m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 12m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- Journey
- 2h 20m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 10m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 03m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 05m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 56m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 02m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 05m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 08m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 00m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 06m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 07m on average.
- Journey
- 2h 10m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 55m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 2h 04m on average.
- Journey
- 2h 15m
- Arrived on time
- 100%
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 1 journeys; it actually took 1h 59m on average.
- Journey
- 20h 45m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 20h 38m on average.
- 7h 40m stopover in Dubai
What this means
A long wait at the airport in Dubai. Check whether you can stay airside or need to pass through immigration.
- Journey
- 25h 25m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 25h 03m on average.
- Journey
- 22h 10m
- Arrived on time
- 100%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 21h 48m on average.
- Journey
- 2h 15m
- Arrived on time
- 67%
- Flies
- Wed, Thu, Fri
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 3 journeys; it actually took 2h 32m on average.
- Journey
- 2h 15m
- Arrived on time
- 50%
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 2h 28m on average.
- Journey
- 21h 55m
- Arrived on time
- 50%
- Missed connections
- 0% of days
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 2 journeys; it actually took 21h 58m on average.
- Journey
- 2h 10m
- Arrived on time
- —
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 2h 15m
- Arrived on time
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 2h 15m
- Arrived on time
- —
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 2h 10m
- Arrived on time
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 2h 15m
- Arrived on time
- —
- Flies
- Wed
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 2h 05m
- Arrived on time
- —
- Flies
- Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 5h 25m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 5h 20m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- 3h 15m stopover in Durban · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 40m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- 3h 15m stopover in Durban · Two airlines: book on one ticket
What this means
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 6h 35m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 8h 30m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- Journey
- 8h 25m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- 7h 00m stopover in Durban
What this means
A long wait at the airport in Durban. Check whether you can stay airside or need to pass through immigration.
- Journey
- 10h 30m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
- 6h 50m stopover in Durban · Two airlines: book on one ticket
What this means
A long wait at the airport in Durban. Check whether you can stay airside or need to pass through immigration.
These flights are on different airlines. Book them together on one ticket so that if the first flight is late, the airline has to get you on a later flight. On separate tickets, a missed connection is your cost, and you'd usually collect your bags and check in again.
- Journey
- 10h 20m
- Arrived on time
- —
- Missed connections
- —
- Flies
- Wed, Thu
- Price
- —
- Passengers
- —
- Verdict
- Not enough history
Based on 0 journeys.
Direct flights by airline
| Rank | Airline | Verdict | On time | Late | Cancelled | Typical delay when late | Passengers | Crew service |
|---|---|---|---|---|---|---|---|---|
| 1 | FlySafair FA101, FA103, FA105, FA113, FA115, FA121, FA125, FA200, FA202, FA204, FA206, FA214, FA216, FA292, FA294, FA298, FA380, FA494, FA512, FA600, FA604, FA620, FA691, FA692, FA702, FA806 | 10.0 | 100% | 0 of 36 | 0 | — | No ratings yet | — |
| 2 | South African Airways SA303, SA313, SA317, SA319, SA327, SA343, SA347, SA355, SA359, SA363, SA375 | 10.0 | 100% | 0 of 17 | 0 | — | No ratings yet | — |
| 3 | Airlink 4Z921, 4Z923, 4Z927, 4Z929, 4Z931, 4Z937, 4Z941, 4Z951 | 9.2 | 92% | 1 of 13 | 0 | 17 min | No ratings yet | — |
| VivaColombia 5Z834, 5Z840 | No score yet | 100% | 0 of 1 | 0 | — | No ratings yet | — | |
| TransAsia Airways GE101, GE111, GE123, GE125, GE131, GE133, GE151, GE153 | No score yet | 100% | 0 of 8 | 0 | — | No ratings yet | — | |
| Singapore Airlines SQ478 | No score yet | 67% | 1 of 3 | 0 | 1h 12m | No ratings yet | — |
On-time record over time
Not enough flights yet to show a trend.
Questions travellers ask
Which airline is most on time from Johannesburg to Cape Town?
Over the past year, FlySafair had the best record on this route, arriving on time on 100% of 36 flights.
Which airlines fly direct from Johannesburg to Cape Town?
FlySafair (FA101, FA103, FA105, FA113, FA115, FA121, FA125, FA200, FA202, FA204, FA206, FA214, FA216, FA292, FA294, FA298, FA380, FA494, FA512, FA600, FA604, FA620, FA691, FA692, FA702, FA806), South African Airways (SA303, SA313, SA317, SA319, SA327, SA343, SA347, SA355, SA359, SA363, SA375), Airlink (4Z921, 4Z923, 4Z927, 4Z929, 4Z931, 4Z937, 4Z941, 4Z951), VivaColombia (5Z834, 5Z840), TransAsia Airways (GE101, GE111, GE123, GE125, GE131, GE133, GE151, GE153), Singapore Airlines (SQ478).
How often are Airlink flights from Johannesburg to Cape Town late?
1 of 13 flights arrived more than 15 minutes late over the past year. When late, the typical delay was 17 min.