Not currently tracked · last seen 1d ago
- Flights observed
- 37
- Avg flight time
- 59m
- Typical route
- -
- Last seen
- 1d ago
Last known area
Recent flights last 37
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-14 | - | Jun 14, 14:50 UTC | Jun 14, 15:00 UTC | 10m |
| 2026-06-12 | - | Jun 12, 17:55 UTC | Jun 12, 18:25 UTC | 30m |
| 2026-06-07 | - | Jun 7, 22:15 UTC | Jun 7, 22:55 UTC | 40m |
| 2026-06-07 | - | Jun 7, 14:35 UTC | Jun 7, 16:05 UTC | 1h 30m |
| 2026-06-06 | - | Jun 6, 14:59 UTC | Jun 6, 16:50 UTC | 1h 50m |
| 2026-06-06 | - | Jun 6, 13:09 UTC | Jun 6, 14:00 UTC | 50m |
| 2026-06-04 | - | Jun 4, 19:55 UTC | Jun 4, 22:05 UTC | 2h 10m |
| 2026-06-04 | - | Jun 4, 18:40 UTC | Jun 4, 19:00 UTC | 20m |
| 2026-06-04 | - | Jun 4, 15:40 UTC | Jun 4, 18:00 UTC | 2h 20m |
| 2026-05-31 | - | May 31, 17:25 UTC | May 31, 17:55 UTC | 30m |
| 2026-05-31 | - | May 31, 12:55 UTC | May 31, 14:25 UTC | 1h 30m |
| 2026-05-30 | - | May 30, 11:05 UTC | May 30, 12:15 UTC | 1h 10m |
| 2026-05-25 | - | May 25, 18:55 UTC | May 25, 19:44 UTC | 50m |
| 2026-05-25 | - | May 25, 12:40 UTC | May 25, 13:30 UTC | 50m |
| 2026-05-24 | TMB → TPF | May 24, 13:10 UTC | May 24, 14:35 UTC | 1h 25m |
| 2026-05-22 | - | May 22, 16:55 UTC | May 22, 18:10 UTC | 1h 15m |
| 2026-05-17 | - | May 17, 15:20 UTC | May 17, 15:40 UTC | 20m |
| 2026-05-17 | - | May 17, 12:25 UTC | May 17, 12:50 UTC | 25m |
| 2026-05-14 | - | May 14, 23:05 UTC | May 14, 23:55 UTC | 50m |
| 2026-05-14 | - | May 14, 13:15 UTC | May 14, 14:05 UTC | 50m |
| 2026-05-13 | - | May 13, 15:45 UTC | May 13, 18:40 UTC | 2h 55m |
| 2026-05-12 | - | May 12, 20:40 UTC | May 12, 20:50 UTC | 10m |
| 2026-05-12 | - | May 12, 19:40 UTC | May 12, 19:55 UTC | 15m |
| 2026-05-11 | - | May 11, 14:45 UTC | May 11, 17:30 UTC | 2h 46m |
| 2026-05-09 | - | May 9, 19:49 UTC | May 9, 20:30 UTC | 40m |
| 2026-05-09 | - | May 9, 13:15 UTC | May 9, 14:05 UTC | 50m |
| 2026-05-06 | - | May 6, 20:05 UTC | May 6, 22:05 UTC | 2h 0m |
| 2026-05-06 | TPF → TPA | May 6, 19:20 UTC | May 6, 19:35 UTC | 15m |
| 2026-05-02 | - | May 2, 12:55 UTC | May 2, 14:00 UTC | 1h 5m |
| 2026-04-30 | - | Apr 30, 18:45 UTC | Apr 30, 19:50 UTC | 1h 5m |
| 2026-04-26 | - | Apr 26, 18:50 UTC | Apr 26, 20:00 UTC | 1h 10m |
| 2026-04-25 | - | Apr 25, 13:30 UTC | Apr 25, 14:35 UTC | 1h 5m |
| 2026-04-23 | - | Apr 23, 18:20 UTC | Apr 23, 18:45 UTC | 25m |
| 2026-04-19 | - | Apr 19, 18:50 UTC | Apr 19, 19:10 UTC | 20m |
| 2026-04-19 | - | Apr 19, 12:45 UTC | Apr 19, 13:10 UTC | 25m |
| 2026-04-16 | - | Apr 16, 20:05 UTC | Apr 16, 20:20 UTC | 15m |
| 2026-04-16 | - | Apr 16, 19:20 UTC | Apr 16, 19:30 UTC | 10m |
Specifications
| Registration | N321ET |
| Operator | CIRRUS DESIGN CORP |
| Mode-S code | A3727D · 50671175 (octal) |
Looking for transponder-level data? View the Mode-S A3727D page for country allocation, callsign history, and ADS-B signal details.
N321ET frequently asked
Who operates N321ET?
N321ET is operated by CIRRUS DESIGN CORP.
What is the Mode-S transponder code for N321ET?
N321ET broadcasts on Mode-S (ICAO 24-bit) address A3727D (octal 50671175). View the transponder page.
Where is N321ET right now?
N321ET is not currently being tracked; last seen 1d ago.