aircraftGlobalType

complexType · extension complexBaseType · all

Top-level requirements and flight envelopes of the aircraft model

The global data hold the top-level aircraft requirements of the model, i.e. the values the design has to reach in range, payload, airport compatibility and flight performance, and the flight envelopes of the aircraft. Each requirement gives the required value and the value the design actually reaches (requirementType).

The example shows some of the requirements of a short-range airliner. Its flight envelope is shown in flightEnvelopeType.

<global>
    <designRange>
        <required>4600000</required>
        <actual>4750000</actual>
    </designRange>
    <payload>
        <paxSeats>
            <required>150</required>
            <actual>150</actual>
        </paxSeats>
        <cargoCapacity>
            <required>3000</required>
            <actual>3400</actual>
        </cargoCapacity>
    </payload>
    <airportCompatibility>
        <wingSpan>
            <required>36</required>
            <actual>34.1</actual>
        </wingSpan>
        <takeOffFieldLength>
            <required>2100</required>
            <actual>2050</actual>
        </takeOffFieldLength>
        ...
    </airportCompatibility>
    <performanceTargets>
        <cruiseMach>
            <required>0.78</required>
            <actual>0.78</actual>
        </cruiseMach>
        <maxOperatingAltitude>
            <required>11887</required>
            <actual>11887</actual>
        </maxOperatingAltitude>
        ...
    </performanceTargets>
    <flightEnvelopes>
        ...
    </flightEnvelopes>
</global>
Top-level requirements of a short-range airliner

Attributes

NameTypeConstraintsUseDefaultDescription
@externalDataDirectoryxsd:stringoptionalDirectory of the external file the element was read from, as URI
@externalDataNodePathxsd:stringoptionalPath of the parent element in the merged dataset, at which the element was inserted from an external file
@externalFileNamexsd:stringoptionalName of the external file the element was read from

Child elements

NameTypeConstraintsOccurrenceHow often the element may appear at this place. The schema writes it as minOccurs and maxOccurs on the declaration.DefaultDescription
allThe children below may appear in any order. Each may appear at most once.
designRangerequirementType[0..1] optionalDesign range, i.e. the range with maximum payload (point B of the payload-range diagram) [m]
payloadpayloadGlobalType[0..1] optionalPayload requirements
airportCompatibilityairportCompatibilityGlobalType[0..1] optionalAirport compatibility requirements
performanceTargetsperformanceTargetsGlobalType[0..1] optionalPerformance requirements
flightEnvelopesflightEnvelopesType[0..1] optionalFlight envelopes

Used by

In a dataset · 1 path

In the schema · 1 declaration

TypeName
aircraftModelTypeglobal