sensors Mode-S transponder
A32FAE
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N304RJ · BOMBARDIER BD-100 Challenger 300 · operated by HAYSTACK JMR LLC
- Hex
- A32FAE
- Octal
- 50627656
- Decimal
- 10,694,574
- Country
- US
- Tail
- N304RJ
- Type
- CL30
- Flights observed
- 47
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address A32FAE 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 2 distinct
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | N304RJ | - | Jul 20, 04:00 UTC | Jul 20, 04:20 UTC | 20m |
| 2026-07-20 | N304RJ | - | Jul 20, 02:15 UTC | Jul 20, 03:20 UTC | 1h 5m |
| 2026-07-20 | N304RJ | - | Jul 20, 00:45 UTC | Jul 20, 01:50 UTC | 1h 5m |
| 2026-07-19 | N304RJ | - | Jul 19, 20:15 UTC | Jul 19, 23:55 UTC | 3h 40m |
| 2026-07-16 | N304RJ | - | Jul 16, 17:54 UTC | Jul 16, 21:30 UTC | 3h 35m |
| 2026-07-16 | N304RJ | - | Jul 16, 16:19 UTC | Jul 16, 17:20 UTC | 1h 0m |
| 2026-07-16 | N304RJ | - | Jul 16, 14:40 UTC | Jul 16, 15:40 UTC | 1h 0m |
| 2026-07-14 | N304RJ | - | Jul 14, 22:30 UTC | Jul 15, 00:30 UTC | 1h 59m |
| 2026-07-14 | N304RJ | - | Jul 14, 18:10 UTC | Jul 14, 21:45 UTC | 3h 35m |
| 2026-07-13 | N304RJ | - | Jul 13, 18:50 UTC | Jul 13, 23:00 UTC | 4h 10m |
| 2026-07-13 | N304RJ | - | Jul 13, 17:10 UTC | Jul 13, 17:35 UTC | 25m |
| 2026-07-08 | LFG304 | YVR → CLD | Jul 8, 15:35 UTC | Jul 8, 18:10 UTC | 2h 35m |
| 2026-07-07 | LFG304 | - | Jul 7, 15:10 UTC | Jul 7, 17:35 UTC | 2h 25m |
| 2026-06-29 | LFG304 | - | Jun 29, 01:20 UTC | Jun 29, 01:39 UTC | 20m |
| 2026-06-28 | LFG304 | - | Jun 28, 20:19 UTC | Jun 29, 00:34 UTC | 4h 15m |
| 2026-06-26 | LFG304 | - | Jun 26, 23:39 UTC | Jun 27, 02:39 UTC | 3h 0m |
| 2026-06-26 | LFG304 | - | Jun 26, 21:35 UTC | Jun 26, 22:34 UTC | 1h 0m |
| 2026-06-25 | LFG304 | - | Jun 25, 20:30 UTC | Jun 26, 01:05 UTC | 4h 35m |
| 2026-06-25 | LFG304 | - | Jun 25, 15:34 UTC | Jun 25, 19:15 UTC | 3h 40m |
| 2026-06-25 | LFG304 | CLD → SNA | Jun 25, 14:24 UTC | Jun 25, 14:44 UTC | 20m |
| 2026-06-22 | LFG304 | - | Jun 22, 22:10 UTC | Jun 22, 22:30 UTC | 20m |
| 2026-06-22 | LFG304 | - | Jun 22, 20:34 UTC | Jun 22, 21:35 UTC | 1h 0m |
| 2026-06-22 | LFG304 | - | Jun 22, 01:35 UTC | Jun 22, 02:34 UTC | 1h 0m |
| 2026-06-21 | LFG304 | - | Jun 21, 23:10 UTC | Jun 22, 00:44 UTC | 1h 35m |
| 2026-06-19 | LFG304 | - | Jun 19, 18:44 UTC | Jun 19, 20:19 UTC | 1h 35m |
| 2026-06-19 | LFG304 | - | Jun 19, 15:34 UTC | Jun 19, 17:55 UTC | 2h 20m |
| 2026-06-19 | LFG304 | - | Jun 19, 14:09 UTC | Jun 19, 14:34 UTC | 25m |
| 2026-06-13 | LFG304 | - | Jun 13, 21:00 UTC | Jun 13, 22:30 UTC | 1h 30m |
| 2026-05-18 | LFG304 | - | May 18, 14:30 UTC | May 18, 15:55 UTC | 1h 25m |
| 2026-05-17 | LFG304 | - | May 17, 20:25 UTC | May 18, 02:20 UTC | 5h 55m |
| 2026-05-17 | LFG304 | - | May 17, 18:15 UTC | May 17, 18:45 UTC | 30m |
| 2026-05-12 | LFG304 | - | May 12, 02:45 UTC | May 12, 03:10 UTC | 25m |
| 2026-05-11 | LFG304 | - | May 11, 22:15 UTC | May 11, 22:35 UTC | 19m |
| 2026-05-10 | LFG304 | - | May 10, 19:09 UTC | May 10, 23:25 UTC | 4h 15m |
| 2026-05-08 | LFG304 | - | May 8, 23:35 UTC | May 9, 00:25 UTC | 50m |
| 2026-05-08 | LFG304 | - | May 8, 21:45 UTC | May 8, 22:30 UTC | 45m |
| 2026-05-07 | LFG304 | - | May 7, 18:25 UTC | May 7, 18:45 UTC | 20m |
| 2026-05-07 | LFG304 | - | May 7, 16:25 UTC | May 7, 17:45 UTC | 1h 20m |
| 2026-05-06 | LFG304 | - | May 6, 15:05 UTC | May 6, 16:40 UTC | 1h 35m |
| 2026-05-06 | LFG304 | - | May 6, 14:10 UTC | May 6, 14:30 UTC | 20m |
| 2026-04-29 | LFG304 | - | Apr 29, 17:50 UTC | Apr 29, 23:35 UTC | 5h 44m |
| 2026-04-23 | LFG304 | - | Apr 23, 21:55 UTC | Apr 23, 22:30 UTC | 35m |
| 2026-04-23 | LFG304 | - | Apr 23, 19:40 UTC | Apr 23, 20:50 UTC | 1h 10m |
| 2026-04-23 | LFG304 | - | Apr 23, 16:40 UTC | Apr 23, 18:50 UTC | 2h 9m |
| 2026-04-23 | LFG304 | - | Apr 23, 15:15 UTC | Apr 23, 16:00 UTC | 45m |
| 2026-04-23 | LFG304 | CLD → SNA | Apr 23, 13:55 UTC | Apr 23, 14:25 UTC | 30m |
| 2026-04-13 | LFG304 | - | Apr 13, 00:55 UTC | Apr 13, 01:35 UTC | 40m |
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 N304RJ page for operator, model, and routing details .