Not currently tracked · last seen 1d ago
- Flights observed
- 38
- Avg flight time
- 1h 24m
- Typical route
- -
- Last seen
- 1d ago
Last known area
Recent flights last 38
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-20 | - | Jul 20, 13:25 UTC | Jul 20, 13:55 UTC | 30m |
| 2026-07-20 | - | Jul 20, 12:00 UTC | Jul 20, 12:25 UTC | 25m |
| 2026-07-16 | - | Jul 16, 15:05 UTC | Jul 16, 15:35 UTC | 30m |
| 2026-07-16 | - | Jul 16, 12:30 UTC | Jul 16, 13:00 UTC | 30m |
| 2026-07-06 | - | Jul 6, 13:40 UTC | Jul 6, 16:00 UTC | 2h 20m |
| 2026-07-02 | - | Jul 2, 12:40 UTC | Jul 2, 14:30 UTC | 1h 50m |
| 2026-07-01 | - | Jul 1, 01:30 UTC | Jul 1, 02:45 UTC | 1h 15m |
| 2026-06-28 | - | Jun 28, 13:25 UTC | Jun 28, 15:24 UTC | 2h 0m |
| 2026-06-26 | - | Jun 26, 13:15 UTC | Jun 26, 14:59 UTC | 1h 45m |
| 2026-06-24 | - | Jun 24, 19:39 UTC | Jun 24, 20:09 UTC | 30m |
| 2026-06-24 | - | Jun 24, 16:29 UTC | Jun 24, 16:54 UTC | 25m |
| 2026-06-14 | - | Jun 14, 13:40 UTC | Jun 14, 15:35 UTC | 1h 55m |
| 2026-06-12 | - | Jun 12, 12:40 UTC | Jun 12, 14:35 UTC | 1h 55m |
| 2026-06-04 | - | Jun 4, 13:55 UTC | Jun 4, 14:20 UTC | 25m |
| 2026-06-04 | - | Jun 4, 12:05 UTC | Jun 4, 12:30 UTC | 25m |
| 2026-05-29 | - | May 29, 21:00 UTC | May 29, 21:30 UTC | 30m |
| 2026-05-29 | - | May 29, 18:55 UTC | May 29, 19:30 UTC | 35m |
| 2026-05-25 | - | May 25, 14:05 UTC | May 25, 16:05 UTC | 2h 0m |
| 2026-05-22 | - | May 22, 12:40 UTC | May 22, 14:35 UTC | 1h 55m |
| 2026-05-14 | - | May 14, 17:10 UTC | May 14, 19:05 UTC | 1h 55m |
| 2026-05-13 | - | May 13, 13:20 UTC | May 13, 15:25 UTC | 2h 5m |
| 2026-05-05 | - | May 5, 16:10 UTC | May 5, 18:05 UTC | 1h 55m |
| 2026-05-04 | - | May 4, 17:40 UTC | May 4, 19:35 UTC | 1h 56m |
| 2026-05-04 | - | May 4, 13:25 UTC | May 4, 16:15 UTC | 2h 50m |
| 2026-05-01 | - | May 1, 16:05 UTC | May 1, 17:40 UTC | 1h 35m |
| 2026-04-30 | - | Apr 30, 17:15 UTC | Apr 30, 18:55 UTC | 1h 40m |
| 2026-04-30 | - | Apr 30, 12:55 UTC | Apr 30, 15:50 UTC | 2h 55m |
| 2026-04-29 | - | Apr 29, 13:30 UTC | Apr 29, 15:25 UTC | 1h 55m |
| 2026-04-26 | - | Apr 26, 13:05 UTC | Apr 26, 15:00 UTC | 1h 55m |
| 2026-04-23 | - | Apr 23, 19:50 UTC | Apr 23, 20:35 UTC | 45m |
| 2026-04-21 | - | Apr 21, 17:40 UTC | Apr 21, 17:55 UTC | 15m |
| 2026-04-20 | - | Apr 20, 12:15 UTC | Apr 20, 12:45 UTC | 30m |
| 2026-04-19 | - | Apr 19, 11:55 UTC | Apr 19, 15:05 UTC | 3h 10m |
| 2026-04-17 | - | Apr 17, 15:20 UTC | Apr 17, 16:10 UTC | 50m |
| 2026-04-17 | - | Apr 17, 13:20 UTC | Apr 17, 15:15 UTC | 1h 54m |
| 2026-04-16 | - | Apr 16, 13:15 UTC | Apr 16, 14:45 UTC | 1h 30m |
| 2026-04-16 | - | Apr 16, 12:55 UTC | Apr 16, 13:05 UTC | 10m |
| 2026-04-13 | FLL → HWO | Apr 13, 12:40 UTC | Apr 13, 14:10 UTC | 1h 30m |
Specifications
| Registration | N26MZ |
| Operator | HVA N26MZ LLC |
| Mode-S code | A27DCF · 50476717 (octal) |
Looking for transponder-level data? View the Mode-S A27DCF page for country allocation, callsign history, and ADS-B signal details.
N26MZ frequently asked
Who operates N26MZ?
N26MZ is operated by HVA N26MZ LLC.
What is the Mode-S transponder code for N26MZ?
N26MZ broadcasts on Mode-S (ICAO 24-bit) address A27DCF (octal 50476717). View the transponder page.
Where is N26MZ right now?
N26MZ is not currently being tracked; last seen 1d ago.