sensors Mode-S transponder
E0659A
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-FVZ · LEARJET 60
- Hex
- E0659A
- Octal
- 70062632
- Decimal
- 14,706,074
- Country
- AR
- Tail
- LV-FVZ
- Type
- LJ60
- Flights observed
- 73
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- Jul 26, 14:50 UTC
Last known position
Country allocation
The ICAO 24-bit address E0659A falls within the block assigned to Argentina (AR) by ICAO Annex 10, Volume III. Every aircraft registered in Argentina 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 |
|---|---|---|---|
| LVFVZ | - | 73 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | LVFVZ | - | Jul 26, 14:15 UTC | Jul 26, 14:50 UTC | 35m |
| 2026-07-26 | LVFVZ | - | Jul 26, 12:50 UTC | Jul 26, 13:15 UTC | 25m |
| 2026-07-25 | LVFVZ | - | Jul 25, 18:10 UTC | Jul 25, 18:45 UTC | 35m |
| 2026-07-25 | LVFVZ | - | Jul 25, 17:00 UTC | Jul 25, 17:20 UTC | 20m |
| 2026-07-15 | LVFVZ | - | Jul 15, 17:20 UTC | Jul 15, 17:45 UTC | 25m |
| 2026-07-15 | LVFVZ | - | Jul 15, 15:35 UTC | Jul 15, 16:05 UTC | 30m |
| 2026-07-14 | LVFVZ | - | Jul 14, 19:45 UTC | Jul 14, 20:15 UTC | 30m |
| 2026-07-14 | LVFVZ | - | Jul 14, 18:35 UTC | Jul 14, 19:00 UTC | 25m |
| 2026-07-08 | LVFVZ | - | Jul 8, 15:55 UTC | Jul 8, 21:00 UTC | 5h 5m |
| 2026-07-03 | LVFVZ | - | Jul 3, 17:30 UTC | Jul 3, 18:10 UTC | 40m |
| 2026-07-03 | LVFVZ | - | Jul 3, 16:20 UTC | Jul 3, 16:45 UTC | 25m |
| 2026-07-01 | LVFVZ | - | Jul 1, 20:10 UTC | Jul 1, 20:55 UTC | 45m |
| 2026-07-01 | LVFVZ | - | Jul 1, 19:00 UTC | Jul 1, 19:20 UTC | 20m |
| 2026-06-30 | LVFVZ | - | Jun 30, 11:35 UTC | Jun 30, 12:05 UTC | 30m |
| 2026-06-30 | LVFVZ | - | Jun 30, 07:30 UTC | Jun 30, 08:00 UTC | 30m |
| 2026-06-30 | LVFVZ | - | Jun 30, 00:04 UTC | Jun 30, 00:20 UTC | 15m |
| 2026-06-29 | LVFVZ | - | Jun 29, 22:44 UTC | Jun 29, 23:14 UTC | 30m |
| 2026-06-29 | LVFVZ | - | Jun 29, 21:34 UTC | Jun 29, 22:05 UTC | 30m |
| 2026-06-27 | LVFVZ | - | Jun 27, 00:55 UTC | Jun 27, 01:24 UTC | 30m |
| 2026-06-26 | LVFVZ | - | Jun 26, 19:39 UTC | Jun 26, 20:10 UTC | 30m |
| 2026-06-26 | LVFVZ | - | Jun 26, 13:45 UTC | Jun 26, 14:29 UTC | 45m |
| 2026-06-26 | LVFVZ | - | Jun 26, 12:29 UTC | Jun 26, 12:50 UTC | 20m |
| 2026-06-18 | LVFVZ | AEP → AEP | Jun 18, 12:20 UTC | Jun 18, 19:55 UTC | 7h 35m |
| 2026-05-25 | LVFVZ | - | May 25, 19:44 UTC | May 25, 20:15 UTC | 30m |
| 2026-05-25 | LVFVZ | - | May 25, 18:35 UTC | May 25, 18:45 UTC | 10m |
| 2026-05-24 | LVFVZ | - | May 24, 12:00 UTC | May 24, 12:30 UTC | 30m |
| 2026-05-23 | LVFVZ | - | May 23, 09:50 UTC | May 23, 10:15 UTC | 25m |
| 2026-05-23 | LVFVZ | - | May 23, 08:25 UTC | May 23, 08:45 UTC | 20m |
| 2026-05-22 | LVFVZ | - | May 22, 17:10 UTC | May 22, 17:40 UTC | 30m |
| 2026-05-22 | LVFVZ | - | May 22, 16:00 UTC | May 22, 16:20 UTC | 20m |
| 2026-05-21 | LVFVZ | - | May 21, 23:00 UTC | May 21, 23:40 UTC | 40m |
| 2026-05-21 | LVFVZ | - | May 21, 21:40 UTC | May 21, 22:10 UTC | 30m |
| 2026-05-20 | LVFVZ | AEP → AEP | May 20, 20:05 UTC | May 21, 01:50 UTC | 5h 45m |
| 2026-05-19 | LVFVZ | - | May 19, 17:55 UTC | May 19, 18:25 UTC | 30m |
| 2026-05-19 | LVFVZ | - | May 19, 16:20 UTC | May 19, 16:40 UTC | 20m |
| 2026-05-19 | LVFVZ | - | May 19, 12:45 UTC | May 19, 13:15 UTC | 30m |
| 2026-05-19 | LVFVZ | - | May 19, 11:25 UTC | May 19, 11:45 UTC | 20m |
| 2026-05-18 | LVFVZ | - | May 18, 19:15 UTC | May 18, 19:45 UTC | 30m |
| 2026-05-18 | LVFVZ | - | May 18, 16:50 UTC | May 18, 17:10 UTC | 20m |
| 2026-05-16 | LVFVZ | - | May 16, 21:05 UTC | May 16, 21:30 UTC | 25m |
| 2026-05-16 | LVFVZ | - | May 16, 19:35 UTC | May 16, 20:00 UTC | 25m |
| 2026-05-15 | LVFVZ | - | May 15, 19:05 UTC | May 15, 19:45 UTC | 40m |
| 2026-05-15 | LVFVZ | - | May 15, 15:00 UTC | May 15, 15:25 UTC | 25m |
| 2026-05-15 | LVFVZ | - | May 15, 12:00 UTC | May 15, 12:25 UTC | 25m |
| 2026-05-15 | LVFVZ | - | May 15, 10:50 UTC | May 15, 11:10 UTC | 20m |
| 2026-05-14 | LVFVZ | - | May 14, 14:15 UTC | May 14, 15:30 UTC | 1h 15m |
| 2026-05-14 | LVFVZ | - | May 14, 12:20 UTC | May 14, 12:50 UTC | 30m |
| 2026-05-13 | LVFVZ | - | May 13, 09:05 UTC | May 13, 16:45 UTC | 7h 40m |
| 2026-05-11 | LVFVZ | AEP → AEP | May 11, 10:40 UTC | May 11, 16:35 UTC | 5h 55m |
| 2026-05-09 | LVFVZ | - | May 9, 08:45 UTC | May 9, 09:10 UTC | 25m |
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 LV-FVZ page for operator, model, and routing details .