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