sensors Mode-S transponder
3AABFE
ICAO 24-bit transponder address · allocated to France
Currently assigned to 99 · SOCATA TBM-700A/B/C
- Hex
- 3AABFE
- Octal
- 16525776
- Decimal
- 3,845,118
- Country
- FR
- Tail
- 99
- Type
- TBM7
- Flights observed
- 65
- Distinct callsigns
- 7
- Country
- FR
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 3AABFE 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-26 | FMY8048 | - | May 26, 11:00 UTC | May 26, 11:44 UTC | 45m |
| 2026-05-26 | FMY8048 | RNS → VIY | May 26, 09:19 UTC | May 26, 10:10 UTC | 50m |
| 2026-05-19 | FMY8041 | - | May 19, 18:10 UTC | May 19, 18:40 UTC | 30m |
| 2026-05-19 | FMY8041 | - | May 19, 15:05 UTC | May 19, 17:30 UTC | 2h 25m |
| 2026-05-19 | FMY8041 | - | May 19, 13:10 UTC | May 19, 14:15 UTC | 1h 5m |
| 2026-05-19 | FMY8041 | - | May 19, 11:40 UTC | May 19, 12:20 UTC | 40m |
| 2026-05-18 | FMY8043 | - | May 18, 14:20 UTC | May 18, 15:05 UTC | 45m |
| 2026-05-18 | FMY8043 | - | May 18, 12:55 UTC | May 18, 13:55 UTC | 1h 0m |
| 2026-05-18 | FMY8043 | - | May 18, 10:45 UTC | May 18, 12:10 UTC | 1h 25m |
| 2026-05-16 | FMY8050 | RKE → RNS | May 16, 07:41 UTC | May 16, 10:35 UTC | 2h 55m |
| 2026-05-16 | FMY8050 | TLL → RKE | May 16, 04:55 UTC | May 16, 06:50 UTC | 1h 56m |
| 2026-05-15 | FMY8050 | - | May 15, 12:30 UTC | May 15, 12:55 UTC | 25m |
| 2026-05-15 | FMY8050 | - | May 15, 05:35 UTC | May 15, 06:00 UTC | 25m |
| 2026-05-14 | FMY8050 | - | May 14, 12:10 UTC | May 14, 14:01 UTC | 1h 50m |
| 2026-05-14 | FMY8050 | - | May 14, 08:50 UTC | May 14, 11:05 UTC | 2h 15m |
| 2026-05-14 | FMY8050 | RNS → VIY | May 14, 07:00 UTC | May 14, 08:00 UTC | 1h 0m |
| 2026-05-12 | FMY8030 | - | May 12, 18:45 UTC | May 12, 19:45 UTC | 1h 0m |
| 2026-05-12 | FMY8030 | - | May 12, 14:15 UTC | May 12, 16:00 UTC | 1h 45m |
| 2026-05-12 | FMY8030 | RNS → FNI | May 12, 11:30 UTC | May 12, 13:15 UTC | 1h 45m |
| 2026-05-09 | FMY8043 | - | May 9, 13:00 UTC | May 9, 14:10 UTC | 1h 10m |
| 2026-05-09 | FMY8043 | - | May 9, 10:40 UTC | May 9, 12:25 UTC | 1h 45m |
| 2026-05-09 | FMY8043 | - | May 9, 08:25 UTC | May 9, 09:20 UTC | 55m |
| 2026-05-08 | FMY8043 | - | May 8, 11:34 UTC | May 9, 09:20 UTC | 21h 45m |
| 2026-05-08 | FMY8043 | SVQ → SVQ | May 8, 10:25 UTC | May 9, 09:20 UTC | 22h 55m |
| 2026-05-08 | FMY8043 | - | May 8, 07:29 UTC | May 8, 09:30 UTC | 2h 0m |
| 2026-05-07 | FMY8043 | - | May 7, 17:05 UTC | May 7, 18:20 UTC | 1h 15m |
| 2026-05-07 | FMY8043 | - | May 7, 15:15 UTC | May 7, 16:30 UTC | 1h 15m |
| 2026-05-07 | FMY8055 | - | May 7, 13:20 UTC | May 7, 14:30 UTC | 1h 10m |
| 2026-05-07 | FMY8055 | - | May 7, 09:25 UTC | May 7, 11:35 UTC | 2h 10m |
| 2026-05-06 | FMY8055 | - | May 6, 13:30 UTC | May 6, 14:40 UTC | 1h 10m |
| 2026-05-06 | FMY8055 | - | May 6, 10:30 UTC | May 6, 12:45 UTC | 2h 15m |
| 2026-05-06 | FMY8055 | - | May 6, 08:35 UTC | May 6, 09:55 UTC | 1h 20m |
| 2026-05-04 | FMY8055 | - | May 4, 12:00 UTC | May 4, 13:25 UTC | 1h 25m |
| 2026-05-04 | FMY8055 | - | May 4, 09:40 UTC | May 4, 11:05 UTC | 1h 25m |
| 2026-05-04 | FMY8055 | RNS → ANE | May 4, 08:40 UTC | May 4, 09:05 UTC | 25m |
| 2026-04-30 | FMY8050 | - | Apr 30, 08:35 UTC | Apr 30, 09:45 UTC | 1h 10m |
| 2026-04-30 | FMY8050 | - | Apr 30, 07:20 UTC | Apr 30, 07:45 UTC | 25m |
| 2026-04-30 | FMY8050 | RNS → VIY | Apr 30, 05:25 UTC | Apr 30, 06:15 UTC | 50m |
| 2026-04-23 | FMY8051 | - | Apr 23, 18:00 UTC | Apr 23, 19:25 UTC | 1h 25m |
| 2026-04-23 | FMY8051 | - | Apr 23, 15:50 UTC | Apr 23, 17:10 UTC | 1h 20m |
| 2026-04-23 | FMY8051 | - | Apr 23, 13:50 UTC | Apr 23, 15:00 UTC | 1h 10m |
| 2026-04-21 | FMY8051 | - | Apr 21, 12:05 UTC | Apr 21, 12:40 UTC | 35m |
| 2026-04-20 | FMY8051 | - | Apr 20, 17:35 UTC | Apr 20, 19:15 UTC | 1h 40m |
| 2026-04-20 | FMY8051 | SXB → VIE | Apr 20, 15:20 UTC | Apr 20, 16:40 UTC | 1h 20m |
| 2026-04-20 | FMY8051 | - | Apr 20, 13:10 UTC | Apr 20, 14:30 UTC | 1h 20m |
| 2026-04-17 | FMY8030 | - | Apr 17, 15:20 UTC | Apr 17, 16:00 UTC | 40m |
| 2026-04-17 | FMY8030 | - | Apr 17, 14:30 UTC | Apr 17, 15:15 UTC | 45m |
| 2026-04-17 | FMY8030 | - | Apr 17, 13:20 UTC | Apr 17, 13:50 UTC | 30m |
| 2026-04-17 | FMY8030 | - | Apr 17, 11:20 UTC | Apr 17, 12:15 UTC | 55m |
| 2026-04-17 | FMY8030 | - | Apr 17, 11:05 UTC | Apr 17, 11:15 UTC | 10m |
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 99 page for operator, model, and routing details .