PartsPerk Resource Intelligence Hub™
AOG Sourcing Guide
When time matters, structure the request around part identity, urgency, location, document needs, and response windows.
What makes a request AOG
Aircraft on ground (AOG) signals operational urgency — not permission to skip verification. The goal is faster structured routing, not automatic promises from the network.
What to include immediately
Stable identity clues, quantity, location, needed-by window, contact path, and trace or export constraints reduce churn while teams qualify responses.
How PartsPerk prioritizes the path
Urgency, document posture, and identifier confidence change the default workflow order — RFQ, escalation lanes, trace review, or alternate discovery — while keeping humans in control.
Supplier response options
Suppliers may decline, propose alternates, or request clarifications. Expect structured follow-ups rather than a single monolithic quote on the first ping.
When to escalate to human review
Escalate when interchange, export, program-specific trace, or safety-critical applicability is unclear — automation should not substitute for engineering judgment.
Urgency timeline
Capture identity
PN, photo, or NSN clue
Time + place
Needed-by + ship-to region
Doc posture
Trace / export constraints
Response window
Who can approve award
AOG checklist
- Part number or photo
- Aircraft/platform
- Quantity
- Location
- Needed-by time
- Trace/document requirement
- Contact path
Say: “AOG, need [part], quantity [x], location [city], trace required.”
Related guides
- Aviation Parts GuideA quick reference for part numbers, NSNs, FSCs, CAGE codes, trace documents, and safe sourcing workflows — read when you want context; use Open Command or the tools below.
- NSN / FSC GuideUse NSN and FSC identifiers to narrow part context, but verify supply, condition, trace, and fit before quoting.
- Trace Documents GuideKnow which documents to request, what may be missing, and when a TraceFit review should happen before quote selection.