sensors Mode-S transponder
3AABFA
ICAO 24-bit transponder address · allocated to France
Currently assigned to 156 · SOCATA TBM-700A/B/C
- Hex
- 3AABFA
- Octal
- 16525772
- Decimal
- 3,845,114
- Country
- FR
- Tail
- 156
- Type
- TBM7
- Flights observed
- 57
- Distinct callsigns
- 11
- Country
- FR
- Last broadcast
- 15h ago
Last known position
Country allocation
The ICAO 24-bit address 3AABFA 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
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FMY8046 | RNS → RNS | Jun 2, 13:10 UTC | Jun 2, 13:20 UTC | 10m |
| 2026-06-02 | FMY8046 | RNS → RNS | Jun 2, 12:20 UTC | Jun 2, 13:05 UTC | 45m |
| 2026-06-01 | FMY8050 | - | Jun 1, 17:05 UTC | Jun 1, 18:30 UTC | 1h 25m |
| 2026-06-01 | FMY8050 | - | Jun 1, 15:50 UTC | Jun 1, 16:15 UTC | 25m |
| 2026-06-01 | FMY8050 | - | Jun 1, 13:40 UTC | Jun 1, 14:50 UTC | 1h 10m |
| 2026-06-01 | FMY8049 | - | Jun 1, 09:10 UTC | Jun 1, 10:25 UTC | 1h 15m |
| 2026-06-01 | FMY8049 | - | Jun 1, 07:10 UTC | Jun 1, 08:25 UTC | 1h 15m |
| 2026-06-01 | FMY8049 | - | Jun 1, 05:20 UTC | Jun 1, 05:50 UTC | 30m |
| 2026-05-31 | FMY8049 | - | May 31, 16:25 UTC | May 31, 17:35 UTC | 1h 10m |
| 2026-05-29 | FMY8049 | - | May 29, 15:30 UTC | May 29, 16:30 UTC | 1h 0m |
| 2026-05-29 | FMY8049 | - | May 29, 14:10 UTC | May 29, 15:15 UTC | 1h 5m |
| 2026-05-29 | FMY8049 | - | May 29, 12:45 UTC | May 29, 13:40 UTC | 55m |
| 2026-05-29 | FMY8049 | - | May 29, 10:45 UTC | May 29, 11:45 UTC | 1h 0m |
| 2026-05-28 | FMY8044 | RNS → RNS | May 28, 12:40 UTC | May 28, 13:35 UTC | 55m |
| 2026-05-28 | FMY8051 | ORY → RNS | May 28, 09:50 UTC | May 28, 10:40 UTC | 50m |
| 2026-05-28 | FMY8051 | - | May 28, 06:35 UTC | May 28, 08:35 UTC | 2h 0m |
| 2026-05-27 | FMY8051 | RNS → INN | May 27, 11:15 UTC | May 27, 13:20 UTC | 2h 5m |
| 2026-05-27 | FMY8051 | RNS → RNS | May 27, 07:50 UTC | May 27, 08:55 UTC | 1h 5m |
| 2026-05-26 | FMY8049 | INN → RNS | May 26, 12:54 UTC | May 26, 15:05 UTC | 2h 10m |
| 2026-05-26 | FMY8049 | - | May 26, 10:20 UTC | May 26, 11:54 UTC | 1h 35m |
| 2026-05-26 | FMY8049 | RNS → VIY | May 26, 09:04 UTC | May 26, 09:55 UTC | 50m |
| 2026-05-21 | FMY8048 | RNS → RNS | May 21, 20:30 UTC | May 21, 21:55 UTC | 1h 25m |
| 2026-05-21 | FMY8051 | - | May 21, 09:55 UTC | May 21, 11:40 UTC | 1h 45m |
| 2026-05-21 | FMY8051 | - | May 21, 08:05 UTC | May 21, 09:05 UTC | 1h 0m |
| 2026-05-21 | FMY8051 | - | May 21, 05:15 UTC | May 21, 06:55 UTC | 1h 40m |
| 2026-05-20 | FMY8043 | - | May 20, 13:35 UTC | May 20, 14:20 UTC | 45m |
| 2026-05-20 | FMY8043 | - | May 20, 12:05 UTC | May 20, 12:50 UTC | 45m |
| 2026-05-20 | FMY8043 | - | May 20, 09:25 UTC | May 20, 10:25 UTC | 1h 0m |
| 2026-05-19 | FMY8055 | - | May 19, 08:15 UTC | May 19, 09:40 UTC | 1h 25m |
| 2026-05-19 | FMY8055 | RNS → BRU | May 19, 05:40 UTC | May 19, 07:00 UTC | 1h 20m |
| 2026-05-18 | FMY8041 | - | May 18, 07:10 UTC | May 18, 08:45 UTC | 1h 35m |
| 2026-05-18 | FMY8041 | - | May 18, 05:30 UTC | May 18, 06:25 UTC | 55m |
| 2026-05-18 | FMY8041 | RNS → VIY | May 18, 03:45 UTC | May 18, 04:40 UTC | 55m |
| 2026-04-30 | FMY8035 | - | Apr 30, 16:35 UTC | Apr 30, 18:35 UTC | 2h 0m |
| 2026-04-30 | FMY8035 | - | Apr 30, 14:40 UTC | Apr 30, 15:50 UTC | 1h 10m |
| 2026-04-30 | FMY8030 | RNS → RNS | Apr 30, 08:00 UTC | Apr 30, 09:05 UTC | 1h 5m |
| 2026-04-29 | FMY8041 | - | Apr 29, 08:40 UTC | Apr 29, 10:40 UTC | 2h 1m |
| 2026-04-29 | FMY8041 | - | Apr 29, 05:45 UTC | Apr 29, 07:35 UTC | 1h 50m |
| 2026-04-28 | FMY8041 | - | Apr 28, 16:55 UTC | Apr 28, 17:25 UTC | 30m |
| 2026-04-28 | FMY8041 | - | Apr 28, 13:30 UTC | Apr 28, 14:55 UTC | 1h 25m |
| 2026-04-28 | FMY8041 | RNS → LDE | Apr 28, 11:10 UTC | Apr 28, 12:50 UTC | 1h 40m |
| 2026-04-28 | FMY8044 | RNS → RNS | Apr 28, 07:15 UTC | Apr 28, 08:15 UTC | 1h 0m |
| 2026-04-23 | FMY8055 | - | Apr 23, 08:01 UTC | Apr 23, 09:15 UTC | 1h 15m |
| 2026-04-23 | FMY8055 | - | Apr 23, 05:20 UTC | Apr 23, 06:25 UTC | 1h 5m |
| 2026-04-22 | FMY8055 | - | Apr 22, 16:25 UTC | Apr 22, 17:05 UTC | 40m |
| 2026-04-22 | FMY8055 | - | Apr 22, 15:15 UTC | Apr 22, 15:45 UTC | 30m |
| 2026-04-21 | FMY8055 | - | Apr 21, 09:40 UTC | Apr 21, 10:40 UTC | 1h 0m |
| 2026-04-21 | FMY8055 | - | Apr 21, 08:30 UTC | Apr 21, 09:05 UTC | 35m |
| 2026-04-21 | FMY8055 | - | Apr 21, 06:45 UTC | Apr 21, 07:35 UTC | 50m |
| 2026-04-21 | FMY8055 | - | Apr 21, 04:30 UTC | Apr 21, 05:30 UTC | 1h 0m |
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 156 page for operator, model, and routing details .