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