sensors Mode-S transponder
A4108B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N361FL · CONVAIR Convairliner · operated by GULF & CARIBBEAN CARGO INC
- Hex
- A4108B
- Octal
- 51010213
- Decimal
- 10,752,139
- Country
- US
- Tail
- N361FL
- Type
- CVLP
- Flights observed
- 42
- Distinct callsigns
- 7
- Country
- US
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address A4108B falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TSU361 | Gulf & Caribbean Cargo / Contract Air Cargo | 16 | 2026-06-03 |
| CAY909 | Cayman Airways | 9 | 2026-06-25 |
| CAY908 | Cayman Airways | 9 | 2026-06-25 |
| CAY2909 | Cayman Airways | 3 | 2026-06-26 |
| CAY2908 | Cayman Airways | 3 | 2026-06-26 |
| TSU802 | Gulf & Caribbean Cargo / Contract Air Cargo | 1 | 2026-06-03 |
| TSU801 | Gulf & Caribbean Cargo / Contract Air Cargo | 1 | 2026-06-03 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-26 | CAY2908 | GCM → MIA | Jun 26, 17:29 UTC | Jun 26, 17:59 UTC | 30m |
| 2026-06-26 | CAY2909 | MIA → GCM | Jun 26, 13:45 UTC | Jun 26, 14:09 UTC | 25m |
| 2026-06-25 | CAY908 | GCM → MIA | Jun 25, 17:34 UTC | Jun 25, 18:04 UTC | 30m |
| 2026-06-25 | CAY909 | MIA → GCM | Jun 25, 14:04 UTC | Jun 25, 14:29 UTC | 25m |
| 2026-06-23 | CAY908 | GCM → MIA | Jun 23, 17:39 UTC | Jun 23, 18:14 UTC | 35m |
| 2026-06-23 | CAY909 | MIA → GCM | Jun 23, 13:45 UTC | Jun 23, 14:19 UTC | 35m |
| 2026-06-18 | CAY908 | GCM → MIA | Jun 18, 17:50 UTC | Jun 18, 18:25 UTC | 35m |
| 2026-06-18 | CAY909 | MIA → GCM | Jun 18, 14:01 UTC | Jun 18, 14:25 UTC | 25m |
| 2026-06-16 | CAY908 | GCM → MIA | Jun 16, 19:05 UTC | Jun 16, 19:40 UTC | 35m |
| 2026-06-16 | CAY909 | MIA → GCM | Jun 16, 15:05 UTC | Jun 16, 15:35 UTC | 30m |
| 2026-06-11 | CAY908 | GCM → MIA | Jun 11, 18:15 UTC | Jun 11, 18:50 UTC | 35m |
| 2026-06-11 | CAY909 | MIA → GCM | Jun 11, 14:35 UTC | Jun 11, 15:10 UTC | 35m |
| 2026-06-10 | CAY2908 | GCM → MIA | Jun 10, 17:00 UTC | Jun 10, 17:35 UTC | 35m |
| 2026-06-10 | CAY2909 | MIA → GCM | Jun 10, 13:20 UTC | Jun 10, 13:55 UTC | 35m |
| 2026-06-09 | CAY908 | GCM → MIA | Jun 9, 18:55 UTC | Jun 9, 19:25 UTC | 30m |
| 2026-06-09 | CAY909 | MIA → GCM | Jun 9, 14:15 UTC | Jun 9, 14:50 UTC | 35m |
| 2026-06-04 | CAY908 | GCM → MIA | Jun 4, 18:05 UTC | Jun 4, 18:35 UTC | 30m |
| 2026-06-04 | CAY909 | MIA → GCM | Jun 4, 14:15 UTC | Jun 4, 14:45 UTC | 30m |
| 2026-06-03 | TSU802 | NAS → OPF | Jun 3, 19:10 UTC | Jun 3, 19:35 UTC | 25m |
| 2026-06-03 | TSU801 | OPF → NAS | Jun 3, 16:25 UTC | Jun 3, 16:50 UTC | 25m |
| 2026-06-03 | TSU361 | - | Jun 3, 11:30 UTC | Jun 3, 11:40 UTC | 10m |
| 2026-06-02 | CAY908 | GCM → MIA | Jun 2, 18:00 UTC | Jun 2, 18:25 UTC | 25m |
| 2026-06-02 | CAY909 | MIA → GCM | Jun 2, 14:00 UTC | Jun 2, 14:25 UTC | 25m |
| 2026-05-29 | CAY2908 | GCM → MIA | May 29, 17:20 UTC | May 29, 17:45 UTC | 25m |
| 2026-05-29 | CAY2909 | MIA → GCM | May 29, 13:30 UTC | May 29, 14:00 UTC | 30m |
| 2026-05-28 | CAY908 | GCM → MIA | May 28, 18:00 UTC | May 28, 19:00 UTC | 1h 0m |
| 2026-05-28 | CAY909 | MIA → GCM | May 28, 14:30 UTC | May 28, 14:55 UTC | 25m |
| 2026-05-23 | TSU361 | - | May 23, 00:30 UTC | May 23, 01:30 UTC | 1h 0m |
| 2026-05-22 | TSU361 | - | May 22, 22:10 UTC | May 22, 23:55 UTC | 1h 45m |
| 2026-05-16 | TSU361 | - | May 16, 16:45 UTC | May 16, 22:05 UTC | 5h 20m |
| 2026-05-16 | TSU361 | - | May 16, 12:05 UTC | May 16, 15:31 UTC | 3h 25m |
| 2026-05-16 | TSU361 | - | May 16, 06:06 UTC | May 16, 09:45 UTC | 3h 40m |
| 2026-05-15 | TSU361 | - | May 15, 08:35 UTC | May 15, 10:50 UTC | 2h 15m |
| 2026-05-15 | TSU361 | - | May 15, 04:40 UTC | May 15, 06:50 UTC | 2h 10m |
| 2026-05-14 | TSU361 | - | May 14, 23:25 UTC | May 15, 02:20 UTC | 2h 55m |
| 2026-05-14 | TSU361 | - | May 14, 02:15 UTC | May 14, 05:05 UTC | 2h 50m |
| 2026-05-13 | TSU361 | - | May 13, 20:40 UTC | May 14, 00:40 UTC | 4h 0m |
| 2026-05-12 | TSU361 | - | May 12, 20:15 UTC | May 12, 21:45 UTC | 1h 30m |
| 2026-05-12 | TSU361 | - | May 12, 17:25 UTC | May 12, 17:50 UTC | 25m |
| 2026-05-12 | TSU361 | - | May 12, 17:05 UTC | May 12, 17:20 UTC | 15m |
| 2026-05-11 | TSU361 | - | May 11, 15:00 UTC | May 11, 15:45 UTC | 45m |
| 2026-05-09 | TSU361 | - | May 9, 11:35 UTC | May 9, 12:00 UTC | 25m |
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 N361FL page for operator, model, and routing details .