Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A6F207

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N547BA · BOMBARDIER CL-600 Challenger · operated by BOEING COMPANY

Hex
A6F207
Octal
51571007
Decimal
10,940,935
Country
US
Tail
N547BA
Type
CL60
No current signal · last broadcast 1h ago
Flights observed
80
Distinct callsigns
20
Country
US
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S A6F207.

Country allocation

The ICAO 24-bit address A6F207 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 20 distinct

Callsign Airline Flights Last seen
RDN693 - 5 2026-04-17
RDN820 - 4 2026-05-11
RDN215 - 4 2026-07-16
RDN030 - 4 2026-07-02
RDN979 - 3 2026-05-28
RDN946 - 3 2026-05-26
RDN837 - 3 2026-05-20
RDN784 - 3 2026-06-16
RDN714 - 3 2026-05-22
RDN706 - 3 2026-04-13
RDN657 - 3 2026-04-15
RDN186 - 3 2026-07-06
RDN063 - 3 2026-06-24
RDN027 - 3 2026-06-15
RDN975 - 2 2026-07-18
RDN869 - 2 2026-05-17
RDN713 - 2 2026-05-08
RDN209 - 2 2026-07-11
RDN202 - 2 2026-07-12
RDN104 - 2 2026-06-17

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 RDN975 - Jul 18, 04:50 UTCJul 18, 09:45 UTC4h 55m
2026-07-18 RDN975 - Jul 18, 00:29 UTCJul 18, 04:00 UTC3h 31m
2026-07-16 RDN234 - Jul 16, 21:55 UTCJul 16, 23:44 UTC1h 50m
2026-07-16 RDN215 - Jul 16, 02:10 UTCJul 16, 03:25 UTC1h 15m
2026-07-15 RDN215 ADS → IAD Jul 15, 22:45 UTCJul 16, 01:20 UTC2h 35m
2026-07-15 RDN215 STL → ADS Jul 15, 19:35 UTCJul 15, 21:00 UTC1h 25m
2026-07-14 RDN215 - Jul 14, 13:10 UTCJul 14, 13:55 UTC45m
2026-07-12 RDN202 - Jul 12, 17:35 UTCJul 12, 21:05 UTC3h 30m
2026-07-12 RDN202 - Jul 12, 11:45 UTCJul 12, 15:45 UTC4h 0m
2026-07-11 RDN209 - Jul 11, 01:45 UTCJul 11, 02:30 UTC45m
2026-07-10 RDN209 IAD → SUS Jul 10, 23:10 UTCJul 11, 01:00 UTC1h 50m
2026-07-09 RDN171 - Jul 9, 20:55 UTCJul 10, 01:15 UTC4h 20m
2026-07-06 RDN186 - Jul 6, 01:20 UTCJul 6, 05:15 UTC3h 55m
2026-07-05 RDN186 - Jul 5, 23:15 UTCJul 6, 00:50 UTC1h 35m
2026-07-05 RDN186 - Jul 5, 18:45 UTCJul 5, 20:10 UTC1h 25m
2026-07-02 RDN030 - Jul 2, 00:15 UTCJul 2, 03:50 UTC3h 35m
2026-07-01 RDN030 - Jul 1, 18:15 UTCJul 1, 23:30 UTC5h 15m
2026-06-30 RDN030 - Jun 30, 18:45 UTCJun 30, 19:20 UTC35m
2026-06-30 RDN030 - Jun 30, 16:05 UTCJun 30, 17:25 UTC1h 20m
2026-06-24 RDN063 - Jun 24, 00:44 UTCJun 24, 03:19 UTC2h 35m
2026-06-23 RDN063 - Jun 23, 22:40 UTCJun 23, 23:59 UTC1h 20m
2026-06-23 RDN063 - Jun 23, 19:59 UTCJun 23, 21:54 UTC1h 55m
2026-06-22 RDN051 - Jun 22, 16:20 UTCJun 22, 17:55 UTC1h 35m
2026-06-22 RDN051 - Jun 22, 13:35 UTCJun 22, 14:59 UTC1h 25m
2026-06-21 RDN087 BFI → PDX Jun 21, 23:24 UTCJun 21, 23:50 UTC25m
2026-06-17 RDN104 - Jun 17, 22:15 UTCJun 18, 03:50 UTC5h 35m
2026-06-17 RDN104 - Jun 17, 17:50 UTCJun 17, 18:20 UTC30m
2026-06-16 RDN784 - Jun 16, 16:00 UTCJun 16, 18:09 UTC2h 10m
2026-06-15 RDN784 IAD → OPF Jun 15, 13:54 UTCJun 15, 15:59 UTC2h 5m
2026-06-15 RDN784 - Jun 15, 10:55 UTCJun 15, 12:10 UTC1h 15m
2026-06-15 RDN027 - Jun 15, 02:39 UTCJun 15, 04:40 UTC2h 0m
2026-06-14 RDN027 BFI → ICT Jun 14, 23:15 UTCJun 15, 02:04 UTC2h 50m
2026-06-14 RDN027 - Jun 14, 18:25 UTCJun 14, 22:20 UTC3h 55m
2026-06-13 RDN004 IAD → GYY Jun 13, 00:55 UTCJun 13, 03:55 UTC3h 0m
2026-06-12 RDN004 - Jun 12, 20:10 UTCJun 12, 21:20 UTC1h 10m
2026-06-08 RDN013 - Jun 8, 14:45 UTCJun 8, 15:00 UTC15m
2026-06-03 RDN988 - Jun 3, 18:00 UTCJun 3, 21:40 UTC3h 40m
2026-05-28 RDN979 - May 28, 20:45 UTCMay 29, 01:30 UTC4h 45m
2026-05-27 RDN979 - May 27, 18:45 UTCMay 27, 23:10 UTC4h 25m
2026-05-27 RDN979 - May 27, 14:05 UTCMay 27, 17:50 UTC3h 45m
2026-05-26 RDN946 - May 26, 02:19 UTCMay 26, 03:45 UTC1h 25m
2026-05-25 RDN946 CLD → IAD May 25, 21:24 UTCMay 26, 01:44 UTC4h 20m
2026-05-24 RDN946 - May 24, 19:00 UTCMay 24, 21:30 UTC2h 30m
2026-05-22 RDN714 - May 22, 18:25 UTCMay 22, 23:55 UTC5h 30m
2026-05-20 RDN714 - May 20, 21:30 UTCMay 21, 02:05 UTC4h 35m
2026-05-20 RDN714 - May 20, 16:05 UTCMay 20, 20:15 UTC4h 10m
2026-05-20 RDN837 IAD → GYY May 20, 01:25 UTCMay 20, 02:50 UTC1h 25m
2026-05-19 RDN837 - May 19, 19:40 UTCMay 20, 00:20 UTC4h 40m
2026-05-18 RDN837 IAD → PAE May 18, 20:15 UTCMay 19, 01:50 UTC5h 35m
2026-05-18 RDN902 SAV → IAD May 18, 17:25 UTCMay 18, 18:50 UTC1h 24m

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 N547BA page for operator, model, and routing details .

Mode-S A6F207 frequently asked

What is Mode-S code A6F207?
A6F207 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N547BA.
Where is Mode-S A6F207 registered?
Mode-S code A6F207 is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A6F207 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A6F207, octal 51571007, decimal 10,940,935.
What flights does A6F207 operate?
Mode-S A6F207 has broadcast 20 distinct callsigns, including RDN693, RDN820, RDN215, RDN030, RDN979.