On the ground · transponder active
- Flights observed
- 181 showing last 50
- Avg flight time
- 8h 33m
- Typical route
- YUL → AMS
- Last seen
- 51m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 23:25 UTC | Jul 14, 05:00 UTC | 5h 35m |
| 2026-07-13 | - | Jul 13, 13:50 UTC | Jul 13, 20:45 UTC | 6h 55m |
| 2026-07-13 | - | Jul 13, 01:25 UTC | Jul 13, 07:30 UTC | 6h 5m |
| 2026-07-12 | - | Jul 12, 23:50 UTC | Jul 13, 00:01 UTC | 10m |
| 2026-07-12 | - | Jul 12, 13:30 UTC | Jul 12, 22:00 UTC | 8h 30m |
| 2026-07-11 | AMS → AMS | Jul 11, 13:00 UTC | Jul 12, 03:45 UTC | 14h 45m |
| 2026-07-09 | AMS → AMS | Jul 9, 12:45 UTC | Jul 10, 04:05 UTC | 15h 20m |
| 2026-07-08 | - | Jul 8, 11:05 UTC | Jul 9, 05:40 UTC | 18h 35m |
| 2026-07-08 | AMS → AMS | Jul 8, 10:50 UTC | Jul 9, 05:40 UTC | 18h 50m |
| 2026-07-07 | - | Jul 7, 21:50 UTC | Jul 8, 06:30 UTC | 8h 40m |
| 2026-07-07 | - | Jul 7, 08:40 UTC | Jul 7, 19:40 UTC | 11h 0m |
| 2026-07-05 | - | Jul 5, 11:05 UTC | Jul 6, 05:40 UTC | 18h 35m |
| 2026-07-05 | - | Jul 5, 10:40 UTC | Jul 6, 05:40 UTC | 19h 0m |
| 2026-07-04 | YUL → AMS | Jul 4, 23:40 UTC | Jul 5, 05:55 UTC | 6h 15m |
| 2026-07-04 | AMS → YUL | Jul 4, 13:50 UTC | Jul 4, 20:55 UTC | 7h 5m |
| 2026-07-03 | YEG → AMS | Jul 3, 23:35 UTC | Jul 4, 07:25 UTC | 7h 50m |
| 2026-07-03 | - | Jul 3, 13:15 UTC | Jul 3, 21:40 UTC | 8h 25m |
| 2026-07-01 | - | Jul 1, 11:05 UTC | Jul 2, 05:30 UTC | 18h 25m |
| 2026-07-01 | AMS → AMS | Jul 1, 10:45 UTC | Jul 2, 05:30 UTC | 18h 45m |
| 2026-07-01 | - | Jul 1, 04:50 UTC | Jul 1, 06:15 UTC | 1h 25m |
| 2026-06-30 | - | Jun 30, 09:05 UTC | Jul 1, 06:15 UTC | 21h 10m |
| 2026-06-30 | - | Jun 30, 08:40 UTC | Jul 1, 06:15 UTC | 21h 35m |
| 2026-06-29 | YYZ → AMS | Jun 29, 20:44 UTC | Jun 30, 03:35 UTC | 6h 51m |
| 2026-06-29 | - | Jun 29, 10:04 UTC | Jun 29, 17:30 UTC | 7h 25m |
| 2026-06-28 | - | Jun 28, 21:40 UTC | Jun 29, 05:59 UTC | 8h 20m |
| 2026-06-28 | - | Jun 28, 08:29 UTC | Jun 28, 19:40 UTC | 11h 10m |
| 2026-06-27 | YUL → AMS | Jun 27, 23:45 UTC | Jun 28, 05:55 UTC | 6h 10m |
| 2026-06-27 | - | Jun 27, 13:49 UTC | Jun 27, 20:34 UTC | 6h 45m |
| 2026-06-26 | YUL → AMS | Jun 26, 23:19 UTC | Jun 27, 05:35 UTC | 6h 15m |
| 2026-06-26 | AMS → YUL | Jun 26, 13:45 UTC | Jun 26, 20:50 UTC | 7h 5m |
| 2026-06-25 | - | Jun 25, 23:09 UTC | Jun 26, 05:30 UTC | 6h 20m |
| 2026-06-25 | - | Jun 25, 13:45 UTC | Jun 25, 20:49 UTC | 7h 5m |
| 2026-06-25 | - | Jun 25, 01:54 UTC | Jun 25, 10:20 UTC | 8h 25m |
| 2026-06-24 | - | Jun 24, 23:20 UTC | Jun 24, 23:34 UTC | 15m |
| 2026-06-24 | - | Jun 24, 21:40 UTC | Jun 24, 21:50 UTC | 10m |
| 2026-06-24 | - | Jun 24, 12:14 UTC | Jun 24, 21:00 UTC | 8h 45m |
| 2026-06-23 | YUL → AMS | Jun 23, 23:24 UTC | Jun 24, 05:40 UTC | 6h 15m |
| 2026-06-23 | AMS → YUL | Jun 23, 13:39 UTC | Jun 23, 20:49 UTC | 7h 10m |
| 2026-06-23 | - | Jun 23, 02:34 UTC | Jun 23, 10:19 UTC | 7h 45m |
| 2026-06-22 | - | Jun 22, 23:29 UTC | Jun 22, 23:39 UTC | 10m |
| 2026-06-22 | - | Jun 22, 21:45 UTC | Jun 22, 21:59 UTC | 15m |
| 2026-06-22 | - | Jun 22, 12:19 UTC | Jun 22, 21:10 UTC | 8h 50m |
| 2026-06-21 | YUL → AMS | Jun 21, 23:30 UTC | Jun 22, 05:44 UTC | 6h 15m |
| 2026-06-21 | - | Jun 21, 13:59 UTC | Jun 21, 20:54 UTC | 6h 55m |
| 2026-06-21 | - | Jun 21, 02:24 UTC | Jun 21, 10:19 UTC | 7h 55m |
| 2026-06-20 | - | Jun 20, 23:19 UTC | Jun 20, 23:29 UTC | 10m |
| 2026-06-20 | - | Jun 20, 21:44 UTC | Jun 20, 21:55 UTC | 10m |
| 2026-06-20 | - | Jun 20, 12:19 UTC | Jun 20, 21:10 UTC | 8h 50m |
| 2026-06-19 | YUL → AMS | Jun 19, 00:20 UTC | Jun 19, 06:35 UTC | 6h 15m |
| 2026-06-18 | AMS → YUL | Jun 18, 13:50 UTC | Jun 18, 20:45 UTC | 6h 55m |
Specifications
| Registration | PH-AOE |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | 484444 · 22042104 (octal) |
Looking for transponder-level data? View the Mode-S 484444 page for country allocation, callsign history, and ADS-B signal details.
PH-AOE frequently asked
What type of aircraft is PH-AOE?
PH-AOE is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for PH-AOE?
PH-AOE broadcasts on Mode-S (ICAO 24-bit) address 484444 (octal 22042104). View the transponder page.
What route does PH-AOE typically fly?
PH-AOE most frequently flies between YUL and AMS based on observed flights.
Where is PH-AOE right now?
PH-AOE is currently on the ground with its transponder active.