sensors Mode-S transponder
A97D34
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N710MV · GULFSTREAM 4 · operated by TAILSPIN MANAGEMENT LLC
- Hex
- A97D34
- Octal
- 52276464
- Decimal
- 11,107,636
- Country
- US
- Tail
- N710MV
- Type
- GLF4
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address A97D34 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 |
|---|---|---|---|
| MVJ71 | - | 48 | 2026-06-11 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | MVJ71 | - | Jun 11, 03:15 UTC | Jun 11, 04:05 UTC | 50m |
| 2026-06-10 | MVJ71 | - | Jun 10, 21:00 UTC | Jun 11, 02:25 UTC | 5h 25m |
| 2026-06-09 | MVJ71 | - | Jun 9, 16:45 UTC | Jun 9, 20:10 UTC | 3h 25m |
| 2026-06-09 | MVJ71 | - | Jun 9, 04:40 UTC | Jun 9, 11:05 UTC | 6h 25m |
| 2026-06-08 | MVJ71 | - | Jun 8, 03:35 UTC | Jun 8, 04:40 UTC | 1h 5m |
| 2026-06-08 | MVJ71 | - | Jun 8, 01:35 UTC | Jun 8, 03:10 UTC | 1h 35m |
| 2026-06-05 | MVJ71 | - | Jun 5, 22:45 UTC | Jun 6, 00:30 UTC | 1h 45m |
| 2026-06-05 | MVJ71 | VNY → NUQ | Jun 5, 18:40 UTC | Jun 5, 19:30 UTC | 50m |
| 2026-06-02 | MVJ71 | - | Jun 2, 17:45 UTC | Jun 2, 18:15 UTC | 30m |
| 2026-06-01 | MVJ71 | - | Jun 1, 19:05 UTC | Jun 2, 14:35 UTC | 19h 30m |
| 2026-06-01 | MVJ71 | - | Jun 1, 18:00 UTC | Jun 2, 14:35 UTC | 20h 35m |
| 2026-06-01 | MVJ71 | - | Jun 1, 15:25 UTC | Jun 1, 16:10 UTC | 45m |
| 2026-05-30 | MVJ71 | - | May 30, 05:40 UTC | May 30, 06:15 UTC | 35m |
| 2026-05-30 | MVJ71 | - | May 30, 01:15 UTC | May 30, 01:40 UTC | 25m |
| 2026-05-19 | MVJ71 | - | May 19, 17:45 UTC | May 19, 18:20 UTC | 35m |
| 2026-05-17 | MVJ71 | - | May 17, 21:20 UTC | May 17, 22:05 UTC | 45m |
| 2026-05-17 | MVJ71 | AUS → HSH | May 17, 18:10 UTC | May 17, 20:40 UTC | 2h 30m |
| 2026-05-16 | MVJ71 | OAK → AUS | May 16, 02:40 UTC | May 16, 05:40 UTC | 3h 0m |
| 2026-05-14 | MVJ71 | - | May 14, 00:30 UTC | May 14, 00:40 UTC | 10m |
| 2026-05-13 | MVJ71 | - | May 13, 17:10 UTC | May 13, 23:10 UTC | 6h 0m |
| 2026-05-12 | MVJ71 | - | May 12, 22:31 UTC | May 13, 01:05 UTC | 2h 35m |
| 2026-05-12 | MVJ71 | - | May 12, 20:20 UTC | May 12, 20:35 UTC | 15m |
| 2026-05-10 | MVJ71 | PPM → LGA | May 10, 22:15 UTC | May 11, 01:40 UTC | 3h 25m |
| 2026-05-10 | MVJ71 | - | May 10, 19:35 UTC | May 10, 19:54 UTC | 20m |
| 2026-05-09 | MVJ71 | - | May 9, 11:50 UTC | May 9, 14:10 UTC | 2h 20m |
| 2026-05-08 | MVJ71 | - | May 8, 22:10 UTC | May 9, 00:20 UTC | 2h 10m |
| 2026-05-08 | MVJ71 | - | May 8, 14:45 UTC | May 8, 16:55 UTC | 2h 10m |
| 2026-05-03 | MVJ71 | - | May 3, 17:00 UTC | May 3, 18:34 UTC | 1h 35m |
| 2026-05-02 | MVJ71 | - | May 2, 17:30 UTC | May 2, 18:10 UTC | 40m |
| 2026-04-30 | MVJ71 | - | Apr 30, 18:15 UTC | Apr 30, 20:30 UTC | 2h 15m |
| 2026-04-30 | MVJ71 | - | Apr 30, 15:05 UTC | Apr 30, 15:40 UTC | 35m |
| 2026-04-28 | MVJ71 | - | Apr 28, 07:40 UTC | Apr 28, 12:00 UTC | 4h 20m |
| 2026-04-25 | MVJ71 | - | Apr 25, 02:40 UTC | Apr 25, 03:15 UTC | 35m |
| 2026-04-24 | MVJ71 | FCM → CLD | Apr 24, 22:30 UTC | Apr 25, 02:00 UTC | 3h 30m |
| 2026-04-24 | MVJ71 | - | Apr 24, 14:25 UTC | Apr 24, 17:25 UTC | 3h 0m |
| 2026-04-24 | MVJ71 | - | Apr 24, 00:15 UTC | Apr 24, 00:35 UTC | 20m |
| 2026-04-23 | MVJ71 | - | Apr 23, 17:50 UTC | Apr 23, 23:25 UTC | 5h 35m |
| 2026-04-21 | MVJ71 | BOS → TEB | Apr 21, 21:25 UTC | Apr 21, 22:20 UTC | 55m |
| 2026-04-20 | MVJ71 | - | Apr 20, 20:40 UTC | Apr 21, 01:35 UTC | 4h 55m |
| 2026-04-20 | MVJ71 | - | Apr 20, 18:55 UTC | Apr 20, 19:15 UTC | 20m |
| 2026-04-19 | MVJ71 | - | Apr 19, 10:20 UTC | Apr 19, 10:50 UTC | 30m |
| 2026-04-19 | MVJ71 | - | Apr 19, 02:20 UTC | Apr 19, 02:45 UTC | 25m |
| 2026-04-18 | MVJ71 | LAS → VNY | Apr 18, 22:10 UTC | Apr 18, 22:55 UTC | 45m |
| 2026-04-18 | MVJ71 | - | Apr 18, 03:25 UTC | Apr 18, 03:50 UTC | 25m |
| 2026-04-17 | MVJ71 | - | Apr 17, 03:40 UTC | Apr 17, 04:15 UTC | 35m |
| 2026-04-14 | MVJ71 | - | Apr 14, 18:55 UTC | Apr 14, 19:35 UTC | 40m |
| 2026-04-13 | MVJ71 | VNY → LAS | Apr 13, 21:55 UTC | Apr 13, 22:40 UTC | 45m |
| 2026-04-12 | MVJ71 | - | Apr 12, 17:15 UTC | Apr 12, 20:15 UTC | 3h 0m |
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 N710MV page for operator, model, and routing details .