This playbook defines how MRO brokers use JETNET API data to identify aircraft requiring maintenance, evaluate certifications and maintenance history, and monitor airworthiness over time. It provides guidance for applying aircraft and operator data in support of maintenance analysis, compliance review, and recommendation workflows.
Key Principles
Bulk-first analysis: Use bulk data access to evaluate aircraft health and maintenance posture across fleets before drilling into individual records.
Compliance as a filter, not an afterthought: Certifications and maintenance history should be evaluated early to eliminate non-viable aircraft.
CRM-ready outputs: Aircraft and company data should be structured for downstream tracking, analysis, and recommendation workflows.
Objectives and Endpoint Use Cases
| Objective | Core Endpoint(s) | Outcome |
|---|---|---|
| Aircraft Discovery |
getAircraftList, getBulkAircraftExport
|
Identify aircraft needing maintenance or approaching scheduled service |
| Technical Vetting & Assessment |
getAirframe, getEngine, getAvionics, getFeatures, getAdditionalEquipment, getInterior, getExterior
|
Assess airframe, engine, avionics, and cabin condition |
| Maintenance & Certification Check | getMaintenance |
Verify airworthiness, certifications, maintenance schedule, and compliance |
| Operator & Contact Insights |
getCondensedOwnerOperators, getCompanyRelationships
|
Map aircraft to operators, owners, and key contacts |
| Flight & Event History Review |
getFlights, getEventList, getHistoryList
|
Track operational hours, cycles, incidents, and modifications |
| Market Intelligence & Trend Analysis |
getModelIntelligence, getModelMarketTrends
|
Analyze model reliability, service intervals, downtime patterns, and market activity |
| Visual Verification | getAircraft |
Confirm aircraft condition visually, including interior/exterior, prior to maintenance engagement |