Aircraft family
Aircraft reference
Identify the airframe.
Then follow the parts path.
Aircraft profiles establish the model and variant context behind a parts search. They stay separate from the parts directories so each page answers one clear job.
Model reference Coverage index
Hawker aircraft families.
These are the site coverage paths, not effectivity statements. Each model profile will document its variant scope and source basis before technical claims are indexed.
Aircraft family
Hawker 750
750 model research pathAircraft family
Hawker 800XP
800 and 800XP research pathAircraft family
Hawker 850XP
850XP model research pathAircraft family
Hawker 900XP
900XP model research pathAircraft family
Hawker 1000
1000 and 1000B research pathAircraft family
Hawker 125 Series
DH, HS, and BAe 125 family research pathTwo search intents
Aircraft context and parts discovery do different work.
What aircraft or variant am I researching?
The aircraft path covers model identity, variant scope, systems context, source notes, and links into the appropriate parts directories.
Browse aircraft families ↗Which records belong to this model and system?
The parts path organizes verified records by aircraft and system, then points to the single canonical record for each normalized part number.
Open Hawker parts ↗Profile quality gate
Model names are not interchangeable shortcuts.
A profile has to state which model and variant names it covers, keep unsupported overlap out, and send part searches into the right directory. Serial effectivity belongs beside the claim it limits.
- 01Name the model
Use the preferred model name and record the relevant naming variants.
- 02State the scope
Separate a family overview from model-specific application and effectivity.
- 03Connect the records
Link the profile to its parts directory, systems, sources, FAQs, and updates.