On the ground · transponder active
- Flights observed
- 355 showing last 50
- Avg flight time
- 2h 37m
- Typical route
- LAS → SDF
- Last seen
- 3h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 20:30 UTC | Jul 14, 23:10 UTC | 2h 39m |
| 2026-07-14 | - | Jul 14, 12:55 UTC | Jul 14, 15:50 UTC | 2h 55m |
| 2026-07-14 | PHX → RFD | Jul 14, 12:57 UTC | Jul 14, 15:50 UTC | 2h 53m |
| 2026-07-14 | - | Jul 14, 07:45 UTC | Jul 14, 10:30 UTC | 2h 45m |
| 2026-07-14 | RFD → PHX | Jul 14, 07:45 UTC | Jul 14, 10:30 UTC | 2h 45m |
| 2026-07-14 | - | Jul 14, 05:15 UTC | Jul 14, 06:00 UTC | 45m |
| 2026-07-14 | SDF → RFD | Jul 14, 05:12 UTC | Jul 14, 06:08 UTC | 56m |
| 2026-07-14 | - | Jul 14, 01:50 UTC | Jul 14, 03:20 UTC | 1h 30m |
| 2026-07-14 | TPA → SDF | Jul 14, 01:43 UTC | Jul 14, 03:25 UTC | 1h 42m |
| 2026-07-12 | - | Jul 12, 21:10 UTC | Jul 12, 22:50 UTC | 1h 40m |
| 2026-07-12 | - | Jul 12, 02:55 UTC | Jul 12, 06:30 UTC | 3h 35m |
| 2026-07-11 | - | Jul 11, 23:00 UTC | Jul 11, 23:25 UTC | 25m |
| 2026-07-11 | - | Jul 11, 19:35 UTC | Jul 11, 21:15 UTC | 1h 40m |
| 2026-07-11 | ATL → SDF | Jul 11, 12:30 UTC | Jul 11, 13:20 UTC | 50m |
| 2026-07-11 | - | Jul 11, 09:50 UTC | Jul 11, 10:40 UTC | 50m |
| 2026-07-11 | - | Jul 11, 02:20 UTC | Jul 11, 05:50 UTC | 3h 30m |
| 2026-07-10 | - | Jul 10, 19:55 UTC | Jul 11, 00:10 UTC | 4h 15m |
| 2026-07-10 | - | Jul 10, 13:30 UTC | Jul 10, 16:45 UTC | 3h 15m |
| 2026-07-10 | LAS → SDF | Jul 10, 13:28 UTC | Jul 10, 16:43 UTC | 3h 15m |
| 2026-07-10 | - | Jul 10, 08:25 UTC | Jul 10, 12:10 UTC | 3h 45m |
| 2026-07-10 | SDF → LAS | Jul 10, 08:09 UTC | Jul 10, 11:59 UTC | 3h 50m |
| 2026-07-10 | - | Jul 10, 02:35 UTC | Jul 10, 06:05 UTC | 3h 30m |
| 2026-07-10 | SAN → SDF | Jul 10, 02:34 UTC | Jul 10, 06:02 UTC | 3h 28m |
| 2026-07-09 | - | Jul 9, 20:10 UTC | Jul 10, 00:10 UTC | 4h 0m |
| 2026-07-09 | LAS → SDF | Jul 9, 13:00 UTC | Jul 9, 16:15 UTC | 3h 15m |
| 2026-07-09 | LAS → SDF | Jul 9, 13:01 UTC | Jul 9, 16:12 UTC | 3h 11m |
| 2026-07-09 | - | Jul 9, 08:20 UTC | Jul 9, 11:35 UTC | 3h 15m |
| 2026-07-09 | DEN → SDF | Jul 9, 04:25 UTC | Jul 9, 06:40 UTC | 2h 15m |
| 2026-07-09 | DEN → SDF | Jul 9, 03:55 UTC | Jul 9, 06:27 UTC | 2h 32m |
| 2026-07-08 | - | Jul 8, 21:30 UTC | Jul 9, 00:10 UTC | 2h 40m |
| 2026-07-08 | LAS → SDF | Jul 8, 13:05 UTC | Jul 8, 16:25 UTC | 3h 20m |
| 2026-07-08 | LAS → SDF | Jul 8, 13:03 UTC | Jul 8, 16:21 UTC | 3h 18m |
| 2026-07-08 | SDF → LAS | Jul 8, 08:15 UTC | Jul 8, 11:25 UTC | 3h 10m |
| 2026-07-08 | SDF → LAS | Jul 8, 08:09 UTC | Jul 8, 11:32 UTC | 3h 23m |
| 2026-07-08 | - | Jul 8, 02:20 UTC | Jul 8, 06:00 UTC | 3h 40m |
| 2026-07-08 | LAX → SDF | Jul 8, 02:20 UTC | Jul 8, 05:49 UTC | 3h 29m |
| 2026-07-07 | - | Jul 7, 19:45 UTC | Jul 7, 23:25 UTC | 3h 40m |
| 2026-07-07 | MIA → SDF | Jul 7, 12:25 UTC | Jul 7, 14:15 UTC | 1h 50m |
| 2026-07-07 | MIA → SDF | Jul 7, 12:20 UTC | Jul 7, 14:13 UTC | 1h 53m |
| 2026-07-07 | - | Jul 7, 07:45 UTC | Jul 7, 09:40 UTC | 1h 55m |
| 2026-07-07 | SDF → MIA | Jul 7, 07:43 UTC | Jul 7, 09:38 UTC | 1h 55m |
| 2026-07-07 | - | Jul 7, 02:40 UTC | Jul 7, 04:35 UTC | 1h 55m |
| 2026-07-07 | MIA → SDF | Jul 7, 02:13 UTC | Jul 7, 04:37 UTC | 2h 24m |
| 2026-07-06 | - | Jul 6, 22:05 UTC | Jul 7, 00:10 UTC | 2h 5m |
| 2026-07-06 | MIA → PTY | Jul 6, 13:05 UTC | Jul 6, 13:30 UTC | 25m |
| 2026-07-06 | MIA → PTY | Jul 6, 13:00 UTC | Jul 6, 15:12 UTC | 2h 12m |
| 2026-07-05 | - | Jul 5, 19:25 UTC | Jul 5, 21:25 UTC | 2h 0m |
| 2026-07-05 | - | Jul 5, 11:30 UTC | Jul 5, 13:25 UTC | 1h 55m |
| 2026-07-05 | MIA → SDF | Jul 5, 11:31 UTC | Jul 5, 13:21 UTC | 1h 50m |
| 2026-07-04 | - | Jul 4, 18:00 UTC | Jul 5, 00:55 UTC | 6h 55m |
Specifications
| Registration | N913UP |
| Operator | BOEING CO |
| Mode-S code | ACA3A0 · 53121640 (octal) |
Looking for transponder-level data? View the Mode-S ACA3A0 page for country allocation, callsign history, and ADS-B signal details.
N913UP frequently asked
Who operates N913UP?
N913UP is operated by BOEING CO.
What is the Mode-S transponder code for N913UP?
N913UP broadcasts on Mode-S (ICAO 24-bit) address ACA3A0 (octal 53121640). View the transponder page.
What route does N913UP typically fly?
N913UP most frequently flies between LAS and SDF based on observed flights.
Where is N913UP right now?
N913UP is currently on the ground with its transponder active.