sensors Mode-S transponder
392AF5
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GKXV · AIRBUS A-320
- Hex
- 392AF5
- Octal
- 16225365
- Decimal
- 3,746,549
- Country
- FR
- Tail
- F-GKXV
- Type
- A320
- Flights observed
- 41
- Distinct callsigns
- 11
- Country
- FR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 392AF5 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFR616 | Air France | 11 | 2026-05-21 |
| AFR617 | Air France | 8 | 2026-05-22 |
| AFR609 | Air France | 5 | 2026-05-12 |
| AFR608 | Air France | 5 | 2026-05-11 |
| AFR601 | Air France | 4 | 2026-04-30 |
| AFR605 | Air France | 2 | 2026-04-18 |
| AFR600 | - | 2 | 2026-04-15 |
| AFR611 | - | 1 | 2026-04-15 |
| AFR604 | Air France | 1 | 2026-04-17 |
| AFR369V | Air France | 1 | 2026-05-28 |
| AFR368V | - | 1 | 2026-05-27 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | AFR369V | PUJ → FDF | May 28, 17:05 UTC | May 28, 18:40 UTC | 1h 35m |
| 2026-05-27 | AFR368V | - | May 27, 14:35 UTC | May 27, 16:40 UTC | 2h 5m |
| 2026-05-22 | AFR617 | MIA → PTP | May 22, 14:20 UTC | May 22, 16:35 UTC | 2h 15m |
| 2026-05-21 | AFR616 | PTP → MIA | May 21, 21:30 UTC | May 22, 00:10 UTC | 2h 40m |
| 2026-05-15 | AFR617 | MIA → PTP | May 15, 14:05 UTC | May 15, 16:30 UTC | 2h 24m |
| 2026-05-14 | AFR616 | PTP → MIA | May 14, 21:25 UTC | May 15, 00:05 UTC | 2h 40m |
| 2026-05-12 | AFR609 | SXM → PTP | May 12, 18:30 UTC | May 12, 18:55 UTC | 25m |
| 2026-05-11 | AFR608 | PTP → SXM | May 11, 17:50 UTC | May 11, 18:25 UTC | 35m |
| 2026-05-08 | AFR617 | MIA → PTP | May 8, 14:05 UTC | May 8, 16:30 UTC | 2h 25m |
| 2026-05-07 | AFR616 | PTP → MIA | May 7, 21:20 UTC | May 7, 23:55 UTC | 2h 34m |
| 2026-05-05 | AFR609 | SXM → PTP | May 5, 20:05 UTC | May 6, 01:20 UTC | 5h 15m |
| 2026-05-04 | AFR608 | PTP → SXM | May 4, 12:55 UTC | May 4, 18:25 UTC | 5h 30m |
| 2026-05-01 | AFR617 | MIA → PTP | May 1, 13:55 UTC | May 2, 00:45 UTC | 10h 50m |
| 2026-05-01 | AFR616 | PTP → MIA | May 1, 00:30 UTC | May 1, 00:50 UTC | 20m |
| 2026-04-30 | AFR616 | PTP → MIA | Apr 30, 22:15 UTC | Apr 30, 22:45 UTC | 30m |
| 2026-04-30 | AFR601 | FDF → PTP | Apr 30, 14:05 UTC | Apr 30, 18:35 UTC | 4h 30m |
| 2026-04-28 | AFR609 | SXM → PTP | Apr 28, 18:40 UTC | Apr 29, 00:34 UTC | 5h 55m |
| 2026-04-27 | AFR608 | PTP → SXM | Apr 27, 12:50 UTC | Apr 27, 18:35 UTC | 5h 45m |
| 2026-04-24 | AFR617 | MIA → PTP | Apr 24, 14:25 UTC | Apr 25, 01:05 UTC | 10h 40m |
| 2026-04-23 | AFR616 | PTP → MIA | Apr 23, 23:50 UTC | Apr 24, 00:15 UTC | 25m |
| 2026-04-23 | AFR616 | PTP → MIA | Apr 23, 21:25 UTC | Apr 23, 22:00 UTC | 35m |
| 2026-04-23 | AFR601 | FDF → PTP | Apr 23, 12:45 UTC | Apr 23, 17:40 UTC | 4h 54m |
| 2026-04-21 | AFR609 | SXM → PTP | Apr 21, 18:25 UTC | Apr 22, 00:30 UTC | 6h 5m |
| 2026-04-20 | AFR608 | PTP → SXM | Apr 20, 12:45 UTC | Apr 20, 18:45 UTC | 6h 0m |
| 2026-04-19 | AFR617 | - | Apr 19, 14:10 UTC | Apr 20, 01:35 UTC | 11h 25m |
| 2026-04-18 | AFR616 | PTP → MIA | Apr 18, 23:40 UTC | Apr 19, 00:00 UTC | 20m |
| 2026-04-18 | AFR616 | PTP → MIA | Apr 18, 21:25 UTC | Apr 18, 21:50 UTC | 25m |
| 2026-04-18 | AFR605 | FDF → PTP | Apr 18, 00:30 UTC | Apr 18, 00:55 UTC | 25m |
| 2026-04-17 | AFR604 | FDF → CAY | Apr 17, 20:20 UTC | Apr 17, 20:40 UTC | 20m |
| 2026-04-17 | AFR617 | - | Apr 17, 16:10 UTC | Apr 17, 16:35 UTC | 25m |
| 2026-04-17 | AFR617 | - | Apr 17, 14:15 UTC | Apr 17, 14:40 UTC | 25m |
| 2026-04-16 | AFR616 | PTP → MIA | Apr 16, 23:20 UTC | Apr 16, 23:40 UTC | 20m |
| 2026-04-16 | AFR616 | PTP → MIA | Apr 16, 21:14 UTC | Apr 16, 23:10 UTC | 1h 55m |
| 2026-04-16 | AFR601 | - | Apr 16, 17:15 UTC | Apr 16, 17:35 UTC | 20m |
| 2026-04-15 | AFR601 | - | Apr 15, 17:20 UTC | Apr 15, 17:50 UTC | 30m |
| 2026-04-15 | AFR600 | - | Apr 15, 12:45 UTC | Apr 15, 12:55 UTC | 10m |
| 2026-04-15 | AFR611 | - | Apr 15, 00:05 UTC | Apr 15, 00:30 UTC | 25m |
| 2026-04-14 | AFR609 | - | Apr 14, 18:30 UTC | Apr 14, 18:45 UTC | 15m |
| 2026-04-13 | AFR608 | - | Apr 13, 18:10 UTC | Apr 13, 18:35 UTC | 25m |
| 2026-04-13 | AFR600 | - | Apr 13, 13:15 UTC | Apr 13, 13:30 UTC | 15m |
| 2026-04-13 | AFR605 | FDF → PTP | Apr 13, 00:25 UTC | Apr 13, 00:55 UTC | 30m |
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-GKXV page for operator, model, and routing details .