Not currently tracked · last seen 6h ago
- Flights observed
- 99 showing last 50
- Avg flight time
- 1h 50m
- Typical route
- MAD → LHR
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-09 | MAD → FRA | Jun 9, 18:55 UTC | Jun 9, 20:55 UTC | 2h 0m |
| 2026-06-09 | VIE → MAD | Jun 9, 14:25 UTC | Jun 9, 17:15 UTC | 2h 50m |
| 2026-06-09 | CTA → MAD | Jun 9, 10:20 UTC | Jun 9, 12:45 UTC | 2h 25m |
| 2026-06-09 | MAD → CTA | Jun 9, 06:50 UTC | Jun 9, 08:55 UTC | 2h 5m |
| 2026-06-08 | MAD → FRA | Jun 8, 18:05 UTC | Jun 8, 20:50 UTC | 2h 45m |
| 2026-06-08 | VIE → MAD | Jun 8, 14:35 UTC | Jun 8, 16:55 UTC | 2h 20m |
| 2026-06-08 | BER → MAD | Jun 8, 07:20 UTC | Jun 8, 10:10 UTC | 2h 50m |
| 2026-06-07 | MAD → BER | Jun 7, 18:35 UTC | Jun 7, 21:05 UTC | 2h 30m |
| 2026-06-07 | MAD → VGO | Jun 7, 16:30 UTC | Jun 7, 17:20 UTC | 50m |
| 2026-06-07 | VGO → MAD | Jun 7, 14:10 UTC | Jun 7, 15:15 UTC | 1h 5m |
| 2026-06-07 | VCE → MAD | Jun 7, 10:15 UTC | Jun 7, 12:30 UTC | 2h 15m |
| 2026-06-07 | MAD → VCE | Jun 7, 07:10 UTC | Jun 7, 09:05 UTC | 1h 55m |
| 2026-06-07 | MAD → LCG | Jun 7, 04:45 UTC | Jun 7, 05:40 UTC | 55m |
| 2026-06-06 | LCG → MAD | Jun 6, 20:35 UTC | Jun 6, 21:20 UTC | 45m |
| 2026-06-06 | MXP → MAD | Jun 6, 17:24 UTC | Jun 6, 19:19 UTC | 1h 55m |
| 2026-06-06 | MAD → MXP | Jun 6, 14:30 UTC | Jun 6, 15:59 UTC | 1h 30m |
| 2026-06-06 | - | Jun 6, 09:39 UTC | Jun 6, 12:10 UTC | 2h 30m |
| 2026-06-06 | MAD → BRI | Jun 6, 06:10 UTC | Jun 6, 08:25 UTC | 2h 15m |
| 2026-06-05 | JTR → MAD | Jun 5, 18:35 UTC | Jun 5, 22:05 UTC | 3h 30m |
| 2026-06-05 | MAD → JTR | Jun 5, 14:25 UTC | Jun 5, 17:25 UTC | 3h 0m |
| 2026-06-05 | CDG → MAD | Jun 5, 11:10 UTC | Jun 5, 12:50 UTC | 1h 40m |
| 2026-06-05 | CDG → MAD | Jun 5, 08:05 UTC | Jun 5, 09:40 UTC | 1h 35m |
| 2026-06-05 | VCE → MAD | Jun 5, 04:45 UTC | Jun 5, 06:55 UTC | 2h 10m |
| 2026-06-04 | MAD → VCE | Jun 4, 19:55 UTC | Jun 4, 21:45 UTC | 1h 50m |
| 2026-06-04 | MAD → LHR | Jun 4, 17:05 UTC | Jun 4, 18:55 UTC | 1h 50m |
| 2026-06-04 | MAD → LHR | Jun 4, 13:30 UTC | Jun 4, 15:15 UTC | 1h 45m |
| 2026-06-04 | ZAG → MAD | Jun 4, 09:25 UTC | Jun 4, 12:00 UTC | 2h 35m |
| 2026-06-04 | MAD → ZAG | Jun 4, 06:05 UTC | Jun 4, 08:20 UTC | 2h 15m |
| 2026-06-03 | OLB → MAD | Jun 3, 18:10 UTC | Jun 3, 19:50 UTC | 1h 40m |
| 2026-06-03 | MAD → OLB | Jun 3, 15:40 UTC | Jun 3, 17:05 UTC | 1h 25m |
| 2026-06-03 | GVA → MAD | Jun 3, 12:55 UTC | Jun 3, 14:25 UTC | 1h 30m |
| 2026-06-03 | MAD → GVA | Jun 3, 10:05 UTC | Jun 3, 11:40 UTC | 1h 35m |
| 2026-06-03 | MAD → BCN | Jun 3, 07:50 UTC | Jun 3, 08:40 UTC | 50m |
| 2026-06-03 | MAD → VGO | Jun 3, 05:45 UTC | Jun 3, 06:30 UTC | 45m |
| 2026-06-02 | BCN → MAD | Jun 2, 19:40 UTC | Jun 2, 20:25 UTC | 45m |
| 2026-06-02 | MAD → BCN | Jun 2, 17:25 UTC | Jun 2, 18:15 UTC | 50m |
| 2026-06-02 | VGO → MAD | Jun 2, 15:20 UTC | Jun 2, 16:15 UTC | 55m |
| 2026-06-02 | MAD → BCN | Jun 2, 13:15 UTC | Jun 2, 14:05 UTC | 50m |
| 2026-06-02 | MAD → BCN | Jun 2, 11:00 UTC | Jun 2, 11:50 UTC | 50m |
| 2026-06-02 | MAD → EAS | Jun 2, 08:50 UTC | Jun 2, 09:40 UTC | 50m |
| 2026-06-02 | BER → MAD | Jun 2, 04:45 UTC | Jun 2, 07:35 UTC | 2h 50m |
| 2026-06-01 | MAD → BER | Jun 1, 18:55 UTC | Jun 1, 21:15 UTC | 2h 20m |
| 2026-06-01 | ZAG → MAD | Jun 1, 09:35 UTC | Jun 1, 11:55 UTC | 2h 20m |
| 2026-06-01 | MAD → ZAG | Jun 1, 06:00 UTC | Jun 1, 08:05 UTC | 2h 5m |
| 2026-05-31 | DBV → MAD | May 31, 18:00 UTC | May 31, 20:25 UTC | 2h 25m |
| 2026-05-31 | MAD → DBV | May 31, 14:35 UTC | May 31, 17:00 UTC | 2h 25m |
| 2026-05-31 | LHR → MAD | May 31, 10:40 UTC | May 31, 12:45 UTC | 2h 5m |
| 2026-05-31 | MAD → LHR | May 31, 08:25 UTC | May 31, 09:15 UTC | 50m |
| 2026-05-30 | MAD → MUC | May 30, 19:25 UTC | May 30, 21:20 UTC | 1h 55m |
| 2026-05-30 | MAD → LHR | May 30, 16:10 UTC | May 30, 18:05 UTC | 1h 55m |
Specifications
| Registration | EC-NFZ |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 346316 · 15061426 (octal) |
Looking for transponder-level data? View the Mode-S 346316 page for country allocation, callsign history, and ADS-B signal details.
EC-NFZ frequently asked
What type of aircraft is EC-NFZ?
EC-NFZ is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for EC-NFZ?
EC-NFZ broadcasts on Mode-S (ICAO 24-bit) address 346316 (octal 15061426). View the transponder page.
What route does EC-NFZ typically fly?
EC-NFZ most frequently flies between MAD and LHR based on observed flights.
Where is EC-NFZ right now?
EC-NFZ is not currently being tracked; last seen 6h ago.