sensors Mode-S transponder
39912E
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-HEJO · CESSNA 510 Citation Mustang
- Hex
- 39912E
- Octal
- 16310456
- Decimal
- 3,772,718
- Country
- FR
- Tail
- F-HEJO
- Type
- C510
- Flights observed
- 71
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 39912E 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 |
|---|---|---|---|
| OYO12 | - | 71 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | OYO12 | - | Jun 17, 13:55 UTC | Jun 17, 14:55 UTC | 1h 0m |
| 2026-06-17 | OYO12 | - | Jun 17, 06:00 UTC | Jun 17, 06:55 UTC | 55m |
| 2026-06-16 | OYO12 | - | Jun 16, 10:04 UTC | Jun 16, 10:35 UTC | 30m |
| 2026-06-16 | OYO12 | - | Jun 16, 09:04 UTC | Jun 16, 09:30 UTC | 25m |
| 2026-06-16 | OYO12 | - | Jun 16, 05:45 UTC | Jun 16, 06:10 UTC | 25m |
| 2026-06-16 | OYO12 | SXB → DIJ | Jun 16, 04:35 UTC | Jun 16, 05:10 UTC | 35m |
| 2026-06-14 | OYO12 | - | Jun 14, 11:20 UTC | Jun 14, 12:35 UTC | 1h 15m |
| 2026-06-14 | OYO12 | - | Jun 14, 09:55 UTC | Jun 14, 10:30 UTC | 35m |
| 2026-06-14 | OYO12 | LYN → LYN | Jun 14, 09:40 UTC | Jun 14, 09:50 UTC | 10m |
| 2026-06-14 | OYO12 | - | Jun 14, 04:55 UTC | Jun 14, 05:25 UTC | 30m |
| 2026-06-14 | OYO12 | - | Jun 14, 02:45 UTC | Jun 14, 04:00 UTC | 1h 15m |
| 2026-06-11 | OYO12 | - | Jun 11, 20:45 UTC | Jun 11, 22:10 UTC | 1h 25m |
| 2026-06-11 | OYO12 | PGF → BOD | Jun 11, 19:15 UTC | Jun 11, 20:05 UTC | 50m |
| 2026-06-11 | OYO12 | SXB → PGF | Jun 11, 16:00 UTC | Jun 11, 17:25 UTC | 1h 25m |
| 2026-06-07 | OYO12 | - | Jun 7, 07:55 UTC | Jun 7, 08:50 UTC | 55m |
| 2026-06-07 | OYO12 | - | Jun 7, 03:40 UTC | Jun 7, 04:45 UTC | 1h 5m |
| 2026-06-05 | OYO12 | - | Jun 5, 16:40 UTC | Jun 5, 17:40 UTC | 1h 0m |
| 2026-06-05 | OYO12 | - | Jun 5, 15:25 UTC | Jun 5, 15:50 UTC | 25m |
| 2026-06-05 | OYO12 | - | Jun 5, 06:20 UTC | Jun 5, 07:00 UTC | 40m |
| 2026-06-05 | OYO12 | - | Jun 5, 04:20 UTC | Jun 5, 05:20 UTC | 1h 0m |
| 2026-06-04 | OYO12 | - | Jun 4, 12:40 UTC | Jun 4, 13:10 UTC | 30m |
| 2026-06-04 | OYO12 | - | Jun 4, 11:25 UTC | Jun 4, 12:05 UTC | 40m |
| 2026-06-04 | OYO12 | - | Jun 4, 07:55 UTC | Jun 4, 08:50 UTC | 55m |
| 2026-06-04 | OYO12 | - | Jun 4, 06:40 UTC | Jun 4, 07:15 UTC | 35m |
| 2026-06-01 | OYO12 | - | Jun 1, 18:40 UTC | Jun 1, 19:50 UTC | 1h 10m |
| 2026-06-01 | OYO12 | - | Jun 1, 16:40 UTC | Jun 1, 17:45 UTC | 1h 5m |
| 2026-06-01 | OYO12 | - | Jun 1, 12:05 UTC | Jun 1, 13:10 UTC | 1h 5m |
| 2026-06-01 | OYO12 | - | Jun 1, 10:00 UTC | Jun 1, 11:20 UTC | 1h 20m |
| 2026-05-30 | OYO12 | - | May 30, 21:20 UTC | May 30, 23:50 UTC | 2h 30m |
| 2026-05-26 | OYO12 | - | May 26, 15:39 UTC | May 26, 16:05 UTC | 25m |
| 2026-05-26 | OYO12 | - | May 26, 13:10 UTC | May 26, 14:55 UTC | 1h 45m |
| 2026-05-24 | OYO12 | - | May 24, 15:25 UTC | May 24, 16:55 UTC | 1h 30m |
| 2026-05-24 | OYO12 | - | May 24, 14:20 UTC | May 24, 15:10 UTC | 50m |
| 2026-05-24 | OYO12 | - | May 24, 08:20 UTC | May 24, 09:15 UTC | 55m |
| 2026-05-24 | OYO12 | - | May 24, 06:40 UTC | May 24, 07:50 UTC | 1h 10m |
| 2026-05-23 | OYO12 | - | May 23, 09:15 UTC | May 23, 10:05 UTC | 50m |
| 2026-05-23 | OYO12 | - | May 23, 07:30 UTC | May 23, 08:25 UTC | 55m |
| 2026-05-22 | OYO12 | - | May 22, 23:00 UTC | May 23, 00:05 UTC | 1h 5m |
| 2026-05-22 | OYO12 | - | May 22, 21:30 UTC | May 22, 22:20 UTC | 50m |
| 2026-05-19 | OYO12 | - | May 19, 05:45 UTC | May 19, 06:55 UTC | 1h 10m |
| 2026-05-19 | OYO12 | - | May 19, 04:00 UTC | May 19, 04:55 UTC | 55m |
| 2026-05-19 | OYO12 | - | May 19, 00:15 UTC | May 19, 01:10 UTC | 55m |
| 2026-05-18 | OYO12 | - | May 18, 22:15 UTC | May 18, 23:20 UTC | 1h 5m |
| 2026-05-16 | OYO12 | - | May 16, 04:15 UTC | May 16, 05:00 UTC | 45m |
| 2026-05-16 | OYO12 | - | May 16, 00:20 UTC | May 16, 00:55 UTC | 35m |
| 2026-05-14 | OYO12 | - | May 14, 20:10 UTC | May 14, 21:35 UTC | 1h 25m |
| 2026-05-14 | OYO12 | TLS → TLS | May 14, 19:55 UTC | May 14, 20:00 UTC | 5m |
| 2026-05-14 | OYO12 | - | May 14, 18:30 UTC | May 14, 19:35 UTC | 1h 5m |
| 2026-05-14 | OYO12 | - | May 14, 13:20 UTC | May 14, 14:10 UTC | 50m |
| 2026-05-14 | OYO12 | TLS → TLS | May 14, 13:05 UTC | May 14, 13:10 UTC | 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-HEJO page for operator, model, and routing details .