flight Aircraft
N780QS
BOMBARDIER BD-100 Challenger 350
Operated by NETJETS SALES INC, NETJETS AVIATION INC
- Tail number
- N780QS
- Type
- CL35
- Mode-S
- AA91F5
Not currently tracked · last seen 8d ago
- Flights observed
- 69 showing last 50
- Avg flight time
- 2h 17m
- Typical route
- CHO → HPN
- Last seen
- 8d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-22 | CHO → HPN | May 22, 00:25 UTC | May 22, 02:10 UTC | 1h 45m |
| 2026-05-21 | CHO → HPN | May 21, 20:50 UTC | May 21, 23:25 UTC | 2h 35m |
| 2026-05-21 | CHO → HPN | May 21, 17:00 UTC | May 21, 20:05 UTC | 3h 5m |
| 2026-05-21 | CHO → HPN | May 21, 03:30 UTC | May 21, 04:30 UTC | 1h 0m |
| 2026-05-21 | CHO → HPN | May 21, 00:55 UTC | May 21, 01:55 UTC | 1h 0m |
| 2026-05-20 | CHO → HPN | May 20, 22:10 UTC | May 21, 00:00 UTC | 1h 50m |
| 2026-05-20 | CHO → HPN | May 20, 19:00 UTC | May 20, 20:05 UTC | 1h 5m |
| 2026-05-20 | CHO → HPN | May 20, 17:00 UTC | May 20, 18:10 UTC | 1h 10m |
| 2026-05-19 | CHO → HPN | May 19, 21:20 UTC | May 20, 18:10 UTC | 20h 51m |
| 2026-05-19 | CHO → HPN | May 19, 19:20 UTC | May 20, 18:10 UTC | 22h 51m |
| 2026-05-19 | CHO → HPN | May 19, 17:00 UTC | May 19, 17:30 UTC | 30m |
| 2026-05-19 | CHO → HPN | May 19, 13:20 UTC | May 19, 15:30 UTC | 2h 10m |
| 2026-05-18 | CHO → HPN | May 18, 21:45 UTC | May 18, 22:10 UTC | 25m |
| 2026-05-18 | - | May 18, 13:20 UTC | May 18, 20:40 UTC | 7h 19m |
| 2026-05-18 | CHO → HPN | May 18, 00:35 UTC | May 18, 00:55 UTC | 20m |
| 2026-05-17 | CHO → HPN | May 17, 21:05 UTC | May 17, 23:45 UTC | 2h 40m |
| 2026-05-14 | CHO → HPN | May 14, 22:40 UTC | May 14, 23:10 UTC | 30m |
| 2026-05-14 | CHO → HPN | May 14, 18:55 UTC | May 14, 20:55 UTC | 2h 0m |
| 2026-05-14 | CHO → HPN | May 14, 16:20 UTC | May 14, 17:15 UTC | 55m |
| 2026-05-14 | CHO → HPN | May 14, 00:40 UTC | May 14, 01:55 UTC | 1h 15m |
| 2026-05-13 | CHO → HPN | May 13, 18:55 UTC | May 13, 20:55 UTC | 2h 0m |
| 2026-05-13 | CHO → HPN | May 13, 15:25 UTC | May 13, 18:00 UTC | 2h 35m |
| 2026-05-12 | CHO → HPN | May 12, 23:55 UTC | May 13, 00:35 UTC | 40m |
| 2026-05-12 | CHO → HPN | May 12, 21:35 UTC | May 12, 22:15 UTC | 40m |
| 2026-05-12 | CHO → HPN | May 12, 14:30 UTC | May 12, 19:50 UTC | 5h 20m |
| 2026-05-11 | CHO → HPN | May 11, 17:55 UTC | May 11, 21:50 UTC | 3h 55m |
| 2026-05-11 | CHO → HPN | May 11, 13:10 UTC | May 11, 15:00 UTC | 1h 50m |
| 2026-05-11 | CHO → HPN | May 11, 11:15 UTC | May 11, 12:00 UTC | 45m |
| 2026-05-11 | CHO → HPN | May 11, 01:05 UTC | May 11, 01:34 UTC | 30m |
| 2026-05-10 | CHO → HPN | May 10, 22:20 UTC | May 11, 00:34 UTC | 2h 15m |
| 2026-05-10 | CHO → HPN | May 10, 19:30 UTC | May 10, 19:45 UTC | 15m |
| 2026-05-10 | CHO → HPN | May 10, 15:35 UTC | May 10, 17:15 UTC | 1h 40m |
| 2026-05-10 | CHO → HPN | May 10, 13:55 UTC | May 10, 14:34 UTC | 40m |
| 2026-05-09 | CHO → HPN | May 9, 21:45 UTC | May 9, 22:20 UTC | 35m |
| 2026-05-09 | CHO → HPN | May 9, 15:00 UTC | May 9, 15:40 UTC | 40m |
| 2026-05-09 | CHO → HPN | May 9, 12:15 UTC | May 9, 13:20 UTC | 1h 5m |
| 2026-05-08 | CHO → HPN | May 8, 17:40 UTC | May 8, 19:30 UTC | 1h 50m |
| 2026-05-08 | CHO → HPN | May 8, 16:35 UTC | May 8, 16:50 UTC | 15m |
| 2026-05-08 | CHO → HPN | May 8, 15:05 UTC | May 8, 15:50 UTC | 45m |
| 2026-05-03 | CHO → HPN | May 3, 11:50 UTC | May 3, 12:25 UTC | 35m |
| 2026-05-02 | CHO → HPN | May 2, 23:00 UTC | May 2, 23:45 UTC | 45m |
| 2026-04-26 | CHO → HPN | Apr 26, 21:30 UTC | Apr 26, 23:05 UTC | 1h 35m |
| 2026-04-26 | CHO → HPN | Apr 26, 16:15 UTC | Apr 26, 20:00 UTC | 3h 46m |
| 2026-04-25 | CHO → HPN | Apr 25, 22:10 UTC | Apr 25, 22:25 UTC | 15m |
| 2026-04-25 | CHO → HPN | Apr 25, 03:20 UTC | Apr 25, 04:00 UTC | 40m |
| 2026-04-24 | CHO → HPN | Apr 24, 22:05 UTC | Apr 24, 23:00 UTC | 55m |
| 2026-04-24 | CHO → HPN | Apr 24, 20:30 UTC | Apr 24, 21:10 UTC | 40m |
| 2026-04-24 | CHO → HPN | Apr 24, 19:00 UTC | Apr 24, 19:15 UTC | 15m |
| 2026-04-24 | CHO → HPN | Apr 24, 16:40 UTC | Apr 24, 17:25 UTC | 45m |
| 2026-04-24 | CHO → HPN | Apr 24, 01:15 UTC | Apr 24, 02:05 UTC | 50m |
Specifications
| Registration | N780QS |
| Aircraft type | BOMBARDIER BD-100 Challenger 350 (CL35) |
| Operator | NETJETS SALES INC, NETJETS AVIATION INC |
| Mode-S code | AA91F5 · 52510765 (octal) |
Looking for transponder-level data? View the Mode-S AA91F5 page for country allocation, callsign history, and ADS-B signal details.
N780QS frequently asked
What type of aircraft is N780QS?
N780QS is a BOMBARDIER BD-100 Challenger 350 (ICAO type code CL35).
Who operates N780QS?
N780QS is operated by NETJETS SALES INC, NETJETS AVIATION INC.
What is the Mode-S transponder code for N780QS?
N780QS broadcasts on Mode-S (ICAO 24-bit) address AA91F5 (octal 52510765). View the transponder page.
What route does N780QS typically fly?
N780QS most frequently flies between CHO and HPN based on observed flights.
Where is N780QS right now?
N780QS is not currently being tracked; last seen 8d ago.