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