Not currently tracked · last seen 19h ago
- Flights observed
- 76 showing last 50
- Avg flight time
- 1h 59m
- Typical route
- SHA → MFM
- Last seen
- 19h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 11:50 UTC | Jul 13, 12:00 UTC | 10m |
| 2026-07-13 | - | Jul 13, 08:45 UTC | Jul 13, 10:05 UTC | 1h 20m |
| 2026-07-05 | - | Jul 5, 13:15 UTC | Jul 5, 13:30 UTC | 15m |
| 2026-07-05 | - | Jul 5, 11:35 UTC | Jul 5, 12:00 UTC | 25m |
| 2026-07-05 | - | Jul 5, 06:45 UTC | Jul 5, 07:10 UTC | 25m |
| 2026-07-05 | - | Jul 5, 04:05 UTC | Jul 5, 04:30 UTC | 25m |
| 2026-07-04 | - | Jul 4, 06:55 UTC | Jul 4, 07:35 UTC | 40m |
| 2026-07-04 | - | Jul 4, 04:00 UTC | Jul 4, 04:30 UTC | 30m |
| 2026-07-01 | - | Jul 1, 07:20 UTC | Jul 1, 07:40 UTC | 20m |
| 2026-07-01 | - | Jul 1, 04:25 UTC | Jul 1, 04:45 UTC | 20m |
| 2026-06-29 | - | Jun 29, 09:50 UTC | Jun 29, 10:00 UTC | 10m |
| 2026-06-29 | - | Jun 29, 06:59 UTC | Jun 29, 07:15 UTC | 15m |
| 2026-06-26 | - | Jun 26, 06:50 UTC | Jun 26, 07:30 UTC | 40m |
| 2026-06-26 | - | Jun 26, 04:00 UTC | Jun 26, 04:20 UTC | 20m |
| 2026-06-22 | - | Jun 22, 06:45 UTC | Jun 22, 07:10 UTC | 25m |
| 2026-06-22 | - | Jun 22, 06:00 UTC | Jun 22, 06:10 UTC | 10m |
| 2026-06-22 | - | Jun 22, 03:54 UTC | Jun 22, 04:24 UTC | 30m |
| 2026-06-18 | - | Jun 18, 06:10 UTC | Jun 18, 10:00 UTC | 3h 50m |
| 2026-06-17 | - | Jun 17, 06:30 UTC | Jun 17, 06:40 UTC | 10m |
| 2026-06-16 | - | Jun 16, 06:45 UTC | Jun 16, 07:05 UTC | 20m |
| 2026-06-15 | - | Jun 15, 06:49 UTC | Jun 15, 08:10 UTC | 1h 20m |
| 2026-06-15 | - | Jun 15, 04:15 UTC | Jun 15, 04:30 UTC | 15m |
| 2026-06-11 | PVG → SYX | Jun 11, 05:45 UTC | Jun 11, 10:00 UTC | 4h 15m |
| 2026-06-10 | SZX → SHA | Jun 10, 09:50 UTC | Jun 10, 10:00 UTC | 10m |
| 2026-06-10 | SHA → SZX | Jun 10, 06:50 UTC | Jun 10, 07:10 UTC | 20m |
| 2026-06-08 | SYX → PVG | Jun 8, 09:55 UTC | Jun 8, 10:50 UTC | 55m |
| 2026-06-07 | MFM → SHA | Jun 7, 07:05 UTC | Jun 7, 08:10 UTC | 1h 5m |
| 2026-06-07 | SHA → MFM | Jun 7, 03:00 UTC | Jun 7, 03:50 UTC | 50m |
| 2026-06-05 | SHA → SZX | Jun 5, 08:35 UTC | Jun 5, 08:55 UTC | 20m |
| 2026-06-03 | MFM → SHA | Jun 3, 05:50 UTC | Jun 3, 06:10 UTC | 20m |
| 2026-06-03 | SHA → MFM | Jun 3, 03:55 UTC | Jun 3, 04:15 UTC | 20m |
| 2026-06-01 | HAK → SHA | Jun 1, 04:50 UTC | Jun 1, 07:50 UTC | 3h 0m |
| 2026-05-31 | HAK → SHA | May 31, 10:00 UTC | Jun 1, 07:50 UTC | 21h 50m |
| 2026-05-27 | ZUH → SHA | May 27, 13:20 UTC | May 27, 13:30 UTC | 10m |
| 2026-05-27 | SHA → ZUH | May 27, 06:44 UTC | May 27, 11:35 UTC | 4h 51m |
| 2026-05-27 | MFM → SHA | May 27, 05:49 UTC | May 27, 06:09 UTC | 20m |
| 2026-05-27 | SHA → MFM | May 27, 03:45 UTC | May 27, 04:04 UTC | 20m |
| 2026-05-26 | SZX → SHA | May 26, 09:35 UTC | May 26, 09:45 UTC | 10m |
| 2026-05-26 | SHA → SZX | May 26, 06:29 UTC | May 26, 07:15 UTC | 45m |
| 2026-05-25 | SHA → SZX | May 25, 12:05 UTC | May 26, 07:15 UTC | 19h 10m |
| 2026-05-21 | HAK → JGS | May 21, 09:40 UTC | May 21, 09:55 UTC | 15m |
| 2026-05-21 | JGS → HAK | May 21, 05:05 UTC | May 21, 05:15 UTC | 10m |
| 2026-05-20 | JGS → HAK | May 20, 06:35 UTC | May 21, 05:15 UTC | 22h 40m |
| 2026-05-20 | MFM → SHA | May 20, 05:55 UTC | May 20, 07:00 UTC | 1h 5m |
| 2026-05-20 | SHA → MFM | May 20, 03:45 UTC | May 20, 04:00 UTC | 15m |
| 2026-05-19 | MFM → SHA | May 19, 08:50 UTC | May 19, 09:55 UTC | 1h 5m |
| 2026-05-19 | SHA → MFM | May 19, 07:05 UTC | May 19, 07:20 UTC | 15m |
| 2026-05-19 | SHA → MFM | May 19, 04:05 UTC | May 19, 04:15 UTC | 10m |
| 2026-05-18 | MFM → SHA | May 18, 06:01 UTC | May 18, 06:20 UTC | 20m |
| 2026-05-18 | SHA → MFM | May 18, 04:11 UTC | May 18, 04:30 UTC | 20m |
Specifications
| Registration | B-5523 |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 78065A · 36003132 (octal) |
Looking for transponder-level data? View the Mode-S 78065A page for country allocation, callsign history, and ADS-B signal details.
B-5523 frequently asked
What type of aircraft is B-5523?
B-5523 is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for B-5523?
B-5523 broadcasts on Mode-S (ICAO 24-bit) address 78065A (octal 36003132). View the transponder page.
What route does B-5523 typically fly?
B-5523 most frequently flies between SHA and MFM based on observed flights.
Where is B-5523 right now?
B-5523 is not currently being tracked; last seen 19h ago.