sensors Mode-S transponder
0AC33D
ICAO 24-bit transponder address · allocated to Costa Rica
Currently assigned to FAC5059 · CESSNA 208 Caravan
- Hex
- 0AC33D
- Octal
- 02541475
- Decimal
- 705,341
- Country
- CR
- Tail
- FAC5059
- Type
- C208
- Flights observed
- 54
- Distinct callsigns
- 4
- Country
- CR
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 0AC33D falls within the block assigned to Costa Rica (CR) by ICAO Annex 10, Volume III. Every aircraft registered in Costa Rica 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | FAC5059 | - | Jul 15, 23:05 UTC | Jul 15, 23:30 UTC | 25m |
| 2026-07-11 | FAC5059 | - | Jul 11, 19:45 UTC | Jul 11, 20:25 UTC | 40m |
| 2026-07-11 | FAC5059 | - | Jul 11, 15:50 UTC | Jul 11, 16:35 UTC | 45m |
| 2026-07-09 | FAC5059 | LET → LET | Jul 9, 23:25 UTC | Jul 10, 01:05 UTC | 1h 40m |
| 2026-07-08 | FAC5059 | - | Jul 8, 16:50 UTC | Jul 8, 17:35 UTC | 45m |
| 2026-07-08 | FAC5059 | - | Jul 8, 13:50 UTC | Jul 8, 14:35 UTC | 45m |
| 2026-07-07 | FAC5059 | LET → LET | Jul 7, 14:10 UTC | Jul 7, 14:15 UTC | 5m |
| 2026-07-07 | FAC5059 | LET → LET | Jul 7, 13:50 UTC | Jul 7, 14:05 UTC | 15m |
| 2026-07-07 | FAC5059 | LET → LET | Jul 7, 13:30 UTC | Jul 7, 13:35 UTC | 5m |
| 2026-07-06 | FAC5059 | LET → LET | Jul 6, 21:35 UTC | Jul 6, 21:40 UTC | 5m |
| 2026-07-06 | FAC5059 | LET → LET | Jul 6, 21:20 UTC | Jul 6, 21:25 UTC | 5m |
| 2026-07-06 | FAC5059 | LET → LET | Jul 6, 21:05 UTC | Jul 6, 21:10 UTC | 5m |
| 2026-06-29 | FAC5059 | - | Jun 29, 18:10 UTC | Jun 29, 19:00 UTC | 50m |
| 2026-06-22 | FAC5059 | - | Jun 22, 14:10 UTC | Jun 22, 14:55 UTC | 45m |
| 2026-06-21 | FAC5059 | - | Jun 21, 18:50 UTC | Jun 21, 19:39 UTC | 50m |
| 2026-06-21 | FAC5059 | - | Jun 21, 15:05 UTC | Jun 21, 15:54 UTC | 50m |
| 2026-06-20 | FAC5059 | LET → LET | Jun 20, 14:35 UTC | Jun 20, 14:39 UTC | 5m |
| 2026-06-20 | FAC5059 | LET → LET | Jun 20, 13:59 UTC | Jun 20, 14:09 UTC | 10m |
| 2026-06-18 | FAC5059 | - | Jun 18, 16:05 UTC | Jun 18, 16:20 UTC | 15m |
| 2026-06-18 | FAC5059 | - | Jun 18, 13:30 UTC | Jun 18, 14:01 UTC | 30m |
| 2026-06-17 | FAC5059 | - | Jun 17, 17:45 UTC | Jun 17, 18:30 UTC | 45m |
| 2026-06-17 | FAC5059 | - | Jun 17, 14:40 UTC | Jun 17, 14:55 UTC | 15m |
| 2026-06-14 | FAC5059 | - | Jun 14, 21:50 UTC | Jun 14, 22:20 UTC | 30m |
| 2026-06-14 | FAC5059 | - | Jun 14, 19:45 UTC | Jun 14, 20:00 UTC | 15m |
| 2026-06-11 | FAC5059 | LET → LET | Jun 11, 15:15 UTC | Jun 11, 15:25 UTC | 10m |
| 2026-06-03 | FAC5059 | - | Jun 3, 23:55 UTC | Jun 4, 00:00 UTC | 5m |
| 2026-06-03 | FAC5059 | - | Jun 3, 22:50 UTC | Jun 3, 23:15 UTC | 25m |
| 2026-06-02 | FAC5059 | - | Jun 2, 21:50 UTC | Jun 2, 22:05 UTC | 15m |
| 2026-06-02 | FAC5059 | - | Jun 2, 20:05 UTC | Jun 2, 20:20 UTC | 15m |
| 2026-05-31 | FAC5059 | - | May 31, 19:30 UTC | May 31, 20:20 UTC | 50m |
| 2026-05-31 | FAC5059 | - | May 31, 15:50 UTC | May 31, 16:25 UTC | 35m |
| 2026-05-26 | FAC5059 | - | May 26, 23:35 UTC | May 26, 23:49 UTC | 15m |
| 2026-05-26 | FAC5059 | - | May 26, 22:50 UTC | May 26, 22:59 UTC | 10m |
| 2026-05-25 | FAC5059 | - | May 25, 20:24 UTC | May 25, 21:24 UTC | 1h 0m |
| 2026-05-25 | FAC5059 | - | May 25, 18:35 UTC | May 25, 19:10 UTC | 35m |
| 2026-05-16 | FAC5059 | - | May 16, 18:20 UTC | May 16, 19:10 UTC | 50m |
| 2026-05-16 | FAC5059 | - | May 16, 15:01 UTC | May 16, 15:55 UTC | 55m |
| 2026-05-14 | MACA | - | May 14, 19:55 UTC | May 14, 20:50 UTC | 55m |
| 2026-05-09 | ICTUS | LET → LET | May 9, 23:30 UTC | May 10, 00:00 UTC | 30m |
| 2026-05-07 | ICTUS | - | May 7, 19:15 UTC | May 7, 20:00 UTC | 45m |
| 2026-05-07 | ICTUS | - | May 7, 15:25 UTC | May 7, 16:00 UTC | 35m |
| 2026-04-28 | ICTUS | - | Apr 28, 22:00 UTC | Apr 28, 22:30 UTC | 30m |
| 2026-04-28 | ICTUS | - | Apr 28, 19:20 UTC | Apr 28, 19:45 UTC | 25m |
| 2026-04-27 | FIGHTER | LET → LET | Apr 27, 14:20 UTC | Apr 27, 14:25 UTC | 5m |
| 2026-04-27 | FIGHTER | LET → LET | Apr 27, 13:30 UTC | Apr 27, 13:50 UTC | 20m |
| 2026-04-26 | FIGHTER | LET → LET | Apr 26, 13:25 UTC | Apr 26, 14:10 UTC | 45m |
| 2026-04-25 | FIGHTER | LET → LET | Apr 25, 22:50 UTC | Apr 25, 23:50 UTC | 1h 0m |
| 2026-04-25 | FIGHTER | - | Apr 25, 20:55 UTC | Apr 25, 21:00 UTC | 5m |
| 2026-04-25 | FIGHTER | - | Apr 25, 19:10 UTC | Apr 25, 19:20 UTC | 10m |
| 2026-04-19 | ICTUS | - | Apr 19, 16:25 UTC | Apr 19, 17:00 UTC | 35m |
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 FAC5059 page for operator, model, and routing details .