Airlines & aviation
One flight changes.
Follow the connections.
Bring schedules, aircraft rotations, passenger journeys and source documents into an operations application.
An arrival is part of a bigger picture.
Start from the flight record, then explore the relationships or documents relevant to the task.
flight:207Which later legs share this aircraft?
aircraft:12rotation:07flight:318Traverse the rotation, then load schedule and crew-assignment records for the connected legs.
Illustrative records. Your application assembles this context for the operations team; the team chooses the next action.
5 use cases / Airlines & aviation
The right modalities for your workflow.
Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.
- SQL Filter, join and aggregate records
- Graph Follow relationships between records
- FTS · Full-text search Find keywords, phrases and exact wording
- Vector Find similar items or meaning
| Use case | Recommended modalities | Why this combination fits |
|---|---|---|
| Disruption context Trace a disrupted flight to its connections and passenger records. | SQL retrieves flight status and itinerary fields. Graph follows route and connection relationships for the operations application. | |
| Maintenance evidence retrieval Connect an aircraft or component to work records and technical documents. | SQL selects work records, Graph follows asset and component links, and FTS searches technical references and maintenance notes. | |
| Flight operations reporting Review delays, service activity and operational status by route. | SQL filters flight records by date, airport and status, then groups operational totals and delay durations. | |
| Passenger service knowledge Retrieve relevant service rules and procedural guidance. | FTS matches rule terminology, Vector finds guidance related to a question, and SQL supplies itinerary context and document versions. | |
| Baggage journey exploration Connect a baggage record to scans, flights and transfer points. | SQL retrieves scan events and timestamps. Graph follows the recorded relationships between baggage, flights and transfer locations. |
Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.
Four models, specific roles
Keep the record.
Add the context.
Use stable flight, aircraft, itinerary and document IDs to connect representations in your application.
Inside the database- SQL
- Filter schedules, bookings and service records by their fields.Query records
- Graph
- Traverse aircraft rotations, connected legs and passenger itineraries.Model relationships
- Vector
- Find related case notes using embeddings supplied by your application.Search similar notes
- Full-text
- Match procedure terms, document titles and exact reference codes.Find exact wording
Implementation path
Start with one flight workflow.
- 01 / Model
Define IDs and relations.
Register the source schemas and the connections your application needs to follow.
- 02 / Index
Prepare the search data.
Write source rows, supply document embeddings and index selected text through separate calls.
- 03 / Assemble
Return useful evidence.
Combine query results by ID, load source details and show their update time or document revision.
Keep ingestion progress explicit so retries and source updates reach the relevant search entries.
See the ingestion pattern