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