Not currently tracked · last seen Jul 26, 07:40 UTC
- Flights observed
- 57 showing last 50
- Avg flight time
- 3h 45m
- Typical route
- MED → CAI
- Last seen
- Jul 26, 07:40 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | CAI → MED | Jul 26, 07:30 UTC | Jul 26, 07:40 UTC | 10m |
| 2026-07-26 | MED → CAI | Jul 26, 05:00 UTC | Jul 26, 05:15 UTC | 15m |
| 2026-07-25 | DMM → MED | Jul 25, 22:50 UTC | Jul 25, 22:55 UTC | 5m |
| 2026-07-25 | MED → CAI | Jul 25, 05:10 UTC | Jul 25, 05:25 UTC | 15m |
| 2026-07-24 | CAI → MED | Jul 24, 08:00 UTC | Jul 24, 08:15 UTC | 15m |
| 2026-07-24 | MED → CAI | Jul 24, 05:00 UTC | Jul 24, 05:30 UTC | 30m |
| 2026-07-23 | MED → CAI | Jul 23, 07:35 UTC | Jul 24, 05:30 UTC | 21h 55m |
| 2026-07-23 | MED → CAI | Jul 23, 05:10 UTC | Jul 23, 05:35 UTC | 25m |
| 2026-07-22 | MED → CAI | Jul 22, 05:05 UTC | Jul 22, 05:20 UTC | 15m |
| 2026-07-21 | MED → CAI | Jul 21, 07:50 UTC | Jul 22, 05:20 UTC | 21h 30m |
| 2026-07-21 | MED → CAI | Jul 21, 05:05 UTC | Jul 21, 05:35 UTC | 30m |
| 2026-07-20 | - | Jul 20, 19:35 UTC | Jul 20, 19:50 UTC | 15m |
| 2026-07-20 | CAI → MED | Jul 20, 07:25 UTC | Jul 20, 07:40 UTC | 15m |
| 2026-07-20 | MED → CAI | Jul 20, 05:00 UTC | Jul 20, 05:20 UTC | 20m |
| 2026-07-18 | MED → CAI | Jul 18, 19:10 UTC | Jul 19, 05:25 UTC | 10h 15m |
| 2026-07-17 | - | Jul 17, 09:25 UTC | Jul 17, 10:20 UTC | 55m |
| 2026-07-17 | - | Jul 17, 06:35 UTC | Jul 17, 07:00 UTC | 25m |
| 2026-07-15 | CAI → RUH | Jul 15, 13:00 UTC | Jul 15, 13:15 UTC | 15m |
| 2026-07-14 | - | Jul 14, 17:50 UTC | Jul 15, 11:25 UTC | 17h 34m |
| 2026-07-14 | - | Jul 14, 15:05 UTC | Jul 14, 16:30 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 19:20 UTC | Jul 9, 20:10 UTC | 50m |
| 2026-07-09 | - | Jul 9, 11:35 UTC | Jul 9, 17:55 UTC | 6h 20m |
| 2026-07-09 | - | Jul 9, 09:15 UTC | Jul 9, 09:35 UTC | 20m |
| 2026-07-06 | - | Jul 6, 08:10 UTC | Jul 6, 08:35 UTC | 25m |
| 2026-07-06 | - | Jul 6, 05:55 UTC | Jul 6, 06:25 UTC | 30m |
| 2026-07-03 | - | Jul 3, 00:20 UTC | Jul 3, 00:30 UTC | 10m |
| 2026-07-02 | - | Jul 2, 06:30 UTC | Jul 2, 07:00 UTC | 30m |
| 2026-07-02 | - | Jul 2, 04:10 UTC | Jul 2, 04:50 UTC | 40m |
| 2026-07-01 | - | Jul 1, 07:25 UTC | Jul 1, 07:35 UTC | 10m |
| 2026-07-01 | - | Jul 1, 05:10 UTC | Jul 1, 05:30 UTC | 20m |
| 2026-06-30 | - | Jun 30, 08:05 UTC | Jul 1, 05:30 UTC | 21h 25m |
| 2026-06-30 | - | Jun 30, 06:00 UTC | Jun 30, 06:20 UTC | 20m |
| 2026-06-29 | - | Jun 29, 07:44 UTC | Jun 30, 06:20 UTC | 22h 35m |
| 2026-06-29 | - | Jun 29, 05:09 UTC | Jun 29, 05:30 UTC | 20m |
| 2026-06-04 | CAI → RUH | Jun 4, 23:50 UTC | Jun 5, 00:00 UTC | 10m |
| 2026-06-04 | RUH → CAI | Jun 4, 21:35 UTC | Jun 4, 21:55 UTC | 20m |
| 2026-05-27 | CAI → RUH | May 27, 23:45 UTC | May 28, 00:00 UTC | 15m |
| 2026-05-27 | RUH → CAI | May 27, 21:45 UTC | May 27, 22:10 UTC | 25m |
| 2026-05-24 | DAM → JED | May 24, 08:00 UTC | May 24, 08:10 UTC | 10m |
| 2026-05-23 | JED → DAM | May 23, 21:20 UTC | May 24, 06:00 UTC | 8h 40m |
| 2026-05-22 | CAI → JED | May 22, 19:05 UTC | May 22, 19:20 UTC | 15m |
| 2026-05-22 | JED → CAI | May 22, 16:45 UTC | May 22, 17:00 UTC | 15m |
| 2026-05-20 | DAM → JED | May 20, 08:00 UTC | May 20, 08:25 UTC | 25m |
| 2026-05-20 | JED → DAM | May 20, 05:50 UTC | May 20, 06:15 UTC | 25m |
| 2026-05-13 | DMM → EAM | May 13, 12:20 UTC | May 14, 06:35 UTC | 18h 15m |
| 2026-05-13 | CAI → DMM | May 13, 08:35 UTC | May 13, 08:45 UTC | 10m |
| 2026-05-13 | DMM → CAI | May 13, 06:15 UTC | May 13, 06:55 UTC | 40m |
| 2026-05-12 | DMM → MED | May 12, 05:10 UTC | May 12, 11:00 UTC | 5h 50m |
| 2026-05-11 | DMM → MED | May 11, 10:50 UTC | May 12, 05:20 UTC | 18h 30m |
| 2026-05-10 | CAI → RUH | May 10, 09:24 UTC | May 10, 09:40 UTC | 15m |
Specifications
| Registration | HZ-FAP |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 717CDB · 34276333 (octal) |
Looking for transponder-level data? View the Mode-S 717CDB page for country allocation, callsign history, and ADS-B signal details.
HZ-FAP frequently asked
What type of aircraft is HZ-FAP?
HZ-FAP is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for HZ-FAP?
HZ-FAP broadcasts on Mode-S (ICAO 24-bit) address 717CDB (octal 34276333). View the transponder page.
What route does HZ-FAP typically fly?
HZ-FAP most frequently flies between MED and CAI based on observed flights.
Where is HZ-FAP right now?
HZ-FAP is not currently being tracked; last seen Jul 26, 07:40 UTC.