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