sensors Mode-S transponder
E030CF
ICAO 24-bit transponder address · allocated to Argentina
Currently assigned to LV-CCO · LEARJET 60
- Hex
- E030CF
- Octal
- 70030317
- Decimal
- 14,692,559
- Country
- AR
- Tail
- LV-CCO
- Type
- LJ60
- Flights observed
- 83
- Distinct callsigns
- 1
- Country
- AR
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address E030CF 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 |
|---|---|---|---|
| LVCCO | - | 60 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | LVCCO | - | Jul 16, 00:45 UTC | Jul 16, 02:15 UTC | 1h 30m |
| 2026-07-15 | - | FXE → FTY | Jul 15, 12:55 UTC | Jul 15, 14:35 UTC | 1h 40m |
| 2026-07-12 | LVCCO | - | Jul 12, 16:50 UTC | Jul 12, 19:40 UTC | 2h 50m |
| 2026-07-12 | LVCCO | - | Jul 12, 13:25 UTC | Jul 12, 16:01 UTC | 2h 35m |
| 2026-07-12 | LVCCO | - | Jul 12, 05:20 UTC | Jul 12, 07:55 UTC | 2h 35m |
| 2026-07-11 | LVCCO | - | Jul 11, 18:05 UTC | Jul 11, 20:45 UTC | 2h 40m |
| 2026-07-11 | LVCCO | - | Jul 11, 13:55 UTC | Jul 11, 16:30 UTC | 2h 35m |
| 2026-07-11 | LVCCO | - | Jul 11, 10:05 UTC | Jul 11, 12:55 UTC | 2h 50m |
| 2026-07-07 | LVCCO | FTY → FXE | Jul 7, 19:40 UTC | Jul 7, 21:15 UTC | 1h 35m |
| 2026-07-07 | - | - | Jul 7, 10:30 UTC | Jul 7, 11:50 UTC | 1h 20m |
| 2026-06-28 | LVCCO | - | Jun 28, 05:40 UTC | Jun 28, 08:09 UTC | 2h 30m |
| 2026-06-27 | LVCCO | - | Jun 27, 19:15 UTC | Jun 27, 21:44 UTC | 2h 30m |
| 2026-06-22 | LVCCO | - | Jun 22, 21:25 UTC | Jun 23, 00:00 UTC | 2h 35m |
| 2026-06-22 | LVCCO | - | Jun 22, 10:34 UTC | Jun 22, 13:05 UTC | 2h 30m |
| 2026-06-17 | LVCCO | - | Jun 17, 04:35 UTC | Jun 17, 07:05 UTC | 2h 30m |
| 2026-06-16 | LVCCO | - | Jun 16, 18:35 UTC | Jun 16, 21:30 UTC | 2h 56m |
| 2026-06-13 | LVCCO | - | Jun 13, 11:20 UTC | Jun 14, 00:35 UTC | 13h 15m |
| 2026-06-12 | - | - | Jun 12, 20:05 UTC | Jun 12, 20:20 UTC | 15m |
| 2026-06-12 | LVCCO | - | Jun 12, 01:15 UTC | Jun 12, 01:30 UTC | 15m |
| 2026-06-11 | LVCCO | - | Jun 11, 17:00 UTC | Jun 11, 17:30 UTC | 30m |
| 2026-06-11 | LVCCO | - | Jun 11, 12:45 UTC | Jun 11, 14:00 UTC | 1h 15m |
| 2026-06-11 | LVCCO | - | Jun 11, 10:15 UTC | Jun 11, 11:35 UTC | 1h 20m |
| 2026-06-10 | - | - | Jun 10, 01:30 UTC | Jun 10, 01:55 UTC | 25m |
| 2026-06-10 | - | - | Jun 10, 00:25 UTC | Jun 10, 00:45 UTC | 20m |
| 2026-06-08 | LVCCO | AEP → AEP | Jun 8, 09:20 UTC | Jun 8, 17:35 UTC | 8h 15m |
| 2026-06-07 | - | - | Jun 7, 18:45 UTC | Jun 7, 19:20 UTC | 35m |
| 2026-06-07 | - | - | Jun 7, 16:35 UTC | Jun 7, 16:55 UTC | 20m |
| 2026-06-06 | - | - | Jun 6, 12:54 UTC | Jun 6, 13:30 UTC | 35m |
| 2026-06-06 | LVCCO | - | Jun 6, 11:25 UTC | Jun 6, 11:45 UTC | 20m |
| 2026-06-05 | - | - | Jun 5, 16:20 UTC | Jun 5, 16:45 UTC | 25m |
| 2026-06-05 | - | - | Jun 5, 14:30 UTC | Jun 5, 14:45 UTC | 15m |
| 2026-06-03 | LVCCO | - | Jun 3, 22:25 UTC | Jun 3, 22:50 UTC | 25m |
| 2026-06-02 | LVCCO | - | Jun 2, 20:30 UTC | Jun 2, 20:55 UTC | 25m |
| 2026-06-01 | LVCCO | - | Jun 1, 18:40 UTC | Jun 1, 19:20 UTC | 40m |
| 2026-06-01 | LVCCO | - | Jun 1, 16:05 UTC | Jun 1, 16:25 UTC | 20m |
| 2026-05-31 | LVCCO | - | May 31, 22:30 UTC | May 31, 22:50 UTC | 20m |
| 2026-05-31 | - | - | May 31, 18:40 UTC | May 31, 19:05 UTC | 25m |
| 2026-05-30 | LVCCO | - | May 30, 19:00 UTC | May 30, 19:40 UTC | 40m |
| 2026-05-29 | LVCCO | - | May 29, 14:00 UTC | May 29, 14:30 UTC | 30m |
| 2026-05-28 | LVCCO | - | May 28, 20:00 UTC | May 28, 21:15 UTC | 1h 15m |
| 2026-05-27 | LVCCO | - | May 27, 09:00 UTC | May 27, 10:15 UTC | 1h 15m |
| 2026-05-24 | LVCCO | - | May 24, 23:00 UTC | May 24, 23:46 UTC | 46m |
| 2026-05-24 | LVCCO | - | May 24, 16:20 UTC | May 24, 17:10 UTC | 50m |
| 2026-05-24 | LVCCO | - | May 24, 13:45 UTC | May 24, 13:55 UTC | 10m |
| 2026-05-23 | - | - | May 23, 23:45 UTC | May 24, 00:10 UTC | 25m |
| 2026-05-23 | LVCCO | - | May 23, 21:45 UTC | May 23, 22:05 UTC | 20m |
| 2026-05-19 | LVCCO | - | May 19, 11:40 UTC | May 19, 19:35 UTC | 7h 55m |
| 2026-05-18 | LVCCO | - | May 18, 18:30 UTC | May 18, 18:55 UTC | 25m |
| 2026-05-18 | - | - | May 18, 16:45 UTC | May 18, 17:05 UTC | 20m |
| 2026-05-18 | LVCCO | - | May 18, 04:00 UTC | May 18, 06:25 UTC | 2h 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-CCO page for operator, model, and routing details .