sensors Mode-S transponder
A32AF8
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N303FD · AGUSTA AW-139 · operated by LOS ANGELES CITY, C/O PURCHASING AGENT
- Hex
- A32AF8
- Octal
- 50625370
- Decimal
- 10,693,368
- Country
- US
- Tail
- N303FD
- Type
- A139
- Flights observed
- 70
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 19:35 UTC
Last known position
Country allocation
The ICAO 24-bit address A32AF8 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FIRE3 | - | 70 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FIRE3 | - | Jul 26, 18:15 UTC | Jul 26, 19:35 UTC | 1h 20m |
| 2026-07-26 | FIRE3 | VNY → VNY | Jul 26, 09:05 UTC | Jul 26, 09:25 UTC | 20m |
| 2026-07-22 | FIRE3 | - | Jul 22, 20:10 UTC | Jul 22, 20:40 UTC | 30m |
| 2026-07-22 | FIRE3 | - | Jul 22, 18:15 UTC | Jul 22, 18:35 UTC | 20m |
| 2026-07-21 | FIRE3 | - | Jul 21, 22:25 UTC | Jul 21, 23:00 UTC | 35m |
| 2026-07-21 | FIRE3 | - | Jul 21, 21:00 UTC | Jul 21, 22:15 UTC | 1h 15m |
| 2026-07-16 | FIRE3 | - | Jul 16, 21:25 UTC | Jul 16, 22:05 UTC | 40m |
| 2026-07-11 | FIRE3 | - | Jul 11, 16:50 UTC | Jul 11, 17:55 UTC | 1h 5m |
| 2026-07-11 | FIRE3 | - | Jul 11, 16:10 UTC | Jul 11, 16:30 UTC | 20m |
| 2026-07-10 | FIRE3 | - | Jul 10, 23:05 UTC | Jul 11, 00:15 UTC | 1h 10m |
| 2026-07-08 | FIRE3 | - | Jul 8, 16:50 UTC | Jul 8, 18:00 UTC | 1h 10m |
| 2026-07-08 | FIRE3 | VNY → VNY | Jul 8, 02:35 UTC | Jul 8, 03:50 UTC | 1h 15m |
| 2026-07-06 | FIRE3 | - | Jul 6, 03:55 UTC | Jul 6, 05:10 UTC | 1h 15m |
| 2026-07-05 | FIRE3 | - | Jul 5, 21:00 UTC | Jul 5, 22:15 UTC | 1h 15m |
| 2026-07-05 | FIRE3 | VNY → VNY | Jul 5, 03:55 UTC | Jul 5, 05:10 UTC | 1h 15m |
| 2026-07-04 | FIRE3 | - | Jul 4, 19:05 UTC | Jul 4, 19:55 UTC | 50m |
| 2026-07-04 | FIRE3 | - | Jul 4, 18:25 UTC | Jul 4, 19:00 UTC | 35m |
| 2026-07-01 | FIRE3 | - | Jul 1, 07:30 UTC | Jul 1, 07:55 UTC | 25m |
| 2026-06-30 | FIRE3 | - | Jun 30, 23:10 UTC | Jul 1, 00:10 UTC | 1h 0m |
| 2026-06-24 | FIRE3 | - | Jun 24, 18:15 UTC | Jun 24, 20:40 UTC | 2h 25m |
| 2026-06-18 | FIRE3 | - | Jun 18, 01:25 UTC | Jun 18, 01:35 UTC | 10m |
| 2026-06-17 | FIRE3 | - | Jun 17, 23:05 UTC | Jun 18, 00:45 UTC | 1h 40m |
| 2026-06-16 | FIRE3 | - | Jun 16, 02:15 UTC | Jun 16, 02:40 UTC | 25m |
| 2026-06-14 | FIRE3 | - | Jun 14, 22:20 UTC | Jun 14, 22:30 UTC | 10m |
| 2026-06-14 | FIRE3 | - | Jun 14, 21:20 UTC | Jun 14, 21:25 UTC | 5m |
| 2026-06-09 | FIRE3 | - | Jun 9, 22:30 UTC | Jun 9, 22:55 UTC | 25m |
| 2026-06-07 | FIRE3 | VNY → VNY | Jun 7, 06:10 UTC | Jun 7, 06:40 UTC | 30m |
| 2026-06-05 | FIRE3 | - | Jun 5, 22:50 UTC | Jun 6, 00:00 UTC | 1h 10m |
| 2026-06-05 | FIRE3 | - | Jun 5, 22:25 UTC | Jun 5, 22:30 UTC | 5m |
| 2026-06-01 | FIRE3 | - | Jun 1, 18:20 UTC | Jun 1, 20:00 UTC | 1h 40m |
| 2026-05-30 | FIRE3 | VNY → VNY | May 30, 21:05 UTC | May 30, 22:10 UTC | 1h 5m |
| 2026-05-27 | FIRE3 | VNY → VNY | May 27, 18:50 UTC | May 27, 19:30 UTC | 40m |
| 2026-05-27 | FIRE3 | - | May 27, 18:10 UTC | May 27, 18:15 UTC | 5m |
| 2026-05-27 | FIRE3 | - | May 27, 17:20 UTC | May 27, 18:05 UTC | 45m |
| 2026-05-27 | FIRE3 | - | May 27, 16:25 UTC | May 27, 16:30 UTC | 5m |
| 2026-05-20 | FIRE3 | - | May 20, 22:35 UTC | May 20, 22:50 UTC | 15m |
| 2026-05-20 | FIRE3 | - | May 20, 21:50 UTC | May 20, 22:20 UTC | 30m |
| 2026-05-20 | FIRE3 | - | May 20, 21:00 UTC | May 20, 21:15 UTC | 15m |
| 2026-05-20 | FIRE3 | - | May 20, 04:25 UTC | May 20, 07:00 UTC | 2h 36m |
| 2026-05-19 | FIRE3 | VNY → VNY | May 19, 23:55 UTC | May 20, 04:20 UTC | 4h 25m |
| 2026-05-16 | FIRE3 | - | May 16, 17:30 UTC | May 16, 17:50 UTC | 20m |
| 2026-05-13 | FIRE3 | - | May 13, 22:40 UTC | May 13, 23:10 UTC | 30m |
| 2026-05-11 | FIRE3 | - | May 11, 00:34 UTC | May 11, 00:54 UTC | 20m |
| 2026-05-05 | FIRE3 | - | May 5, 22:25 UTC | May 5, 22:45 UTC | 20m |
| 2026-05-04 | FIRE3 | VNY → VNY | May 4, 03:24 UTC | May 4, 04:39 UTC | 1h 15m |
| 2026-05-03 | FIRE3 | - | May 3, 21:24 UTC | May 3, 22:54 UTC | 1h 30m |
| 2026-05-03 | FIRE3 | - | May 3, 21:10 UTC | May 3, 21:14 UTC | 5m |
| 2026-05-02 | FIRE3 | - | May 2, 23:55 UTC | May 3, 02:10 UTC | 2h 15m |
| 2026-04-26 | FIRE3 | - | Apr 26, 19:30 UTC | Apr 26, 19:40 UTC | 10m |
| 2026-04-26 | FIRE3 | - | Apr 26, 19:00 UTC | Apr 26, 19:20 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 N303FD page for operator, model, and routing details .