sensors Mode-S transponder
740D29
ICAO 24-bit transponder address · allocated to Jordan
Currently assigned to JY-CII · EMBRAER EMB-135 Legacy
- Hex
- 740D29
- Octal
- 35006451
- Decimal
- 7,605,545
- Country
- JO
- Tail
- JY-CII
- Type
- E35L
- Flights observed
- 35
- Distinct callsigns
- 5
- Country
- JO
- Last broadcast
- 38m ago
Last known position
Country allocation
The ICAO 24-bit address 740D29 falls within the block assigned to Jordan (JO) by ICAO Annex 10, Volume III. Every aircraft registered in Jordan 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 5 distinct
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | AWS901 | - | Jun 30, 11:25 UTC | Jun 30, 13:45 UTC | 2h 20m |
| 2026-06-23 | AWS901 | - | Jun 23, 12:55 UTC | Jun 23, 14:29 UTC | 1h 35m |
| 2026-06-23 | AWS901 | - | Jun 23, 10:10 UTC | Jun 23, 11:54 UTC | 1h 45m |
| 2026-06-22 | JYCII | - | Jun 22, 14:14 UTC | Jun 22, 18:09 UTC | 3h 55m |
| 2026-06-22 | JYCII | - | Jun 22, 09:14 UTC | Jun 22, 11:54 UTC | 2h 40m |
| 2026-06-20 | JYCII | - | Jun 20, 12:19 UTC | Jun 20, 12:39 UTC | 20m |
| 2026-06-18 | AWS901 | - | Jun 18, 02:15 UTC | Jun 18, 06:20 UTC | 4h 5m |
| 2026-06-16 | AWS902 | - | Jun 16, 19:00 UTC | Jun 16, 22:15 UTC | 3h 16m |
| 2026-06-16 | AWS902 | - | Jun 16, 15:35 UTC | Jun 16, 18:05 UTC | 2h 30m |
| 2026-06-15 | AWS901 | - | Jun 15, 12:00 UTC | Jun 15, 12:19 UTC | 20m |
| 2026-06-10 | AWS903 | - | Jun 10, 21:15 UTC | Jun 11, 01:05 UTC | 3h 50m |
| 2026-06-10 | AWS902 | - | Jun 10, 15:00 UTC | Jun 10, 20:00 UTC | 5h 0m |
| 2026-06-09 | AWS901 | - | Jun 9, 07:55 UTC | Jun 9, 09:40 UTC | 1h 45m |
| 2026-06-09 | AWS901 | - | Jun 9, 04:30 UTC | Jun 9, 06:15 UTC | 1h 45m |
| 2026-06-07 | AWS903 | - | Jun 7, 04:10 UTC | Jun 7, 14:10 UTC | 10h 0m |
| 2026-06-06 | AWS901 | - | Jun 6, 13:15 UTC | Jun 6, 14:34 UTC | 1h 20m |
| 2026-06-06 | AWS901 | - | Jun 6, 06:45 UTC | Jun 6, 10:09 UTC | 3h 25m |
| 2026-06-05 | AWS904 | - | Jun 5, 12:00 UTC | Jun 5, 12:25 UTC | 25m |
| 2026-06-04 | AWS904 | - | Jun 4, 12:20 UTC | Jun 5, 12:15 UTC | 23h 55m |
| 2026-06-04 | AWS901 | - | Jun 4, 12:00 UTC | Jun 4, 12:20 UTC | 20m |
| 2026-06-02 | AWS901 | - | Jun 2, 22:45 UTC | Jun 2, 23:00 UTC | 15m |
| 2026-06-02 | AWS901 | - | Jun 2, 17:50 UTC | Jun 2, 18:00 UTC | 10m |
| 2026-06-01 | AWS901 | - | Jun 1, 20:00 UTC | Jun 1, 20:35 UTC | 35m |
| 2026-05-29 | AWS901 | - | May 29, 07:55 UTC | May 29, 09:40 UTC | 1h 45m |
| 2026-05-28 | JYCII | - | May 28, 09:25 UTC | May 28, 11:35 UTC | 2h 10m |
| 2026-05-25 | AWS902 | - | May 25, 12:45 UTC | May 25, 17:55 UTC | 5h 10m |
| 2026-05-24 | AWS901 | - | May 24, 06:40 UTC | May 24, 14:45 UTC | 8h 5m |
| 2026-05-23 | JYCII | - | May 23, 13:35 UTC | May 23, 15:00 UTC | 1h 25m |
| 2026-05-22 | JYCII | - | May 22, 13:00 UTC | May 22, 13:50 UTC | 50m |
| 2026-05-22 | JYCII | - | May 22, 08:20 UTC | May 22, 11:35 UTC | 3h 14m |
| 2026-05-16 | JYCII | - | May 16, 08:26 UTC | May 16, 14:16 UTC | 5h 50m |
| 2026-05-07 | JYCII | - | May 7, 17:50 UTC | May 7, 20:50 UTC | 3h 0m |
| 2026-05-07 | JYCII | - | May 7, 13:50 UTC | May 7, 16:40 UTC | 2h 50m |
| 2026-05-01 | AWS901 | - | May 1, 09:10 UTC | May 1, 09:25 UTC | 15m |
| 2026-04-27 | AWS901 | - | Apr 27, 07:15 UTC | Apr 27, 07:40 UTC | 25m |
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 JY-CII page for operator, model, and routing details .