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