sensors Mode-S transponder
A2F94A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N291B · DASSAULT Falcon 50 · operated by BATTELLE MEMORIAL INSTITUTE
- Hex
- A2F94A
- Octal
- 50574512
- Decimal
- 10,680,650
- Country
- US
- Tail
- N291B
- Type
- FA50
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A2F94A 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 |
|---|---|---|---|
| N291B | - | 50 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | N291B | - | Jul 12, 16:45 UTC | Jul 12, 19:35 UTC | 2h 50m |
| 2026-07-10 | N291B | BJC → CMH | Jul 10, 21:05 UTC | Jul 10, 23:40 UTC | 2h 35m |
| 2026-07-09 | N291B | - | Jul 9, 18:05 UTC | Jul 9, 20:45 UTC | 2h 40m |
| 2026-07-01 | N291B | - | Jul 1, 21:20 UTC | Jul 1, 22:30 UTC | 1h 10m |
| 2026-07-01 | N291B | - | Jul 1, 20:15 UTC | Jul 1, 20:40 UTC | 25m |
| 2026-07-01 | N291B | - | Jul 1, 13:00 UTC | Jul 1, 13:25 UTC | 25m |
| 2026-07-01 | N291B | - | Jul 1, 11:15 UTC | Jul 1, 12:20 UTC | 1h 5m |
| 2026-06-30 | N291B | - | Jun 30, 00:55 UTC | Jun 30, 04:35 UTC | 3h 41m |
| 2026-06-29 | N291B | - | Jun 29, 20:15 UTC | Jun 29, 23:54 UTC | 3h 40m |
| 2026-06-26 | N291B | - | Jun 26, 20:10 UTC | Jun 26, 21:59 UTC | 1h 50m |
| 2026-06-26 | N291B | - | Jun 26, 18:15 UTC | Jun 26, 19:39 UTC | 1h 25m |
| 2026-06-25 | N291B | - | Jun 25, 14:09 UTC | Jun 25, 15:29 UTC | 1h 20m |
| 2026-06-24 | N291B | - | Jun 24, 17:55 UTC | Jun 24, 19:55 UTC | 2h 0m |
| 2026-06-18 | N291B | - | Jun 18, 19:45 UTC | Jun 18, 20:45 UTC | 1h 0m |
| 2026-05-29 | N291B | - | May 29, 17:45 UTC | May 29, 18:40 UTC | 55m |
| 2026-05-26 | N291B | - | May 26, 20:40 UTC | May 26, 21:34 UTC | 55m |
| 2026-05-26 | N291B | - | May 26, 19:15 UTC | May 26, 20:05 UTC | 50m |
| 2026-05-22 | N291B | - | May 22, 13:10 UTC | May 22, 15:30 UTC | 2h 20m |
| 2026-05-21 | N291B | - | May 21, 20:20 UTC | May 21, 23:35 UTC | 3h 15m |
| 2026-05-21 | N291B | - | May 21, 18:35 UTC | May 21, 19:45 UTC | 1h 10m |
| 2026-05-21 | N291B | - | May 21, 17:05 UTC | May 21, 18:00 UTC | 55m |
| 2026-05-19 | N291B | - | May 19, 20:05 UTC | May 19, 20:50 UTC | 45m |
| 2026-05-19 | N291B | - | May 19, 17:55 UTC | May 19, 19:05 UTC | 1h 10m |
| 2026-05-19 | N291B | - | May 19, 16:00 UTC | May 19, 17:10 UTC | 1h 10m |
| 2026-05-18 | N291B | - | May 18, 10:45 UTC | May 18, 12:40 UTC | 1h 55m |
| 2026-05-17 | N291B | - | May 17, 17:50 UTC | May 17, 19:40 UTC | 1h 50m |
| 2026-05-15 | N291B | - | May 15, 19:50 UTC | May 15, 21:05 UTC | 1h 15m |
| 2026-05-15 | N291B | - | May 15, 17:55 UTC | May 15, 19:05 UTC | 1h 10m |
| 2026-05-14 | N291B | - | May 14, 19:30 UTC | May 14, 21:20 UTC | 1h 50m |
| 2026-05-14 | N291B | CMH → AGS | May 14, 15:15 UTC | May 14, 18:35 UTC | 3h 20m |
| 2026-05-13 | N291B | - | May 13, 17:50 UTC | May 13, 21:00 UTC | 3h 10m |
| 2026-05-12 | N291B | IAD → CMH | May 12, 21:25 UTC | May 12, 22:10 UTC | 45m |
| 2026-05-11 | N291B | - | May 11, 10:50 UTC | May 11, 11:35 UTC | 45m |
| 2026-05-04 | N291B | - | May 4, 10:45 UTC | May 4, 12:45 UTC | 2h 0m |
| 2026-05-03 | N291B | - | May 3, 18:55 UTC | May 3, 20:55 UTC | 2h 0m |
| 2026-05-01 | N291B | - | May 1, 20:15 UTC | May 1, 21:10 UTC | 55m |
| 2026-05-01 | N291B | - | May 1, 14:20 UTC | May 1, 15:05 UTC | 45m |
| 2026-04-28 | N291B | BJC → CMH | Apr 28, 23:45 UTC | Apr 29, 01:54 UTC | 2h 10m |
| 2026-04-28 | N291B | - | Apr 28, 16:35 UTC | Apr 28, 19:30 UTC | 2h 55m |
| 2026-04-21 | N291B | - | Apr 21, 21:10 UTC | Apr 21, 22:20 UTC | 1h 10m |
| 2026-04-19 | N291B | - | Apr 19, 18:10 UTC | Apr 19, 19:20 UTC | 1h 10m |
| 2026-04-16 | N291B | - | Apr 16, 19:15 UTC | Apr 16, 21:10 UTC | 1h 55m |
| 2026-04-16 | N291B | - | Apr 16, 18:50 UTC | Apr 16, 19:10 UTC | 20m |
| 2026-04-14 | N291B | - | Apr 14, 14:55 UTC | Apr 14, 15:20 UTC | 25m |
| 2026-04-14 | N291B | - | Apr 14, 13:05 UTC | Apr 14, 14:10 UTC | 1h 5m |
| 2026-04-14 | N291B | - | Apr 14, 10:50 UTC | Apr 14, 12:40 UTC | 1h 50m |
| 2026-04-14 | N291B | - | Apr 14, 10:05 UTC | Apr 14, 11:05 UTC | 1h 0m |
| 2026-04-13 | N291B | - | Apr 13, 15:50 UTC | Apr 13, 16:10 UTC | 20m |
| 2026-04-13 | N291B | - | Apr 13, 13:30 UTC | Apr 13, 16:10 UTC | 2h 40m |
| 2026-04-12 | N291B | - | Apr 12, 18:00 UTC | Apr 12, 20:15 UTC | 2h 15m |
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 N291B page for operator, model, and routing details .