Every number in this app’s library traces to something. This document says what, and — just as importantly — how strongly each number was verified during the build.
Read §1 before using any of these values in a publication.
Three levels are used throughout the data files:
| Level | Meaning |
|---|---|
| verified | Retrieved from the cited source during this build and checked figure-for-figure. |
| medium | Well-established published engineering practice, reproduced from the standard literature, but not opened against a primary document during this build. Check before publication use. |
| low | Representative of the vehicle type; not a specific model, not a cited figure. Adequate for illustrating a configuration, not for quoting. |
What was verified during this build:
What was NOT verified during this build:
W = 500[LN/(N−1) + 12N + 36].test/run.mjs, which independently confirms that a two-axle group at 4.0 ft
is allowed exactly 34 000 lb — the arithmetic origin of the statutory tandem
limit.src/core/tires.js compute aircraft tire dimensions arithmetically; and the
inch-nominal truck tire dimension table.Derived, and therefore reproducible:
DECISIONS.md §D7.Typical practice, confidence medium — check before quoting:
Low confidence — representative only:
Computed exactly from the designation — no table, no uncertainty:
445/50R22.5, 295/75R22.5,
LT245/75R16, …). Overall diameter follows arithmetically:
OD = rim + 2 × section × aspect.H44.5x16.5-21, 52x21.0R22, 1400x530R23, …).
The three-part designation encodes all three dimensions directly.Table lookup, in src/data/tires.json:
| Size | Confidence | Note |
|---|---|---|
11R22.5 |
high | 279 mm section / 1054 mm OD. The reference truck tire of the flexible-pavement literature; dimensions agree across the major medium-truck data books. |
11R24.5, 12R22.5, 10.00R20, 11.00R20, 9.00R20 |
medium | Reproduced from the standard truck-tire literature. Not checked against a TRA yearbook during this build. |
A size that is not in the table is reported by the app as unknown and
refuses to produce geometry. It is never guessed. Adding one requires a
source and a confidence field, and the test suite fails without them.
Static loaded radius. Two models are implemented and the choice is exposed:
radiusRatio (default): SLR = ratio × free radius, 0.97 truck / 0.965
aircraft. These defaults come from the build specification and are
user-adjustable. Confidence: medium — they are reasonable engineering
values, not a cited standard.sectionDeflection: SLR = free radius − deflection × section height, with
0.32 for aircraft, following the Tire and Rim Association convention that
aircraft tires are rated at a nominal 32 % deflection.The aircraft library ships in v1.2 with four Boeing aircraft spanning gear codes D, 2D and 3D: 737-800, 757-200, 767-400ER and 777-300ER.
An earlier attempt was abandoned because the sources could not be reached
(the FAA database returned 403 to the fetch tool, and the ACAP PDFs exceeded
its size limit). Both were tooling limits, not access limits: the FAA site
serves the spreadsheet normally to a browser user-agent, and the PDFs download
fine with curl. Every number below was retrieved and read directly.
| Quantity | Source |
|---|---|
Gear designation (Main_Gear_Config) |
FAA Aircraft Characteristics Database |
| Wheelbase, nose to main gear | FAA Aircraft Characteristics Database |
| Main gear outer width | FAA Aircraft Characteristics Database |
| MTOW | FAA Aircraft Characteristics Database |
| Maximum design taxi weight | Manufacturer ACAP, section 7.2 |
| Tire size and tire pressure, nose and main | Manufacturer ACAP, section 7.2 |
| Percent gross weight on the whole main gear (95 %) | FAA AC 150/5320-6G, G.1.3 |
ACAP editions used: 737 D6-58325-7 Rev C (Oct 2025), 757 D6-58327 Rev H (Dec 2024), 767 D6-58328 Rev K (Dec 2024), 777 D6-58329-2 Rev G (Dec 2024).
The FAA field is not the centreline tread. Its own data dictionary defines
Main_Gear_Width_ft as “Distance between outer tires in the main landing
gear.” Treating it as the track would push every main wheel outboard by half
a dual spacing plus half a tire — for a 777 that is nearly a metre per side,
and the figure would look entirely reasonable while being wrong.
So the track is derived, never assumed:
track = outerWidth − (wheelsAcross − 1) × dualSpacing − sectionWidth
Section width comes exactly from the three-part tire designation.
Nothing in that derivation uses the manufacturers’ separately published tread figures, so agreement between them is real corroboration rather than circularity. With the dual spacings recorded in the data files:
| Aircraft | Derived track | Manufacturer published tread | Difference |
|---|---|---|---|
| 737-800 | 5727 mm | 5715 mm (18 ft 9 in) | 12 mm |
| 757-200 | 7302 mm | 7315 mm (24 ft 0 in) | 13 mm |
| 767-400ER | 9322 mm | 9296 mm (30 ft 6 in) | 26 mm |
| 777-300ER | 10 963 mm | 10 973 mm (36 ft 0 in) | 10 mm |
All four agree to within a few centimetres, on quantities of 6 to 11 metres.
test/run.mjs asserts both the derivation and this cross-check.
Two quantities are not constrained by any source consulted:
Every aircraft unit lists these in assumedFields, the schema fails
validation if that array is missing, and the app shows an amber notice naming
them whenever an aircraft is loaded. Set them from FAARFIELD before using the
output for pavement work — and note that changing a dual spacing re-derives the
track, so the authoritative outer width is preserved whatever you enter.
The 747 (2D/2D2) and A380 (2D/3D2) are omitted. Their wing-plus-body gear layouts need the longitudinal and transverse offsets of the body gear relative to the wing gear. A single outer width closes a two-strut layout; it cannot close a four-bogie one. Including them would mean inventing geometry rather than deriving it, which is the one thing this library exists not to do.
Every axle carries a source string and every load a basis string, both
shown in the properties panel when you select an axle. Export unit.json
alongside any figure and the citations travel with it.
The test suite (npm test, 74 checks) fails the build if any axle, gear, load,
GVW, MTOW, tire pressure or multi-axle group spacing lacks provenance, and
includes a negative control that confirms the validator actually rejects a
missing source rather than passing vacuously.