sensors Mode-S transponder
AC6CD2
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N90 · BOMBARDIER CL-600 Challenger · operated by FEDERAL AVIATION ADMINISTRATION
- Hex
- AC6CD2
- Octal
- 53066322
- Decimal
- 11,300,050
- Country
- US
- Tail
- N90
- Type
- CL60
- Flights observed
- 55
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AC6CD2 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 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | FFP90 | - | Jul 12, 15:45 UTC | Jul 12, 18:30 UTC | 2h 45m |
| 2026-07-02 | FLC90 | - | Jul 2, 17:00 UTC | Jul 2, 18:45 UTC | 1h 45m |
| 2026-07-02 | FLC90 | - | Jul 2, 14:45 UTC | Jul 2, 15:15 UTC | 30m |
| 2026-07-01 | FLC90 | - | Jul 1, 20:10 UTC | Jul 1, 20:45 UTC | 35m |
| 2026-07-01 | FLC90 | - | Jul 1, 18:45 UTC | Jul 1, 18:55 UTC | 10m |
| 2026-06-30 | FLC90 | - | Jun 30, 03:35 UTC | Jun 30, 04:05 UTC | 30m |
| 2026-06-29 | FLC90 | - | Jun 29, 23:54 UTC | Jun 30, 01:00 UTC | 1h 5m |
| 2026-06-29 | FLC90 | - | Jun 29, 20:49 UTC | Jun 29, 22:39 UTC | 1h 50m |
| 2026-06-26 | FLC90 | - | Jun 26, 14:19 UTC | Jun 26, 18:34 UTC | 4h 15m |
| 2026-06-13 | FLC90 | - | Jun 13, 20:25 UTC | Jun 13, 21:55 UTC | 1h 30m |
| 2026-06-13 | FLC90 | - | Jun 13, 19:25 UTC | Jun 13, 19:50 UTC | 25m |
| 2026-06-13 | FLC90 | - | Jun 13, 17:15 UTC | Jun 13, 18:05 UTC | 50m |
| 2026-06-13 | FLC90 | - | Jun 13, 14:40 UTC | Jun 13, 14:50 UTC | 10m |
| 2026-06-05 | FLC90 | - | Jun 5, 18:05 UTC | Jun 5, 18:25 UTC | 20m |
| 2026-06-05 | FLC90 | - | Jun 5, 15:10 UTC | Jun 5, 17:05 UTC | 1h 55m |
| 2026-06-04 | FLC90 | - | Jun 4, 17:50 UTC | Jun 4, 19:10 UTC | 1h 20m |
| 2026-06-02 | FLC90 | - | Jun 2, 18:00 UTC | Jun 2, 18:10 UTC | 10m |
| 2026-06-02 | FLC90 | - | Jun 2, 14:40 UTC | Jun 2, 16:50 UTC | 2h 10m |
| 2026-05-29 | FLC90 | ABQ → OKC | May 29, 15:40 UTC | May 29, 18:40 UTC | 3h 0m |
| 2026-05-28 | FLC90 | - | May 28, 15:15 UTC | May 28, 17:25 UTC | 2h 10m |
| 2026-05-27 | FLC90 | - | May 27, 18:15 UTC | May 27, 18:50 UTC | 35m |
| 2026-05-27 | FLC90 | - | May 27, 17:25 UTC | May 27, 17:35 UTC | 10m |
| 2026-05-27 | FLC90 | - | May 27, 12:40 UTC | May 27, 15:20 UTC | 2h 40m |
| 2026-05-26 | FLC90 | - | May 26, 15:45 UTC | May 26, 19:34 UTC | 3h 50m |
| 2026-05-26 | FLC90 | - | May 26, 14:35 UTC | May 26, 15:14 UTC | 40m |
| 2026-05-09 | FFP90 | - | May 9, 17:35 UTC | May 9, 20:10 UTC | 2h 35m |
| 2026-05-08 | FFP90 | - | May 8, 23:45 UTC | May 9, 02:55 UTC | 3h 10m |
| 2026-05-08 | FLC90 | - | May 8, 16:50 UTC | May 8, 23:05 UTC | 6h 15m |
| 2026-05-07 | FLC90 | - | May 7, 22:20 UTC | May 7, 23:14 UTC | 55m |
| 2026-05-07 | FLC90 | - | May 7, 19:35 UTC | May 7, 20:40 UTC | 1h 5m |
| 2026-05-07 | FLC90 | - | May 7, 18:30 UTC | May 7, 18:40 UTC | 10m |
| 2026-05-07 | FLC90 | - | May 7, 16:40 UTC | May 7, 17:15 UTC | 35m |
| 2026-05-06 | FLC90 | - | May 6, 15:20 UTC | May 6, 18:05 UTC | 2h 44m |
| 2026-05-05 | FLC90 | - | May 5, 21:20 UTC | May 5, 23:20 UTC | 2h 0m |
| 2026-05-05 | FLC90 | - | May 5, 00:35 UTC | May 5, 01:40 UTC | 1h 5m |
| 2026-05-04 | FLC90 | - | May 4, 21:40 UTC | May 4, 23:50 UTC | 2h 10m |
| 2026-05-03 | FLC90 | - | May 3, 23:55 UTC | May 4, 00:45 UTC | 50m |
| 2026-05-03 | FLC90 | - | May 3, 18:55 UTC | May 3, 19:25 UTC | 30m |
| 2026-04-27 | FLC90 | - | Apr 27, 20:50 UTC | Apr 27, 22:45 UTC | 1h 55m |
| 2026-04-27 | FLC90 | - | Apr 27, 17:15 UTC | Apr 27, 19:45 UTC | 2h 30m |
| 2026-04-27 | FLC90 | - | Apr 27, 01:25 UTC | Apr 27, 01:30 UTC | 5m |
| 2026-04-24 | FLC90 | - | Apr 24, 23:35 UTC | Apr 25, 00:35 UTC | 1h 0m |
| 2026-04-23 | FLC90 | - | Apr 23, 17:30 UTC | Apr 23, 19:20 UTC | 1h 49m |
| 2026-04-22 | FLC90 | - | Apr 22, 23:20 UTC | Apr 23, 00:05 UTC | 45m |
| 2026-04-22 | FLC90 | - | Apr 22, 20:40 UTC | Apr 22, 21:25 UTC | 45m |
| 2026-04-22 | FLC90 | - | Apr 22, 17:15 UTC | Apr 22, 19:10 UTC | 1h 55m |
| 2026-04-21 | FLC90 | - | Apr 21, 21:45 UTC | Apr 21, 23:00 UTC | 1h 15m |
| 2026-04-21 | FLC90 | - | Apr 21, 17:15 UTC | Apr 21, 20:05 UTC | 2h 50m |
| 2026-04-20 | FLC90 | - | Apr 20, 20:50 UTC | Apr 20, 22:50 UTC | 2h 0m |
| 2026-04-20 | FLC90 | - | Apr 20, 17:10 UTC | Apr 20, 17:40 UTC | 30m |
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 N90 page for operator, model, and routing details .