AEROWAY TECHNICAL REFERENCE
STD: 29.92 inHg
AEROWAY.ORGREF-01
Aeronautical Reference Architecture
MATHEMATICAL CLASSIFICATIONS & VERIFICATIONPublished: Framework Audited:

Calculation Methodology & Engineering Standards

Aeroway establishes an uncompromising boundary between theoretical mathematical physics, standardized aviation authority procedures, and practical pilot rules-of-thumb.

01 //The Four Mathematical Exactness Classes

Exact Mathematical Model

exact_model

Exact within the stated mathematical model and assumptions (e.g. 2D vector wind triangle, runway crosswind trigonometry, scalar time-speed-distance). Represents theoretical kinematic physics, while real-world conditions remain subject to atmospheric turbulence and sensor variability.

Representative Model: Crosswind = WindSpeed × |sin(Δ)|

Standardized Reference Method

standardized_reference

Implementation follows a codified civil aviation procedure or standardized international atmospheric table (e.g. ICAO Doc 7488 geopotential lapse, TERPS departure gradient calculations).

Representative Model: ICAO Standard Atmosphere barometric geopotential formulas

Engineering Approximation

engineering_approximation

A simplified empirical relationship intentionally used for pilot-facing convenience where full thermodynamic modeling is impractical without airborne sensor suites (e.g. 120 × (OAT - ISA) for density altitude, 2.5°C spread for cloud base). Never represented as exact.

Representative Model: Cloud Base AGL ≈ (Spread °C / 2.5) × 1,000 ft

Screening Estimate

screening_estimate

Rough order-of-magnitude estimation intended solely for educational and preliminary planning checks. Must never be used in place of approved aircraft flight manuals or official operational procedures.

Representative Model: 3:1 rule of thumb for top of descent

02 //Unit Conventions & Precision Boundary

1. Internal Canonical Precision: All calculation engines execute on native double-precision floating point numbers without premature intermediate rounding.

2. Presentation Boundary Rounding: Rounding is applied solely at the UI presentation boundary according to physical significance (e.g. 1 decimal for crosswinds, whole feet for pressure altitude).

3. Explicit Unit Labels: Every input and output must explicitly declare its unit of measurement. Silent conversions or implicit assumptions are strictly prohibited.

03 //Aviation Safety Language Standard

Aeroway UI components use conservative, factual terminology:

AUTHORIZED TERMINOLOGY:
  • "Estimated value"
  • "Calculated component"
  • "Reference value under selected assumptions"
  • "Verify against applicable AFM/POH"
PROHIBITED CLAIMS:
  • "Safe to fly"
  • "Approved for flight"
  • "Legal to depart"
  • "Within aircraft limits" (without AFM data)

04 //Multi-Jurisdictional Regulatory Framework (FAA · EASA · ICAO)

A core principle of the Aeroway architecture is strict regulatory isolation. We never assume United States FAA rules apply universally to pilots operating in Europe, the United Kingdom, or under ICAO Annex mandates.

1. Mandatory Jurisdiction Labeling:

Whenever a regulatory calculation mode is activated (e.g. minimum fuel reserves or cloud distance minimums), the receiving engine must visibly identify the governing rule: e.g. FAA 14 CFR § 91.151 versus EASA Part-NCO.OP.125.

2. Dual Barometric & Unit Standards:

Altimetry and weather modules support both U.S. customary units (inHg) and European/ICAO standard units (hPa / millibars) with exact 33.8639 hPa/inHg conversion factors.

3. Harmonized PIC Authority Disclaimers:

Safety notices cite both 14 CFR § 91.3 and EASA NCO.GEN.105, reminding aviators in all jurisdictions that digital calculators never supersede Pilot-in-Command authority or approved Aircraft Flight Manual (AFM/POH) limitations.