sensors Mode-S transponder
A41FED
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N365LV · operated by AULT AVIATION LLC
- Hex
- A41FED
- Octal
- 51017755
- Decimal
- 10,756,077
- Country
- US
- Tail
- N365LV
- Type
- GLF5
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address A41FED 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 |
|---|---|---|---|
| N365LV | - | 54 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | N365LV | VNY → LAS | Jul 11, 01:10 UTC | Jul 11, 01:55 UTC | 45m |
| 2026-07-10 | N365LV | - | Jul 10, 23:25 UTC | Jul 11, 00:05 UTC | 40m |
| 2026-07-10 | N365LV | - | Jul 10, 14:25 UTC | Jul 10, 19:15 UTC | 4h 50m |
| 2026-07-07 | N365LV | LAS → TEB | Jul 7, 00:45 UTC | Jul 7, 05:10 UTC | 4h 25m |
| 2026-07-06 | N365LV | - | Jul 6, 20:05 UTC | Jul 6, 20:50 UTC | 45m |
| 2026-07-06 | N365LV | SFO → LAX | Jul 6, 07:40 UTC | Jul 6, 08:35 UTC | 55m |
| 2026-07-06 | N365LV | LAS → SFO | Jul 6, 03:40 UTC | Jul 6, 04:55 UTC | 1h 15m |
| 2026-06-28 | N365LV | - | Jun 28, 23:54 UTC | Jun 29, 00:34 UTC | 40m |
| 2026-06-28 | N365LV | - | Jun 28, 17:04 UTC | Jun 28, 17:50 UTC | 45m |
| 2026-06-26 | N365LV | - | Jun 26, 00:50 UTC | Jun 26, 02:44 UTC | 1h 55m |
| 2026-06-25 | N365LV | - | Jun 25, 22:20 UTC | Jun 26, 00:05 UTC | 1h 45m |
| 2026-06-25 | N365LV | LAS → SLC | Jun 25, 16:50 UTC | Jun 25, 17:49 UTC | 1h 0m |
| 2026-06-21 | N365LV | - | Jun 21, 22:04 UTC | Jun 22, 01:19 UTC | 3h 15m |
| 2026-06-19 | N365LV | BFI → SBM | Jun 19, 19:39 UTC | Jun 19, 22:39 UTC | 3h 0m |
| 2026-06-19 | N365LV | - | Jun 19, 07:54 UTC | Jun 19, 17:55 UTC | 10h 0m |
| 2026-06-19 | N365LV | - | Jun 19, 04:19 UTC | Jun 19, 05:05 UTC | 45m |
| 2026-06-13 | N365LV | - | Jun 13, 19:30 UTC | Jun 14, 06:00 UTC | 10h 30m |
| 2026-06-13 | N365LV | - | Jun 13, 16:35 UTC | Jun 13, 18:35 UTC | 2h 0m |
| 2026-06-09 | N365LV | - | Jun 9, 10:15 UTC | Jun 9, 21:40 UTC | 11h 25m |
| 2026-06-09 | N365LV | NCE → NCE | Jun 9, 09:45 UTC | Jun 9, 09:55 UTC | 10m |
| 2026-06-03 | N365LV | - | Jun 3, 05:00 UTC | Jun 3, 13:40 UTC | 8h 40m |
| 2026-06-03 | N365LV | - | Jun 3, 01:10 UTC | Jun 3, 04:15 UTC | 3h 5m |
| 2026-05-31 | N365LV | - | May 31, 21:05 UTC | Jun 1, 00:50 UTC | 3h 45m |
| 2026-05-30 | N365LV | - | May 30, 12:55 UTC | May 30, 16:15 UTC | 3h 20m |
| 2026-05-26 | N365LV | - | May 26, 21:00 UTC | May 26, 22:59 UTC | 2h 0m |
| 2026-05-26 | N365LV | - | May 26, 16:30 UTC | May 26, 20:15 UTC | 3h 45m |
| 2026-05-21 | N365LV | - | May 21, 20:25 UTC | May 21, 20:55 UTC | 30m |
| 2026-05-21 | N365LV | - | May 21, 12:30 UTC | May 21, 15:25 UTC | 2h 55m |
| 2026-05-17 | N365LV | - | May 17, 16:10 UTC | May 17, 18:50 UTC | 2h 40m |
| 2026-05-17 | N365LV | - | May 17, 04:55 UTC | May 17, 15:05 UTC | 10h 10m |
| 2026-05-16 | N365LV | - | May 16, 06:25 UTC | May 16, 07:51 UTC | 1h 25m |
| 2026-05-15 | N365LV | - | May 15, 23:30 UTC | May 16, 00:05 UTC | 35m |
| 2026-05-14 | N365LV | - | May 14, 02:20 UTC | May 14, 12:25 UTC | 10h 5m |
| 2026-05-13 | N365LV | - | May 13, 22:15 UTC | May 14, 00:10 UTC | 1h 55m |
| 2026-05-13 | N365LV | - | May 13, 20:25 UTC | May 13, 20:55 UTC | 30m |
| 2026-05-11 | N365LV | - | May 11, 05:30 UTC | May 11, 07:25 UTC | 1h 55m |
| 2026-05-10 | N365LV | - | May 10, 16:25 UTC | May 10, 20:35 UTC | 4h 10m |
| 2026-05-08 | N365LV | - | May 8, 17:00 UTC | May 8, 19:15 UTC | 2h 15m |
| 2026-05-03 | N365LV | - | May 3, 16:05 UTC | May 4, 02:50 UTC | 10h 45m |
| 2026-04-30 | N365LV | LAS → WAW | Apr 30, 02:10 UTC | Apr 30, 12:40 UTC | 10h 30m |
| 2026-04-27 | N365LV | - | Apr 27, 15:05 UTC | Apr 27, 19:50 UTC | 4h 45m |
| 2026-04-27 | N365LV | - | Apr 27, 11:50 UTC | Apr 27, 14:00 UTC | 2h 10m |
| 2026-04-24 | N365LV | - | Apr 24, 16:35 UTC | Apr 24, 17:55 UTC | 1h 20m |
| 2026-04-24 | N365LV | - | Apr 24, 14:45 UTC | Apr 24, 15:30 UTC | 45m |
| 2026-04-23 | N365LV | - | Apr 23, 17:45 UTC | Apr 23, 18:35 UTC | 50m |
| 2026-04-23 | N365LV | - | Apr 23, 13:35 UTC | Apr 23, 17:05 UTC | 3h 30m |
| 2026-04-20 | N365LV | - | Apr 20, 02:45 UTC | Apr 20, 03:25 UTC | 40m |
| 2026-04-16 | N365LV | - | Apr 16, 09:19 UTC | Apr 16, 09:54 UTC | 35m |
| 2026-04-14 | N365LV | - | Apr 14, 19:00 UTC | Apr 14, 20:45 UTC | 1h 45m |
| 2026-04-14 | N365LV | - | Apr 14, 16:50 UTC | Apr 14, 18:30 UTC | 1h 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 N365LV page for operator, model, and routing details .