One language for the flight bag
Aeronautic models connect editable plans, navigation data, recorded flights and weather. Use this library to choose the right object, preserve its meaning across clients, and validate what you read or write.
Start with planning documents: the native producer, portable JSON contracts and independent readers are implemented. The wider catalog records existing owners and the remaining interoperability work for each family.
Build with a model
| Your task | Start here |
|---|---|
| Save a plan, calculate a leg and draw an accepted result | Planning quickstart |
| Integrate an internal engine or service adapter | Native API |
| Import fixes, procedures, airways or airspace | Navigation model layers |
| Work with observations, forecasts, Weather Fusion or MOS | Weather semantics |
| Record a flight or connect a track to a trip | Trips and recorded tracks |
| Design or extend a shared model | Model conventions |
Know what you are adopting
The model catalog names each owner, contract version, consumer and validation entry point. Contract means a versioned contract with executable validation exists; internal means a working owner implementation with portability work still to do; audited means the current representation has been inspected and its known gaps recorded. These labels describe engineering maturity, not operational data suitability.
There is no universal model version or single installable SDK. Compatibility is explicit per family. Begin with the source-backed examples, use the owning validators, and keep source observations separate from derived results and map presentation.