sensors Mode-S transponder
A7FA00
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N613BD · DASSAULT Falcon 2000 · operated by LYNX MEDICAL TRANSPORT LLC
- Hex
- A7FA00
- Octal
- 51775000
- Decimal
- 11,008,512
- Country
- US
- Tail
- N613BD
- Type
- F2TH
- Flights observed
- 44
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Current position
Country allocation
The ICAO 24-bit address A7FA00 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 |
|---|---|---|---|
| PGN613 | - | 44 | 2026-07-13 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | PGN613 | - | Jul 13, 11:40 UTC | Jul 13, 13:05 UTC | 1h 25m |
| 2026-07-12 | PGN613 | LUK → EWR | Jul 12, 17:20 UTC | Jul 12, 18:50 UTC | 1h 30m |
| 2026-07-05 | PGN613 | YYZ → LUK | Jul 5, 21:30 UTC | Jul 5, 22:40 UTC | 1h 10m |
| 2026-07-03 | PGN613 | - | Jul 3, 14:45 UTC | Jul 3, 15:50 UTC | 1h 5m |
| 2026-06-22 | PGN613 | - | Jun 22, 23:39 UTC | Jun 23, 01:25 UTC | 1h 45m |
| 2026-06-22 | PGN613 | - | Jun 22, 20:49 UTC | Jun 22, 22:10 UTC | 1h 20m |
| 2026-06-15 | PGN613 | OPF → LUK | Jun 15, 14:30 UTC | Jun 15, 15:59 UTC | 1h 30m |
| 2026-06-15 | PGN613 | OPF → LUK | Jun 15, 04:04 UTC | Jun 15, 06:35 UTC | 2h 30m |
| 2026-06-14 | PGN613 | OPF → LUK | Jun 14, 13:05 UTC | Jun 14, 15:30 UTC | 2h 25m |
| 2026-06-13 | PGN613 | OPF → LUK | Jun 13, 20:30 UTC | Jun 13, 22:05 UTC | 1h 35m |
| 2026-06-09 | PGN613 | OPF → LUK | Jun 9, 21:20 UTC | Jun 9, 22:00 UTC | 40m |
| 2026-06-08 | PGN613 | OPF → LUK | Jun 8, 13:00 UTC | Jun 8, 13:40 UTC | 40m |
| 2026-06-07 | PGN613 | OPF → LUK | Jun 7, 22:30 UTC | Jun 7, 23:45 UTC | 1h 15m |
| 2026-06-07 | PGN613 | OPF → LUK | Jun 7, 21:25 UTC | Jun 7, 22:05 UTC | 40m |
| 2026-06-07 | PGN613 | OPF → LUK | Jun 7, 14:10 UTC | Jun 7, 14:50 UTC | 40m |
| 2026-06-06 | PGN613 | OPF → LUK | Jun 6, 20:14 UTC | Jun 6, 22:20 UTC | 2h 5m |
| 2026-06-01 | PGN613 | OPF → LUK | Jun 1, 02:20 UTC | Jun 1, 03:40 UTC | 1h 20m |
| 2026-05-31 | PGN613 | OPF → LUK | May 31, 18:05 UTC | May 31, 19:20 UTC | 1h 15m |
| 2026-05-26 | PGN613 | OPF → LUK | May 26, 21:09 UTC | May 27, 01:09 UTC | 4h 0m |
| 2026-05-26 | PGN613 | OPF → LUK | May 26, 18:10 UTC | May 26, 18:34 UTC | 25m |
| 2026-05-25 | PGN613 | OPF → LUK | May 25, 14:40 UTC | May 25, 18:50 UTC | 4h 10m |
| 2026-05-20 | PGN613 | OPF → LUK | May 20, 18:30 UTC | May 20, 20:15 UTC | 1h 45m |
| 2026-05-20 | PGN613 | OPF → LUK | May 20, 03:35 UTC | May 20, 05:05 UTC | 1h 31m |
| 2026-05-19 | PGN613 | OPF → LUK | May 19, 19:25 UTC | May 19, 21:00 UTC | 1h 35m |
| 2026-05-19 | PGN613 | OPF → LUK | May 19, 16:50 UTC | May 19, 18:20 UTC | 1h 30m |
| 2026-05-19 | PGN613 | OPF → LUK | May 19, 02:40 UTC | May 19, 03:15 UTC | 35m |
| 2026-05-18 | PGN613 | OPF → LUK | May 18, 21:30 UTC | May 18, 22:10 UTC | 40m |
| 2026-05-13 | PGN613 | OPF → LUK | May 13, 21:05 UTC | May 13, 21:35 UTC | 30m |
| 2026-05-13 | PGN613 | OPF → LUK | May 13, 16:25 UTC | May 13, 16:50 UTC | 25m |
| 2026-05-12 | PGN613 | OPF → LUK | May 12, 02:50 UTC | May 12, 04:25 UTC | 1h 35m |
| 2026-05-11 | PGN613 | OPF → LUK | May 11, 19:05 UTC | May 11, 20:30 UTC | 1h 25m |
| 2026-05-08 | PGN613 | OPF → LUK | May 8, 03:09 UTC | May 8, 04:44 UTC | 1h 35m |
| 2026-05-07 | PGN613 | OPF → LUK | May 7, 19:55 UTC | May 7, 21:15 UTC | 1h 20m |
| 2026-05-06 | PGN613 | OPF → LUK | May 6, 20:36 UTC | May 6, 22:55 UTC | 2h 19m |
| 2026-05-03 | PGN613 | OPF → LUK | May 3, 17:10 UTC | May 3, 19:25 UTC | 2h 15m |
| 2026-05-03 | PGN613 | OPF → LUK | May 3, 15:20 UTC | May 3, 16:20 UTC | 1h 0m |
| 2026-04-27 | PGN613 | OPF → LUK | Apr 27, 06:00 UTC | Apr 27, 07:05 UTC | 1h 5m |
| 2026-04-27 | PGN613 | OPF → LUK | Apr 27, 01:55 UTC | Apr 27, 03:00 UTC | 1h 5m |
| 2026-04-19 | PGN613 | OPF → LUK | Apr 19, 21:15 UTC | Apr 19, 22:55 UTC | 1h 40m |
| 2026-04-19 | PGN613 | OPF → LUK | Apr 19, 18:00 UTC | Apr 19, 19:35 UTC | 1h 35m |
| 2026-04-15 | PGN613 | OPF → LUK | Apr 15, 02:55 UTC | Apr 15, 04:30 UTC | 1h 35m |
| 2026-04-15 | PGN613 | OPF → LUK | Apr 15, 00:15 UTC | Apr 15, 00:35 UTC | 20m |
| 2026-04-14 | PGN613 | OPF → LUK | Apr 14, 20:55 UTC | Apr 14, 21:40 UTC | 45m |
| 2026-04-14 | PGN613 | OPF → LUK | Apr 14, 20:15 UTC | Apr 14, 20:50 UTC | 35m |
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 N613BD page for operator, model, and routing details .