Flight
SAA024
Flight history and live tracking for SAA024, operated by South African Airways. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | South African Airways |
| Observed route | FAJS → FALT |
Flight history 46 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-19estimated | ? | ? | 04:56Z | 18:42Z | 13h 45m | B22E |
| 2026-08-18estimated | ? | ? | 18:28Z | 19:47Z | 1h 19m | B22E |
| 2026-08-17estimated | ? | ? | 11:21Z | 19:22Z | 8h 00m | B22F |
| 2026-08-16estimated | ? | ? | 18:15Z | 18:42Z | 0h 26m | B22F |
| 2026-08-13estimated | ? | ? | 18:20Z | 18:44Z | 0h 23m | B230 |
| 2026-08-12estimated | ? | ? | 18:18Z | 18:42Z | 0h 23m | B230 |
Earlier flights (40) - back to 2026-03-31
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-22estimated | ? | ? | 05:02Z | 18:34Z | 13h 31m | B22B |
| 2026-07-21estimated | ? | ? | 18:08Z | 18:34Z | 0h 25m | B22B |
| 2026-07-20estimated | ? | ? | 18:25Z | 18:42Z | 0h 16m | B230 |
| 2026-07-19estimated | ? | ? | 18:10Z | 18:36Z | 0h 25m | A51A |
| 2026-07-16estimated | ? | ? | 05:04Z | 18:56Z | 13h 52m | B22D |
| 2026-07-15estimated | ? | ? | 18:13Z | 18:44Z | 0h 30m | B22D |
| 2026-07-14 | FAJS | FAGC | 06:57 SAST | 20:36 SAST | 13h 38m | 9893 |
| 2026-07-13estimated | FAPP | FAJS | 06:59 SAST | 20:38 SAST | 13h 38m | 9E06 |
| 2026-07-12estimated | FAJS | FAPB | 20:06 SAST | 20:30 SAST | 0h 24m | 9E06 |
| 2026-07-09estimated | FAJS | FAPP | 20:11 SAST | 20:34 SAST | 0h 22m | 9AD8 |
| 2026-06-17partial | FAJS | ? | 06:50 SAST | B230 | ||
| 2026-06-16estimated | FAJS | FAPB | 20:13 SAST | 20:38 SAST | 0h 24m | B230 |
| 2026-06-15estimated | FAJS | FALT | 20:07 SAST | 20:34 SAST | 0h 26m | 9D4A |
| 2026-06-14estimated | FAJS | FALT | 21:03 SAST | 21:28 SAST | 0h 24m | 9893 |
| 2026-05-27partial | FAJS | ? | 06:50 SAST | B22D | ||
| 2026-05-26estimated | FAJS | FAPP | 20:10 SAST | 20:32 SAST | 0h 21m | B22D |
| 2026-05-25 | FAJS | FAGC | 06:58 SAST | 20:32 SAST | 13h 33m | B22F |
| 2026-05-24estimated | FAJS | FALT | 20:36 SAST | 21:06 SAST | 0h 30m | B22F |
| 2026-05-21partial | FAJS | ? | 06:36 SAST | B230 | ||
| 2026-05-20 | FAJS | FAGC | 03:18 SAST | 20:32 SAST | 17h 13m | 9E06 |
| 2026-05-19partial | FAJS | ? | 06:03 SAST | B230 | ||
| 2026-05-12estimated | FAJS | FALT | 20:22 SAST | 20:50 SAST | 0h 27m | B230 |
| 2026-05-11estimated | FAJS | FAPB | 20:26 SAST | 20:50 SAST | 0h 24m | AF60 |
| 2026-05-10estimated | FAJS | FALT | 20:21 SAST | 20:48 SAST | 0h 26m | AF60 |
| 2026-05-06 | FAWK | FAGC | 07:28 SAST | 20:38 SAST | 13h 09m | 81EF |
| 2026-05-04estimated | FAJS | FAPP | 20:13 SAST | 20:34 SAST | 0h 20m | B22B |
| 2026-04-30partial | FAJS | ? | 06:51 SAST | B22E | ||
| 2026-04-29estimated | FAJS | FAPI | 20:08 SAST | 20:30 SAST | 0h 21m | B22E |
| 2026-04-28partial | FAJS | ? | 07:06 SAST | AF60 | ||
| 2026-04-27partial | FAJS | ? | 06:57 SAST | 9E06 | ||
| 2026-04-26estimated | FAJS | FALT | 20:18 SAST | 20:42 SAST | 0h 24m | 9E06 |
| 2026-04-23estimated | ? | ? | 04:54Z | 18:52Z | 13h 57m | B231 |
| 2026-04-22estimated | ? | ? | 04:47Z | 18:38Z | 13h 50m | B230 |
| 2026-04-21estimated | ? | ? | 04:56Z | 18:44Z | 13h 47m | 9D4A |
| 2026-04-20estimated | ? | ? | 05:03Z | 18:34Z | 13h 31m | B22D |
| 2026-04-19estimated | ? | ? | 18:16Z | 18:36Z | 0h 19m | B22D |
| 2026-04-16estimated | ? | ? | 18:16Z | 18:38Z | 0h 22m | 9D4A |
| 2026-04-15estimated | ? | ? | 05:05Z | 18:36Z | 13h 30m | B230 |
| 2026-04-14estimated | ? | ? | 18:18Z | 18:42Z | 0h 23m | B230 |
| 2026-03-31estimated | ? | ? | 05:18Z | 20:06Z | 14h 47m | B22B |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]