- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address A58135 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 |
|---|---|---|---|
| N454CL | - | 59 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | N454CL | - | Jul 17, 20:10 UTC | Jul 17, 22:05 UTC | 1h 55m |
| 2026-07-13 | N454CL | - | Jul 13, 13:15 UTC | Jul 13, 14:55 UTC | 1h 40m |
| 2026-07-12 | N454CL | LAS → RDU | Jul 12, 16:50 UTC | Jul 12, 20:55 UTC | 4h 5m |
| 2026-07-10 | N454CL | - | Jul 10, 20:20 UTC | Jul 11, 00:45 UTC | 4h 25m |
| 2026-07-10 | N454CL | LAS → RDU | Jul 10, 15:40 UTC | Jul 10, 19:40 UTC | 4h 0m |
| 2026-07-08 | N454CL | - | Jul 8, 17:20 UTC | Jul 8, 21:35 UTC | 4h 15m |
| 2026-07-06 | N454CL | - | Jul 6, 00:25 UTC | Jul 6, 00:45 UTC | 20m |
| 2026-07-05 | N454CL | - | Jul 5, 19:05 UTC | Jul 5, 21:00 UTC | 1h 55m |
| 2026-07-02 | N454CL | - | Jul 2, 20:50 UTC | Jul 2, 22:25 UTC | 1h 35m |
| 2026-06-29 | N454CL | - | Jun 29, 16:25 UTC | Jun 29, 17:45 UTC | 1h 20m |
| 2026-06-29 | N454CL | - | Jun 29, 14:19 UTC | Jun 29, 15:45 UTC | 1h 25m |
| 2026-06-21 | N454CL | - | Jun 21, 20:09 UTC | Jun 21, 20:59 UTC | 50m |
| 2026-06-19 | N454CL | RDU → MTN | Jun 19, 15:59 UTC | Jun 19, 16:44 UTC | 45m |
| 2026-06-16 | N454CL | IAD → RDU | Jun 16, 22:20 UTC | Jun 17, 00:05 UTC | 1h 45m |
| 2026-06-16 | N454CL | - | Jun 16, 13:00 UTC | Jun 16, 13:50 UTC | 50m |
| 2026-06-16 | N454CL | - | Jun 16, 11:55 UTC | Jun 16, 12:14 UTC | 20m |
| 2026-06-14 | N454CL | - | Jun 14, 20:45 UTC | Jun 14, 21:10 UTC | 25m |
| 2026-06-14 | N454CL | - | Jun 14, 18:55 UTC | Jun 14, 20:05 UTC | 1h 10m |
| 2026-06-10 | N454CL | - | Jun 10, 20:15 UTC | Jun 10, 21:35 UTC | 1h 20m |
| 2026-06-10 | N454CL | - | Jun 10, 18:30 UTC | Jun 10, 18:45 UTC | 15m |
| 2026-06-10 | N454CL | TEB → RDU | Jun 10, 01:15 UTC | Jun 10, 02:20 UTC | 1h 5m |
| 2026-06-09 | N454CL | - | Jun 9, 18:55 UTC | Jun 9, 20:15 UTC | 1h 20m |
| 2026-06-07 | N454CL | MCO → RDU | Jun 7, 16:30 UTC | Jun 7, 17:50 UTC | 1h 20m |
| 2026-06-07 | N454CL | RDU → MCO | Jun 7, 10:35 UTC | Jun 7, 11:50 UTC | 1h 15m |
| 2026-06-06 | N454CL | - | Jun 6, 22:55 UTC | Jun 7, 00:25 UTC | 1h 30m |
| 2026-06-06 | N454CL | TEB → ILG | Jun 6, 17:34 UTC | Jun 6, 18:19 UTC | 45m |
| 2026-06-04 | N454CL | - | Jun 4, 22:00 UTC | Jun 4, 23:05 UTC | 1h 5m |
| 2026-06-04 | N454CL | - | Jun 4, 20:10 UTC | Jun 4, 20:30 UTC | 20m |
| 2026-06-03 | N454CL | - | Jun 3, 18:40 UTC | Jun 3, 19:35 UTC | 55m |
| 2026-06-03 | N454CL | RDU → CMH | Jun 3, 11:30 UTC | Jun 3, 12:30 UTC | 1h 0m |
| 2026-06-02 | N454CL | - | Jun 2, 20:05 UTC | Jun 2, 21:20 UTC | 1h 15m |
| 2026-06-02 | N454CL | RDU → IND | Jun 2, 18:10 UTC | Jun 2, 19:25 UTC | 1h 15m |
| 2026-06-02 | N454CL | - | Jun 2, 15:50 UTC | Jun 2, 17:20 UTC | 1h 30m |
| 2026-05-29 | N454CL | - | May 29, 15:35 UTC | May 29, 16:45 UTC | 1h 10m |
| 2026-05-29 | N454CL | - | May 29, 13:35 UTC | May 29, 14:50 UTC | 1h 15m |
| 2026-05-29 | N454CL | RDU → IND | May 29, 11:40 UTC | May 29, 12:50 UTC | 1h 10m |
| 2026-05-25 | N454CL | - | May 25, 17:40 UTC | May 25, 19:10 UTC | 1h 30m |
| 2026-05-25 | N454CL | - | May 25, 14:05 UTC | May 25, 15:50 UTC | 1h 45m |
| 2026-05-23 | N454CL | - | May 23, 17:00 UTC | May 23, 18:30 UTC | 1h 31m |
| 2026-05-23 | N454CL | - | May 23, 12:50 UTC | May 23, 14:10 UTC | 1h 20m |
| 2026-05-22 | N454CL | LAS → RDU | May 22, 14:50 UTC | May 22, 18:50 UTC | 4h 0m |
| 2026-05-17 | N454CL | - | May 17, 14:55 UTC | May 17, 19:20 UTC | 4h 25m |
| 2026-05-16 | N454CL | - | May 16, 21:15 UTC | May 16, 22:40 UTC | 1h 25m |
| 2026-05-16 | N454CL | - | May 16, 12:31 UTC | May 16, 14:01 UTC | 1h 30m |
| 2026-05-15 | N454CL | RDU → RDU | May 15, 17:25 UTC | May 15, 17:30 UTC | 5m |
| 2026-05-12 | N454CL | - | May 12, 18:20 UTC | May 12, 19:25 UTC | 1h 5m |
| 2026-05-11 | N454CL | - | May 11, 16:30 UTC | May 11, 17:30 UTC | 1h 1m |
| 2026-04-30 | N454CL | - | Apr 30, 14:45 UTC | Apr 30, 18:55 UTC | 4h 10m |
| 2026-04-26 | N454CL | - | Apr 26, 14:45 UTC | Apr 26, 20:00 UTC | 5h 16m |
| 2026-04-24 | N454CL | - | Apr 24, 23:15 UTC | Apr 25, 01:30 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 N454CL page for operator, model, and routing details .