N800EM — Hawker 800
Landed Raleigh/Durham, NC
4 trips since December 2024 · home field Raleigh/Durham.
History
- A four-stop jet trip may explain UNC Officials' belichick-day travel4h 37mGreensboro, NC → home, with Atlantic City and Baltimore stops
Where it goes
| Raleigh/Durham, NC — home field | 1 trip |
The aircraft
Airframe
- Type
- Hawker 800
Identity
- Registration
- N800EM
- Mode-S hex
- AAE24D
- Last tracked
- Dec 12, 2024
Registration
- Registrant
- Montana Aircraft Trust
- Registry
- United States
Title history
- Sold: DRAGONS FLIGHT LLC → MONTANA AIRCRAFT TRUST INC TRUSTEE
- Sold: MONTANA AIRCRAFT TRUST INC TRUSTEE → not listed
- Registered to Montana Aircraft Trust
Owner history
| Years | Registered owner | Where | How it ended |
|---|---|---|---|
| Present | Montana Aircraft Trust | Not recorded | Open — still the registered owner of record |
Every filing
| Date | Filing |
|---|---|
| Sep 1, 2026 | Dropped out of the FAA registry snapshot |
| Jul 29, 2026 | Sold — DRAGONS FLIGHT LLC → MONTANA AIRCRAFT TRUST INC TRUSTEE Now registered to a corporation in Bozeman, MT; previously co-owners in High Point, NC. Also recorded: other names on the registration changed. 13 fields changed
|
| Apr 19, 2024 | Part 135 listing — Listed under KOURY AVIATION, INC., certificate 3KUA Seen 2024-04-19 through 2025-11-22 across 8 dated FAA workbooks. Gone from the list by 2026-05-01. |
Full ownership file and every filing.
Jump Seat · $15/monthAttribution
RegistrantMontana Aircraft Trust · FAA record
Attribution reflects public context; registration records show registrants, not passengers.
Built from JetSweep’s retained FAA registry snapshots. 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 →