Not currently tracked · last seen 7h ago
- Flights observed
- 71 showing last 50
- Avg flight time
- 1h 24m
- Typical route
- CMH → SDF
- Last seen
- 7h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-16 | CMH → SDF | Jun 16, 20:05 UTC | Jun 16, 20:15 UTC | 10m |
| 2026-06-10 | - | Jun 10, 20:35 UTC | Jun 10, 21:15 UTC | 40m |
| 2026-06-01 | - | Jun 1, 17:25 UTC | Jun 1, 17:45 UTC | 20m |
| 2026-06-01 | CMH → SDF | Jun 1, 02:10 UTC | Jun 1, 04:10 UTC | 2h 0m |
| 2026-05-31 | - | May 31, 14:05 UTC | May 31, 16:35 UTC | 2h 30m |
| 2026-05-31 | - | May 31, 11:20 UTC | May 31, 12:05 UTC | 45m |
| 2026-05-30 | CMH → SDF | May 30, 15:25 UTC | May 30, 17:40 UTC | 2h 15m |
| 2026-05-29 | CMH → SDF | May 29, 20:05 UTC | May 29, 21:40 UTC | 1h 35m |
| 2026-05-29 | CMH → SDF | May 29, 18:10 UTC | May 29, 19:20 UTC | 1h 10m |
| 2026-05-29 | CMH → SDF | May 29, 12:40 UTC | May 29, 14:05 UTC | 1h 25m |
| 2026-05-28 | CMH → SDF | May 28, 20:20 UTC | May 28, 21:50 UTC | 1h 30m |
| 2026-05-28 | CMH → SDF | May 28, 18:20 UTC | May 28, 19:30 UTC | 1h 10m |
| 2026-05-28 | CMH → SDF | May 28, 15:40 UTC | May 28, 16:50 UTC | 1h 10m |
| 2026-05-28 | CMH → SDF | May 28, 12:05 UTC | May 28, 14:35 UTC | 2h 30m |
| 2026-05-27 | - | May 27, 19:50 UTC | May 27, 20:45 UTC | 55m |
| 2026-05-27 | - | May 27, 16:15 UTC | May 27, 18:00 UTC | 1h 45m |
| 2026-05-27 | CMH → SDF | May 27, 14:10 UTC | May 27, 15:15 UTC | 1h 5m |
| 2026-05-26 | CMH → SDF | May 26, 21:09 UTC | May 26, 22:15 UTC | 1h 5m |
| 2026-05-26 | CMH → SDF | May 26, 18:19 UTC | May 26, 18:59 UTC | 40m |
| 2026-05-26 | CMH → SDF | May 26, 15:00 UTC | May 26, 15:39 UTC | 40m |
| 2026-05-25 | CMH → SDF | May 25, 21:15 UTC | May 25, 22:44 UTC | 1h 30m |
| 2026-05-25 | CMH → SDF | May 25, 17:00 UTC | May 25, 18:35 UTC | 1h 35m |
| 2026-05-25 | CMH → SDF | May 25, 13:45 UTC | May 25, 15:45 UTC | 2h 0m |
| 2026-05-24 | CMH → SDF | May 24, 18:40 UTC | May 24, 19:55 UTC | 1h 15m |
| 2026-05-24 | CMH → SDF | May 24, 16:55 UTC | May 24, 17:25 UTC | 30m |
| 2026-05-23 | CMH → SDF | May 23, 20:05 UTC | May 24, 00:35 UTC | 4h 30m |
| 2026-05-23 | CMH → SDF | May 23, 17:40 UTC | May 23, 18:30 UTC | 51m |
| 2026-05-22 | CMH → SDF | May 22, 22:10 UTC | May 23, 00:25 UTC | 2h 15m |
| 2026-05-22 | CMH → SDF | May 22, 20:15 UTC | May 22, 21:00 UTC | 45m |
| 2026-05-22 | CMH → SDF | May 22, 17:15 UTC | May 22, 18:55 UTC | 1h 40m |
| 2026-05-22 | CMH → SDF | May 22, 15:10 UTC | May 22, 16:00 UTC | 50m |
| 2026-05-21 | CMH → SDF | May 21, 19:45 UTC | May 21, 22:05 UTC | 2h 20m |
| 2026-05-21 | CMH → SDF | May 21, 18:00 UTC | May 21, 18:35 UTC | 35m |
| 2026-05-20 | CMH → SDF | May 20, 02:45 UTC | May 20, 03:30 UTC | 45m |
| 2026-05-19 | CMH → SDF | May 19, 21:35 UTC | May 19, 22:45 UTC | 1h 10m |
| 2026-05-18 | CMH → SDF | May 18, 13:10 UTC | May 18, 17:30 UTC | 4h 20m |
| 2026-05-17 | CMH → SDF | May 17, 20:55 UTC | May 17, 21:55 UTC | 1h 0m |
| 2026-05-17 | CMH → SDF | May 17, 16:55 UTC | May 17, 19:50 UTC | 2h 55m |
| 2026-05-16 | CMH → SDF | May 16, 21:55 UTC | May 16, 22:15 UTC | 20m |
| 2026-05-16 | CMH → SDF | May 16, 19:00 UTC | May 16, 19:35 UTC | 35m |
| 2026-05-16 | CMH → SDF | May 16, 16:35 UTC | May 16, 17:20 UTC | 45m |
| 2026-05-15 | CMH → SDF | May 15, 23:35 UTC | May 16, 00:50 UTC | 1h 15m |
| 2026-05-15 | CMH → SDF | May 15, 21:10 UTC | May 15, 21:50 UTC | 40m |
| 2026-05-15 | CMH → SDF | May 15, 16:35 UTC | May 15, 19:30 UTC | 2h 55m |
| 2026-05-15 | CMH → SDF | May 15, 00:35 UTC | May 15, 01:25 UTC | 50m |
| 2026-05-14 | CMH → SDF | May 14, 21:40 UTC | May 14, 23:40 UTC | 2h 0m |
| 2026-05-14 | CMH → SDF | May 14, 18:45 UTC | May 14, 19:45 UTC | 1h 0m |
| 2026-05-14 | CMH → SDF | May 14, 16:20 UTC | May 14, 17:30 UTC | 1h 10m |
| 2026-05-13 | CMH → SDF | May 13, 23:25 UTC | May 14, 01:50 UTC | 2h 25m |
| 2026-05-13 | CMH → SDF | May 13, 21:10 UTC | May 13, 21:25 UTC | 15m |
Specifications
| Registration | N213QS |
| Operator | NETJETS SALES INC |
| Mode-S code | A1C616 · 50343026 (octal) |
Looking for transponder-level data? View the Mode-S A1C616 page for country allocation, callsign history, and ADS-B signal details.
N213QS frequently asked
Who operates N213QS?
N213QS is operated by NETJETS SALES INC.
What is the Mode-S transponder code for N213QS?
N213QS broadcasts on Mode-S (ICAO 24-bit) address A1C616 (octal 50343026). View the transponder page.
What route does N213QS typically fly?
N213QS most frequently flies between CMH and SDF based on observed flights.
Where is N213QS right now?
N213QS is not currently being tracked; last seen 7h ago.