Not currently tracked · last seen 49m ago
- Flights observed
- 282 showing last 50
- Avg flight time
- 2h 7m
- Typical route
- OPO → ORY
- Last seen
- 49m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 01:30 UTC | Jul 14, 04:15 UTC | 2h 45m |
| 2026-07-13 | - | Jul 13, 20:15 UTC | Jul 14, 00:10 UTC | 3h 55m |
| 2026-07-13 | CFU → ORY | Jul 13, 14:05 UTC | Jul 13, 16:45 UTC | 2h 40m |
| 2026-07-13 | - | Jul 13, 10:15 UTC | Jul 13, 12:15 UTC | 2h 0m |
| 2026-07-13 | - | Jul 13, 04:15 UTC | Jul 13, 05:31 UTC | 1h 15m |
| 2026-07-12 | ORY → MAD | Jul 12, 20:10 UTC | Jul 12, 22:00 UTC | 1h 50m |
| 2026-07-12 | JMK → ORY | Jul 12, 15:25 UTC | Jul 12, 18:40 UTC | 3h 15m |
| 2026-07-12 | ORY → JMK | Jul 12, 11:25 UTC | Jul 12, 14:20 UTC | 2h 55m |
| 2026-07-12 | - | Jul 12, 08:05 UTC | Jul 12, 10:05 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 04:55 UTC | Jul 12, 06:40 UTC | 1h 45m |
| 2026-07-11 | IBZ → ORY | Jul 11, 19:20 UTC | Jul 11, 21:15 UTC | 1h 55m |
| 2026-07-11 | ORY → IBZ | Jul 11, 16:25 UTC | Jul 11, 18:10 UTC | 1h 45m |
| 2026-07-11 | OPO → ORY | Jul 11, 13:25 UTC | Jul 11, 15:10 UTC | 1h 45m |
| 2026-07-11 | ORY → OPO | Jul 11, 10:00 UTC | Jul 11, 11:45 UTC | 1h 45m |
| 2026-07-11 | - | Jul 11, 05:35 UTC | Jul 11, 07:55 UTC | 2h 20m |
| 2026-07-10 | - | Jul 10, 16:40 UTC | Jul 10, 19:05 UTC | 2h 25m |
| 2026-07-10 | - | Jul 10, 12:50 UTC | Jul 10, 15:10 UTC | 2h 20m |
| 2026-07-10 | - | Jul 10, 09:05 UTC | Jul 10, 11:05 UTC | 2h 0m |
| 2026-07-10 | LIS → ORY | Jul 10, 05:40 UTC | Jul 10, 07:40 UTC | 2h 0m |
| 2026-07-09 | ORY → LIS | Jul 9, 19:50 UTC | Jul 9, 22:00 UTC | 2h 10m |
| 2026-07-09 | BCN → ORY | Jul 9, 17:00 UTC | Jul 9, 18:15 UTC | 1h 15m |
| 2026-07-09 | - | Jul 9, 14:25 UTC | Jul 9, 15:40 UTC | 1h 15m |
| 2026-07-09 | ORY → ORY | Jul 9, 05:20 UTC | Jul 9, 12:05 UTC | 6h 45m |
| 2026-07-08 | - | Jul 8, 17:25 UTC | Jul 8, 20:35 UTC | 3h 10m |
| 2026-07-08 | - | Jul 8, 16:20 UTC | Jul 8, 16:30 UTC | 10m |
| 2026-07-08 | - | Jul 8, 13:10 UTC | Jul 8, 15:35 UTC | 2h 25m |
| 2026-07-06 | OPO → ORY | Jul 6, 17:15 UTC | Jul 6, 19:00 UTC | 1h 45m |
| 2026-07-06 | ORY → OPO | Jul 6, 14:05 UTC | Jul 6, 16:00 UTC | 1h 55m |
| 2026-07-06 | - | Jul 6, 07:35 UTC | Jul 6, 09:55 UTC | 2h 20m |
| 2026-07-06 | - | Jul 6, 04:25 UTC | Jul 6, 06:10 UTC | 1h 45m |
| 2026-07-05 | OPO → ORY | Jul 5, 18:55 UTC | Jul 5, 20:40 UTC | 1h 45m |
| 2026-07-05 | ORY → OPO | Jul 5, 15:55 UTC | Jul 5, 17:40 UTC | 1h 45m |
| 2026-07-05 | SVQ → ORY | Jul 5, 12:30 UTC | Jul 5, 14:40 UTC | 2h 10m |
| 2026-07-05 | ORY → SVQ | Jul 5, 09:30 UTC | Jul 5, 11:30 UTC | 2h 0m |
| 2026-07-05 | - | Jul 5, 04:40 UTC | Jul 5, 06:45 UTC | 2h 5m |
| 2026-07-04 | - | Jul 4, 19:15 UTC | Jul 4, 21:20 UTC | 2h 5m |
| 2026-07-04 | OPO → ORY | Jul 4, 15:50 UTC | Jul 4, 17:40 UTC | 1h 50m |
| 2026-07-04 | ORY → OPO | Jul 4, 12:35 UTC | Jul 4, 14:35 UTC | 2h 0m |
| 2026-07-04 | OPO → ORY | Jul 4, 09:30 UTC | Jul 4, 11:20 UTC | 1h 50m |
| 2026-07-04 | ORY → OPO | Jul 4, 06:40 UTC | Jul 4, 08:30 UTC | 1h 50m |
| 2026-07-03 | - | Jul 3, 19:00 UTC | Jul 3, 21:10 UTC | 2h 10m |
| 2026-07-03 | - | Jul 3, 15:25 UTC | Jul 3, 17:25 UTC | 2h 0m |
| 2026-07-03 | - | Jul 3, 11:45 UTC | Jul 3, 13:45 UTC | 2h 0m |
| 2026-07-03 | - | Jul 3, 08:50 UTC | Jul 3, 10:30 UTC | 1h 40m |
| 2026-07-03 | - | Jul 3, 05:10 UTC | Jul 3, 07:20 UTC | 2h 10m |
| 2026-07-02 | ORY → FAO | Jul 2, 19:05 UTC | Jul 2, 21:15 UTC | 2h 10m |
| 2026-07-02 | - | Jul 2, 16:00 UTC | Jul 2, 17:50 UTC | 1h 50m |
| 2026-07-02 | - | Jul 2, 12:35 UTC | Jul 2, 14:10 UTC | 1h 35m |
| 2026-07-02 | OPO → ORY | Jul 2, 09:20 UTC | Jul 2, 11:20 UTC | 2h 0m |
| 2026-07-02 | ORY → OPO | Jul 2, 06:25 UTC | Jul 2, 08:10 UTC | 1h 45m |
Specifications
| Registration | F-GZHJ |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 3964E9 · 16262351 (octal) |
Looking for transponder-level data? View the Mode-S 3964E9 page for country allocation, callsign history, and ADS-B signal details.
F-GZHJ frequently asked
What type of aircraft is F-GZHJ?
F-GZHJ is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for F-GZHJ?
F-GZHJ broadcasts on Mode-S (ICAO 24-bit) address 3964E9 (octal 16262351). View the transponder page.
What route does F-GZHJ typically fly?
F-GZHJ most frequently flies between OPO and ORY based on observed flights.
Where is F-GZHJ right now?
F-GZHJ is not currently being tracked; last seen 49m ago.