Boeing · Narrowbody

Boeing 737

Three generations of 737 in one application, from the Classic through the NG to the MAX, with the freighter conversions and the BBJ versions alongside them.

Coverage

What is supported

Operators rarely run a single 737 generation. A fleet that mixes Classics, NGs and MAX aircraft is handled as one fleet in one application: the crew opens the same interface whichever airframe they are on, and the calculation resolves against the registration in front of them.

  • Every generation in the same application, with no separate tool per sub-fleet
  • Calculations resolved against the individual registration and its current configuration
  • MEL and CDL penalties applied inside the calculation, not bolted on afterwards
TYPE · COVERAGE
ICAO TYPES
B733 B734 B735 B736 B737 …
SUPPORTED
CONFIGURATION
2 × turbofan
MODELLED
WAKE CATEGORY
M
SET
PERFORMANCE
Offline
COVERED
Variants

Every version in the family

The designators below are the ICAO type codes the application recognises for this family. Freighter conversions fly on the same data as the passenger aircraft.

PERFORMANCE · OFFLINE
ENGINE
One calculation
SHARED
RUNWAYS
Usable runways & intersections
COMPUTED
MEL / CDL
Applied in the calculation
ACTIVE
RECORD
Retained in JAWS
LOGGED
Offline performance

Calculations that work with no connectivity

Takeoff and landing performance is computed on the device itself. No connectivity is required at the aircraft, which is what makes the calculation dependable at an outstation or on a stand with no signal.

  • Takeoff and landing calculations computed on the device, with no connectivity required
  • Usable runways and intersections for the actual registration
  • MEL and CDL penalties applied inside the calculation
  • Every calculation logged and retained in DS JAWS
Weight & balance

One signed loadsheet for the crew

A mixed 737 fleet is where a shared loadsheet earns its keep. Each generation carries its own weight and balance data, maintained by your administrators and published centrally, but the crew sees one sheet and one signature whichever aircraft they are assigned.

  • Built on the fleet data your administrators maintain and publish
  • Signed on the flight deck together with the NOTOC
  • Late changes recalculated and re-signed on the current edition
  • Every edition retained for audit
LOADSHEET · STATE
FLEET DATA
AHM 565, held in JAWS
PUBLISHED
LOADSHEET
Subscribed or by hand
CURRENT
SIGNATURE
Biometric, with the NOTOC
SIGNED
LATE CHANGE
Recalculated and re-signed
IN STEP

Flying the Boeing 737?

We will show you the type running in our application, on your procedures and your fleet data. The rest of your fleet comes with it: our engine is not tied to a single data source, so a mixed fleet stays one workflow for the crew.