Not currently tracked · last seen 1d ago
- Flights observed
- 8
- Avg flight time
- 42m
- Typical route
- -
- Last seen
- 1d ago
Last known area
Recent flights last 8
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-04-13 | - | Apr 13, 12:20 UTC | Apr 13, 13:15 UTC | 55m |
| 2026-04-13 | - | Apr 13, 12:10 UTC | Apr 13, 12:15 UTC | 5m |
| 2026-04-13 | - | Apr 13, 09:55 UTC | Apr 13, 10:45 UTC | 50m |
| 2026-04-13 | - | Apr 13, 07:55 UTC | Apr 13, 08:20 UTC | 25m |
| 2026-04-13 | - | Apr 13, 07:40 UTC | Apr 13, 08:15 UTC | 35m |
| 2026-04-13 | - | Apr 13, 05:35 UTC | Apr 13, 06:30 UTC | 55m |
| 2026-04-13 | - | Apr 13, 03:20 UTC | Apr 13, 04:00 UTC | 40m |
| 2026-04-13 | FUK → HND | Apr 13, 00:30 UTC | Apr 13, 01:40 UTC | 1h 10m |
Specifications
| Registration | JA26MC |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 84CB66 · 41145546 (octal) |
Looking for transponder-level data? View the Mode-S 84CB66 page for country allocation, callsign history, and ADS-B signal details.
JA26MC frequently asked
What type of aircraft is JA26MC?
JA26MC is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for JA26MC?
JA26MC broadcasts on Mode-S (ICAO 24-bit) address 84CB66 (octal 41145546). View the transponder page.
Where is JA26MC right now?
JA26MC is not currently being tracked; last seen 1d ago.