sensors Mode-S transponder
A209C6
ICAO 24-bit transponder address · allocated to United States
Currently assigned to YV573T · BOEING 737-400 · operated by SL AVIATION LLC
- Hex
- A209C6
- Octal
- 50404706
- Decimal
- 10,619,334
- Country
- US
- Tail
- YV573T
- Type
- B734
- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address A209C6 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 |
|---|---|---|---|
| BRW30 | - | 59 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | BRW30 | FCM → FCM | Jul 13, 18:55 UTC | Jul 13, 19:45 UTC | 50m |
| 2026-07-13 | BRW30 | - | Jul 13, 14:00 UTC | Jul 13, 15:40 UTC | 1h 40m |
| 2026-07-10 | BRW30 | FCM → FCM | Jul 10, 13:05 UTC | Jul 10, 13:50 UTC | 45m |
| 2026-07-10 | BRW30 | FCM → FCM | Jul 10, 02:55 UTC | Jul 10, 04:20 UTC | 1h 25m |
| 2026-07-07 | BRW30 | FCM → FCM | Jul 7, 20:00 UTC | Jul 7, 21:05 UTC | 1h 5m |
| 2026-07-07 | BRW30 | - | Jul 7, 14:40 UTC | Jul 7, 15:50 UTC | 1h 10m |
| 2026-07-06 | BRW30 | FCM → FCM | Jul 6, 14:40 UTC | Jul 6, 15:50 UTC | 1h 10m |
| 2026-07-02 | BRW30 | - | Jul 2, 20:55 UTC | Jul 2, 22:40 UTC | 1h 45m |
| 2026-06-26 | BRW30 | FCM → FCM | Jun 26, 14:55 UTC | Jun 26, 16:00 UTC | 1h 5m |
| 2026-06-25 | BRW30 | - | Jun 25, 14:55 UTC | Jun 25, 16:24 UTC | 1h 30m |
| 2026-06-24 | BRW30 | - | Jun 24, 18:15 UTC | Jun 24, 18:34 UTC | 20m |
| 2026-06-24 | BRW30 | - | Jun 24, 14:50 UTC | Jun 24, 15:29 UTC | 40m |
| 2026-06-20 | BRW30 | - | Jun 20, 22:25 UTC | Jun 20, 22:50 UTC | 25m |
| 2026-06-20 | BRW30 | - | Jun 20, 16:55 UTC | Jun 20, 17:34 UTC | 40m |
| 2026-06-20 | BRW30 | - | Jun 20, 14:39 UTC | Jun 20, 14:54 UTC | 15m |
| 2026-06-15 | BRW30 | - | Jun 15, 13:54 UTC | Jun 15, 15:15 UTC | 1h 20m |
| 2026-06-09 | BRW30 | - | Jun 9, 22:45 UTC | Jun 9, 23:10 UTC | 25m |
| 2026-06-09 | BRW30 | - | Jun 9, 21:10 UTC | Jun 9, 21:30 UTC | 20m |
| 2026-06-09 | BRW30 | - | Jun 9, 18:45 UTC | Jun 9, 20:00 UTC | 1h 15m |
| 2026-06-03 | BRW30 | - | Jun 3, 15:20 UTC | Jun 3, 16:20 UTC | 1h 0m |
| 2026-06-02 | BRW30 | - | Jun 2, 22:10 UTC | Jun 2, 23:15 UTC | 1h 5m |
| 2026-06-01 | BRW30 | FCM → FCM | Jun 1, 15:20 UTC | Jun 1, 16:45 UTC | 1h 25m |
| 2026-05-29 | BRW30 | - | May 29, 20:15 UTC | May 29, 21:40 UTC | 1h 25m |
| 2026-05-28 | BRW30 | - | May 28, 16:55 UTC | May 28, 18:15 UTC | 1h 20m |
| 2026-05-28 | BRW30 | - | May 28, 13:45 UTC | May 28, 15:05 UTC | 1h 20m |
| 2026-05-26 | BRW30 | FCM → FCM | May 26, 22:25 UTC | May 26, 22:44 UTC | 20m |
| 2026-05-26 | BRW30 | FCM → FCM | May 26, 16:10 UTC | May 26, 17:20 UTC | 1h 10m |
| 2026-05-22 | BRW30 | FCM → FCM | May 22, 16:15 UTC | May 22, 16:25 UTC | 10m |
| 2026-05-21 | BRW30 | FCM → FCM | May 21, 15:45 UTC | May 21, 17:20 UTC | 1h 35m |
| 2026-05-15 | BRW30 | - | May 15, 16:50 UTC | May 15, 18:20 UTC | 1h 30m |
| 2026-05-13 | BRW30 | - | May 13, 15:05 UTC | May 13, 16:35 UTC | 1h 30m |
| 2026-05-06 | BRW30 | - | May 6, 13:50 UTC | May 6, 14:50 UTC | 1h 0m |
| 2026-05-05 | BRW30 | - | May 5, 13:45 UTC | May 5, 14:50 UTC | 1h 5m |
| 2026-05-02 | BRW30 | - | May 2, 17:20 UTC | May 2, 18:20 UTC | 1h 0m |
| 2026-05-01 | BRW30 | - | May 1, 17:40 UTC | May 1, 18:55 UTC | 1h 15m |
| 2026-04-30 | BRW30 | - | Apr 30, 20:50 UTC | Apr 30, 22:10 UTC | 1h 20m |
| 2026-04-30 | BRW30 | - | Apr 30, 18:15 UTC | Apr 30, 19:25 UTC | 1h 10m |
| 2026-04-30 | BRW30 | - | Apr 30, 16:00 UTC | Apr 30, 17:30 UTC | 1h 30m |
| 2026-04-29 | BRW30 | FCM → FCM | Apr 29, 16:05 UTC | Apr 29, 17:30 UTC | 1h 25m |
| 2026-04-28 | BRW30 | - | Apr 28, 21:10 UTC | Apr 28, 21:40 UTC | 30m |
| 2026-04-28 | BRW30 | - | Apr 28, 20:00 UTC | Apr 28, 20:35 UTC | 35m |
| 2026-04-25 | BRW30 | FCM → FCM | Apr 25, 00:45 UTC | Apr 25, 02:25 UTC | 1h 40m |
| 2026-04-22 | BRW30 | - | Apr 22, 20:25 UTC | Apr 22, 21:00 UTC | 35m |
| 2026-04-22 | BRW30 | - | Apr 22, 18:20 UTC | Apr 22, 19:55 UTC | 1h 35m |
| 2026-04-22 | BRW30 | FCM → FCM | Apr 22, 15:50 UTC | Apr 22, 17:15 UTC | 1h 25m |
| 2026-04-21 | BRW30 | - | Apr 21, 18:45 UTC | Apr 21, 20:10 UTC | 1h 25m |
| 2026-04-19 | BRW30 | - | Apr 19, 18:40 UTC | Apr 19, 20:15 UTC | 1h 35m |
| 2026-04-19 | BRW30 | - | Apr 19, 14:10 UTC | Apr 19, 15:10 UTC | 1h 0m |
| 2026-04-16 | BRW30 | - | Apr 16, 19:20 UTC | Apr 16, 19:45 UTC | 25m |
| 2026-04-16 | BRW30 | - | Apr 16, 18:30 UTC | Apr 16, 19:10 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 YV573T page for operator, model, and routing details .