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