sensors Mode-S transponder
E49C7F
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-VMQ · PIPER PA-46-310/350
- Hex
- E49C7F
- Octal
- 71116177
- Decimal
- 14,982,271
- Country
- BR
- Tail
- PS-VMQ
- Type
- PA46
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address E49C7F falls within the block assigned to Brazil (BR) by ICAO Annex 10, Volume III. Every aircraft registered in Brazil 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 |
|---|---|---|---|
| PSVMQ | - | 52 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | PSVMQ | - | Jul 10, 21:35 UTC | Jul 10, 22:05 UTC | 30m |
| 2026-07-10 | PSVMQ | - | Jul 10, 18:20 UTC | Jul 10, 18:50 UTC | 30m |
| 2026-07-02 | PSVMQ | - | Jul 2, 18:05 UTC | Jul 2, 19:10 UTC | 1h 5m |
| 2026-07-02 | PSVMQ | - | Jul 2, 11:20 UTC | Jul 2, 12:30 UTC | 1h 10m |
| 2026-06-26 | PSVMQ | - | Jun 26, 18:29 UTC | Jun 26, 19:24 UTC | 55m |
| 2026-06-26 | PSVMQ | - | Jun 26, 15:25 UTC | Jun 26, 16:20 UTC | 55m |
| 2026-06-26 | PSVMQ | - | Jun 26, 12:39 UTC | Jun 26, 13:19 UTC | 40m |
| 2026-06-26 | PSVMQ | - | Jun 26, 10:15 UTC | Jun 26, 11:05 UTC | 50m |
| 2026-06-23 | PSVMQ | - | Jun 23, 20:10 UTC | Jun 23, 21:14 UTC | 1h 5m |
| 2026-06-23 | PSVMQ | - | Jun 23, 09:34 UTC | Jun 23, 10:29 UTC | 55m |
| 2026-06-09 | PSVMQ | - | Jun 9, 14:10 UTC | Jun 9, 14:40 UTC | 30m |
| 2026-06-08 | PSVMQ | - | Jun 8, 15:35 UTC | Jun 8, 16:05 UTC | 30m |
| 2026-06-08 | PSVMQ | - | Jun 8, 13:00 UTC | Jun 8, 13:35 UTC | 35m |
| 2026-06-06 | PSVMQ | - | Jun 6, 13:30 UTC | Jun 6, 14:04 UTC | 35m |
| 2026-06-06 | PSVMQ | - | Jun 6, 12:10 UTC | Jun 6, 12:45 UTC | 35m |
| 2026-06-04 | PSVMQ | - | Jun 4, 18:40 UTC | Jun 4, 19:10 UTC | 30m |
| 2026-06-04 | PSVMQ | - | Jun 4, 17:15 UTC | Jun 4, 17:45 UTC | 30m |
| 2026-05-30 | PSVMQ | - | May 30, 15:30 UTC | May 30, 16:00 UTC | 30m |
| 2026-05-29 | PSVMQ | - | May 29, 20:05 UTC | May 29, 20:35 UTC | 30m |
| 2026-05-19 | PSVMQ | - | May 19, 15:30 UTC | May 19, 16:00 UTC | 30m |
| 2026-05-19 | PSVMQ | - | May 19, 12:25 UTC | May 19, 12:50 UTC | 25m |
| 2026-05-18 | PSVMQ | - | May 18, 20:40 UTC | May 18, 21:15 UTC | 35m |
| 2026-05-18 | PSVMQ | - | May 18, 18:35 UTC | May 18, 19:05 UTC | 30m |
| 2026-05-14 | PSVMQ | - | May 14, 19:00 UTC | May 14, 19:35 UTC | 35m |
| 2026-05-14 | PSVMQ | - | May 14, 17:45 UTC | May 14, 18:15 UTC | 30m |
| 2026-05-13 | PSVMQ | - | May 13, 00:50 UTC | May 13, 01:25 UTC | 35m |
| 2026-05-12 | PSVMQ | - | May 12, 23:20 UTC | May 12, 23:55 UTC | 35m |
| 2026-05-06 | PSVMQ | - | May 6, 21:10 UTC | May 6, 21:40 UTC | 30m |
| 2026-05-06 | PSVMQ | - | May 6, 19:30 UTC | May 6, 20:05 UTC | 35m |
| 2026-05-06 | PSVMQ | - | May 6, 13:15 UTC | May 6, 13:40 UTC | 25m |
| 2026-05-06 | PSVMQ | - | May 6, 11:20 UTC | May 6, 12:01 UTC | 40m |
| 2026-05-05 | PSVMQ | - | May 5, 20:20 UTC | May 5, 20:50 UTC | 30m |
| 2026-05-05 | PSVMQ | - | May 5, 19:00 UTC | May 5, 19:35 UTC | 35m |
| 2026-04-30 | PSVMQ | - | Apr 30, 21:40 UTC | Apr 30, 22:10 UTC | 30m |
| 2026-04-30 | PSVMQ | - | Apr 30, 19:05 UTC | Apr 30, 20:20 UTC | 1h 15m |
| 2026-04-30 | PSVMQ | - | Apr 30, 13:15 UTC | Apr 30, 14:00 UTC | 45m |
| 2026-04-29 | PSVMQ | - | Apr 29, 13:15 UTC | Apr 29, 13:45 UTC | 30m |
| 2026-04-29 | PSVMQ | - | Apr 29, 11:25 UTC | Apr 29, 12:15 UTC | 50m |
| 2026-04-26 | PSVMQ | - | Apr 26, 12:45 UTC | Apr 26, 13:20 UTC | 35m |
| 2026-04-26 | PSVMQ | - | Apr 26, 11:10 UTC | Apr 26, 11:50 UTC | 40m |
| 2026-04-25 | PSVMQ | - | Apr 25, 22:00 UTC | Apr 25, 22:35 UTC | 35m |
| 2026-04-25 | PSVMQ | - | Apr 25, 19:30 UTC | Apr 25, 20:05 UTC | 35m |
| 2026-04-24 | PSVMQ | - | Apr 24, 20:25 UTC | Apr 24, 20:40 UTC | 15m |
| 2026-04-24 | PSVMQ | - | Apr 24, 17:35 UTC | Apr 24, 17:55 UTC | 20m |
| 2026-04-21 | PSVMQ | - | Apr 21, 11:05 UTC | Apr 21, 11:40 UTC | 35m |
| 2026-04-21 | PSVMQ | - | Apr 21, 09:40 UTC | Apr 21, 10:15 UTC | 35m |
| 2026-04-18 | PSVMQ | - | Apr 18, 21:20 UTC | Apr 18, 21:55 UTC | 35m |
| 2026-04-18 | PSVMQ | - | Apr 18, 19:05 UTC | Apr 18, 19:40 UTC | 35m |
| 2026-04-15 | PSVMQ | - | Apr 15, 12:10 UTC | Apr 15, 12:40 UTC | 30m |
| 2026-04-14 | PSVMQ | - | Apr 14, 17:55 UTC | Apr 14, 18:20 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 PS-VMQ page for operator, model, and routing details .