Flight
UAL848
Flight history and live tracking for UAL848, operated by United Airlines. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Next flight
| Date | Sun 23 Aug 2026 |
| Route | RJTT TOKYO INTERNATIONAL → PGUM GUAM INTERNATIONAL |
| Scheduled departure | 23:35 JST |
Scheduled and estimated times from the FAA SWIM feed, local to each airport.
Route
| Airline | United Airlines |
| Observed route | RJTT → RJTH |
Flight history 99 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-21estimated | ? | ? | 14:24Z | 15:22Z | 0h 57m | N17309 |
| 2026-08-20estimated | ? | ? | 00:03Z | 15:22Z | 15h 18m | N33262 |
| 2026-08-19estimated | RJTT | RJTH | 23:51 JST | 00:32 JST | 0h 40m | N33262 |
| 2026-08-17estimated | ? | ? | 14:20Z | 15:16Z | 0h 55m | N37293 |
| 2026-08-16estimated | ? | ? | 14:30Z | 15:28Z | 0h 57m | N17303 |
| 2026-08-15estimated | ? | ? | 01:10Z | 15:04Z | 13h 53m | N37293 |
| 2026-08-14estimated | ? | ? | 14:24Z | 15:10Z | 0h 45m | N37293 |
| 2026-08-13estimated | ? | ? | 04:58Z | 15:19Z | 10h 20m | N17316 |
| 2026-08-12estimated | ? | ? | 14:28Z | 15:18Z | 0h 49m | N17316 |
Earlier flights (90) - back to 2026-03-13
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | ? | ? | 14:32Z | 15:28Z | 0h 55m | A126EC |
| 2026-07-22partial | ? | ? | 00:03Z | N33264 | ||
| 2026-07-21estimated | ? | ? | 14:37Z | 15:20Z | 0h 43m | N33264 |
| 2026-07-20estimated | ? | ? | 14:23Z | 15:20Z | 0h 56m | N33262 |
| 2026-07-19estimated | ? | ? | 05:00Z | 15:26Z | 10h 25m | N33264 |
| 2026-07-18estimated | ? | ? | 14:28Z | 15:22Z | 0h 53m | N33264 |
| 2026-07-17estimated | ? | ? | 14:25Z | 15:24Z | 0h 59m | A126C6 |
| 2026-07-16estimated | ? | ? | 00:21Z | 15:30Z | 15h 08m | N37293 |
| 2026-07-15estimated | ? | ? | 14:27Z | 15:12Z | 0h 44m | N37293 |
| 2026-07-14estimated | ? | RJTK | 00:02Z | 00:34 JST | 15h 31m | N33264 |
| 2026-07-13estimated | RJTT | RJTH | 23:23 JST | 00:08 JST | 0h 44m | N33264 |
| 2026-07-12 | RJTT | RJTH | 23:28 JST | 00:24 JST | 0h 55m | A126CC |
| 2026-07-11 | RJTT | RJTK | 23:36 JST | 00:42 JST | 1h 06m | A126CC |
| 2026-07-10partial | RJTK | ? | 13:48 JST | N33264 | ||
| 2026-07-09 | RJTK | RJTH | 23:29 JST | 00:10 JST | 0h 40m | N33264 |
| 2026-07-08estimated | RJTT | RJTH | 23:32 JST | 00:14 JST | 0h 41m | N37293 |
| 2026-07-07 | RJTT | RJTK | 01:41 JST | 02:20 JST | 0h 38m | N33264 |
| 2026-07-04estimated | RJTT | RJTH | 23:24 JST | 00:20 JST | 0h 55m | A126C9 |
| 2026-07-03estimated | RJTT | RJTH | 23:30 JST | 00:16 JST | 0h 45m | A126C6 |
| 2026-07-02 | RJTT | RJTK | 13:59 JST | 00:24 JST | 10h 24m | N37293 |
| 2026-07-01 | RJTT | RJTH | 23:25 JST | 00:06 JST | 0h 40m | N37293 |
| 2026-06-30partial | RJTT | ? | 14:04 JST | A2B416 | ||
| 2026-06-29estimated | RJTT | RJTK | 14:09 JST | 00:36 JST | 10h 26m | A1270B |
| 2026-06-28estimated | RJTT | RJTH | 23:24 JST | 00:16 JST | 0h 51m | N37293 |
| 2026-06-27estimated | RJTT | RJTH | 23:22 JST | 00:20 JST | 0h 57m | A1270B |
| 2026-06-26 | RJTT | RJTK | 23:43 JST | 00:46 JST | 1h 02m | A2B416 |
| 2026-06-25 | RJTT | RJTH | 23:44 JST | 00:32 JST | 0h 47m | A2B416 |
| 2026-06-24estimated | RJTT | ? | 23:31 JST | 15:12Z | 0h 40m | N37293 |
| 2026-06-23partial | RJTT | ? | 14:53 JST | N73299 | ||
| 2026-06-22estimated | RJTT | RJTK | 21:53 JST | 00:42 JST | 2h 48m | A1270B |
| 2026-06-21 | RJTT | RJTK | 23:28 JST | 00:14 JST | 0h 46m | A1270B |
| 2026-06-20estimated | RJTT | RJTH | 23:35 JST | 00:22 JST | 0h 46m | A126C6 |
| 2026-06-19estimated | RJTT | RJTK | 09:39 JST | 00:26 JST | 14h 46m | A126EC |
| 2026-06-18partial | RJTT | ? | 00:25 JST | N37293 | ||
| 2026-06-17estimated | RJTT | RJTH | 23:40 JST | 00:24 JST | 0h 43m | N37293 |
| 2026-06-16estimated | RJTT | RJTH | 14:51 JST | 00:12 JST | 9h 20m | A126C9 |
| 2026-06-15estimated | RJTT | RJTK | 22:06 JST | 00:18 JST | 2h 11m | A126CC |
| 2026-06-14estimated | RJTT | RJTK | 14:10 JST | 00:28 JST | 10h 17m | N33264 |
| 2026-06-13 | RJTT | RJTK | 23:36 JST | 02:38 JST | 3h 02m | A126CC |
| 2026-06-12estimated | RJTT | RJTH | 23:21 JST | 00:20 JST | 0h 59m | N33264 |
| 2026-05-29partial | RJTT | ? | 09:37 JST | N33262 | ||
| 2026-05-28estimated | RJTT | RJTK | 09:27 JST | 00:20 JST | 14h 52m | N33262 |
| 2026-05-27estimated | RJTT | RJTH | 23:22 JST | 00:12 JST | 0h 50m | N33262 |
| 2026-05-25estimated | RJTT | RJTH | 23:58 JST | 00:36 JST | 0h 37m | A126C6 |
| 2026-05-24estimated | RJTT | RJTH | 23:26 JST | 00:10 JST | 0h 43m | A2B416 |
| 2026-05-23estimated | RJTT | RJTH | 23:24 JST | 00:08 JST | 0h 43m | N39297 |
| 2026-05-22estimated | RJTT | RJTH | 23:34 JST | 00:14 JST | 0h 39m | N39297 |
| 2026-05-21partial | RJTT | ? | 23:31 JST | N37293 | ||
| 2026-05-20 | RJTT | RJTK | 09:46 JST | 00:12 JST | 14h 25m | N33262 |
| 2026-05-19partial | RJTT | ? | 12:17 JST | N33262 | ||
| 2026-05-12 | RJTT | RJTK | 14:42 JST | 00:02 JST | 9h 20m | N77261 |
| 2026-05-11estimated | RJTT | RJTH | 23:27 JST | 00:26 JST | 0h 58m | N77261 |
| 2026-05-10estimated | RJTT | RJTK | 14:11 JST | 00:18 JST | 10h 06m | N33264 |
| 2026-05-09partial | RJTT | ? | 09:04 JST | N35260 | ||
| 2026-05-08partial | RJTT | ? | 09:12 JST | N35260 | ||
| 2026-05-07estimated | RJTT | RJTH | 23:18 JST | 00:14 JST | 0h 55m | N35260 |
| 2026-05-06estimated | RJTT | RJTH | 23:23 JST | 08:48 JST | 9h 24m | N35260 |
| 2026-05-05estimated | RJTT | RJTH | 23:22 JST | 00:14 JST | 0h 51m | N35260 |
| 2026-05-04estimated | RJTT | RJTH | 23:23 JST | 00:16 JST | 0h 52m | N77261 |
| 2026-05-03 | RJTT | RJTH | 23:36 JST | 00:20 JST | 0h 43m | N33262 |
| 2026-05-02 | RJTT | RJTH | 23:15 JST | 00:02 JST | 0h 46m | N39297 |
| 2026-05-01estimated | RJTT | RJTH | 23:29 JST | 00:16 JST | 0h 46m | N77261 |
| 2026-04-30estimated | RJTT | RJTH | 23:32 JST | 00:22 JST | 0h 49m | N33262 |
| 2026-04-28estimated | RJTT | RJTH | 23:33 JST | 00:26 JST | 0h 52m | N33262 |
| 2026-04-27estimated | RJTT | RJTH | 23:31 JST | 00:24 JST | 0h 52m | N37293 |
| 2026-04-26partial | RJTT | ? | 13:47 JST | N77261 | ||
| 2026-04-25partial | RJTT | ? | 09:44 JST | N77261 | ||
| 2026-04-24estimated | ? | ? | 16:34Z | 17:24Z | 0h 49m | N77261 |
| 2026-04-23estimated | ? | ? | 14:33Z | 15:32Z | 0h 58m | N77261 |
| 2026-04-22estimated | ? | ? | 04:47Z | 14:58Z | 10h 10m | N35260 |
| 2026-04-21estimated | RJTT | RJTH | 00:07 JST | 00:44 JST | 0h 36m | N35260 |
| 2026-04-20estimated | ? | ? | 05:02Z | 15:30Z | 10h 27m | N77261 |
| 2026-04-19estimated | ? | ? | 05:27Z | 15:24Z | 9h 56m | N35260 |
| 2026-04-18estimated | ? | ? | 14:29Z | 15:26Z | 0h 56m | N35260 |
| 2026-04-17estimated | ? | ? | 14:37Z | 15:32Z | 0h 54m | N37293 |
| 2026-04-16estimated | ? | ? | 14:56Z | 15:56Z | 0h 59m | A126C6 |
| 2026-04-11estimated | ? | ? | 14:29Z | 15:20Z | 0h 50m | N39297 |
| 2026-04-06estimated | ? | ? | 00:22Z | 15:26Z | 15h 04m | N39297 |
| 2026-04-05estimated | RJTT | RJTH | 23:33 JST | 00:21 JST | 0h 48m | N39297 |
| 2026-04-04estimated | ? | ? | 14:33Z | 15:28Z | 0h 54m | N37293 |
| 2026-04-03estimated | ? | ? | 12:30Z | 15:26Z | 2h 55m | N37293 |
| 2026-04-02estimated | ? | ? | 12:22Z | 15:08Z | 2h 45m | N37293 |
| 2026-03-31estimated | ? | ? | 14:44Z | 15:32Z | 0h 47m | A126C6 |
| 2026-03-30estimated | ? | ? | 15:51Z | 16:28Z | 0h 36m | A2B416 |
| 2026-03-29estimated | ? | ? | 00:31Z | 15:44Z | 15h 12m | N35260 |
| 2026-03-28estimated | ? | ? | 14:44Z | 15:32Z | 0h 47m | N35260 |
| 2026-03-16estimated | ? | ? | 05:48Z | 15:26Z | 9h 37m | N33264 |
| 2026-03-15estimated | ? | ? | 05:09Z | 15:42Z | 10h 32m | N73270 |
| 2026-03-14estimated | ? | ? | 14:42Z | 15:34Z | 0h 51m | N33264 |
| 2026-03-13estimated | ? | ? | 14:47Z | 15:50Z | 1h 02m | N73270 |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when UAL848 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our own receiver network archive. Questions: [email protected]