Flight
UIA8627
Flight history and live tracking for UIA8627, operated by Uni Air. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Uni Air |
| Observed route | RCSS → RCMQ |
Flight history 38 flights since Aug 2025
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-03estimated | RCSS | RCMQ | 18:57 CST | 19:16 CST | 0h 18m | B-16221 |
| 2026-10-02estimated | RCSS | RCMQ | 19:09 CST | 19:26 CST | 0h 17m | B-16212 |
| 2026-10-01estimated | RCSS | RCMQ | 19:05 CST | 19:32 CST | 0h 26m | B-17017 |
| 2026-09-24estimated | RCSS | RCMQ | 19:19 CST | 19:38 CST | 0h 19m | B-17016 |
| 2026-09-22estimated | RCSS | RCMQ | 19:08 CST | 19:30 CST | 0h 21m | B-17006 |
Earlier flights (33) - back to 2025-08-20
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-23estimated | RCSS | RCMQ | 18:31 CST | 18:48 CST | 0h 16m | B-17016 |
| 2026-07-22estimated | RCSS | RCMQ | 18:40 CST | 19:02 CST | 0h 21m | B-17011 |
| 2026-07-19estimated | RCSS | RCMQ | 19:08 CST | 20:48 CST | 1h 39m | B-17017 |
| 2026-07-18estimated | ? | ? | 10:20Z | 10:38Z | 0h 17m | B-17001 |
| 2026-07-12estimated | RCSS | RCMQ | 18:16 CST | 18:46 CST | 0h 29m | B-17015 |
| 2026-07-08estimated | RCSS | RCMQ | 18:17 CST | 18:44 CST | 0h 26m | B-17009 |
| 2026-07-06estimated | RCSS | RCMQ | 18:40 CST | 19:34 CST | 0h 53m | B-17008 |
| 2026-07-05estimated | RCSS | RCMQ | 18:30 CST | 18:52 CST | 0h 21m | B-17005 |
| 2026-07-04estimated | RCSS | RCMQ | 18:16 CST | 18:40 CST | 0h 23m | B-17007 |
| 2026-07-03estimated | RCSS | RCMQ | 18:26 CST | 18:54 CST | 0h 28m | B-17013 |
| 2026-07-01estimated | RCSS | RCMQ | 18:32 CST | 18:50 CST | 0h 17m | B-17006 |
| 2026-06-16estimated | RCSS | RCMQ | 19:10 CST | 19:34 CST | 0h 23m | B-17002 |
| 2026-05-28estimated | RCSS | RCMQ | 19:22 CST | 19:42 CST | 0h 19m | B-17017 |
| 2026-05-26estimated | RCSS | ? | 20:11 CST | 12:38Z | 0h 26m | B-17003 |
| 2026-05-23estimated | RCSS | RCMQ | 19:15 CST | 19:36 CST | 0h 20m | B-17007 |
| 2026-05-21estimated | RCSS | RCMQ | 19:35 CST | 21:11 CST | 1h 35m | B-17002 |
| 2026-05-09estimated | RCSS | RCMQ | 19:04 CST | 19:22 CST | 0h 17m | B-17011 |
| 2026-05-07estimated | RCSS | RCMQ | 19:18 CST | 19:36 CST | 0h 17m | B-17003 |
| 2026-05-02estimated | RCSS | RCMQ | 19:04 CST | 19:24 CST | 0h 20m | B-17003 |
| 2026-04-30estimated | RCSS | RCMQ | 19:35 CST | 19:52 CST | 0h 16m | B-16211 |
| 2026-04-25estimated | RCSS | RCMQ | 20:01 CST | 20:20 CST | 0h 18m | B-17009 |
| 2026-04-23estimated | RCSS | RCMQ | 20:00 CST | 20:22 CST | 0h 21m | B-17016 |
| 2026-04-22estimated | RCSS | RCMQ | 19:22 CST | 19:40 CST | 0h 17m | B-16221 |
| 2026-04-20estimated | RCSS | RCMQ | 21:12 CST | 21:50 CST | 0h 38m | B-16220 |
| 2026-04-18estimated | RCSS | RCMQ | 19:25 CST | 19:42 CST | 0h 16m | B-16220 |
| 2026-04-04estimated | RCSS | RCMQ | 20:23 CST | 20:42 CST | 0h 18m | B-17003 |
| 2025-10-30estimated | RCSS | RCMQ | 19:26 CST | 19:46 CST | 0h 20m | B-17013 |
| 2025-10-29estimated | RCSS | RCMQ | 19:18 CST | 19:36 CST | 0h 17m | B-17003 |
| 2025-10-27estimated | RCSS | RCMQ | 19:27 CST | 19:46 CST | 0h 18m | B-17012 |
| 2025-10-14estimated | RCSS | RCMQ | 19:14 CST | 19:32 CST | 0h 17m | B-17013 |
| 2025-10-13estimated | RCSS | RCMQ | 19:17 CST | 19:38 CST | 0h 20m | B-17009 |
| 2025-10-06estimated | RCSS | RCMQ | 19:37 CST | 19:56 CST | 0h 18m | B-17006 |
| 2025-08-20estimated | RCSS | RCMQ | 01:55 CST | 02:28 CST | 0h 33m | B-17016 |
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 UIA8627 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 archive (from $9.99, with a free one-day sample). Questions: [email protected]