Not currently tracked · last seen 1d ago
- Flights observed
- 146 showing last 50
- Avg flight time
- 1h 5m
- Typical route
- MTN → MTN
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-16 | - | Jul 16, 18:29 UTC | Jul 16, 19:45 UTC | 1h 15m |
| 2026-07-16 | - | Jul 16, 02:10 UTC | Jul 16, 04:00 UTC | 1h 50m |
| 2026-07-15 | - | Jul 15, 23:30 UTC | Jul 16, 01:05 UTC | 1h 35m |
| 2026-07-15 | - | Jul 15, 02:10 UTC | Jul 15, 04:10 UTC | 2h 0m |
| 2026-07-14 | - | Jul 14, 23:10 UTC | Jul 15, 01:00 UTC | 1h 50m |
| 2026-07-13 | MNZ → MNZ | Jul 13, 21:55 UTC | Jul 13, 23:25 UTC | 1h 30m |
| 2026-07-13 | - | Jul 13, 20:15 UTC | Jul 13, 21:00 UTC | 45m |
| 2026-07-13 | - | Jul 13, 19:15 UTC | Jul 13, 19:40 UTC | 25m |
| 2026-07-13 | - | Jul 13, 16:20 UTC | Jul 13, 17:25 UTC | 1h 5m |
| 2026-07-11 | MTN → MNZ | Jul 11, 20:35 UTC | Jul 11, 21:40 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 16:10 UTC | Jul 11, 16:45 UTC | 35m |
| 2026-07-11 | - | Jul 11, 12:40 UTC | Jul 11, 14:00 UTC | 1h 20m |
| 2026-07-11 | MTN → RDG | Jul 11, 11:45 UTC | Jul 11, 12:35 UTC | 50m |
| 2026-07-11 | MTN → MTN | Jul 11, 10:55 UTC | Jul 11, 11:10 UTC | 15m |
| 2026-07-10 | MTN → MTN | Jul 10, 20:40 UTC | Jul 10, 20:50 UTC | 10m |
| 2026-07-10 | MTN → MTN | Jul 10, 18:00 UTC | Jul 10, 19:05 UTC | 1h 5m |
| 2026-07-03 | - | Jul 3, 18:45 UTC | Jul 3, 20:00 UTC | 1h 15m |
| 2026-07-03 | - | Jul 3, 16:55 UTC | Jul 3, 17:30 UTC | 35m |
| 2026-07-03 | MTN → MTN | Jul 3, 11:35 UTC | Jul 3, 13:10 UTC | 1h 35m |
| 2026-07-02 | - | Jul 2, 18:25 UTC | Jul 2, 19:05 UTC | 40m |
| 2026-07-02 | - | Jul 2, 16:50 UTC | Jul 2, 17:10 UTC | 20m |
| 2026-07-02 | - | Jul 2, 16:20 UTC | Jul 2, 16:45 UTC | 25m |
| 2026-07-02 | - | Jul 2, 12:30 UTC | Jul 2, 13:45 UTC | 1h 15m |
| 2026-07-02 | MTN → RDG | Jul 2, 11:00 UTC | Jul 2, 12:25 UTC | 1h 25m |
| 2026-07-01 | - | Jul 1, 12:20 UTC | Jul 1, 13:40 UTC | 1h 20m |
| 2026-07-01 | - | Jul 1, 11:35 UTC | Jul 1, 12:15 UTC | 40m |
| 2026-07-01 | MTN → MTN | Jul 1, 10:40 UTC | Jul 1, 11:00 UTC | 20m |
| 2026-06-30 | MTN → MTN | Jun 30, 17:45 UTC | Jun 30, 18:30 UTC | 45m |
| 2026-06-30 | MTN → MTN | Jun 30, 15:25 UTC | Jun 30, 16:15 UTC | 50m |
| 2026-06-29 | - | Jun 29, 20:54 UTC | Jun 29, 22:55 UTC | 2h 0m |
| 2026-06-29 | MTN → RDG | Jun 29, 19:49 UTC | Jun 29, 20:49 UTC | 1h 0m |
| 2026-06-29 | - | Jun 29, 17:49 UTC | Jun 29, 18:19 UTC | 30m |
| 2026-06-28 | MTN → MTN | Jun 28, 22:24 UTC | Jun 28, 23:04 UTC | 40m |
| 2026-06-27 | - | Jun 27, 13:09 UTC | Jun 27, 14:35 UTC | 1h 25m |
| 2026-06-26 | MTN → MTN | Jun 26, 01:29 UTC | Jun 26, 04:04 UTC | 2h 35m |
| 2026-06-25 | MTN → MTN | Jun 25, 21:55 UTC | Jun 25, 22:59 UTC | 1h 5m |
| 2026-06-24 | - | Jun 24, 17:05 UTC | Jun 24, 18:50 UTC | 1h 45m |
| 2026-06-24 | MTN → MTN | Jun 24, 13:24 UTC | Jun 24, 14:50 UTC | 1h 25m |
| 2026-06-23 | - | Jun 23, 20:44 UTC | Jun 23, 22:05 UTC | 1h 20m |
| 2026-06-22 | - | Jun 22, 14:05 UTC | Jun 22, 15:24 UTC | 1h 20m |
| 2026-06-22 | - | Jun 22, 13:19 UTC | Jun 22, 13:59 UTC | 40m |
| 2026-06-21 | - | Jun 21, 20:14 UTC | Jun 21, 21:19 UTC | 1h 5m |
| 2026-06-21 | - | Jun 21, 16:10 UTC | Jun 21, 16:49 UTC | 40m |
| 2026-06-21 | - | Jun 21, 11:30 UTC | Jun 21, 12:19 UTC | 50m |
| 2026-06-21 | MTN → MTN | Jun 21, 10:40 UTC | Jun 21, 11:00 UTC | 20m |
| 2026-06-20 | - | Jun 20, 18:04 UTC | Jun 20, 18:45 UTC | 40m |
| 2026-06-20 | MTN → MTN | Jun 20, 16:00 UTC | Jun 20, 16:39 UTC | 40m |
| 2026-06-19 | MTN → MTN | Jun 19, 19:59 UTC | Jun 19, 21:14 UTC | 1h 15m |
| 2026-06-18 | MTN → MTN | Jun 18, 23:10 UTC | Jun 19, 01:29 UTC | 2h 19m |
| 2026-06-17 | - | Jun 17, 18:45 UTC | Jun 17, 20:10 UTC | 1h 25m |
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 MTN and MTN based on observed flights.
Where is N226DF right now?
N226DF is not currently being tracked; last seen 1d ago.