N725QS — Bombardier Challenger 300
No tracked position on file
Registered since 2025.
History
No flight history is loaded for this tail.
The aircraft
Airframe
- Type
- Bombardier Challenger 300
- Make and model on the certificate
- BOMBARDIER INC BD-100-1A10
- Category and class
- Fixed wing, multi engine · 2 × turbofan
- Serial
- 20663
- Built
- 2016
- Engines
- HONEYWELL AS907-2-1A
- Seats
- 8
- Airworthiness
- Dec 20, 2016
- Type certificate
- T00005NY
Identity
- Registration
- N725QS
- Mode-S hex
- A9B78E
Registration
- Registrant
- Owner withheld
- Address of record
- No location
- FAA status
- Valid
- Certificate issued
- Jul 21, 2025
- Registration expires
- Jul 31, 2032
- Registry
- United States
FAA Registry N725QS, snapshot Nov 9, 2026.
Title history
- N725QS assigned — first registration
- Registered to Owner withheld
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | Owner withheld | No location | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Aug 17, 2026 | Part 135 listing — Listed under NetJets Aviation, Inc., certificate DXTA Seen 2026-08-17 through 2026-11-09 across 9 dated FAA workbooks. Still on the current list. |
| Apr 19, 2024 | Part 135 listing — Listed under NetJets Aviation, Inc., certificate DXTA Seen 2024-04-19 through 2026-05-01 across 9 dated FAA workbooks. Gone from the list by 2026-08-04. |
Attribution
RegistrantOwner withheld · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Built from JetSweep’s retained FAA registry snapshots, sourced from FAA Registry N725QS (snapshot Nov 9, 2026). Dates shown are FAA recording and snapshot dates — the day a filing was indexed or a difference was first observed, not necessarily the day the underlying transaction happened. Part 135 rows come from dated workbook retrievals and bound a listing, never date it. We track the aircraft, not who is aboard.
Registration records show registrants, not beneficial owners; FAA recording dates lag transactions. How we source this →