Bombardier Challenger 604 · representative
N605MM — Bombardier Challenger 604
No tracked position on file
Registered since 2025.
History
No flight history is loaded for this tail.
The aircraft
Airframe
- Type
- Bombardier Challenger 604
- Make and model on the certificate
- BOMBARDIER INC CL-600-2B16
- Category and class
- Fixed wing, multi engine · 2 × turbofan
- Serial
- 5769
- Built
- 2008
- Engines
- GE CF34-3B
- Seats
- 22
- Airworthiness
- Mar 26, 2009
Identity
- Registration
- N605MM
- Mode-S hex
- A7DAF1
Registration
- Registrant
- AA NOT E LLC
- Address of record
- NEW YORK, NY
- FAA status
- Valid
- Certificate issued
- Apr 29, 2025
- Registration expires
- Apr 30, 2032
- Registry
- United States
FAA Registry N605MM, snapshot Nov 8, 2026.
Title history
- N605MM assigned — first registration
- Registered to AA NOT E LLC
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | AA NOT E LLC | New York, NY | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Nov 22, 2025 | Part 135 listing — Listed under TALON AIR, LLC, certificate OZTA Seen 2025-11-22 through 2026-11-09 across 12 dated FAA workbooks. Still on the current list. |
| Apr 19, 2024 | Part 135 listing — Listed under Sunset Aviation LLC, certificate 7SSA Seen 2024-04-19 through 2025-04-28 across 6 dated FAA workbooks. Gone from the list by 2025-10-06. |
Attribution
RegistrantAA NOT E LLC · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Built from JetSweep’s retained FAA registry snapshots, sourced from FAA Registry N605MM (snapshot Nov 8, 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 →