Flight
ETH3651
Flight history and live tracking for ETH3651, operated by Ethiopian Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Ethiopian Airlines |
| Observed route | SBGR → SBCH |
Flight history 47 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-20estimated | ? | ? | 10:21Z | 15:06Z | 4h 44m | 4015C |
| 2026-08-16estimated | ? | ? | 00:13Z | 14:58Z | 14h 44m | 4008C |
| 2026-08-13estimated | ? | ? | 16:19Z | 19:50Z | 3h 31m | 4008C |
Earlier flights (44) - back to 2026-01-19
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 04:36Z | 07:44Z | 3h 07m | 4008B |
| 2026-07-19estimated | ? | ? | 03:55Z | 04:54Z | 0h 58m | 4008C |
| 2026-07-16estimated | ? | ? | 06:37Z | 09:54Z | 3h 16m | 4008C |
| 2026-07-12estimated | SBGR | SBMT | 06:46 -03 | 12:26 -03 | 5h 39m | 40168 |
| 2026-07-09partial | SBGR | ? | 13:40 -03 | 40168 | ||
| 2026-07-05estimated | SBMT | SBCH | 22:22 -03 | 08:40 -03 | 10h 18m | 40168 |
| 2026-07-02estimated | SBGR | SBCH | 04:44 -03 | 15:14 -03 | 10h 29m | 40168 |
| 2026-06-28estimated | SBGR | SBPF | 06:32 -03 | 17:43 -03 | 11h 11m | 40060 |
| 2026-06-25 | SBMT | SBGR | 13:20 -03 | 16:56 -03 | 3h 35m | 40060 |
| 2026-06-21estimated | SBSJ | SBCH | 00:07 -03 | 10:51 -03 | 10h 43m | 4022C |
| 2026-06-18partial | SBGR | ? | 09:25 -03 | 4022C | ||
| 2026-06-15estimated | SBGR | SBCH | 21:52 -03 | 05:49 -03 | 7h 56m | 40156 |
| 2026-05-28 | SBMT | SBGR | 13:42 -03 | 16:24 -03 | 2h 41m | 40159 |
| 2026-05-24estimated | SBGR | SBCH | 23:55 -03 | 02:18 -03 | 2h 22m | 40159 |
| 2026-05-23partial | SBGR | ? | 20:06 -03 | 40159 | ||
| 2026-05-21 | SBMT | SBCH | 03:00 -03 | 06:22 -03 | 3h 21m | 40159 |
| 2026-05-19partial | SBGR | ? | 03:46 -03 | 4008B | ||
| 2026-05-10 | SBGR | SBMT | 08:03 -03 | 11:32 -03 | 3h 28m | 4008B |
| 2026-05-07 | SBGR | SBCH | 02:04 -03 | 12:13 -03 | 10h 09m | 4015C |
| 2026-05-04estimated | SBGR | SBCH | 09:57 -03 | 20:29 -03 | 10h 31m | 4015C |
| 2026-04-30partial | SBGR | ? | 22:49 -03 | 40062 | ||
| 2026-04-29partial | SBGR | ? | 19:53 -03 | 40062 | ||
| 2026-04-26partial | SBGR | ? | 22:11 -03 | 40159 | ||
| 2026-04-23estimated | ? | ? | 03:41Z | 06:56Z | 3h 14m | 40159 |
| 2026-04-19estimated | ? | ? | 00:46Z | 08:13Z | 7h 26m | 4008B |
| 2026-04-16estimated | ? | ? | 00:13Z | 03:34Z | 3h 20m | 4008B |
| 2026-04-11estimated | ? | ? | 00:17Z | 13:50Z | 13h 33m | 40159 |
| 2026-04-01estimated | ? | ? | 10:01Z | 10:20Z | 0h 18m | 4008B |
| 2026-03-30estimated | ? | ? | 08:27Z | 20:31Z | 12h 04m | 4008C |
| 2026-03-12 | SBSJ | SBGR | 03:13 -03 | 05:50 -03 | 2h 36m | 4008B |
| 2026-03-09 | SBJF | SBSP | 09:03 -03 | 11:58 -03 | 2h 55m | 04008B |
| 2026-03-04 | ? | SBGR | 04:54Z | 11:26 -03 | 9h 32m | 04022B |
| 2026-03-01 | ? | SBGR | 12:58Z | 12:39 -03 | 2h 40m | 04022B |
| 2026-02-26 | ? | SBSP | 10:43Z | 11:20 -03 | 3h 36m | 04008B |
| 2026-02-24 | ? | SBSP | 02:09Z | 02:07 -03 | 2h 58m | 040168 |
| 2026-02-20 | ? | SBGR | 05:52Z | 05:18 -03 | 2h 26m | 04008B |
| 2026-02-16 | SBJF | SBGR | 05:12 -03 | 08:11 -03 | 2h 59m | 040156 |
| 2026-02-12 | SBGL | SBGR | 03:04 -03 | 05:35 -03 | 2h 30m | 40060 |
| 2026-02-10estimated | ? | ? | 09:18Z | 13:14Z | 3h 55m | 04008B |
| 2026-02-02 | ? | SBSP | 10:25Z | 10:19 -03 | 2h 53m | 040060 |
| 2026-01-28 | ? | SBSP | 03:11Z | 02:50 -03 | 2h 38m | 04008B |
| 2026-01-26 | ? | SBGR | 06:16Z | 06:08 -03 | 2h 52m | 040062 |
| 2026-01-21 | ? | SBGR | 08:07Z | 08:47 -03 | 3h 40m | 040062 |
| 2026-01-19 | SBES | SBGR | 04:32 -03 | 07:12 -03 | 2h 40m | 04022A |
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]