Flight
UIA8806
Flight history and live tracking for UIA8806, 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 |
| Typical origin | RCBS SHANG YI |
| Typical destination | RCSS SUNGSHAN |
| Distance | 178 nm |
Flight history 40 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-02estimated | ? | RCSS | 02:21Z | 10:54 CST | 0h 32m | B-16212 |
| 2026-10-01estimated | ? | RCSS | 02:08Z | 10:40 CST | 0h 31m | B-16221 |
Earlier flights (38) - back to 2026-01-04
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-03-31estimated | ? | RCSS | 06:44Z | 15:08 CST | 0h 24m | B-17012 |
| 2026-03-30estimated | ? | RCSS | 06:53Z | 15:14 CST | 0h 20m | B-17007 |
| 2026-03-29estimated | ? | RCTP | 06:43Z | 15:00 CST | 0h 16m | B-17016 |
| 2026-03-12estimated | ? | RCSS | 06:23Z | 15:00 CST | 0h 37m | B-17012 |
| 2026-03-11estimated | ? | RCSS | 06:36Z | 15:08 CST | 0h 31m | B-17016 |
| 2026-03-10estimated | ? | RCSS | 06:31Z | 15:08 CST | 0h 36m | B-17007 |
| 2026-03-07estimated | ? | RCSS | 06:30Z | 15:02 CST | 0h 31m | B-17003 |
| 2026-03-06estimated | ? | RCSS | 08:21Z | 16:52 CST | 0h 31m | B-17017 |
| 2026-03-02estimated | ? | RCSS | 08:07Z | 16:44 CST | 0h 36m | B-17012 |
| 2026-03-01estimated | ? | RCSS | 06:36Z | 15:04 CST | 0h 27m | B-17001 |
| 2026-02-28estimated | ? | RCSS | 02:28Z | 11:00 CST | 0h 31m | B-17007 |
| 2026-02-27estimated | ? | RCSS | 06:39Z | 15:10 CST | 0h 31m | B-17017 |
| 2026-02-26estimated | ? | RCSS | 07:54Z | 16:26 CST | 0h 32m | B-17017 |
| 2026-02-25estimated | ? | RCSS | 06:33Z | 15:06 CST | 0h 32m | B-17001 |
| 2026-02-24estimated | ? | RCSS | 06:35Z | 15:08 CST | 0h 32m | B-17001 |
| 2026-02-23estimated | ? | RCSS | 07:10Z | 15:48 CST | 0h 37m | B-17005 |
| 2026-02-22estimated | ? | RCSS | 06:34Z | 14:58 CST | 0h 23m | B-17016 |
| 2026-02-21estimated | ? | RCSS | 06:39Z | 15:00 CST | 0h 21m | B-17017 |
| 2026-02-20estimated | ? | RCSS | 06:22Z | 14:58 CST | 0h 35m | B-17003 |
| 2026-02-18estimated | ? | RCSS | 06:32Z | 15:08 CST | 0h 36m | B-17007 |
| 2026-02-17estimated | ? | RCSS | 06:37Z | 15:00 CST | 0h 22m | B-17016 |
| 2026-02-16estimated | ? | RCSS | 06:31Z | 14:58 CST | 0h 27m | B-17016 |
| 2026-02-15estimated | ? | RCSS | 06:40Z | 15:02 CST | 0h 21m | B-17013 |
| 2026-02-14estimated | ? | RCSS | 06:32Z | 15:04 CST | 0h 31m | B-17013 |
| 2026-02-13estimated | ? | RCSS | 06:18Z | 15:04 CST | 0h 46m | B-17013 |
| 2026-02-12estimated | ? | RCSS | 06:43Z | 15:12 CST | 0h 29m | B-17015 |
| 2026-02-11estimated | ? | RCSS | 06:39Z | 15:04 CST | 0h 24m | B-17006 |
| 2026-02-07estimated | ? | RCSS | 06:42Z | 15:06 CST | 0h 23m | B-17009 |
| 2026-02-06estimated | ? | RCSS | 06:37Z | 15:00 CST | 0h 22m | B-17009 |
| 2026-02-05estimated | ? | RCSS | 06:46Z | 15:14 CST | 0h 28m | B-17016 |
| 2026-02-04estimated | ? | RCSS | 06:29Z | 15:14 CST | 0h 45m | B-17017 |
| 2026-02-02estimated | ? | RCSS | 06:38Z | 15:06 CST | 0h 27m | B-17011 |
| 2026-01-30estimated | ? | RCSS | 06:33Z | 15:10 CST | 0h 37m | B-17007 |
| 2026-01-28estimated | ? | RCSS | 06:35Z | 15:04 CST | 0h 28m | B-17016 |
| 2026-01-26estimated | ? | RCSS | 06:39Z | 15:08 CST | 0h 28m | B-17007 |
| 2026-01-21estimated | ? | RCSS | 06:30Z | 15:06 CST | 0h 36m | B-17002 |
| 2026-01-20estimated | ? | RCSS | 06:38Z | 15:06 CST | 0h 28m | B-17017 |
| 2026-01-04estimated | ? | RCSS | 06:29Z | 14:56 CST | 0h 27m | B-17006 |
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 UIA8806 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]