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