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