Not currently tracked · last seen 11h ago
- Flights observed
- 194 showing last 50
- Avg flight time
- 2h 50m
- Typical route
- TUL → SDF
- Last seen
- 11h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | SDF → MDT | Jun 2, 08:35 UTC | Jun 2, 09:45 UTC | 1h 10m |
| 2026-06-02 | SDF → MDT | Jun 2, 08:31 UTC | Jun 2, 09:41 UTC | 1h 10m |
| 2026-06-02 | TUL → SDF | Jun 2, 04:35 UTC | Jun 2, 06:00 UTC | 1h 25m |
| 2026-06-02 | TUL → SDF | Jun 2, 04:29 UTC | Jun 2, 05:59 UTC | 1h 30m |
| 2026-06-02 | TUL → SDF | Jun 2, 02:05 UTC | Jun 2, 02:30 UTC | 25m |
| 2026-05-29 | SDF → TUL | May 29, 09:20 UTC | May 29, 10:35 UTC | 1h 15m |
| 2026-05-29 | PHX → SDF | May 29, 03:10 UTC | May 29, 06:10 UTC | 3h 0m |
| 2026-05-28 | SDF → PHX | May 28, 19:25 UTC | May 28, 22:45 UTC | 3h 20m |
| 2026-05-28 | BOS → SDF | May 28, 12:10 UTC | May 28, 14:10 UTC | 2h 0m |
| 2026-05-28 | SDF → BOS | May 28, 08:35 UTC | May 28, 10:10 UTC | 1h 35m |
| 2026-05-28 | BOS → SDF | May 28, 02:35 UTC | May 28, 04:40 UTC | 2h 5m |
| 2026-05-27 | ONT → BOS | May 27, 18:25 UTC | May 27, 23:25 UTC | 5h 0m |
| 2026-05-27 | BOS → EWR | May 27, 11:35 UTC | May 27, 13:30 UTC | 1h 55m |
| 2026-05-27 | BOS → EWR | May 27, 11:35 UTC | May 27, 13:21 UTC | 1h 46m |
| 2026-05-27 | RFD → DEN | May 27, 07:50 UTC | May 27, 09:30 UTC | 1h 40m |
| 2026-05-27 | RFD → DEN | May 27, 07:54 UTC | May 27, 09:28 UTC | 1h 34m |
| 2026-05-27 | ONT → RFD | May 27, 02:59 UTC | May 27, 06:04 UTC | 3h 5m |
| 2026-05-26 | SDF → ANC | May 26, 18:19 UTC | May 26, 21:59 UTC | 3h 40m |
| 2026-05-26 | MIA → SDF | May 26, 11:30 UTC | May 26, 13:34 UTC | 2h 5m |
| 2026-05-26 | SJO → MIA | May 26, 00:09 UTC | May 26, 00:35 UTC | 25m |
| 2026-05-25 | MIA → PTY | May 25, 13:25 UTC | May 25, 13:50 UTC | 25m |
| 2026-05-25 | MIA → PTY | May 25, 13:08 UTC | May 25, 15:31 UTC | 2h 23m |
| 2026-05-24 | UIO → MIA | May 24, 14:30 UTC | May 25, 08:45 UTC | 18h 15m |
| 2026-05-24 | MIA → BOG | May 24, 12:59 UTC | May 24, 16:34 UTC | 3h 35m |
| 2026-05-24 | MIA → BOG | May 24, 13:05 UTC | May 25, 08:45 UTC | 19h 40m |
| 2026-05-24 | BOG → MIA | May 24, 08:20 UTC | May 24, 11:35 UTC | 3h 15m |
| 2026-05-24 | BOG → MIA | May 24, 08:08 UTC | May 24, 11:36 UTC | 3h 28m |
| 2026-05-24 | MIA → BOG | May 24, 01:15 UTC | May 24, 04:20 UTC | 3h 5m |
| 2026-05-22 | SDQ → MIA | May 22, 22:50 UTC | May 23, 00:25 UTC | 1h 35m |
| 2026-05-22 | SDQ → MIA | May 22, 22:34 UTC | May 23, 00:29 UTC | 1h 55m |
| 2026-05-22 | MIA → SDQ | May 22, 13:05 UTC | May 22, 14:25 UTC | 1h 20m |
| 2026-05-22 | MIA → SDQ | May 22, 12:54 UTC | May 22, 14:50 UTC | 1h 56m |
| 2026-05-22 | PHL → PBI | May 22, 08:40 UTC | May 22, 09:15 UTC | 35m |
| 2026-05-22 | PHL → PBI | May 22, 08:48 UTC | May 22, 09:19 UTC | 31m |
| 2026-05-22 | PHL → PBI | May 22, 06:15 UTC | May 22, 07:50 UTC | 1h 35m |
| 2026-05-22 | AUS → SDF | May 22, 01:25 UTC | May 22, 03:45 UTC | 2h 20m |
| 2026-05-22 | AUS → SDF | May 22, 01:26 UTC | May 22, 03:48 UTC | 2h 22m |
| 2026-05-21 | SDF → AUS | May 21, 09:50 UTC | May 21, 12:35 UTC | 2h 45m |
| 2026-05-21 | SDF → AUS | May 21, 09:50 UTC | May 21, 12:34 UTC | 2h 44m |
| 2026-05-21 | SJU → SDF | May 21, 04:40 UTC | May 21, 08:25 UTC | 3h 45m |
| 2026-05-21 | SJU → SDF | May 21, 04:35 UTC | May 21, 08:37 UTC | 4h 2m |
| 2026-05-21 | SDF → SJU | May 21, 00:30 UTC | May 21, 00:50 UTC | 20m |
| 2026-05-20 | SDF → SJU | May 20, 21:20 UTC | May 20, 23:00 UTC | 1h 40m |
| 2026-05-20 | SDF → SJU | May 20, 21:14 UTC | May 21, 00:52 UTC | 3h 38m |
| 2026-05-20 | TPA → SDF | May 20, 12:10 UTC | May 20, 13:45 UTC | 1h 35m |
| 2026-05-20 | TPA → SDF | May 20, 12:05 UTC | May 20, 13:50 UTC | 1h 45m |
| 2026-05-20 | SDF → PIE | May 20, 08:25 UTC | May 20, 10:00 UTC | 1h 35m |
| 2026-05-20 | SDF → PIE | May 20, 08:21 UTC | May 20, 09:57 UTC | 1h 36m |
| 2026-05-20 | BFI → SDF | May 20, 02:35 UTC | May 20, 06:25 UTC | 3h 51m |
| 2026-05-20 | BFI → SDF | May 20, 02:30 UTC | May 20, 06:22 UTC | 3h 52m |
Specifications
| Registration | N912UP |
| Operator | BOEING CO |
| Mode-S code | AC9FE9 · 53117751 (octal) |
Looking for transponder-level data? View the Mode-S AC9FE9 page for country allocation, callsign history, and ADS-B signal details.
N912UP frequently asked
Who operates N912UP?
N912UP is operated by BOEING CO.
What is the Mode-S transponder code for N912UP?
N912UP broadcasts on Mode-S (ICAO 24-bit) address AC9FE9 (octal 53117751). View the transponder page.
What route does N912UP typically fly?
N912UP most frequently flies between TUL and SDF based on observed flights.
Where is N912UP right now?
N912UP is not currently being tracked; last seen 11h ago.