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