sensors Mode-S transponder
06CF01
ICAO 24-bit transponder address · allocated to Central African Republic
Currently assigned to TL-AIT · AIRBUS A-300-200
- Hex
- 06CF01
- Octal
- 01547401
- Decimal
- 446,209
- Country
- CF
- Tail
- TL-AIT
- Type
- A30B
- Flights observed
- 47
- Distinct callsigns
- 5
- Country
- CF
- Last broadcast
- 17d ago
Last known position
Country allocation
The ICAO 24-bit address 06CF01 falls within the block assigned to Central African Republic (CF) by ICAO Annex 10, Volume III. Every aircraft registered in Central African Republic 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 5 distinct
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-20 | IVC3002 | - | May 20, 02:45 UTC | May 20, 03:25 UTC | 40m |
| 2026-05-19 | IVC3001 | - | May 19, 22:10 UTC | May 19, 22:50 UTC | 40m |
| 2026-05-18 | IVC3004 | - | May 18, 02:10 UTC | May 18, 02:50 UTC | 40m |
| 2026-05-17 | IVC3003 | - | May 17, 23:30 UTC | May 18, 00:15 UTC | 45m |
| 2026-05-17 | IVC3003 | DEL → DEL | May 17, 02:40 UTC | May 18, 00:15 UTC | 21h 35m |
| 2026-05-16 | IVC3001 | - | May 16, 23:40 UTC | May 17, 00:15 UTC | 35m |
| 2026-05-15 | IVC3004 | - | May 15, 02:55 UTC | May 15, 03:35 UTC | 40m |
| 2026-05-14 | IVC3003 | - | May 14, 23:10 UTC | May 15, 00:05 UTC | 55m |
| 2026-05-14 | IVC3003 | - | May 14, 03:15 UTC | May 15, 00:05 UTC | 20h 50m |
| 2026-05-13 | IVC3001 | - | May 13, 22:30 UTC | May 13, 23:15 UTC | 45m |
| 2026-05-12 | IVC3004 | - | May 12, 02:45 UTC | May 12, 02:55 UTC | 10m |
| 2026-05-11 | IVC3002 | - | May 11, 02:25 UTC | May 11, 03:00 UTC | 35m |
| 2026-05-10 | IVC3001 | - | May 10, 22:40 UTC | May 10, 23:35 UTC | 55m |
| 2026-05-10 | IVC3001 | DEL → DEL | May 10, 03:20 UTC | May 10, 23:35 UTC | 20h 15m |
| 2026-05-10 | IVC3003 | - | May 10, 00:20 UTC | May 10, 01:00 UTC | 40m |
| 2026-05-09 | IVC3002 | - | May 9, 02:35 UTC | May 10, 01:00 UTC | 22h 25m |
| 2026-05-08 | IVC3001 | - | May 8, 23:25 UTC | May 9, 00:05 UTC | 40m |
| 2026-05-07 | IVC3004 | - | May 7, 02:20 UTC | May 7, 03:00 UTC | 40m |
| 2026-05-06 | IVC3003 | - | May 6, 23:25 UTC | May 7, 00:15 UTC | 50m |
| 2026-05-05 | IVC3002 | - | May 5, 02:10 UTC | May 5, 02:50 UTC | 40m |
| 2026-05-04 | IVC3001 | - | May 4, 23:20 UTC | May 5, 00:00 UTC | 40m |
| 2026-05-02 | IVC3004 | - | May 2, 04:20 UTC | May 2, 05:00 UTC | 40m |
| 2026-05-01 | IVC3003 | - | May 1, 23:40 UTC | May 2, 00:10 UTC | 30m |
| 2026-05-01 | IVC3002 | - | May 1, 02:20 UTC | May 2, 00:10 UTC | 21h 50m |
| 2026-04-30 | IVC3001 | - | Apr 30, 23:30 UTC | May 1, 00:15 UTC | 45m |
| 2026-04-30 | IVC3004 | DEL → DEL | Apr 30, 02:40 UTC | May 1, 00:15 UTC | 21h 35m |
| 2026-04-30 | IVC3003 | - | Apr 30, 00:00 UTC | Apr 30, 00:40 UTC | 40m |
| 2026-04-29 | IVC3002 | DEL → DEL | Apr 29, 02:50 UTC | Apr 30, 00:40 UTC | 21h 50m |
| 2026-04-28 | IVC3001 | - | Apr 28, 23:29 UTC | Apr 29, 00:30 UTC | 1h 0m |
| 2026-04-28 | IVC3001 | DEL → DEL | Apr 28, 02:50 UTC | Apr 29, 00:30 UTC | 21h 40m |
| 2026-04-27 | IVC3003 | - | Apr 27, 23:50 UTC | Apr 28, 00:35 UTC | 45m |
| 2026-04-27 | IVC3003 | - | Apr 27, 03:25 UTC | Apr 28, 00:35 UTC | 21h 10m |
| 2026-04-27 | IVC3001 | - | Apr 27, 00:10 UTC | Apr 27, 00:50 UTC | 40m |
| 2026-04-26 | IVC3001 | - | Apr 26, 04:20 UTC | Apr 27, 00:50 UTC | 20h 30m |
| 2026-04-26 | IVC3001 | - | Apr 26, 03:55 UTC | Apr 27, 00:50 UTC | 20h 55m |
| 2026-04-25 | IVC3003 | - | Apr 25, 23:35 UTC | Apr 26, 00:25 UTC | 50m |
| 2026-04-25 | IVC3003 | - | Apr 25, 04:20 UTC | Apr 26, 00:25 UTC | 20h 5m |
| 2026-04-25 | IVC3001 | - | Apr 25, 00:45 UTC | Apr 25, 01:30 UTC | 45m |
| 2026-04-24 | IVC3001 | - | Apr 24, 05:30 UTC | Apr 25, 01:30 UTC | 20h 0m |
| 2026-04-24 | TLAIT | - | Apr 24, 02:10 UTC | Apr 24, 03:00 UTC | 50m |
| 2026-04-23 | TLAIT | - | Apr 23, 00:05 UTC | Apr 23, 00:40 UTC | 35m |
| 2026-04-22 | TLAIT | - | Apr 22, 18:20 UTC | Apr 22, 19:00 UTC | 40m |
| 2026-04-22 | TLAIT | - | Apr 22, 16:05 UTC | Apr 22, 16:15 UTC | 10m |
| 2026-04-17 | TLAIT | - | Apr 17, 07:40 UTC | Apr 17, 08:00 UTC | 20m |
| 2026-04-15 | TLAIT | - | Apr 15, 21:35 UTC | Apr 15, 22:05 UTC | 30m |
| 2026-04-14 | TLAIT | - | Apr 14, 08:20 UTC | Apr 14, 08:40 UTC | 20m |
| 2026-04-13 | TLAIT | - | Apr 13, 21:15 UTC | Apr 13, 21:35 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 TL-AIT page for operator, model, and routing details .