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