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