Not currently tracked · last seen 12h ago
- Flights observed
- 58 showing last 50
- Avg flight time
- 1h 9m
- Typical route
- MNZ → MNZ
- Last seen
- 12h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | - | Jun 2, 20:45 UTC | Jun 2, 21:45 UTC | 1h 0m |
| 2026-06-01 | - | Jun 1, 17:45 UTC | Jun 1, 18:45 UTC | 1h 0m |
| 2026-05-19 | HAR → MNZ | May 19, 20:45 UTC | May 19, 22:00 UTC | 1h 15m |
| 2026-05-19 | - | May 19, 17:55 UTC | May 19, 18:55 UTC | 1h 0m |
| 2026-05-19 | MNZ → MNZ | May 19, 15:35 UTC | May 19, 16:35 UTC | 1h 0m |
| 2026-05-18 | - | May 18, 19:30 UTC | May 18, 21:25 UTC | 1h 55m |
| 2026-05-17 | MNZ → MNZ | May 17, 18:10 UTC | May 17, 19:45 UTC | 1h 35m |
| 2026-05-16 | - | May 16, 17:55 UTC | May 16, 19:25 UTC | 1h 30m |
| 2026-05-16 | MNZ → MNZ | May 16, 15:40 UTC | May 16, 16:15 UTC | 35m |
| 2026-05-14 | - | May 14, 17:20 UTC | May 14, 18:00 UTC | 40m |
| 2026-05-14 | - | May 14, 16:15 UTC | May 14, 16:45 UTC | 30m |
| 2026-05-14 | - | May 14, 13:01 UTC | May 14, 14:40 UTC | 1h 40m |
| 2026-05-13 | - | May 13, 21:00 UTC | May 13, 22:00 UTC | 1h 0m |
| 2026-05-13 | - | May 13, 18:00 UTC | May 13, 19:25 UTC | 1h 25m |
| 2026-05-13 | - | May 13, 11:10 UTC | May 13, 11:45 UTC | 35m |
| 2026-05-12 | MNZ → MNZ | May 12, 21:10 UTC | May 12, 23:45 UTC | 2h 35m |
| 2026-05-12 | - | May 12, 15:50 UTC | May 12, 18:50 UTC | 3h 0m |
| 2026-05-08 | - | May 8, 23:20 UTC | May 9, 00:40 UTC | 1h 20m |
| 2026-05-08 | - | May 8, 21:00 UTC | May 8, 22:40 UTC | 1h 40m |
| 2026-05-08 | - | May 8, 15:10 UTC | May 8, 17:05 UTC | 1h 55m |
| 2026-05-07 | MNZ → MNZ | May 7, 21:40 UTC | May 7, 22:59 UTC | 1h 19m |
| 2026-05-07 | MNZ → MNZ | May 7, 18:05 UTC | May 7, 19:40 UTC | 1h 35m |
| 2026-05-07 | - | May 7, 15:05 UTC | May 7, 16:50 UTC | 1h 45m |
| 2026-05-04 | MNZ → MNZ | May 4, 19:25 UTC | May 4, 20:05 UTC | 40m |
| 2026-05-04 | - | May 4, 16:20 UTC | May 4, 18:00 UTC | 1h 40m |
| 2026-04-30 | - | Apr 30, 10:10 UTC | Apr 30, 11:45 UTC | 1h 35m |
| 2026-04-29 | - | Apr 29, 18:00 UTC | Apr 29, 19:45 UTC | 1h 45m |
| 2026-04-21 | - | Apr 21, 22:30 UTC | Apr 21, 22:45 UTC | 15m |
| 2026-04-21 | - | Apr 21, 21:00 UTC | Apr 21, 21:40 UTC | 40m |
| 2026-04-21 | - | Apr 21, 17:20 UTC | Apr 21, 19:45 UTC | 2h 25m |
| 2026-04-21 | - | Apr 21, 15:20 UTC | Apr 21, 16:05 UTC | 45m |
| 2026-04-21 | - | Apr 21, 12:20 UTC | Apr 21, 14:05 UTC | 1h 45m |
| 2026-04-20 | - | Apr 20, 17:45 UTC | Apr 20, 19:00 UTC | 1h 15m |
| 2026-04-20 | LNS → LNS | Apr 20, 17:35 UTC | Apr 20, 17:40 UTC | 5m |
| 2026-04-20 | - | Apr 20, 15:05 UTC | Apr 20, 16:05 UTC | 1h 0m |
| 2026-04-17 | - | Apr 17, 21:55 UTC | Apr 17, 23:05 UTC | 1h 10m |
| 2026-04-17 | - | Apr 17, 15:20 UTC | Apr 17, 16:50 UTC | 1h 30m |
| 2026-04-17 | - | Apr 17, 14:55 UTC | Apr 17, 15:15 UTC | 20m |
| 2026-04-17 | - | Apr 17, 13:20 UTC | Apr 17, 13:35 UTC | 15m |
| 2026-04-17 | MMU → MMU | Apr 17, 12:30 UTC | Apr 17, 13:15 UTC | 45m |
| 2026-04-16 | - | Apr 16, 21:14 UTC | Apr 16, 21:34 UTC | 20m |
| 2026-04-16 | - | Apr 16, 19:50 UTC | Apr 16, 21:10 UTC | 1h 20m |
| 2026-04-16 | MMU → MMU | Apr 16, 15:35 UTC | Apr 16, 16:10 UTC | 35m |
| 2026-04-16 | - | Apr 16, 13:15 UTC | Apr 16, 14:05 UTC | 50m |
| 2026-04-16 | - | Apr 16, 12:14 UTC | Apr 16, 13:05 UTC | 50m |
| 2026-04-15 | - | Apr 15, 21:15 UTC | Apr 15, 22:10 UTC | 55m |
| 2026-04-15 | - | Apr 15, 20:50 UTC | Apr 15, 21:00 UTC | 10m |
| 2026-04-15 | - | Apr 15, 19:30 UTC | Apr 15, 20:40 UTC | 1h 10m |
| 2026-04-15 | - | Apr 15, 17:40 UTC | Apr 15, 18:05 UTC | 25m |
| 2026-04-15 | - | Apr 15, 13:20 UTC | Apr 15, 14:25 UTC | 1h 5m |
Specifications
| Registration | N226DF |
| Operator | MERIDIAN AIRCRAFT LLC |
| Mode-S code | A1F79C · 50373634 (octal) |
Looking for transponder-level data? View the Mode-S A1F79C page for country allocation, callsign history, and ADS-B signal details.
N226DF frequently asked
Who operates N226DF?
N226DF is operated by MERIDIAN AIRCRAFT LLC.
What is the Mode-S transponder code for N226DF?
N226DF broadcasts on Mode-S (ICAO 24-bit) address A1F79C (octal 50373634). View the transponder page.
What route does N226DF typically fly?
N226DF most frequently flies between MNZ and MNZ based on observed flights.
Where is N226DF right now?
N226DF is not currently being tracked; last seen 12h ago.