Not currently tracked · last seen 8d ago
- Flights observed
- 32
- Avg flight time
- 3h 18m
- Typical route
- HKT → TFU
- Last seen
- 8d ago
Last known area
Recent flights last 32
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-06 | - | Jul 6, 04:10 UTC | Jul 6, 04:20 UTC | 10m |
| 2026-07-04 | - | Jul 4, 13:30 UTC | Jul 4, 13:45 UTC | 15m |
| 2026-06-29 | - | Jun 29, 13:34 UTC | Jun 29, 13:49 UTC | 15m |
| 2026-06-19 | - | Jun 19, 10:19 UTC | Jun 19, 10:35 UTC | 15m |
| 2026-06-18 | - | Jun 18, 04:30 UTC | Jun 18, 04:40 UTC | 10m |
| 2026-06-18 | - | Jun 18, 00:40 UTC | Jun 18, 00:50 UTC | 10m |
| 2026-06-17 | - | Jun 17, 04:30 UTC | Jun 17, 04:45 UTC | 15m |
| 2026-05-31 | HKT → TFU | May 31, 09:10 UTC | May 31, 14:10 UTC | 5h 0m |
| 2026-05-30 | TFU → HKT | May 30, 11:10 UTC | May 31, 10:25 UTC | 23h 15m |
| 2026-05-30 | TFU → BKK | May 30, 08:35 UTC | May 30, 09:35 UTC | 1h 0m |
| 2026-05-24 | SZX → CTU | May 24, 02:25 UTC | May 24, 02:45 UTC | 20m |
| 2026-05-20 | SZX → CTU | May 20, 02:30 UTC | May 20, 02:40 UTC | 10m |
| 2026-05-04 | SZX → CTU | May 4, 11:45 UTC | May 4, 12:00 UTC | 15m |
| 2026-05-02 | PEK → CTU | May 2, 03:50 UTC | May 2, 04:05 UTC | 15m |
| 2026-05-01 | PEK → TFU | May 1, 12:30 UTC | May 1, 12:45 UTC | 15m |
| 2026-05-01 | CTU → PEK | May 1, 10:55 UTC | May 1, 11:05 UTC | 10m |
| 2026-05-01 | PEK → CTU | May 1, 03:55 UTC | May 1, 04:15 UTC | 20m |
| 2026-04-30 | TFU → SHE | Apr 30, 08:10 UTC | Apr 30, 08:20 UTC | 10m |
| 2026-04-29 | BKK → TFU | Apr 29, 11:35 UTC | Apr 30, 08:20 UTC | 20h 44m |
| 2026-04-29 | TFU → BKK | Apr 29, 09:20 UTC | Apr 29, 09:55 UTC | 35m |
| 2026-04-28 | TFU → BKK | Apr 28, 11:20 UTC | Apr 29, 09:55 UTC | 22h 36m |
| 2026-04-28 | TFU → BKK | Apr 28, 09:10 UTC | Apr 28, 09:35 UTC | 25m |
| 2026-04-27 | HKT → TFU | Apr 27, 12:50 UTC | Apr 28, 09:35 UTC | 20h 45m |
| 2026-04-27 | TFU → HKT | Apr 27, 09:40 UTC | Apr 27, 13:40 UTC | 4h 0m |
| 2026-04-18 | SZX → CTU | Apr 18, 02:15 UTC | Apr 18, 02:30 UTC | 15m |
| 2026-04-15 | HKT → TFU | Apr 15, 13:01 UTC | Apr 15, 13:35 UTC | 35m |
| 2026-04-15 | HKT → TFU | Apr 15, 12:45 UTC | Apr 15, 12:55 UTC | 10m |
| 2026-04-15 | TFU → HKT | Apr 15, 09:40 UTC | Apr 15, 10:40 UTC | 1h 0m |
| 2026-04-14 | HKT → TFU | Apr 14, 13:05 UTC | Apr 14, 13:30 UTC | 25m |
| 2026-04-14 | TFU → HKT | Apr 14, 09:50 UTC | Apr 14, 10:15 UTC | 25m |
| 2026-04-13 | - | Apr 13, 12:45 UTC | Apr 13, 13:30 UTC | 45m |
| 2026-04-13 | TFU → HKT | Apr 13, 09:40 UTC | Apr 13, 10:10 UTC | 30m |
Specifications
| Registration | B-8378 |
| Aircraft type | AIRBUS A-321 (A321) |
| Mode-S code | 780F33 · 36007463 (octal) |
Looking for transponder-level data? View the Mode-S 780F33 page for country allocation, callsign history, and ADS-B signal details.
B-8378 frequently asked
What type of aircraft is B-8378?
B-8378 is a AIRBUS A-321 (ICAO type code A321).
What is the Mode-S transponder code for B-8378?
B-8378 broadcasts on Mode-S (ICAO 24-bit) address 780F33 (octal 36007463). View the transponder page.
What route does B-8378 typically fly?
B-8378 most frequently flies between HKT and TFU based on observed flights.
Where is B-8378 right now?
B-8378 is not currently being tracked; last seen 8d ago.