sensors Mode-S transponder
3A444F
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-ORCP · TECNAM P-2006T
- Hex
- 3A444F
- Octal
- 16442117
- Decimal
- 3,818,575
- Country
- FR
- Tail
- F-ORCP
- Type
- P06T
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- FR
- Last broadcast
- 18d ago
Last known position
Country allocation
The ICAO 24-bit address 3A444F 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 |
|---|---|---|---|
| FORCP | - | 67 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | FORCP | - | Jun 30, 01:35 UTC | Jun 30, 03:00 UTC | 1h 25m |
| 2026-06-26 | FORCP | PPT → PPT | Jun 26, 00:50 UTC | Jun 26, 01:54 UTC | 1h 5m |
| 2026-06-18 | FORCP | - | Jun 18, 23:00 UTC | Jun 18, 23:45 UTC | 45m |
| 2026-06-18 | FORCP | - | Jun 18, 20:40 UTC | Jun 18, 21:10 UTC | 30m |
| 2026-06-18 | FORCP | - | Jun 18, 18:55 UTC | Jun 18, 19:45 UTC | 50m |
| 2026-06-17 | FORCP | - | Jun 17, 00:25 UTC | Jun 17, 01:35 UTC | 1h 10m |
| 2026-06-08 | FORCP | - | Jun 8, 23:20 UTC | Jun 9, 00:10 UTC | 50m |
| 2026-06-08 | FORCP | - | Jun 8, 21:00 UTC | Jun 8, 21:55 UTC | 55m |
| 2026-06-07 | FORCP | - | Jun 7, 03:25 UTC | Jun 7, 04:10 UTC | 45m |
| 2026-06-07 | FORCP | - | Jun 7, 01:24 UTC | Jun 7, 02:00 UTC | 35m |
| 2026-06-04 | FORCP | - | Jun 4, 21:15 UTC | Jun 4, 22:30 UTC | 1h 15m |
| 2026-06-04 | FORCP | - | Jun 4, 18:45 UTC | Jun 4, 19:50 UTC | 1h 5m |
| 2026-06-03 | FORCP | - | Jun 3, 20:20 UTC | Jun 3, 21:45 UTC | 1h 25m |
| 2026-05-31 | FORCP | - | May 31, 21:00 UTC | May 31, 21:50 UTC | 50m |
| 2026-05-31 | FORCP | - | May 31, 19:10 UTC | May 31, 19:35 UTC | 25m |
| 2026-05-29 | FORCP | - | May 29, 21:10 UTC | May 29, 22:15 UTC | 1h 5m |
| 2026-05-27 | FORCP | PPT → PPT | May 27, 23:05 UTC | May 27, 23:55 UTC | 50m |
| 2026-05-27 | FORCP | - | May 27, 20:40 UTC | May 27, 21:50 UTC | 1h 10m |
| 2026-05-27 | FORCP | - | May 27, 17:35 UTC | May 27, 18:40 UTC | 1h 5m |
| 2026-05-26 | FORCP | - | May 26, 22:15 UTC | May 26, 23:25 UTC | 1h 10m |
| 2026-05-26 | FORCP | - | May 26, 18:55 UTC | May 26, 20:20 UTC | 1h 25m |
| 2026-05-26 | FORCP | - | May 26, 01:00 UTC | May 26, 02:04 UTC | 1h 5m |
| 2026-05-25 | FORCP | - | May 25, 23:00 UTC | May 26, 00:00 UTC | 1h 0m |
| 2026-05-25 | FORCP | - | May 25, 20:45 UTC | May 25, 21:45 UTC | 1h 0m |
| 2026-05-23 | FORCP | - | May 23, 01:35 UTC | May 23, 02:20 UTC | 45m |
| 2026-05-22 | FORCP | - | May 22, 23:40 UTC | May 23, 00:50 UTC | 1h 10m |
| 2026-05-22 | FORCP | - | May 22, 20:25 UTC | May 22, 21:50 UTC | 1h 25m |
| 2026-05-22 | FORCP | - | May 22, 18:25 UTC | May 22, 19:25 UTC | 1h 0m |
| 2026-05-22 | FORCP | - | May 22, 00:20 UTC | May 22, 01:10 UTC | 50m |
| 2026-05-21 | FORCP | - | May 21, 22:30 UTC | May 21, 23:20 UTC | 50m |
| 2026-05-21 | FORCP | - | May 21, 20:45 UTC | May 21, 21:30 UTC | 45m |
| 2026-05-21 | FORCP | - | May 21, 19:00 UTC | May 21, 19:50 UTC | 50m |
| 2026-05-04 | FORCP | - | May 4, 20:50 UTC | May 4, 21:40 UTC | 50m |
| 2026-05-01 | FORCP | - | May 1, 01:20 UTC | May 1, 02:40 UTC | 1h 20m |
| 2026-04-30 | FORCP | - | Apr 30, 20:45 UTC | Apr 30, 21:00 UTC | 15m |
| 2026-04-30 | FORCP | - | Apr 30, 03:10 UTC | Apr 30, 04:05 UTC | 55m |
| 2026-04-29 | FORCP | - | Apr 29, 23:10 UTC | Apr 29, 23:25 UTC | 15m |
| 2026-04-29 | FORCP | PPT → PPT | Apr 29, 21:20 UTC | Apr 29, 21:35 UTC | 15m |
| 2026-04-29 | FORCP | - | Apr 29, 02:50 UTC | Apr 29, 04:15 UTC | 1h 25m |
| 2026-04-28 | FORCP | - | Apr 28, 22:55 UTC | Apr 28, 23:54 UTC | 1h 0m |
| 2026-04-28 | FORCP | - | Apr 28, 17:05 UTC | Apr 28, 17:25 UTC | 20m |
| 2026-04-28 | FORCP | - | Apr 28, 01:30 UTC | Apr 28, 02:00 UTC | 30m |
| 2026-04-27 | FORCP | - | Apr 27, 23:20 UTC | Apr 28, 00:30 UTC | 1h 10m |
| 2026-04-27 | FORCP | - | Apr 27, 21:20 UTC | Apr 27, 21:50 UTC | 30m |
| 2026-04-25 | FORCP | - | Apr 25, 23:45 UTC | Apr 26, 00:45 UTC | 1h 0m |
| 2026-04-24 | FORCP | - | Apr 24, 23:20 UTC | Apr 24, 23:35 UTC | 15m |
| 2026-04-24 | FORCP | - | Apr 24, 21:00 UTC | Apr 24, 21:10 UTC | 10m |
| 2026-04-23 | FORCP | - | Apr 23, 23:10 UTC | Apr 23, 23:55 UTC | 45m |
| 2026-04-23 | FORCP | - | Apr 23, 20:35 UTC | Apr 23, 21:25 UTC | 50m |
| 2026-04-22 | FORCP | - | Apr 22, 23:45 UTC | Apr 23, 00:05 UTC | 20m |
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-ORCP page for operator, model, and routing details .