Not currently tracked · last seen Jul 24, 13:00 UTC
- Flights observed
- 35
- Avg flight time
- 48m
- Typical route
- -
- Last seen
- Jul 24, 13:00 UTC
Last known area
Recent flights last 35
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-24 | - | Jul 24, 12:45 UTC | Jul 24, 13:00 UTC | 15m |
| 2026-07-23 | - | Jul 23, 21:20 UTC | Jul 23, 23:25 UTC | 2h 5m |
| 2026-07-20 | - | Jul 20, 18:50 UTC | Jul 20, 20:25 UTC | 1h 35m |
| 2026-07-18 | - | Jul 18, 12:55 UTC | Jul 18, 14:05 UTC | 1h 10m |
| 2026-07-17 | - | Jul 17, 21:50 UTC | Jul 17, 22:45 UTC | 55m |
| 2026-07-08 | - | Jul 8, 14:45 UTC | Jul 8, 15:10 UTC | 25m |
| 2026-06-30 | - | Jun 30, 15:15 UTC | Jun 30, 15:35 UTC | 20m |
| 2026-06-30 | - | Jun 30, 13:45 UTC | Jun 30, 14:15 UTC | 30m |
| 2026-06-22 | - | Jun 22, 14:59 UTC | Jun 22, 15:10 UTC | 10m |
| 2026-06-21 | - | Jun 21, 13:44 UTC | Jun 21, 14:30 UTC | 45m |
| 2026-06-20 | - | Jun 20, 02:04 UTC | Jun 20, 02:54 UTC | 50m |
| 2026-06-18 | - | Jun 18, 01:20 UTC | Jun 18, 02:10 UTC | 50m |
| 2026-06-14 | - | Jun 14, 13:35 UTC | Jun 14, 14:25 UTC | 50m |
| 2026-06-04 | - | Jun 4, 17:55 UTC | Jun 4, 19:20 UTC | 1h 25m |
| 2026-06-04 | - | Jun 4, 15:20 UTC | Jun 4, 16:35 UTC | 1h 15m |
| 2026-06-04 | - | Jun 4, 14:25 UTC | Jun 4, 14:50 UTC | 25m |
| 2026-06-01 | - | Jun 1, 14:30 UTC | Jun 1, 15:25 UTC | 55m |
| 2026-05-31 | - | May 31, 13:10 UTC | May 31, 13:45 UTC | 35m |
| 2026-05-27 | - | May 27, 20:10 UTC | May 27, 21:05 UTC | 55m |
| 2026-05-27 | - | May 27, 19:00 UTC | May 27, 19:30 UTC | 30m |
| 2026-05-27 | - | May 27, 13:25 UTC | May 27, 13:45 UTC | 20m |
| 2026-05-26 | - | May 26, 22:29 UTC | May 26, 22:54 UTC | 25m |
| 2026-05-26 | - | May 26, 18:10 UTC | May 26, 18:40 UTC | 30m |
| 2026-05-24 | - | May 24, 13:20 UTC | May 24, 14:05 UTC | 45m |
| 2026-05-22 | - | May 22, 17:40 UTC | May 22, 17:50 UTC | 10m |
| 2026-05-22 | - | May 22, 15:05 UTC | May 22, 16:45 UTC | 1h 40m |
| 2026-05-22 | - | May 22, 12:15 UTC | May 22, 13:50 UTC | 1h 35m |
| 2026-05-19 | - | May 19, 19:45 UTC | May 19, 20:15 UTC | 30m |
| 2026-05-18 | - | May 18, 17:30 UTC | May 18, 18:15 UTC | 45m |
| 2026-05-17 | - | May 17, 13:25 UTC | May 17, 14:35 UTC | 1h 10m |
| 2026-05-11 | - | May 11, 17:25 UTC | May 11, 18:10 UTC | 45m |
| 2026-04-27 | - | Apr 27, 15:20 UTC | Apr 27, 16:05 UTC | 45m |
| 2026-04-26 | - | Apr 26, 21:10 UTC | Apr 26, 22:10 UTC | 1h 0m |
| 2026-04-26 | - | Apr 26, 18:35 UTC | Apr 26, 19:00 UTC | 25m |
| 2026-04-17 | - | Apr 17, 16:10 UTC | Apr 17, 16:45 UTC | 35m |
Specifications
| Registration | N207SL |
| Operator | CIRRUS DESIGN CORP |
| Mode-S code | A1AD9F · 50326637 (octal) |
Looking for transponder-level data? View the Mode-S A1AD9F page for country allocation, callsign history, and ADS-B signal details.
N207SL frequently asked
Who operates N207SL?
N207SL is operated by CIRRUS DESIGN CORP.
What is the Mode-S transponder code for N207SL?
N207SL broadcasts on Mode-S (ICAO 24-bit) address A1AD9F (octal 50326637). View the transponder page.
Where is N207SL right now?
N207SL is not currently being tracked; last seen Jul 24, 13:00 UTC.