sensors Mode-S transponder
A67FF0
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N518JA · BOMBARDIER CL-600 Challenger · operated by BFJA LLC
- Hex
- A67FF0
- Octal
- 51477760
- Decimal
- 10,911,728
- Country
- US
- Tail
- N518JA
- Type
- CL60
- Flights observed
- 61
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address A67FF0 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 |
|---|---|---|---|
| N518JA | - | 61 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N518JA | - | Jul 24, 20:35 UTC | Jul 24, 21:05 UTC | 30m |
| 2026-07-23 | N518JA | - | Jul 23, 00:10 UTC | Jul 23, 01:15 UTC | 1h 5m |
| 2026-07-18 | N518JA | HIO → MEV | Jul 18, 00:55 UTC | Jul 18, 02:05 UTC | 1h 10m |
| 2026-07-16 | N518JA | - | Jul 16, 22:45 UTC | Jul 16, 23:20 UTC | 35m |
| 2026-07-16 | N518JA | - | Jul 16, 21:25 UTC | Jul 16, 22:00 UTC | 35m |
| 2026-07-16 | N518JA | - | Jul 16, 17:20 UTC | Jul 16, 17:49 UTC | 30m |
| 2026-07-16 | N518JA | - | Jul 16, 15:19 UTC | Jul 16, 15:45 UTC | 25m |
| 2026-07-12 | N518JA | - | Jul 12, 14:30 UTC | Jul 12, 16:05 UTC | 1h 35m |
| 2026-07-12 | N518JA | - | Jul 12, 00:50 UTC | Jul 12, 02:55 UTC | 2h 5m |
| 2026-07-08 | N518JA | - | Jul 8, 13:20 UTC | Jul 8, 18:35 UTC | 5h 15m |
| 2026-07-06 | N518JA | HIO → TEB | Jul 6, 15:20 UTC | Jul 6, 19:55 UTC | 4h 35m |
| 2026-07-04 | N518JA | - | Jul 4, 04:20 UTC | Jul 4, 04:40 UTC | 20m |
| 2026-07-03 | N518JA | - | Jul 3, 16:10 UTC | Jul 4, 03:35 UTC | 11h 25m |
| 2026-07-03 | N518JA | - | Jul 3, 12:35 UTC | Jul 3, 15:05 UTC | 2h 30m |
| 2026-06-27 | N518JA | - | Jun 27, 13:35 UTC | Jun 27, 16:04 UTC | 2h 30m |
| 2026-06-27 | N518JA | - | Jun 27, 12:15 UTC | Jun 27, 12:34 UTC | 20m |
| 2026-06-25 | N518JA | - | Jun 25, 08:40 UTC | Jun 25, 09:05 UTC | 25m |
| 2026-06-25 | N518JA | - | Jun 25, 07:30 UTC | Jun 25, 07:45 UTC | 15m |
| 2026-06-25 | N518JA | - | Jun 25, 02:54 UTC | Jun 25, 03:40 UTC | 45m |
| 2026-06-24 | N518JA | HIO → BGR | Jun 24, 21:14 UTC | Jun 25, 01:50 UTC | 4h 35m |
| 2026-06-24 | N518JA | HIO → HIO | Jun 24, 18:34 UTC | Jun 24, 19:49 UTC | 1h 15m |
| 2026-06-23 | N518JA | VNY → HIO | Jun 23, 22:44 UTC | Jun 24, 00:30 UTC | 1h 45m |
| 2026-06-23 | N518JA | HIO → VNY | Jun 23, 20:15 UTC | Jun 23, 22:05 UTC | 1h 50m |
| 2026-06-20 | N518JA | BGR → HIO | Jun 20, 19:55 UTC | Jun 21, 01:25 UTC | 5h 30m |
| 2026-06-20 | N518JA | - | Jun 20, 12:54 UTC | Jun 20, 17:54 UTC | 5h 0m |
| 2026-06-17 | N518JA | - | Jun 17, 13:40 UTC | Jun 17, 14:35 UTC | 55m |
| 2026-06-15 | N518JA | - | Jun 15, 16:49 UTC | Jun 15, 17:34 UTC | 45m |
| 2026-06-15 | N518JA | - | Jun 15, 07:40 UTC | Jun 15, 08:25 UTC | 45m |
| 2026-06-12 | N518JA | ORK → LTN | Jun 12, 16:25 UTC | Jun 12, 17:35 UTC | 1h 10m |
| 2026-06-12 | N518JA | - | Jun 12, 14:15 UTC | Jun 12, 15:20 UTC | 1h 5m |
| 2026-06-12 | N518JA | ORK → LTN | Jun 12, 12:20 UTC | Jun 12, 13:30 UTC | 1h 10m |
| 2026-06-12 | N518JA | - | Jun 12, 09:30 UTC | Jun 12, 10:05 UTC | 35m |
| 2026-06-12 | N518JA | ORK → DUB | Jun 12, 08:25 UTC | Jun 12, 09:00 UTC | 35m |
| 2026-06-07 | N518JA | - | Jun 7, 09:40 UTC | Jun 7, 10:45 UTC | 1h 5m |
| 2026-06-07 | N518JA | - | Jun 7, 07:50 UTC | Jun 7, 08:40 UTC | 50m |
| 2026-06-07 | N518JA | BGR → ORK | Jun 7, 01:20 UTC | Jun 7, 06:15 UTC | 4h 55m |
| 2026-06-06 | N518JA | HIO → BGR | Jun 6, 19:24 UTC | Jun 7, 00:10 UTC | 4h 45m |
| 2026-06-02 | N518JA | - | Jun 2, 00:40 UTC | Jun 2, 01:15 UTC | 35m |
| 2026-06-01 | N518JA | - | Jun 1, 18:10 UTC | Jun 1, 18:30 UTC | 20m |
| 2026-05-31 | N518JA | - | May 31, 17:15 UTC | May 31, 19:25 UTC | 2h 10m |
| 2026-05-30 | N518JA | HIO → APA | May 30, 17:05 UTC | May 30, 19:30 UTC | 2h 25m |
| 2026-05-24 | N518JA | - | May 24, 18:25 UTC | May 24, 21:40 UTC | 3h 15m |
| 2026-05-22 | N518JA | - | May 22, 19:50 UTC | May 22, 22:50 UTC | 3h 0m |
| 2026-05-20 | N518JA | - | May 20, 17:00 UTC | May 20, 20:55 UTC | 3h 55m |
| 2026-05-19 | N518JA | HIO → MVY | May 19, 17:40 UTC | May 19, 22:55 UTC | 5h 15m |
| 2026-05-11 | N518JA | - | May 11, 16:10 UTC | May 11, 17:15 UTC | 1h 6m |
| 2026-05-07 | N518JA | HIO → MEV | May 7, 00:15 UTC | May 7, 01:15 UTC | 1h 0m |
| 2026-05-04 | N518JA | LAS → HIO | May 4, 20:30 UTC | May 4, 22:15 UTC | 1h 45m |
| 2026-05-04 | N518JA | APA → LAS | May 4, 18:05 UTC | May 4, 19:40 UTC | 1h 36m |
| 2026-05-01 | N518JA | LAS → APA | May 1, 23:15 UTC | May 2, 00:35 UTC | 1h 20m |
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 N518JA page for operator, model, and routing details .