sensors Mode-S transponder
A34F59
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N312MG · operated by MYLES TO GO AVIATION LLC, 312MG LLC
- Hex
- A34F59
- Octal
- 50647531
- Decimal
- 10,702,681
- Country
- US
- Tail
- N312MG
- Type
- S22T
- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 15, 20:30 UTC
Last known position
Country allocation
The ICAO 24-bit address A34F59 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| N312MG | - | 59 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | N312MG | - | Jul 15, 19:45 UTC | Jul 15, 20:30 UTC | 45m |
| 2026-07-15 | N312MG | - | Jul 15, 17:40 UTC | Jul 15, 18:45 UTC | 1h 5m |
| 2026-07-12 | N312MG | - | Jul 12, 12:50 UTC | Jul 12, 13:45 UTC | 55m |
| 2026-07-12 | N312MG | MGW → YKF | Jul 12, 10:20 UTC | Jul 12, 11:50 UTC | 1h 30m |
| 2026-07-10 | N312MG | - | Jul 10, 18:55 UTC | Jul 10, 19:30 UTC | 35m |
| 2026-07-10 | N312MG | - | Jul 10, 13:30 UTC | Jul 10, 14:30 UTC | 1h 0m |
| 2026-07-07 | N312MG | - | Jul 7, 23:00 UTC | Jul 8, 00:40 UTC | 1h 40m |
| 2026-07-07 | N312MG | - | Jul 7, 22:20 UTC | Jul 7, 22:30 UTC | 10m |
| 2026-07-01 | N312MG | - | Jul 1, 16:25 UTC | Jul 1, 17:05 UTC | 40m |
| 2026-07-01 | N312MG | - | Jul 1, 12:20 UTC | Jul 1, 13:00 UTC | 40m |
| 2026-06-29 | N312MG | - | Jun 29, 22:15 UTC | Jun 29, 23:44 UTC | 1h 30m |
| 2026-06-29 | N312MG | - | Jun 29, 12:39 UTC | Jun 29, 14:04 UTC | 1h 25m |
| 2026-06-26 | N312MG | MGW → MGW | Jun 26, 19:45 UTC | Jun 26, 22:34 UTC | 2h 50m |
| 2026-06-25 | N312MG | MGW → MGW | Jun 25, 19:29 UTC | Jun 25, 22:14 UTC | 2h 45m |
| 2026-06-23 | N312MG | - | Jun 23, 18:25 UTC | Jun 23, 21:20 UTC | 2h 55m |
| 2026-06-21 | N312MG | - | Jun 21, 23:44 UTC | Jun 22, 00:10 UTC | 25m |
| 2026-06-21 | N312MG | - | Jun 21, 18:44 UTC | Jun 21, 20:00 UTC | 1h 15m |
| 2026-06-21 | N312MG | - | Jun 21, 18:00 UTC | Jun 21, 18:04 UTC | 5m |
| 2026-06-16 | N312MG | - | Jun 16, 19:00 UTC | Jun 16, 20:15 UTC | 1h 16m |
| 2026-06-16 | N312MG | - | Jun 16, 13:30 UTC | Jun 16, 14:50 UTC | 1h 20m |
| 2026-06-02 | N312MG | - | Jun 2, 22:30 UTC | Jun 2, 22:55 UTC | 25m |
| 2026-06-02 | N312MG | - | Jun 2, 10:45 UTC | Jun 2, 10:55 UTC | 10m |
| 2026-05-31 | N312MG | - | May 31, 22:00 UTC | May 31, 23:15 UTC | 1h 15m |
| 2026-05-31 | N312MG | - | May 31, 17:25 UTC | May 31, 18:50 UTC | 1h 25m |
| 2026-05-31 | N312MG | - | May 31, 15:30 UTC | May 31, 16:40 UTC | 1h 10m |
| 2026-05-30 | N312MG | - | May 30, 15:30 UTC | May 30, 16:40 UTC | 1h 10m |
| 2026-05-19 | N312MG | - | May 19, 18:00 UTC | May 19, 19:00 UTC | 1h 0m |
| 2026-05-19 | N312MG | - | May 19, 14:40 UTC | May 19, 16:20 UTC | 1h 40m |
| 2026-05-15 | N312MG | - | May 15, 13:20 UTC | May 15, 14:20 UTC | 1h 0m |
| 2026-05-15 | N312MG | - | May 15, 10:40 UTC | May 15, 12:20 UTC | 1h 40m |
| 2026-05-11 | N312MG | - | May 11, 20:25 UTC | May 11, 20:35 UTC | 10m |
| 2026-05-11 | N312MG | - | May 11, 16:15 UTC | May 11, 16:40 UTC | 25m |
| 2026-05-10 | N312MG | - | May 10, 23:50 UTC | May 11, 02:30 UTC | 2h 40m |
| 2026-05-10 | N312MG | - | May 10, 19:45 UTC | May 10, 21:19 UTC | 1h 35m |
| 2026-05-08 | N312MG | MGW → MGW | May 8, 01:04 UTC | May 8, 01:24 UTC | 20m |
| 2026-05-04 | N312MG | - | May 4, 23:05 UTC | May 4, 23:35 UTC | 30m |
| 2026-05-04 | N312MG | - | May 4, 20:25 UTC | May 4, 21:40 UTC | 1h 15m |
| 2026-05-04 | N312MG | - | May 4, 18:10 UTC | May 4, 18:30 UTC | 20m |
| 2026-05-04 | N312MG | - | May 4, 14:20 UTC | May 4, 15:25 UTC | 1h 5m |
| 2026-05-01 | N312MG | - | May 1, 22:15 UTC | May 1, 23:30 UTC | 1h 15m |
| 2026-05-01 | N312MG | - | May 1, 20:25 UTC | May 1, 21:50 UTC | 1h 25m |
| 2026-05-01 | N312MG | - | May 1, 03:20 UTC | May 1, 03:50 UTC | 30m |
| 2026-05-01 | N312MG | - | May 1, 02:30 UTC | May 1, 03:05 UTC | 35m |
| 2026-05-01 | N312MG | - | May 1, 00:15 UTC | May 1, 01:45 UTC | 1h 30m |
| 2026-04-30 | N312MG | - | Apr 30, 22:50 UTC | Apr 30, 23:10 UTC | 20m |
| 2026-04-28 | N312MG | - | Apr 28, 23:25 UTC | Apr 28, 23:35 UTC | 10m |
| 2026-04-28 | N312MG | - | Apr 28, 20:20 UTC | Apr 28, 22:20 UTC | 2h 0m |
| 2026-04-28 | N312MG | MGW → BTP | Apr 28, 19:05 UTC | Apr 28, 19:40 UTC | 35m |
| 2026-04-26 | N312MG | - | Apr 26, 22:55 UTC | Apr 26, 23:35 UTC | 40m |
| 2026-04-26 | N312MG | - | Apr 26, 21:30 UTC | Apr 26, 22:15 UTC | 45m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the N312MG page for operator, model, and routing details .