Not currently tracked · last seen Jul 25, 20:10 UTC
- Flights observed
- 384 showing last 50
- Avg flight time
- 2h 41m
- Typical route
- ORY → CMN
- Last seen
- Jul 25, 20:10 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-25 | CFU → AMS | Jul 25, 17:30 UTC | Jul 25, 19:55 UTC | 2h 25m |
| 2026-07-25 | AMS → CFU | Jul 25, 14:00 UTC | Jul 25, 16:05 UTC | 2h 5m |
| 2026-07-25 | ZTH → AMS | Jul 25, 09:30 UTC | Jul 25, 12:35 UTC | 3h 5m |
| 2026-07-25 | AMS → ZTH | Jul 25, 05:30 UTC | Jul 25, 08:05 UTC | 2h 35m |
| 2026-07-24 | - | Jul 24, 20:20 UTC | Jul 24, 22:25 UTC | 2h 5m |
| 2026-07-24 | AMS → PMI | Jul 24, 17:00 UTC | Jul 24, 19:05 UTC | 2h 5m |
| 2026-07-24 | AMS → BJV | Jul 24, 11:25 UTC | Jul 24, 15:00 UTC | 3h 35m |
| 2026-07-24 | AMS → BJV | Jul 24, 09:45 UTC | Jul 24, 09:55 UTC | 10m |
| 2026-07-24 | AMS → BJV | Jul 24, 05:30 UTC | Jul 24, 08:25 UTC | 2h 55m |
| 2026-07-23 | - | Jul 23, 17:45 UTC | Jul 23, 21:35 UTC | 3h 50m |
| 2026-07-23 | AMS → AYT | Jul 23, 13:15 UTC | Jul 23, 16:25 UTC | 3h 10m |
| 2026-07-22 | AYT → AMS | Jul 22, 21:20 UTC | Jul 23, 01:05 UTC | 3h 45m |
| 2026-07-22 | RTM → AYT | Jul 22, 16:50 UTC | Jul 22, 20:05 UTC | 3h 15m |
| 2026-07-22 | AYT → RTM | Jul 22, 11:40 UTC | Jul 22, 15:30 UTC | 3h 50m |
| 2026-07-22 | - | Jul 22, 02:40 UTC | Jul 22, 05:10 UTC | 2h 30m |
| 2026-07-21 | SOF → RAK | Jul 21, 01:25 UTC | Jul 21, 04:50 UTC | 3h 25m |
| 2026-07-20 | - | Jul 20, 18:10 UTC | Jul 20, 21:15 UTC | 3h 5m |
| 2026-07-20 | CMN → ETZ | Jul 20, 13:45 UTC | Jul 20, 16:25 UTC | 2h 40m |
| 2026-07-20 | ORY → CMN | Jul 20, 09:25 UTC | Jul 20, 12:15 UTC | 2h 50m |
| 2026-07-20 | CMN → ORY | Jul 20, 05:25 UTC | Jul 20, 07:55 UTC | 2h 30m |
| 2026-07-19 | ORY → CMN | Jul 19, 18:15 UTC | Jul 19, 21:00 UTC | 2h 45m |
| 2026-07-19 | RBA → ORY | Jul 19, 14:50 UTC | Jul 19, 17:00 UTC | 2h 10m |
| 2026-07-19 | ORY → RBA | Jul 19, 10:50 UTC | Jul 19, 13:30 UTC | 2h 40m |
| 2026-07-19 | - | Jul 19, 06:45 UTC | Jul 19, 09:05 UTC | 2h 20m |
| 2026-07-18 | - | Jul 18, 18:10 UTC | Jul 18, 21:10 UTC | 3h 0m |
| 2026-07-18 | - | Jul 18, 14:25 UTC | Jul 18, 16:50 UTC | 2h 25m |
| 2026-07-18 | - | Jul 18, 09:50 UTC | Jul 18, 12:35 UTC | 2h 45m |
| 2026-07-18 | - | Jul 18, 05:45 UTC | Jul 18, 08:10 UTC | 2h 25m |
| 2026-07-17 | ORY → CMN | Jul 17, 18:44 UTC | Jul 17, 21:34 UTC | 2h 50m |
| 2026-07-17 | RBA → ORY | Jul 17, 14:50 UTC | Jul 17, 17:09 UTC | 2h 20m |
| 2026-07-17 | - | Jul 17, 11:00 UTC | Jul 17, 13:35 UTC | 2h 35m |
| 2026-07-17 | CMN → ORY | Jul 17, 07:14 UTC | Jul 17, 09:40 UTC | 2h 25m |
| 2026-07-16 | ORY → CMN | Jul 16, 18:19 UTC | Jul 16, 21:19 UTC | 3h 0m |
| 2026-07-16 | - | Jul 16, 14:29 UTC | Jul 16, 16:55 UTC | 2h 25m |
| 2026-07-16 | - | Jul 16, 09:55 UTC | Jul 16, 13:10 UTC | 3h 15m |
| 2026-07-16 | - | Jul 16, 05:40 UTC | Jul 16, 08:10 UTC | 2h 30m |
| 2026-07-15 | ORY → CMN | Jul 15, 18:20 UTC | Jul 15, 21:15 UTC | 2h 55m |
| 2026-07-15 | RBA → ORY | Jul 15, 14:35 UTC | Jul 15, 16:55 UTC | 2h 20m |
| 2026-07-15 | ORY → RBA | Jul 15, 10:50 UTC | Jul 15, 13:25 UTC | 2h 35m |
| 2026-07-15 | - | Jul 15, 06:40 UTC | Jul 15, 08:55 UTC | 2h 15m |
| 2026-07-14 | - | Jul 14, 17:55 UTC | Jul 14, 20:50 UTC | 2h 55m |
| 2026-07-14 | - | Jul 14, 14:25 UTC | Jul 14, 16:40 UTC | 2h 15m |
| 2026-07-14 | ORY → CMN | Jul 14, 09:55 UTC | Jul 14, 12:50 UTC | 2h 55m |
| 2026-07-14 | - | Jul 14, 05:35 UTC | Jul 14, 07:55 UTC | 2h 20m |
| 2026-07-13 | - | Jul 13, 17:55 UTC | Jul 13, 21:10 UTC | 3h 15m |
| 2026-07-13 | - | Jul 13, 14:00 UTC | Jul 13, 16:35 UTC | 2h 35m |
| 2026-07-13 | - | Jul 13, 09:15 UTC | Jul 13, 12:05 UTC | 2h 50m |
| 2026-07-13 | - | Jul 13, 05:31 UTC | Jul 13, 07:45 UTC | 2h 15m |
| 2026-07-12 | - | Jul 12, 18:05 UTC | Jul 12, 20:40 UTC | 2h 35m |
| 2026-07-12 | - | Jul 12, 13:55 UTC | Jul 12, 16:05 UTC | 2h 10m |
Specifications
| Registration | LZ-FBK |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4520CE · 21220316 (octal) |
Looking for transponder-level data? View the Mode-S 4520CE page for country allocation, callsign history, and ADS-B signal details.
LZ-FBK frequently asked
What type of aircraft is LZ-FBK?
LZ-FBK is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for LZ-FBK?
LZ-FBK broadcasts on Mode-S (ICAO 24-bit) address 4520CE (octal 21220316). View the transponder page.
What route does LZ-FBK typically fly?
LZ-FBK most frequently flies between ORY and CMN based on observed flights.
Where is LZ-FBK right now?
LZ-FBK is not currently being tracked; last seen Jul 25, 20:10 UTC.