Not currently tracked · last seen 1h ago
- Flights observed
- 109 showing last 50
- Avg flight time
- 5h 29m
- Typical route
- CGK → DPS
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | CGK → DPS | May 30, 01:30 UTC | May 30, 02:10 UTC | 40m |
| 2026-05-29 | CGK → DPS | May 29, 12:40 UTC | May 30, 00:25 UTC | 11h 45m |
| 2026-05-29 | CGK → DPS | May 29, 03:00 UTC | May 29, 11:35 UTC | 8h 35m |
| 2026-05-27 | CGK → DPS | May 27, 12:40 UTC | May 27, 13:20 UTC | 40m |
| 2026-05-27 | DPS → CGK | May 27, 11:35 UTC | May 27, 11:50 UTC | 15m |
| 2026-05-26 | CGK → DPS | May 26, 04:35 UTC | May 26, 05:15 UTC | 40m |
| 2026-05-23 | HKT → DPS | May 23, 04:45 UTC | May 23, 14:30 UTC | 9h 45m |
| 2026-05-22 | CGK → DPS | May 22, 12:50 UTC | May 23, 03:55 UTC | 15h 4m |
| 2026-05-22 | CGK → DPS | May 22, 03:05 UTC | May 22, 11:45 UTC | 8h 40m |
| 2026-05-22 | DPS → CGK | May 22, 01:40 UTC | May 22, 02:05 UTC | 25m |
| 2026-05-21 | PER → DPS | May 21, 04:05 UTC | May 22, 02:05 UTC | 22h 0m |
| 2026-05-21 | DPS → PER | May 21, 02:15 UTC | May 21, 02:55 UTC | 40m |
| 2026-05-19 | PER → DPS | May 19, 04:15 UTC | May 19, 04:50 UTC | 35m |
| 2026-05-19 | DPS → PER | May 19, 02:25 UTC | May 19, 03:05 UTC | 40m |
| 2026-05-18 | CGK → DPS | May 18, 01:45 UTC | May 18, 02:25 UTC | 40m |
| 2026-05-16 | CGK → DPS | May 16, 07:11 UTC | May 16, 07:51 UTC | 40m |
| 2026-05-15 | CGK → DPS | May 15, 12:40 UTC | May 16, 05:51 UTC | 17h 10m |
| 2026-05-15 | CGK → DPS | May 15, 02:55 UTC | May 15, 11:35 UTC | 8h 40m |
| 2026-05-14 | CGK → DPS | May 14, 07:05 UTC | May 14, 07:15 UTC | 10m |
| 2026-05-14 | CGK → DPS | May 14, 01:50 UTC | May 14, 06:05 UTC | 4h 15m |
| 2026-05-12 | PER → DPS | May 12, 04:25 UTC | May 12, 05:00 UTC | 35m |
| 2026-05-12 | DPS → PER | May 12, 02:45 UTC | May 12, 03:15 UTC | 30m |
| 2026-05-10 | CGK → DPS | May 10, 01:55 UTC | May 10, 02:34 UTC | 40m |
| 2026-05-10 | DPS → CGK | May 10, 00:34 UTC | May 10, 00:49 UTC | 15m |
| 2026-05-09 | HKT → DPS | May 9, 10:30 UTC | May 9, 14:40 UTC | 4h 10m |
| 2026-05-07 | CGK → DPS | May 7, 07:25 UTC | May 7, 07:50 UTC | 25m |
| 2026-05-07 | DPS → CGK | May 7, 06:15 UTC | May 7, 06:30 UTC | 15m |
| 2026-05-07 | CGK → DPS | May 7, 01:45 UTC | May 7, 05:35 UTC | 3h 50m |
| 2026-05-07 | DPS → CGK | May 7, 00:30 UTC | May 7, 00:45 UTC | 15m |
| 2026-05-06 | KUL → DPS | May 6, 10:35 UTC | May 6, 11:00 UTC | 25m |
| 2026-05-06 | DPS → KUL | May 6, 08:55 UTC | May 6, 09:20 UTC | 25m |
| 2026-05-04 | PER → DPS | May 4, 09:15 UTC | May 4, 09:50 UTC | 35m |
| 2026-05-04 | DPS → PER | May 4, 01:44 UTC | May 4, 08:00 UTC | 6h 15m |
| 2026-05-03 | DAD → DPS | May 3, 01:40 UTC | May 3, 14:55 UTC | 13h 14m |
| 2026-05-02 | CGK → DPS | May 2, 08:45 UTC | May 3, 00:45 UTC | 16h 0m |
| 2026-05-02 | KUL → DPS | May 2, 02:45 UTC | May 2, 07:50 UTC | 5h 5m |
| 2026-05-01 | HKT → DPS | May 1, 10:30 UTC | May 2, 01:40 UTC | 15h 10m |
| 2026-04-30 | HKT → DPS | Apr 30, 20:50 UTC | May 1, 14:50 UTC | 18h 0m |
| 2026-04-30 | MEL → DPS | Apr 30, 20:25 UTC | May 1, 14:50 UTC | 18h 25m |
| 2026-04-30 | DPS → MEL | Apr 30, 17:40 UTC | Apr 30, 18:55 UTC | 1h 15m |
| 2026-04-29 | DPS → MEL | Apr 29, 23:35 UTC | Apr 30, 18:55 UTC | 19h 20m |
| 2026-04-29 | PER → DPS | Apr 29, 12:40 UTC | Apr 29, 21:40 UTC | 9h 0m |
| 2026-04-29 | KUL → DPS | Apr 29, 03:00 UTC | Apr 29, 11:40 UTC | 8h 41m |
| 2026-04-28 | DPS → KUL | Apr 28, 13:10 UTC | Apr 29, 01:59 UTC | 12h 50m |
| 2026-04-28 | CGK → DPS | Apr 28, 07:40 UTC | Apr 28, 12:15 UTC | 4h 35m |
| 2026-04-28 | DPS → CGK | Apr 28, 06:35 UTC | Apr 28, 06:45 UTC | 10m |
| 2026-04-28 | CGK → DPS | Apr 28, 02:10 UTC | Apr 28, 02:55 UTC | 45m |
| 2026-04-27 | SIN → CGK | Apr 27, 13:35 UTC | Apr 27, 13:55 UTC | 20m |
| 2026-04-27 | SIN → CGK | Apr 27, 12:35 UTC | Apr 27, 12:45 UTC | 10m |
| 2026-04-27 | CGK → SIN | Apr 27, 09:55 UTC | Apr 27, 10:20 UTC | 25m |
Specifications
| Registration | PK-AZE |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 8A03F3 · 42401763 (octal) |
Looking for transponder-level data? View the Mode-S 8A03F3 page for country allocation, callsign history, and ADS-B signal details.
PK-AZE frequently asked
What type of aircraft is PK-AZE?
PK-AZE is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for PK-AZE?
PK-AZE broadcasts on Mode-S (ICAO 24-bit) address 8A03F3 (octal 42401763). View the transponder page.
What route does PK-AZE typically fly?
PK-AZE most frequently flies between CGK and DPS based on observed flights.
Where is PK-AZE right now?
PK-AZE is not currently being tracked; last seen 1h ago.