Not currently tracked · last seen 5h ago
- Flights observed
- 299 showing last 50
- Avg flight time
- 3h 10m
- Typical route
- PFO → EXT
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 19:20 UTC | Jul 13, 22:40 UTC | 3h 20m |
| 2026-07-13 | CFU → BOH | Jul 13, 15:00 UTC | Jul 13, 17:55 UTC | 2h 55m |
| 2026-07-13 | - | Jul 13, 10:20 UTC | Jul 13, 13:30 UTC | 3h 10m |
| 2026-07-13 | - | Jul 13, 06:01 UTC | Jul 13, 08:25 UTC | 2h 25m |
| 2026-07-12 | - | Jul 12, 13:50 UTC | Jul 12, 17:15 UTC | 3h 25m |
| 2026-07-12 | - | Jul 12, 07:25 UTC | Jul 12, 10:30 UTC | 3h 5m |
| 2026-07-11 | PFO → EXT | Jul 11, 18:25 UTC | Jul 11, 23:00 UTC | 4h 35m |
| 2026-07-11 | EXT → PFO | Jul 11, 12:30 UTC | Jul 11, 16:55 UTC | 4h 25m |
| 2026-07-11 | IBZ → EXT | Jul 11, 08:25 UTC | Jul 11, 10:25 UTC | 2h 0m |
| 2026-07-11 | EXT → IBZ | Jul 11, 05:05 UTC | Jul 11, 07:05 UTC | 2h 0m |
| 2026-07-10 | - | Jul 10, 19:30 UTC | Jul 10, 22:35 UTC | 3h 5m |
| 2026-07-10 | BHX → PMI | Jul 10, 14:20 UTC | Jul 10, 17:50 UTC | 3h 30m |
| 2026-07-10 | - | Jul 10, 10:05 UTC | Jul 10, 12:55 UTC | 2h 50m |
| 2026-07-10 | - | Jul 10, 05:15 UTC | Jul 10, 07:50 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 20:00 UTC | Jul 10, 00:00 UTC | 4h 0m |
| 2026-07-09 | - | Jul 9, 14:55 UTC | Jul 9, 18:20 UTC | 3h 25m |
| 2026-07-09 | - | Jul 9, 10:00 UTC | Jul 9, 13:30 UTC | 3h 30m |
| 2026-07-09 | - | Jul 9, 05:25 UTC | Jul 9, 08:30 UTC | 3h 5m |
| 2026-07-08 | RHO → EXT | Jul 8, 17:45 UTC | Jul 8, 21:55 UTC | 4h 10m |
| 2026-07-08 | EXT → RHO | Jul 8, 12:30 UTC | Jul 8, 16:10 UTC | 3h 40m |
| 2026-07-08 | - | Jul 8, 08:45 UTC | Jul 8, 10:35 UTC | 1h 50m |
| 2026-07-08 | BRS → FUE | Jul 8, 05:10 UTC | Jul 8, 07:05 UTC | 1h 55m |
| 2026-07-07 | - | Jul 7, 12:10 UTC | Jul 7, 15:35 UTC | 3h 25m |
| 2026-07-07 | - | Jul 7, 06:45 UTC | Jul 7, 10:25 UTC | 3h 40m |
| 2026-07-06 | - | Jul 6, 17:50 UTC | Jul 6, 21:50 UTC | 4h 0m |
| 2026-07-06 | EXT → DLM | Jul 6, 12:25 UTC | Jul 6, 16:00 UTC | 3h 35m |
| 2026-07-06 | SKG → LGW | Jul 6, 08:45 UTC | Jul 6, 10:45 UTC | 2h 0m |
| 2026-07-06 | LCA → CWL | Jul 6, 05:30 UTC | Jul 6, 07:20 UTC | 1h 50m |
| 2026-07-05 | - | Jul 5, 18:10 UTC | Jul 5, 22:15 UTC | 4h 5m |
| 2026-07-05 | - | Jul 5, 13:20 UTC | Jul 5, 16:55 UTC | 3h 35m |
| 2026-07-05 | - | Jul 5, 10:10 UTC | Jul 5, 12:05 UTC | 1h 55m |
| 2026-07-05 | - | Jul 5, 06:30 UTC | Jul 5, 08:30 UTC | 2h 0m |
| 2026-07-04 | - | Jul 4, 18:15 UTC | Jul 4, 22:55 UTC | 4h 40m |
| 2026-07-04 | - | Jul 4, 12:30 UTC | Jul 4, 16:30 UTC | 4h 0m |
| 2026-07-04 | IBZ → EXT | Jul 4, 08:25 UTC | Jul 4, 10:25 UTC | 2h 0m |
| 2026-07-04 | EXT → IBZ | Jul 4, 05:00 UTC | Jul 4, 06:55 UTC | 1h 55m |
| 2026-07-03 | - | Jul 3, 20:35 UTC | Jul 4, 00:10 UTC | 3h 35m |
| 2026-07-03 | BHX → PMI | Jul 3, 15:40 UTC | Jul 3, 19:10 UTC | 3h 30m |
| 2026-07-03 | TFS → MAN | Jul 3, 11:05 UTC | Jul 3, 14:05 UTC | 3h 0m |
| 2026-07-03 | EXT → CFU | Jul 3, 05:55 UTC | Jul 3, 08:25 UTC | 2h 30m |
| 2026-07-02 | - | Jul 2, 20:15 UTC | Jul 3, 00:25 UTC | 4h 10m |
| 2026-07-02 | - | Jul 2, 15:00 UTC | Jul 2, 18:35 UTC | 3h 35m |
| 2026-07-02 | - | Jul 2, 10:15 UTC | Jul 2, 13:40 UTC | 3h 25m |
| 2026-07-02 | - | Jul 2, 05:40 UTC | Jul 2, 08:55 UTC | 3h 15m |
| 2026-07-01 | PFO → EXT | Jul 1, 14:35 UTC | Jul 1, 19:00 UTC | 4h 25m |
| 2026-07-01 | EXT → PFO | Jul 1, 09:05 UTC | Jul 1, 13:15 UTC | 4h 10m |
| 2026-06-30 | - | Jun 30, 19:05 UTC | Jun 30, 22:55 UTC | 3h 50m |
| 2026-06-30 | CWL → CWL | Jun 30, 13:50 UTC | Jun 30, 17:20 UTC | 3h 30m |
| 2026-06-30 | - | Jun 30, 10:10 UTC | Jun 30, 12:15 UTC | 2h 5m |
| 2026-06-30 | - | Jun 30, 05:50 UTC | Jun 30, 07:45 UTC | 1h 55m |
Specifications
| Registration | G-FDZS |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 405E24 · 20057044 (octal) |
Looking for transponder-level data? View the Mode-S 405E24 page for country allocation, callsign history, and ADS-B signal details.
G-FDZS frequently asked
What type of aircraft is G-FDZS?
G-FDZS is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for G-FDZS?
G-FDZS broadcasts on Mode-S (ICAO 24-bit) address 405E24 (octal 20057044). View the transponder page.
What route does G-FDZS typically fly?
G-FDZS most frequently flies between PFO and EXT based on observed flights.
Where is G-FDZS right now?
G-FDZS is not currently being tracked; last seen 5h ago.