sensors Mode-S transponder
39C5C6
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HROG · PIAGGIO P-180 Avanti
- Hex
- 39C5C6
- Octal
- 16342706
- Decimal
- 3,786,182
- Country
- FR
- Tail
- F-HROG
- Type
- P180
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 39C5C6 falls within the block assigned to France (FR) by ICAO Annex 10, Volume III. Every aircraft registered in France 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 |
|---|---|---|---|
| OYO2 | - | 56 | 2026-05-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-24 | OYO2 | - | May 24, 13:40 UTC | May 24, 14:15 UTC | 35m |
| 2026-05-24 | OYO2 | - | May 24, 09:45 UTC | May 24, 11:35 UTC | 1h 50m |
| 2026-05-24 | OYO2 | - | May 24, 06:15 UTC | May 24, 08:05 UTC | 1h 50m |
| 2026-05-22 | OYO2 | - | May 22, 11:35 UTC | May 22, 12:55 UTC | 1h 20m |
| 2026-05-22 | OYO2 | - | May 22, 07:45 UTC | May 22, 09:15 UTC | 1h 30m |
| 2026-05-21 | OYO2 | - | May 21, 13:05 UTC | May 21, 13:15 UTC | 10m |
| 2026-05-21 | OYO2 | - | May 21, 11:15 UTC | May 21, 12:10 UTC | 55m |
| 2026-05-21 | OYO2 | - | May 21, 07:50 UTC | May 21, 08:45 UTC | 55m |
| 2026-05-21 | OYO2 | - | May 21, 06:45 UTC | May 21, 06:55 UTC | 10m |
| 2026-05-17 | OYO2 | - | May 17, 13:55 UTC | May 17, 14:25 UTC | 30m |
| 2026-05-17 | OYO2 | - | May 17, 11:01 UTC | May 17, 12:55 UTC | 1h 55m |
| 2026-05-17 | OYO2 | - | May 17, 08:25 UTC | May 17, 09:45 UTC | 1h 20m |
| 2026-05-16 | OYO2 | - | May 16, 13:35 UTC | May 17, 09:45 UTC | 20h 10m |
| 2026-05-16 | OYO2 | - | May 16, 13:11 UTC | May 17, 09:45 UTC | 20h 35m |
| 2026-05-16 | OYO2 | - | May 16, 10:05 UTC | May 16, 12:21 UTC | 2h 15m |
| 2026-05-11 | OYO2 | - | May 11, 19:05 UTC | May 11, 19:20 UTC | 15m |
| 2026-05-11 | OYO2 | - | May 11, 16:30 UTC | May 11, 17:45 UTC | 1h 15m |
| 2026-05-11 | OYO2 | - | May 11, 13:05 UTC | May 11, 14:25 UTC | 1h 20m |
| 2026-05-11 | OYO2 | GNB → FNI | May 11, 10:05 UTC | May 11, 10:35 UTC | 30m |
| 2026-05-08 | OYO2 | - | May 8, 07:44 UTC | May 8, 09:04 UTC | 1h 20m |
| 2026-05-08 | OYO2 | - | May 8, 06:20 UTC | May 8, 06:54 UTC | 35m |
| 2026-05-04 | OYO2 | - | May 4, 18:15 UTC | May 4, 19:00 UTC | 46m |
| 2026-05-04 | OYO2 | - | May 4, 15:50 UTC | May 4, 16:40 UTC | 50m |
| 2026-05-04 | OYO2 | - | May 4, 14:05 UTC | May 4, 15:05 UTC | 1h 0m |
| 2026-05-04 | OYO2 | - | May 4, 08:10 UTC | May 4, 09:10 UTC | 1h 0m |
| 2026-05-04 | OYO2 | BRU → LBG | May 4, 06:30 UTC | May 4, 07:20 UTC | 50m |
| 2026-05-04 | OYO2 | - | May 4, 05:05 UTC | May 4, 05:45 UTC | 40m |
| 2026-05-01 | OYO2 | SVQ → LBG | May 1, 12:15 UTC | May 1, 14:30 UTC | 2h 15m |
| 2026-05-01 | OYO2 | - | May 1, 09:20 UTC | May 1, 11:15 UTC | 1h 55m |
| 2026-04-30 | OYO2 | - | Apr 30, 14:10 UTC | Apr 30, 15:00 UTC | 50m |
| 2026-04-30 | OYO2 | - | Apr 30, 10:20 UTC | Apr 30, 13:15 UTC | 2h 55m |
| 2026-04-29 | OYO2 | - | Apr 29, 19:25 UTC | Apr 29, 20:10 UTC | 45m |
| 2026-04-29 | OYO2 | - | Apr 29, 16:20 UTC | Apr 29, 16:40 UTC | 20m |
| 2026-04-29 | OYO2 | - | Apr 29, 07:20 UTC | Apr 29, 15:40 UTC | 8h 21m |
| 2026-04-29 | OYO2 | - | Apr 29, 05:15 UTC | Apr 29, 06:29 UTC | 1h 15m |
| 2026-04-28 | OYO2 | - | Apr 28, 12:40 UTC | Apr 28, 14:55 UTC | 2h 15m |
| 2026-04-28 | OYO2 | - | Apr 28, 06:10 UTC | Apr 28, 08:15 UTC | 2h 5m |
| 2026-04-24 | OYO2 | - | Apr 24, 14:05 UTC | Apr 24, 15:25 UTC | 1h 20m |
| 2026-04-24 | OYO2 | LYN → NCE | Apr 24, 11:50 UTC | Apr 24, 12:40 UTC | 50m |
| 2026-04-24 | OYO2 | - | Apr 24, 09:00 UTC | Apr 24, 11:10 UTC | 2h 10m |
| 2026-04-24 | OYO2 | - | Apr 24, 06:00 UTC | Apr 24, 07:50 UTC | 1h 50m |
| 2026-04-23 | OYO2 | BEG → LBG | Apr 23, 07:01 UTC | Apr 23, 09:20 UTC | 2h 20m |
| 2026-04-22 | OYO2 | - | Apr 22, 12:05 UTC | Apr 22, 14:25 UTC | 2h 20m |
| 2026-04-20 | OYO2 | - | Apr 20, 13:35 UTC | Apr 20, 13:55 UTC | 20m |
| 2026-04-20 | OYO2 | - | Apr 20, 10:20 UTC | Apr 20, 12:50 UTC | 2h 31m |
| 2026-04-20 | OYO2 | - | Apr 20, 07:30 UTC | Apr 20, 09:30 UTC | 2h 0m |
| 2026-04-19 | OYO2 | - | Apr 19, 10:35 UTC | Apr 19, 12:50 UTC | 2h 15m |
| 2026-04-19 | OYO2 | LBG → TNG | Apr 19, 07:05 UTC | Apr 19, 09:45 UTC | 2h 40m |
| 2026-04-18 | OYO2 | - | Apr 18, 07:20 UTC | Apr 18, 08:30 UTC | 1h 10m |
| 2026-04-18 | OYO2 | - | Apr 18, 05:25 UTC | Apr 18, 06:30 UTC | 1h 5m |
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 F-HROG page for operator, model, and routing details .