Not currently tracked · last seen Jul 26, 21:30 UTC
- Flights observed
- 135 showing last 50
- Avg flight time
- 13h 41m
- Typical route
- CAN → ADD
- Last seen
- Jul 26, 21:30 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | ADD → CAN | Jul 26, 01:15 UTC | Jul 26, 21:30 UTC | 20h 16m |
| 2026-07-24 | TFU → ADD | Jul 24, 04:15 UTC | Jul 24, 22:50 UTC | 18h 35m |
| 2026-07-24 | ADD → TFU | Jul 24, 02:20 UTC | Jul 24, 22:50 UTC | 20h 30m |
| 2026-07-22 | ADD → DXB | Jul 22, 23:10 UTC | Jul 22, 23:35 UTC | 25m |
| 2026-07-21 | - | Jul 21, 03:35 UTC | Jul 21, 21:40 UTC | 18h 5m |
| 2026-07-21 | - | Jul 21, 01:35 UTC | Jul 21, 21:40 UTC | 20h 5m |
| 2026-07-21 | ADD → CAN | Jul 21, 01:00 UTC | Jul 21, 21:40 UTC | 20h 40m |
| 2026-07-19 | TFU → ADD | Jul 19, 03:55 UTC | Jul 19, 22:20 UTC | 18h 25m |
| 2026-07-19 | ADD → TFU | Jul 19, 02:00 UTC | Jul 19, 22:20 UTC | 20h 20m |
| 2026-07-17 | TFU → ADD | Jul 17, 03:34 UTC | Jul 17, 22:40 UTC | 19h 5m |
| 2026-07-17 | ADD → TFU | Jul 17, 01:39 UTC | Jul 17, 22:40 UTC | 21h 0m |
| 2026-07-16 | ADD → TFU | Jul 16, 14:00 UTC | Jul 17, 05:20 UTC | 15h 20m |
| 2026-07-15 | - | Jul 15, 19:00 UTC | Jul 16, 11:40 UTC | 16h 40m |
| 2026-07-15 | - | Jul 15, 03:35 UTC | Jul 15, 22:25 UTC | 18h 50m |
| 2026-07-15 | - | Jul 15, 01:35 UTC | Jul 15, 22:25 UTC | 20h 50m |
| 2026-07-15 | - | Jul 15, 00:55 UTC | Jul 15, 22:25 UTC | 21h 30m |
| 2026-07-13 | - | Jul 13, 03:40 UTC | Jul 13, 22:45 UTC | 19h 5m |
| 2026-07-13 | - | Jul 13, 01:35 UTC | Jul 13, 22:45 UTC | 21h 10m |
| 2026-07-13 | - | Jul 13, 00:55 UTC | Jul 13, 22:45 UTC | 21h 50m |
| 2026-07-12 | - | Jul 12, 09:45 UTC | Jul 12, 09:55 UTC | 10m |
| 2026-07-11 | - | Jul 11, 18:45 UTC | Jul 11, 22:20 UTC | 3h 35m |
| 2026-07-11 | - | Jul 11, 02:00 UTC | Jul 11, 05:50 UTC | 3h 50m |
| 2026-07-09 | - | Jul 9, 19:05 UTC | Jul 9, 22:50 UTC | 3h 45m |
| 2026-07-09 | - | Jul 9, 01:05 UTC | Jul 9, 04:45 UTC | 3h 40m |
| 2026-07-07 | CAN → ADD | Jul 7, 03:35 UTC | Jul 7, 21:45 UTC | 18h 10m |
| 2026-07-07 | - | Jul 7, 01:35 UTC | Jul 7, 21:45 UTC | 20h 10m |
| 2026-07-06 | - | Jul 6, 09:30 UTC | Jul 6, 09:45 UTC | 15m |
| 2026-07-05 | - | Jul 5, 03:45 UTC | Jul 5, 22:50 UTC | 19h 5m |
| 2026-07-05 | - | Jul 5, 01:50 UTC | Jul 5, 22:50 UTC | 21h 0m |
| 2026-07-04 | - | Jul 4, 13:40 UTC | Jul 5, 05:25 UTC | 15h 45m |
| 2026-07-03 | - | Jul 3, 19:35 UTC | Jul 4, 11:40 UTC | 16h 5m |
| 2026-07-03 | - | Jul 3, 03:40 UTC | Jul 3, 22:55 UTC | 19h 15m |
| 2026-07-03 | - | Jul 3, 01:50 UTC | Jul 3, 22:55 UTC | 21h 5m |
| 2026-06-30 | - | Jun 30, 13:05 UTC | Jun 30, 13:30 UTC | 25m |
| 2026-06-29 | CAN → ADD | Jun 29, 18:25 UTC | Jun 30, 11:40 UTC | 17h 16m |
| 2026-06-29 | CAN → ADD | Jun 29, 16:55 UTC | Jun 30, 11:40 UTC | 18h 46m |
| 2026-06-29 | - | Jun 29, 01:00 UTC | Jun 29, 04:39 UTC | 3h 40m |
| 2026-06-28 | - | Jun 28, 10:00 UTC | Jun 28, 10:10 UTC | 10m |
| 2026-06-27 | CAN → ADD | Jun 27, 05:35 UTC | Jun 27, 23:34 UTC | 18h 0m |
| 2026-06-27 | CAN → ADD | Jun 27, 03:34 UTC | Jun 27, 23:34 UTC | 20h 0m |
| 2026-06-27 | CAN → ADD | Jun 27, 01:35 UTC | Jun 27, 23:34 UTC | 22h 0m |
| 2026-06-27 | CAN → ADD | Jun 27, 00:55 UTC | Jun 27, 23:29 UTC | 22h 35m |
| 2026-06-24 | - | Jun 24, 22:45 UTC | Jun 24, 23:14 UTC | 30m |
| 2026-06-24 | - | Jun 24, 06:10 UTC | Jun 24, 20:20 UTC | 14h 10m |
| 2026-06-24 | - | Jun 24, 01:49 UTC | Jun 24, 02:45 UTC | 55m |
| 2026-06-23 | - | Jun 23, 09:24 UTC | Jun 23, 09:40 UTC | 15m |
| 2026-06-22 | CAN → ADD | Jun 22, 17:10 UTC | Jun 22, 21:45 UTC | 4h 35m |
| 2026-06-22 | - | Jun 22, 00:50 UTC | Jun 22, 03:45 UTC | 2h 55m |
| 2026-06-20 | CAN → ADD | Jun 20, 20:34 UTC | Jun 20, 22:25 UTC | 1h 50m |
| 2026-06-20 | CAN → ADD | Jun 20, 02:44 UTC | Jun 20, 20:29 UTC | 17h 45m |
Specifications
| Registration | ET-APY |
| Aircraft type | BOEING 777-300ER (B77W) |
| Mode-S code | 040066 · 01000146 (octal) |
Looking for transponder-level data? View the Mode-S 040066 page for country allocation, callsign history, and ADS-B signal details.
ET-APY frequently asked
What type of aircraft is ET-APY?
ET-APY is a BOEING 777-300ER (ICAO type code B77W).
What is the Mode-S transponder code for ET-APY?
ET-APY broadcasts on Mode-S (ICAO 24-bit) address 040066 (octal 01000146). View the transponder page.
What route does ET-APY typically fly?
ET-APY most frequently flies between CAN and ADD based on observed flights.
Where is ET-APY right now?
ET-APY is not currently being tracked; last seen Jul 26, 21:30 UTC.