Commercial aerospace OEMs Lingo

Aircraft Program Architecture

Clean-Sheet Program

A clean-sheet program starts with a substantially new aircraft or major product architecture rather than modifying an existing certified design. It normally requires a new type certificate, extensive development testing, a new industrial system, and significant non-recurring investment.

Clean-sheet does not mean every component is new. OEMs deliberately reuse proven equipment, design methods, and supplier technology. The expression signals that the program lacks the certification, production, and in-service inheritance enjoyed by a derivative. When executives call an idea clean-sheet, finance usually hears a large funding requirement and engineering hears several years of unresolved interfaces.

Derivative

A derivative is a new model or variant developed from an existing product. Common examples include stretches, shrinks, freighters, higher-weight versions, re-engined aircraft, and equipment variants based on an established platform.

Derivatives are often certified through an amended type certificate, but the label is commercial and architectural, not itself a certification category. The business case usually depends on inherited design, commonality, and a shorter development schedule. Newcomers sometimes assume a derivative is a minor modification. Some derivatives replace wings, engines, systems, and large portions of the certification basis, making derivative a surprisingly elastic word.

Type Design

The type design is the controlled technical definition of a certificated product. It includes the drawings, specifications, materials, processes, structural and system definitions, airworthiness limitations, and other data needed to establish conformity with the approved design.

The type design is not merely the three-dimensional model or engineering bill of material. It is the approved configuration against which aircraft, engines, and propellers are shown to conform. Changes affecting it require controlled approval because the type certificate holder remains responsible for the continued integrity of that design.

Aircraft Family and Commonality

An aircraft family consists of related models that share enough architecture, systems, parts, production methods, or operating characteristics to create economic commonality. OEMs may discuss cockpit commonality, pilot commonality, spares commonality, maintenance commonality, or common type ratings.

These are not interchangeable claims. Two models can share a marketing family while requiring different pilot type ratings or carrying substantially different maintenance programs. In an airline campaign, commonality often means lower transition and fleet-mixing costs. In engineering, it may mean constraining a new model to preserve interfaces that everyone would otherwise prefer to redesign.

Launch Customer

The launch customer is an early customer whose commitment helps justify program launch and often influences the initial specification. For an engine or equipment OEM, the equivalent may be a launch airline, launch airframer application, or lead customer.

The launch customer is not necessarily the first operator to receive the product. Certification delays, airline readiness, production sequencing, or customer-specific issues can change delivery order. Early influence may also come with risk: the launch customer gets a product shaped around its requirements, along with the operational discovery process politely known as entry into service.

Authority to Offer

Authority to Offer, usually abbreviated ATO, is an internal approval allowing the commercial organization to make defined product, price, performance, schedule, or configuration commitments to customers. The exact governance varies by OEM.

ATO is not program launch, certification approval, or a customer order. It means the organization believes the proposed commitment is sufficiently mature to sell under specified assumptions. A proposal outside ATO limits may require special engineering, industrial, financial, or executive approval. In practice, this is where an attractive sales idea encounters weight, certification, lead time, and physics.

Configuration Freeze

A configuration freeze is a program milestone at which a defined portion of the product configuration is treated as stable enough for downstream design, tooling, procurement, certification, or production work. Programs may have separate freezes for overall architecture, customer definition, systems interfaces, cabin content, and detailed design.

Freeze does not mean changes stop. It means later changes become formally controlled and increasingly expensive. When a team says a requirement arrived after freeze, the subtext is usually that schedule protection, rework, certification impact, and commercial responsibility are about to be discussed.

Block Point

A block point is a planned production effectivity at which a coordinated package of design, supplier, software, or manufacturing changes enters the build stream. Rather than incorporating every change aircraft by aircraft, the OEM establishes a controlled configuration boundary.

Block points simplify planning and fleet configuration, but only if the required parts, data, tooling, and approvals arrive together. Missing the block point can mean deferring the change, retrofitting completed aircraft, or creating travelled work. Hearing that a modification is “targeting the next block point” usually means its technical merit is only one part of the decision.

Type Certification

Type Certificate

A Type Certificate, or TC, is the aviation authority’s approval of a product type design and its demonstrated compliance with the applicable airworthiness standards. Aircraft, aircraft engines, and propellers can each have their own TCs.

The TC approves the design, not every physical unit automatically produced from it. Individual products must conform to the approved design and be in a condition for safe operation. The TC holder also carries continuing obligations, including addressing unsafe conditions and maintaining approved design data.

Production Certificate

A Production Certificate, or PC in the United States, authorizes production under an approved quality system for products conforming to an approved type design. EASA uses Production Organisation Approval, or POA, within its own regulatory framework.

The easiest distinction is that the TC concerns the approved design, while the production approval concerns the organization’s ability to reproduce conforming products. Having one does not silently grant the other. This distinction becomes very real when production configuration, supplier control, or conformity evidence is questioned.

Amended Type Certificate

An amended type certificate approves a change to an existing type design under the original TC rather than creating a completely separate certificate. Derivative models are frequently handled this way.

The certification basis for the change is determined through changed-product rules, such as 14 CFR 21.101 or EASA Part 21 provisions. The authority decides which existing standards may remain and where later amendment levels apply. “It is only an amended TC” therefore does not mean the original certification basis carries forward untouched.

Supplemental Type Certificate

A Supplemental Type Certificate, or STC, approves a major change to a type-certificated product when the change is not handled solely under the original TC holder’s normal change approval. Cabin conversions, connectivity installations, auxiliary fuel systems, and cargo conversions commonly use STCs.

An OEM can hold an STC, although independent modification houses often do. An STC is not the same as a service bulletin: the STC is an approval of design data, while a service bulletin provides incorporation instructions and related information. Ownership of the underlying approval matters when later changes or continued-airworthiness actions are required.

Type Certificate Data Sheet

The Type Certificate Data Sheet, or TCDS, summarizes the approved product models, defining characteristics, operating limitations, approved engines or propellers, certification basis, and other conditions associated with the TC.

It is a useful regulatory map, but it is not the entire type design. Practitioners consult it to confirm exactly which model, rating, limitation, or certification standard applies. A marketing family name may cover several models, while the TCDS preserves the distinctions that certification engineers care about.

Certification Basis

The certification basis is the specific set of regulations, amendment levels, special conditions, equivalent-safety findings, exemptions, and other requirements against which a product or change will be approved.

It is established for the product and then refined as novel features and changes are understood. An “open certification basis” means key requirements or interpretations remain unresolved, which can affect architecture and test planning. This is not regulatory paperwork trailing behind engineering; it can determine what must be designed in the first place.

Means of Compliance

A Means of Compliance, or MoC, is the accepted method used to demonstrate that a certification requirement has been satisfied. Methods include analysis, inspection, laboratory testing, ground testing, flight testing, simulation, equipment qualification, and formal compliance statements.

The requirement answers what must be shown; the MoC answers how it will be shown. A persuasive engineering analysis may be insufficient if the agreed MoC calls for a conforming flight test. Do not confuse this with an Alternative Method of Compliance, or AMOC, which is an approved alternative for meeting an Airworthiness Directive.

Issue Paper and Certification Review Item

An Issue Paper is commonly used in FAA certification, while a Certification Review Item, or CRI, is common in EASA projects. Both are formal mechanisms for documenting and resolving significant certification questions, interpretations, novel features, or compliance positions.

An open issue paper or CRI may contain competing technical and regulatory positions rather than a missing signature. Closure can require new analysis, design changes, or tests. When a certification review says “three CRIs remain open,” the useful follow-up is what decisions they control, not merely when someone expects to close them.

Special Condition and Equivalent Level of Safety

A special condition adds tailored airworthiness standards when existing regulations do not adequately address a novel or unusual design feature. An Equivalent Level of Safety, or ELOS, finding accepts an alternative that provides safety equivalent to the intent of an existing rule.

They solve different problems. A special condition fills a regulatory gap; an ELOS addresses compliance with a rule whose literal method is not being followed. Both become part of the certification basis and can drive substantial design and test work.

Conformity

Conformity establishes that a test article, installation, part, or aircraft matches the controlled design data and configuration intended for an official compliance demonstration. Authorities or authorized designees document conformity before credit is given to specified tests.

A test can produce excellent technical data and still fail to earn certification credit if the article was not conforming or its configuration was inadequately recorded. In meetings, “we need conformity” usually means the team must lock hardware, software, instrumentation, drawings, and inspection evidence before testing proceeds.

Type Inspection Authorization and Report

A Type Inspection Authorization, or TIA, is an FAA mechanism authorizing specified official inspections, ground tests, and flight tests for a certification program. The associated Type Inspection Report, or TIR, records the results and findings.

The TIA is not a general permission to begin development testing. It identifies the configuration, prerequisites, limitations, and official test activity for which certification credit is sought. Reaching TIA readiness usually signals that design maturity, conformity, safety reviews, and test procedures have converged sufficiently for authority-facing work.

ODA, DOA, and POA

In the United States, Organization Designation Authorization, or ODA, allows an approved organization to perform specified functions on behalf of the FAA under oversight. In the EASA system, Design Organisation Approval, or DOA, recognizes design capability and grants defined privileges; Production Organisation Approval, or POA, addresses production capability.

These are not exact regulatory equivalents, and none means the authority has surrendered oversight. Certain findings may remain authority-retained, while others can be made by authorized personnel. A practical question is always: who has the formal finding authority for this compliance item?

Systems Safety and Development Assurance

SAE ARP4754A

SAE ARP4754A provides guidance for developing civil aircraft and systems, including requirements capture, architecture, validation, verification, configuration control, and development assurance. Authorities commonly recognize it as an acceptable framework for complex aircraft programs.

ARP4754A is concerned with disciplined development at aircraft and system level, not just document production. When a team says a change has a “4754 impact,” it may need requirements tracing, safety reassessment, verification, and renewed configuration evidence across several system levels.

SAE ARP4761A

SAE ARP4761A provides methods supporting aircraft and system safety assessment. It covers processes such as Functional Hazard Assessment, Preliminary System Safety Assessment, System Safety Assessment, and common-cause analyses.

Safety assessment is iterative. Early results influence architecture; later assessments verify that the implemented design meets allocated safety objectives. Treating it as a report written after design completion misses the point and usually creates an unpleasant late-program rediscovery of redundancy requirements.

Functional Hazard Assessment

A Functional Hazard Assessment, or FHA, identifies aircraft or system functions, considers failure conditions, and classifies their effects. Typical severity classifications include catastrophic, hazardous, major, minor, and no safety effect.

These words have formal meanings and drive development rigor, probability objectives, independence, and architecture. “Catastrophic” does not mean very inconvenient; it indicates effects such as multiple fatalities or loss of the aircraft. The FHA begins with functional effects, before assuming a particular hardware solution.

Preliminary System Safety Assessment

The Preliminary System Safety Assessment, or PSSA, evaluates whether the proposed system architecture can satisfy the safety objectives derived from the FHA. It examines redundancy, independence, monitoring, failure propagation, and preliminary quantitative allocations.

The PSSA is architecture-facing. If it shows that two supposedly independent channels share power, software, sensors, or installation zones, the design may need to change. That is why safety engineers become interested in physical routing and supplier interfaces much earlier than newcomers often expect.

System Safety Assessment

The System Safety Assessment, or SSA, evaluates the implemented system and supporting evidence to show that safety requirements and objectives have been met. It uses verified failure rates, design details, analyses, and test results.

The PSSA asks whether the planned architecture should work; the SSA asks whether the completed implementation demonstrably does. Closing the SSA can be blocked by apparently small items such as unresolved supplier failure-rate data, software configuration differences, or incomplete independence evidence.

Development Assurance Level

A Development Assurance Level, or DAL, establishes the rigor required to reduce the likelihood of development errors that could contribute to a failure condition. Levels generally run from A, the most rigorous, through E, where no safety effect is involved.

Programs may distinguish functional and item development assurance allocations, often using terms such as FDAL and IDAL. DAL is not a measure of component quality or probability of random hardware failure. It controls the discipline and evidence applied to development, verification, independence, and configuration management.

Common Cause Analysis

Common Cause Analysis, or CCA, examines failures that can defeat supposedly independent systems or protections. It commonly includes Zonal Safety Analysis, Particular Risk Analysis, and Common Mode Analysis.

Examples include fire affecting multiple channels in one zone, a shared power source, common software logic, lightning exposure, rotor burst, fluid leakage, or maintenance errors applied to redundant equipment. Redundancy is impressive on a block diagram; CCA asks whether the real aircraft installed both channels next to the same hazard.

DO-178C and DO-254

RTCA DO-178C addresses airborne software development assurance, while RTCA DO-254 addresses airborne electronic hardware such as complex programmable devices. Both use assurance levels linked to the safety consequences of failure.

Neither standard is simply a test specification. They require lifecycle evidence covering planning, requirements, design, implementation, verification, configuration management, and quality assurance. Supplier statements that software is “DO-178 compliant” deserve a follow-up question about level, approved plans, certification credit, and available lifecycle data.

DO-160

RTCA DO-160 defines environmental test conditions and procedures for airborne equipment. Categories address temperature, altitude, vibration, power input, radio-frequency susceptibility, lightning effects, electrostatic discharge, fluids, sand, dust, and other environments.

A piece of equipment is qualified to a particular set of DO-160 categories, not generically “DO-160 certified.” The required categories depend on installation location and aircraft environment. Moving equipment to a different zone can therefore invalidate assumptions even when the box itself is unchanged.

Flight Test

Iron Bird

An iron bird is a ground-based integration rig containing representative aircraft systems, wiring, hydraulics, flight controls, actuators, computers, and simulated interfaces. It allows engineers to exercise system interactions before and during flight testing.

The name survives even when much of the rig is software and electronics. It is used for integration, failure testing, control-law verification, troubleshooting, and regression work. An issue found on the iron bird is usually cheaper than the same issue found at altitude, which is among the more dependable truths in aircraft development.

System Integration Rig

A System Integration Rig, or SIR, is a laboratory setup used to integrate and test selected systems, equipment, networks, or software. It may include real hardware, simulated equipment, hardware-in-the-loop components, and representative aircraft data buses.

An SIR is normally narrower than a full iron bird, although terminology varies by OEM. Teams use multiple rigs at different fidelities. When test results conflict, the first question is often whether the rig had the correct hardware, software load, database, and interface simulation.

Flight Test Vehicle and FTI

A Flight Test Vehicle, or FTV, is an aircraft assigned to development or certification testing. Flight Test Instrumentation, or FTI, includes sensors, wiring, recording systems, telemetry, ballast, and special equipment installed to collect test data.

Different FTVs may be configured for aerodynamics, performance, systems, cabin, icing, fatigue, or propulsion testing. Their configurations can diverge significantly from production aircraft. Converting an FTV for sale later can require extensive removal, rework, conformity, and record reconciliation.

Test Point and Test Card

A test point is a defined aircraft condition or maneuver used to collect evidence. A test card translates the objective into a controlled sequence covering configuration, entry conditions, actions, tolerances, hazards, data requirements, and termination criteria.

A single flight may contain many test points, but weather, aircraft serviceability, instrumentation, airspace, or unexpected behavior can prevent completion. Counting scheduled points as completed evidence is a familiar planning temptation and an unreliable one.

Envelope Expansion

Envelope expansion is the progressive exploration and clearance of an aircraft’s operating range, including speed, altitude, weight, center of gravity, load factor, configuration, and environmental conditions.

Testing proceeds incrementally from known safe conditions toward intended limits, supported by analysis and real-time monitoring. A first flight therefore uses a deliberately restricted envelope. “The aircraft has flown” is a meaningful milestone, but it is not evidence that the aircraft has demonstrated its full certified capability.

Flutter Clearance

Flutter is a potentially unstable interaction among aerodynamic forces, structural elasticity, and inertia. Flutter clearance uses analysis, ground vibration testing, and carefully controlled flight testing to show adequate stability margins across the required envelope.

Because flutter can become destructive rapidly, test points use disciplined build-up and monitoring. Changes to mass distribution, stiffness, external shapes, control surfaces, or stores can reopen flutter questions. A seemingly modest installation change can therefore have aircraft-level consequences.

Development Test and Certification Test

Development testing explores behavior, finds problems, and matures the design. Certification testing produces accepted evidence that specific regulatory requirements have been met, generally using conforming articles and approved procedures.

The same flight or ground event may support both purposes, but certification credit requires the right configuration, documentation, witnessing, and data integrity. Calling a successful development result “basically certified” is a reliable way to make a certification specialist become very precise.

Configuration Management

ATA Chapter

ATA chapters organize aircraft systems and maintenance information using standardized numbering. Examples include Chapter 21 for air conditioning, 24 for electrical power, 27 for flight controls, 32 for landing gear, and 72 for engine sections.

Practitioners often identify a problem by chapter rather than by organizational owner. The chapter structure appears in technical publications, reliability reports, work packages, parts data, and customer discussions. “It is an ATA 27 issue” immediately places the conversation in the flight-control domain.

Effectivity

Effectivity identifies the products, serial numbers, models, customer configurations, or production ranges to which a part, drawing, modification, document, or instruction applies.

An technically correct change with incorrect effectivity can send the wrong part or instruction to the wrong aircraft. Practitioners therefore ask for effectivity before assuming a service bulletin, repair, or modification applies. Fleet-wide rarely means every aircraft without qualification.

Modification Standard

A modification standard, often shortened to mod standard, describes the incorporated set or level of approved design changes on an aircraft, assembly, system, or component.

Two units with the same base part number may behave differently because they embody different modifications. Troubleshooting, interchangeability, software loading, and retrofit planning all depend on knowing the mod standard. “Same model” is often too coarse a description for useful engineering work.

As-Designed, As-Built, and As-Delivered

As-designed describes the approved engineering definition. As-built records what production actually installed, including approved deviations and repairs. As-delivered reflects the configuration accepted by the customer after production changes, completion work, and delivery actions.

These states should reconcile, but they are not conceptually identical. Later support also depends on the operator’s as-maintained configuration. Many difficult investigations are configuration investigations wearing a technical-problem costume.

Interchangeability

Interchangeability describes whether one part or configuration can replace another without unacceptable alteration or loss of function. It may be two-way, one-way, conditional, or limited by effectivity.

Physical fit is not enough. Software compatibility, certification status, performance, wiring, maintenance instructions, and future removability may all matter. A replacement can be approved as a successor without being fully interchangeable in every application.

Supersedure

Supersedure is the controlled replacement of one part number, document, or configuration by another for procurement, support, or design purposes. It can be one-way or involve specified conditions.

Supersedure does not automatically prove drop-in interchangeability. A new part may require an associated kit, software load, wiring change, or companion modification. Supply systems often show the latest procurable item, while engineering data controls whether it can actually be installed.

Dash Number

A dash number is the suffix used to identify a specific variant of a part or assembly within a part-number family. A changed dash number may represent different geometry, material, software, rating, interface, or approved application.

The difference between -001 and -003 may be trivial or certification-critical. Practitioners do not infer compatibility merely because the base number matches. The applicable drawing, effectivity, and interchangeability data control.

Interface Control Document

An Interface Control Document, or ICD, defines the physical, electrical, data, functional, environmental, and installation boundaries between systems or organizations.

ICDs are central when equipment comes from different suppliers. A requirement can be satisfied inside each individual box while the integrated system still fails because the interface assumptions disagree. “The ICD is not stable” means several teams may be designing against moving boundaries.

Layout of Passenger Accommodations

The Layout of Passenger Accommodations, or LOPA, is the controlled cabin layout showing seats, aisles, exits, galleys, lavatories, partitions, monuments, and other interior features.

The LOPA affects more than aesthetics. It connects customer configuration to evacuation, weight and balance, oxygen, electrical loads, emergency equipment, crew procedures, and certification. Moving a monument a few inches can acquire a remarkably large supporting cast.

Supplier Industrialization

Risk-Sharing Partner

A Risk-Sharing Partner, or RSP, takes responsibility for a major program work package and contributes development funding, engineering resources, tooling, or industrial investment. Recovery is commonly linked to future production shipsets.

An RSP carries more program exposure than a conventional build-to-print supplier. The structure can reduce the prime OEM’s up-front funding but creates deep dependencies on partner design maturity, financial health, capacity, and configuration control. Risk has been shared, not removed.

Build-to-Print and Design-and-Build

A build-to-print supplier manufactures to detailed OEM-controlled design data. A design-and-build supplier develops detailed equipment or structure against allocated requirements and interface constraints.

The distinction determines who owns design decisions, substantiation, change data, intellectual property, and recurring technical support. Even where a supplier owns detailed design, the type certificate holder retains responsibility for aircraft-level compliance. Commercial responsibility and airworthiness responsibility do not always stop at the same organizational boundary.

Shipset

A shipset is the complete quantity of a supplier’s parts, equipment, or assemblies required for one aircraft or engine. Pricing, demand, shortages, and production rates are frequently expressed per shipset.

One shipset may contain two landing gear assemblies, hundreds of brackets, or a complete avionics suite. “Three shipsets short” describes aircraft-level exposure, not three individual missing parts. Shipset definitions must also follow model and configuration differences.

BFE and SFE

Buyer-Furnished Equipment, or BFE, is selected or procured by the airline and supplied for installation, subject to OEM approval and interface requirements. Seller-Furnished Equipment, or SFE, is procured and supplied by the airframer as part of the aircraft offering.

The boundary affects price, lead-time responsibility, warranty routing, certification data, logistics, and schedule exposure. A late BFE seat or connectivity unit can still stop an OEM delivery line, even though the OEM did not purchase it. Ownership of the purchase order does not eliminate integration consequences.

Source Control Drawing

A Source Control Drawing, or SCD, defines an item whose detailed design is controlled by an approved source while the OEM controls required performance, interfaces, qualification, and approved-source status.

SCD items are common where supplier proprietary technology is involved. Changing source is not a routine purchasing substitution because qualification, certification evidence, and interface compatibility may be source-specific.

AS9100

AS9100 is the aerospace quality management system standard built on ISO 9001 with additional aviation, space, and defense requirements. Major commercial OEMs generally require relevant suppliers to maintain accredited systems and satisfy additional customer-specific requirements.

AS9100 certification does not approve a particular part or prove compliance with every OEM requirement. It establishes the management-system foundation. Product approval still depends on design data, process qualification, inspection, conformity, and customer authorization.

AS9102 First Article Inspection

First Article Inspection, or FAI, under AS9102 verifies that the production process can produce an item conforming to the full engineering definition. The documented output is commonly called a First Article Inspection Report, or FAIR.

FAI is not merely inspecting the first unit off the line. It accounts for all drawing characteristics, materials, processes, and referenced requirements. A full or partial FAI may be triggered by design, source, tooling, process, location, or production-interruption changes.

Key Characteristic

A key characteristic is a product feature or process parameter whose variation has a significant effect on fit, performance, service life, safety, or manufacturability and therefore requires focused variation control.

It is not simply another name for a tight tolerance or critical part. The designation drives process monitoring and control planning. Practitioners care about demonstrated process stability, not just whether the latest inspected unit happened to fall inside limits.

Special Process and Nadcap

A special process produces results that cannot be fully verified through later inspection alone. Heat treatment, welding, chemical processing, coatings, non-destructive testing, and some composite processes are common examples.

Nadcap provides industry accreditation for many such processes. Accreditation is important but may not replace OEM-specific approval, personnel qualification, or process-source restrictions. Moving work to another approved-looking facility can still require formal validation and customer consent.

Delegated Product Release Verification

Delegated Product Release Verification, or DPRV, allows qualified supplier personnel to perform specified product-release verification activities on behalf of an OEM under a controlled delegation program.

DPRV is not a general transfer of acceptance responsibility. It depends on approved individuals, scope, training, records, and continuing oversight. Loss or suspension of delegation can create immediate shipment constraints even when production itself continues.

Final Assembly and Delivery

Final Assembly Line

The Final Assembly Line, or FAL, is where major aircraft sections, systems, interiors, engines, and customer configuration converge into completed aircraft. Depending on the OEM, earlier structural assembly and later completion work may sit outside the formal FAL boundary.

FAL performance reflects the maturity of the entire upstream system. A missing supplier part, late software load, unresolved drawing, or cabin change eventually becomes visible on the aircraft. The line is therefore less a factory island than the place where the program’s accumulated promises meet one another.

MSN and Line Number

A Manufacturer Serial Number, or MSN, uniquely identifies an aircraft in the manufacturer’s system. A line number, often abbreviated LN, identifies its position in a production sequence. OEM nomenclature differs, and engines and major equipment have their own serial-number systems.

MSN, line number, customer sequence, registration, and delivery order are not necessarily the same. Practitioners use MSN or LN to establish exact configuration and effectivity. A customer name alone is rarely precise enough.

Pulse Line and Takt

A pulse line moves aircraft or major assemblies between stations at planned intervals. Takt is the production rhythm required to match output demand, often expressed as available production time per unit.

Aircraft lines may pulse every few days rather than every few minutes, but the logic is the same. Missing a station’s work window can create out-of-sequence or travelled work. Increasing rate therefore requires more than asking each station to work faster; suppliers, tooling, staffing, test capacity, and rework loops must all support the new rhythm.

Join-Up

Join-up is the assembly milestone at which major structural sections, such as the forward fuselage, center fuselage, aft body, and wings, are physically joined.

The term sounds simple but depends on dimensional control, interface readiness, drilling, fastening, systems routing, and completed upstream work. Misalignment or incomplete section work at join-up can generate expensive downstream disruption because the aircraft has become substantially less convenient to take apart.

Travelled Work

Travelled work, also written traveled work, is unfinished work that moves with an aircraft or assembly beyond the station where it was planned to be completed.

Some travelled work is deliberately managed, but high levels signal disruption. Downstream teams must work around completed installations, compete for access, and reconcile records across stations. A line can appear to maintain pulse while unfinished work accumulates inside each moving aircraft.

Out-of-Sequence Work

Out-of-sequence work is performed in a different order or location from the approved production plan because of shortages, design changes, access constraints, defects, or schedule recovery actions.

It often takes longer than in-sequence work and can create additional inspection or configuration risk. A missing bracket may appear minor until installing it later requires removing insulation, wiring, cabin panels, and the optimism of several planning assumptions.

Green Aircraft

A green aircraft is a structurally and mechanically advanced aircraft that has not yet received some combination of final paint, cabin completion, customer equipment, or delivery finishing. The exact boundary varies among market segments and OEMs.

Green-aircraft delivery is common where a separate completion center installs a highly customized interior. In airline production discussions, the term may describe an aircraft at a pre-completion stage rather than a separately sold product. Always ask what work remains within the local definition.

Power-On

Power-on is the production milestone at which electrical power is first applied to defined aircraft systems in a controlled configuration. It enables system activation, software loading, troubleshooting, and functional testing.

The milestone requires more than connecting electricity. Wiring status, grounding, safety precautions, equipment configuration, and test procedures must be ready. A successful initial power-on does not mean every system is operational; it means the integration problem has become electrically visible.

Weight on Wheels

Weight on Wheels, or WoW, is a physical production milestone at which the aircraft is supported on its own landing gear rather than assembly tooling. In systems discussions, the same phrase can refer to landing-gear sensors indicating whether the aircraft is on the ground.

Context matters because the production milestone and the aircraft logic signal are different concepts. The WoW signal affects functions such as braking, thrust reversers, pressurization, and flight-control modes, making erroneous indications a serious integration issue.

Production Flight Test and Customer Acceptance Flight

A Production Flight Test, or PFT, verifies that an individual production aircraft functions correctly and is ready for delivery. A Customer Acceptance Flight, or CAF, allows the customer to participate in evaluating the aircraft against agreed acceptance criteria.

Neither is the same as developmental certification flight testing. Findings may create rectification work, contractual discussion, or another flight. Technical acceptance is usually documented before contractual delivery, title transfer, or revenue recognition, although the precise sequence depends on the purchase agreement.

Production Nonconformance

Nonconformance Record

A Nonconformance Record, often called an NCR, documents a product, material, process, or record that does not meet the applicable requirement. Organizations also use terms such as discrepancy report or quality notification.

The record preserves traceability from detection through technical disposition and closure. An NCR does not automatically mean the item is unusable; it means normal acceptance cannot proceed until authorized personnel determine what happens next.

Material Review Board

In production quality, the Material Review Board, or MRB, is the authorized function that evaluates nonconforming material and approves permitted dispositions within delegated limits.

Do not confuse it with the Maintenance Review Board used to develop scheduled maintenance requirements. Aerospace uses the same three letters for two materially different activities, apparently to ensure newcomers remain attentive. Production MRB authority is tightly controlled because its decisions can affect type-design conformity.

Rework and Repair

Rework returns an item to full conformity with the original engineering requirements using approved processes. A repair restores an acceptable condition but does not necessarily return the item to the original design definition.

The distinction affects engineering approval, records, interchangeability, fatigue substantiation, and future maintenance. Polishing a surface back within drawing limits may be rework; adding a doubler to restore structural capability is generally a repair.

Use-As-Is

A use-as-is disposition accepts a specific nonconforming item without physical correction because authorized engineering evaluation shows that it remains fit for its intended application.

It does not redefine the drawing requirement for future production. The acceptance applies to the identified item and configuration unless the design is separately changed. Repeated use-as-is dispositions usually prompt the question of whether the process or design requirement itself needs correction.

Deviation, Concession, and Waiver

A deviation commonly authorizes a planned departure from a requirement before manufacture or installation. A concession generally accepts a known nonconformance after it has occurred. Waiver is used by some organizations for similar customer or authority acceptance.

Terminology varies, so the controlling procedure matters more than casual usage. The essential questions are whether the departure is prospective or retrospective, who has approval authority, which serial numbers are covered, and whether regulatory approval is implicated.

Quality Escape

A quality escape occurs when a nonconformance passes beyond the control point where it should have been detected. Supplier escapes reach the OEM; internal escapes reach later production stages; delivered escapes reach customers or the operating fleet.

Severity depends on the condition, affected population, and containment point. An escape triggers effectivity analysis and containment because the discovered unit may not be the only one. “We have an escape” often means serial-number tracing has just become the most important activity in the room.

Suspected Unapproved Part

A Suspected Unapproved Part, or SUP, is a part suspected of lacking the required approval, eligibility, documentation, or production source for installation on a certificated product.

A SUP is not necessarily counterfeit, and an authentic-looking part is not necessarily approved. Practitioners examine source, traceability, release documents, modification status, life records, and installation eligibility. The issue is airworthiness approval, not merely whether the part physically exists and appears serviceable.

Orderbook and Skyline

LOI, MOU, and Firm Order

A Letter of Intent, or LOI, and Memorandum of Understanding, or MOU, record preliminary commercial intent but generally precede the fully executed purchase agreement that supports a firm order. Announcement practices differ among OEMs.

A firm order is materially stronger, but not immutable. Purchase agreements contain conditions precedent, cancellation rights, performance protections, and delivery remedies. In market reporting, ask whether an announcement is a commitment, a firm order, or already included in the published orderbook.

Option and Purchase Right

An option gives a customer a contractual right to acquire additional units under defined pricing, timing, and exercise conditions. A purchase right is usually less committed or less specific, although terminology varies by OEM agreement.

Neither is normally included in firm backlog until exercised and recorded as an order. Options can still influence long-range capacity planning because exercising them may provide access to valuable delivery positions. Headline fleet potential is therefore often larger than contractual backlog.

Backlog

Backlog is the set of undelivered firm orders recognized under the OEM’s orderbook rules. It may be expressed in units or estimated value.

Backlog is not guaranteed future revenue. It depends on customer credit, contractual rights, financing, product performance, escalation, and the OEM’s ability to deliver. A large backlog supports production visibility, but the quality, timing, and profitability of that backlog matter as much as the count.

Gross Orders and Net Orders

Gross orders count new firm orders booked during a period. Net orders adjust gross orders for cancellations, conversions, and other removals under the OEM’s reporting method.

Conversions between models can complicate interpretation because the family total may stay stable while individual model demand changes. Market discussions often celebrate gross orders and quietly footnote net orders. Capacity planning ultimately cares about the executable mix.

Delivery Slot and Position

A delivery slot is capacity allocated for a product within a future production period. A delivery position is the customer’s contractual or planned place within that capacity.

Positions can carry strategic value when popular models are sold out for years. They are not always freely transferable, and a calendar-year commitment may not identify a precise production sequence. Protecting a slot usually requires timely payments, specification decisions, and satisfaction of contractual milestones.

Skyline

The skyline is the time-phased view of planned production and deliveries by model, customer, configuration, and status. It shows how the orderbook occupies future capacity.

Commercial teams use it to place campaigns; operations use it to plan mix and rate; finance uses it to anticipate deliveries and cash. A skyline can contain firm customers, reserved positions, internal assumptions, and gaps. Before treating it as fact, ask what status categories are included.

Deferral

A deferral moves a contracted delivery to a later period without necessarily cancelling the order. Deferrals may result from airline capacity plans, financing, infrastructure, product delays, or negotiated restructuring.

For the OEM, a deferral creates more than a date change. It can open a near-term production gap, alter payment timing, disrupt customer-specific material, and require another buyer for the original slot. Whether the position can be backfilled is usually the economic question.

White Tail

A white tail is an aircraft produced or materially advanced without a committed end customer, often because an original customer defaulted, cancelled, or could not accept delivery. The name comes from the absence of customer livery.

White tails create financing and remarketing exposure, especially when cabin, engine, or equipment choices are customer-specific. A nominally available aircraft may need expensive reconfiguration before another airline can use it.

Book-to-Bill

Book-to-bill compares orders booked with revenue recognized or units delivered during a period. A value above 1.0 generally indicates that orders exceeded the period’s output; below 1.0 indicates backlog contraction.

The metric is directional, not a complete demand diagnosis. Large campaigns, cancellations, mix, escalation, and accounting conventions can distort short periods. In commercial aerospace, unit book-to-bill and value book-to-bill may tell different stories because product prices differ substantially.

Program Economics

Pre-Delivery Payments

Pre-Delivery Payments, or PDPs, are customer payments made before aircraft delivery according to a contractual milestone schedule. They help finance working capital and demonstrate the customer’s continuing commitment.

PDP treatment, refundability, security, and default rights depend on the purchase agreement. For customers, PDPs create financing needs before the aircraft generates revenue. For OEMs, a delayed delivery can postpone the final payment while leaving substantial customer cash subject to contractual obligations.

Escalation Formula

Commercial aerospace purchase agreements commonly escalate base prices using formulas tied to labor and material indices. The formula may include fixed weights, index lags, floors, caps, and a contractual base date.

Escalation is intended to address input-cost inflation, but it rarely tracks actual program cost perfectly. A quoted base price and an escalated delivery price can differ materially. Practitioners therefore ask whether a number is in base-year or delivery-year economics.

Non-Recurring and Recurring Cost

Non-Recurring Engineering, or NRE, includes development, design, certification, test, tooling, and industrialization effort incurred to create or substantially change a product. Recurring cost is incurred as additional production units are built.

The boundary is important in supplier proposals and program business cases. Tooling, software, test assets, and change activity can be classified differently under different arrangements. A low recurring price may be supported by a large up-front NRE payment, supplier amortization, or optimistic volume assumptions.

Unit Recurring Cost

Unit Recurring Cost, or URC, estimates the recurring cost of producing a unit at a specified point or rate. It typically includes recurring labor, material, supplier content, and manufacturing support under the organization’s defined cost rules.

URC excludes or allocates development and other non-recurring costs differently from a fully burdened accounting cost. It also moves with learning, rate, mix, inflation, and supply conditions. A URC statement without a unit number, production rate, currency basis, and scope is not yet a useful comparison.

Learning Curve

A learning curve models how labor hours or cost decline as cumulative production experience increases. An 85 percent curve, under one common convention, means the modeled value falls to 85 percent when cumulative quantity doubles.

There are unit and cumulative-average curve conventions, so practitioners must confirm which one is being used. Learning can be interrupted by rate changes, redesign, workforce turnover, or production transfer. The curve is a model of improvement, not a contractual arrangement with reality.

Shipset Value and Rate-Break Pricing

Shipset value is the revenue or cost associated with all of a supplier’s content on one aircraft or engine. Rate-break pricing changes unit or shipset price when production volume crosses specified thresholds.

The commercial logic assumes fixed-cost absorption, purchasing leverage, and operational efficiency at higher rates. Disputes arise when announced rate, ordered quantity, scheduled quantity, and actually delivered quantity differ. The contract’s definition of the applicable rate controls, not the most attractive number on the production chart.

Program Accounting and Accounting Quantity

Program accounting estimates average revenues and costs across an accounting quantity, meaning a defined block of expected program deliveries. It is particularly associated with certain large commercial aircraft accounting practices and is not universal across OEMs or reporting regimes.

Early units usually cost far more than mature units, so expected later efficiencies influence reported program economics. Changes in production cost, price, demand, or accounting quantity can materially alter the outlook. This should not be confused with the engineering break-even quantity in a business case, although the numbers may influence one another.

Deferred Production Balance and Reach-Forward Loss

A deferred production balance can arise when actual early production costs exceed the average cost recognized under program accounting. The balance is expected to be recovered through future units with lower cost or better economics.

A reach-forward loss is recognized when expected revenues over the remaining accounting block are insufficient to cover expected costs. Hearing the term signals that the problem is not merely an expensive current unit; the projected economics of the remaining block have deteriorated.

Continued Airworthiness Data

Instructions for Continued Airworthiness

Instructions for Continued Airworthiness, or ICA, are the maintenance and support instructions necessary to keep a certificated product airworthy. They include maintenance procedures, inspection requirements, troubleshooting information, servicing data, and mandatory limitations.

ICA are part of the certification ecosystem, not merely customer documentation. They may be distributed across several manuals and supplier publications. Late ICA can affect product approval, operator readiness, and the ability to maintain delivered equipment legally and effectively.

Airworthiness Limitations Section

The Airworthiness Limitations Section, or ALS, contains mandatory replacement times, structural inspection requirements, certification maintenance requirements, and other limitations approved as part of the type design.

ALS tasks are not simply OEM recommendations. Operators must incorporate them into approved maintenance programs unless an authority approves an alternative. This distinguishes them from many planning recommendations in the Maintenance Planning Document.

MSG-3

MSG-3 is the industry decision logic used to develop scheduled maintenance tasks for transport aircraft. It analyzes systems, structures, zonal areas, and failure consequences to identify applicable and effective maintenance tasks.

MSG-3 does not prescribe a generic interval for every component. Working groups apply the logic using design, reliability, safety, and operational information. The resulting tasks feed the Maintenance Review Board process and ultimately the operator’s maintenance program.

MRBR and MPD

The Maintenance Review Board Report, or MRBR, records the authority-approved minimum initial scheduled-maintenance requirements developed through the industry process. The Maintenance Planning Document, or MPD, is the OEM’s broader planning document containing maintenance tasks and supporting planning information.

The MPD generally includes the MRBR requirements plus other OEM recommendations and limitations. Neither is the airline’s final approved maintenance program; the operator adapts the source requirements to its fleet and obtains authority approval.

Aircraft Maintenance Manual

The Aircraft Maintenance Manual, or AMM, provides approved or accepted procedures for maintaining the aircraft and its installed systems. It includes removal, installation, adjustment, testing, servicing, and specified maintenance practices.

The AMM tells technicians how to perform aircraft-level work. It does not normally provide full internal overhaul instructions for every component, which belong in a Component Maintenance Manual. Correct aircraft effectivity and revision status are essential.

Illustrated Parts Catalog

The Illustrated Parts Catalog, or IPC, identifies procurable aircraft parts and assemblies through illustrated breakdowns, part numbers, quantities, effectivity, and interchangeability information.

The IPC is a provisioning and identification tool, not independent engineering authority to install any item that appears nearby on a page. Applicability, modification status, and accompanying instructions still control. Parts specialists live in the intersection between the IPC and configuration data.

Structural Repair Manual

The Structural Repair Manual, or SRM, provides allowable damage limits and approved repair instructions for defined aircraft structural areas and materials.

Damage within SRM limits can generally be addressed without obtaining a new case-specific repair from the OEM. Damage outside those limits requires engineering evaluation and approved repair data. “Outside SRM” often signals aircraft downtime because technical disposition must be developed before return to service.

Component Maintenance Manual

A Component Maintenance Manual, or CMM, provides shop-level maintenance, disassembly, inspection, repair, assembly, and testing instructions for a component. It is generally produced by the component OEM.

The CMM operates below the aircraft-level AMM. Removing a line-replaceable unit may be covered by the AMM, while opening and repairing that unit belongs under the CMM. Approved repair capability, tooling, and test equipment may still be required.

Service Bulletin and Service Letter

A Service Bulletin, or SB, provides technical instructions for inspecting, modifying, or correcting a product. Service letters and similar communications usually provide operational or technical information without the same formal modification package.

An SB is not automatically mandatory. It becomes mandatory when required by an Airworthiness Directive, an approved limitation, or another controlling obligation. OEM classifications such as alert, recommended, or optional communicate urgency but do not by themselves replace regulatory status.

Airworthiness Directive

An Airworthiness Directive, or AD, is a legally enforceable rule issued by an aviation authority to correct an unsafe condition in a product. It specifies affected products, required actions, compliance times, and permitted alternatives.

An AD may reference an OEM service bulletin for technical instructions, but the authority’s directive controls the legal requirement. Differences in effectivity or wording matter. Operators may seek an Alternative Method of Compliance when they can demonstrate an acceptable alternative.

MMEL and MEL

The Master Minimum Equipment List, or MMEL, identifies equipment that may be temporarily inoperative under specified conditions while preserving an acceptable level of safety. It is developed for the aircraft type and approved by the responsible authority.

The operator’s Minimum Equipment List, or MEL, is fleet-specific, authority-approved, and no less restrictive than the applicable MMEL framework. MMEL relief does not automatically authorize dispatch; the operator must have the item in its MEL and satisfy all operational and maintenance procedures.

Configuration Deviation List

The Configuration Deviation List, or CDL, permits operation with specified external parts missing, subject to limitations, performance penalties, and procedures. Examples may include certain fairings, panels, or aerodynamic seals.

The CDL differs from the MEL. The MEL addresses inoperative equipment; the CDL addresses approved deviations from the normal external configuration. A missing part not listed in the CDL cannot be treated as harmless merely because the aircraft can physically fly without it.

ETOPS Configuration, Maintenance, and Procedures

The ETOPS Configuration, Maintenance, and Procedures document, commonly called the CMP, defines configuration standards, maintenance practices, and operational provisions needed to support extended operations with limited diversion options.

ETOPS capability depends on more than engine reliability. Aircraft configuration, system modifications, parts status, maintenance controls, and dispatch procedures must remain aligned. An aircraft of an ETOPS-capable model is not automatically eligible for every ETOPS approval.

Fleet Support

Entry Into Service

Entry Into Service, or EIS, is the transition from development and delivery into revenue operation with the launch or initial operators. OEMs plan enhanced field support, spares, engineering response, reliability monitoring, and rapid issue resolution around this period.

EIS is both a date and an operating phase. Early dispatch problems may reflect immature documentation, training, software, supply support, or maintenance learning rather than fundamental design failure. The objective is to stabilize the fleet before small issues become schedule headlines.

Aircraft on Ground

Aircraft on Ground, or AOG, indicates that an aircraft cannot return to service until an urgent technical, material, or regulatory issue is resolved. OEMs and suppliers maintain dedicated AOG response channels.

AOG status drives expedited engineering, logistics, repair, and technical-publication activity. It does not mean every grounded aircraft has a safety crisis; it means the operator is losing usable aircraft time and expects response measured in hours, not normal lead times.

Initial Provisioning

Initial provisioning determines the spare parts, tools, ground equipment, and support material an operator should acquire before introducing a new aircraft or equipment type.

Recommendations use fleet size, utilization, route structure, removal rates, repair turnaround times, part criticality, and resupply lead times. Under-provisioning creates AOG exposure; over-provisioning creates expensive inventory. The difficult items are often high-value rotables with uncertain early reliability.

Line-Fit and Retrofit

Line-fit means equipment or a modification is installed during original production. Retrofit means it is incorporated after the aircraft has progressed beyond the relevant production point or entered service.

The same technical feature is usually cheaper and easier to line-fit. Retrofit requires kits, aircraft access, downtime, labor instructions, effectivity control, and possibly separate approval. A sales commitment that misses its line-fit decision date can become a much larger aftermarket program.

Fleet Campaign

A fleet campaign is a coordinated effort to inspect, modify, or replace items across an affected in-service population. It may be voluntary, reliability-driven, warranty-supported, or mandated through an AD.

OEM communications may use names such as All Operator Telex, Operator Information Telex, multi-operator message, or fleet team digest, depending on manufacturer and urgency. A campaign requires kits, labor plans, slot coordination, records, and incorporation tracking. Issuing the bulletin is the beginning of the operational work, not the end.

Rotable and Pool

A rotable is a serialized component designed to be removed, repaired or overhauled, and returned to service through repeated cycles. A rotable pool is shared inventory used to provide replacement units while removed units undergo shop work.

Pool performance depends on removal rates, repair turnaround time, serviceability, location, and configuration compatibility. One nominal spare can be useless if it has the wrong modification status for the aircraft that needs it.

No Fault Found

No Fault Found, or NFF, describes a removed component that passes shop testing without reproducing the reported fault. Repeated NFF removals can indicate intermittent equipment behavior, wiring faults, inadequate test coverage, ambiguous maintenance messages, or troubleshooting practices.

NFF is not proof that nothing was wrong. It means the available shop process could not confirm the fault. High NFF rates inflate spares demand and repair activity while leaving the underlying aircraft issue unresolved.

Dispatch Reliability

Dispatch reliability measures the percentage of scheduled departures completed without a qualifying technical delay or cancellation. A simplified expression is:

Dispatch reliability = 1 - (technical delays and cancellations / scheduled departures)

Definitions vary by operator, delay threshold, and reporting system, so comparisons require care. Technical dispatch reliability excludes some non-technical causes. A value above 99 percent can still represent substantial disruption across a large fleet, and it says little about maintenance labor or repeated deferred defects.

Propulsion Programs

Thrust Rating

A thrust rating is an approved engine thrust level for a specific engine model, aircraft application, and operating condition. Closely related engine hardware may be offered at several ratings through software, control, hardware, or contractual configuration differences.

Higher rating can improve aircraft capability but may affect life consumption, temperature margin, maintenance cost, and commercial price. Treating a rating change as a simple software switch overlooks certification, aircraft integration, and engine-life consequences.

Derate and Assumed Temperature

A fixed derate uses an approved lower takeoff thrust rating. An assumed-temperature or flexible takeoff calculation commands less than maximum available thrust for the actual conditions while preserving access to higher thrust when required.

Both reduce engine stress, but they are not identical. Derates change the selected rating framework; assumed-temperature techniques calculate reduced thrust for a particular takeoff. Engine OEM analyses care because takeoff severity influences exhaust-gas temperature margin and time on wing.

EGT Margin

Exhaust Gas Temperature margin, or EGT margin, is the difference between an engine’s current takeoff exhaust-gas temperature and the applicable operating limit under corrected reference conditions.

Margin generally deteriorates as the engine ages, fouls, or experiences component wear. Low margin can drive removals, particularly in hot conditions or demanding operations. A fleet can remain dispatchable while its future shop-visit exposure is quietly increasing.

Time on Wing

Time on wing is the operating duration an installed engine remains in service before removal. It may be expressed in flight hours, flight cycles, calendar time, or a combination.

Longer time on wing generally improves economics, but mission severity matters. Short sectors, high thrust, hot and sandy environments, and limited derate use can shorten intervals. Comparisons without aircraft type, route profile, rating, and maintenance policy are often misleading.

Life-Limited Part

A Life-Limited Part, or LLP, is a critical rotating or structural engine part with an approved life limit, usually controlled in flight cycles. It must be removed from service before reaching that limit.

LLP records require rigorous traceability. Remaining life affects engine value and shop-visit planning because replacing LLPs can represent a large portion of event cost. “The engine has hours left” is not useful if a major LLP stack is about to reach its cycle limit.

Shop Visit and Workscope

A shop visit occurs when an engine enters an approved maintenance facility for inspection, repair, module work, overhaul, or life-limited-part replacement. The workscope defines which modules will be opened and which tasks, repairs, and replacements will be performed.

Removal does not automatically imply a full overhaul. Workscope decisions balance condition, remaining life, expected next removal, lease requirements, material availability, and cost. Once the engine is opened, findings can expand the plan, a phenomenon budgets experience more vividly than presentations do.

Performance Restoration

A performance-restoration shop visit restores engine efficiency and EGT margin by refurbishing or replacing deteriorated gas-path components. It may focus on core modules without replacing every life-limited part.

The distinction from a heavier overhaul matters commercially. An operator may seek enough restored margin to reach a planned horizon rather than maximize theoretical build life. The correct workscope depends on future mission, ownership, lease status, and expected time on wing.

Flight-Hour Agreement and Power-by-the-Hour

A flight-hour agreement charges the operator according to engine utilization, commonly by flight hour, cycle, or an agreed combination, in exchange for defined maintenance and support coverage. Power-by-the-Hour is widely used as a colloquial description of this model.

Coverage depends on exclusions, life-limited parts, escalation, utilization assumptions, shop findings, and operational severity. The acronym FHA may mean Flight-Hour Agreement in a commercial engine discussion and Functional Hazard Assessment in a safety discussion. Context is doing important work.

Green Time

Green time is the estimated usable life remaining on an engine or module before major maintenance is expected. It is commonly discussed in used-engine, leasing, spare-engine, and short-term capacity decisions.

There is no single universal green-time definition. It may be constrained by EGT margin, LLP life, borescope condition, contractual return conditions, or expected shop-visit timing. Ask what limiting factor and operating assumptions support the estimate.

The Phrase Translator

“We have ATO, but not launch authority.”

It may mean: The commercial team may make controlled offers, but the company has not committed the full development funding, industrial capacity, or executive sponsorship needed to launch the program.

“The derivative case works only if we preserve commonality.”

It may mean: The business case assumes inherited certification, training, parts, tooling, or maintenance benefits. Engineering changes that break those assumptions may turn the affordable derivative into something suspiciously close to a clean-sheet program.

“Two CRIs are still holding the certification basis open.”

It may mean: The authority and applicant have not resolved two material regulatory questions. Architecture, testing, or schedule may remain provisional until they do.

“We think this can stay on the amended TC, but the changed-product review is not closed.”

It may mean: The preferred approval path is an amendment to the existing design, but the authority may require compliance with newer standards or broader certification work than the plan currently assumes.

“The test result is good, but the article was not conforming.”

It may mean: Engineering learned something useful, but the result may not receive formal certification credit. The test may need to be repeated with controlled configuration and conformity evidence.

“The iron bird is stable; the aircraft load is not flight standard.”

It may mean: Ground integration is progressing, but the hardware, software, databases, or configuration intended for flight have not reached the required maturity.

“That change missed the block point and will travel with the aircraft.”

It may mean: The modification was not ready for normal station incorporation. It will either be completed downstream at higher cost or deferred to a later effectivity.

“We are holding pulse, but travelled work is increasing.”

It may mean: Aircraft continue moving on schedule while unfinished work accumulates inside them. The visible line rate looks healthy; the recovery burden does not.

“The shipset is complete except for one SFE LRU.”

It may mean: Nearly all supplier content is available, but one seller-furnished line-replaceable unit may still prevent system test or aircraft completion. Aircraft production has a low tolerance for the phrase “except for one.”

“The FAI is closed, but DPRV has not been granted.”

It may mean: The production process has passed first-article verification, but the supplier is not yet authorized to perform delegated release verification. Shipment may still require OEM inspection or approval.

“MRB approved a repair, not rework.”

It may mean: The item will be restored to an acceptable condition but will not fully return to the original drawing definition. Repair data, records, and future configuration implications matter.

“The customer wants the feature line-fit after configuration freeze.”

It may mean: The customer wants production installation without paying the full schedule and engineering consequences of a late change. Several functions are now calculating those consequences.

“The slot is protected, but the skyline still shows customer risk.”

It may mean: Capacity remains reserved, but financing, PDPs, specification readiness, or contractual conditions could still prevent the customer from taking delivery.

“If they defer, this becomes a white tail unless we can backfill the position.”

It may mean: The aircraft is already too far into customer-specific production to pause cleanly. The OEM needs another buyer quickly or will carry inventory and reconfiguration exposure.

“URC is not on curve at the planned rate.”

It may mean: Actual recurring production cost is not declining as the business case assumed. Learning, supplier pricing, disruption, mix, or rate inefficiency may be eroding program economics.

“The SB is recommended; the AD is what makes it mandatory.”

It may mean: The OEM strongly prefers incorporation, but the legal obligation comes from the authority directive and its specific effectivity and compliance time.

“MMEL relief exists, but this is a CDL item.”

It may mean: The team may be looking at the wrong dispatch mechanism. Inoperative equipment and missing external configuration items are controlled through different approved documents.

“Dispatch reliability is acceptable, but NFF is consuming the pool.”

It may mean: Flights are mostly departing, yet repeated component removals and inconclusive shop tests are driving spares demand, repair activity, and support cost.

“EGT margin is coming off faster than the model.”

It may mean: Engine deterioration is exceeding assumptions, so expected time on wing may shorten and shop visits may arrive earlier than the commercial plan anticipated.

“The LLP stack makes this more than a performance restoration.”

It may mean: Several life-limited parts are approaching their limits, so a relatively focused engine shop visit may expand into a much more expensive workscope.

Net Net

Commercial aerospace OEM language is difficult because one conversation can cross type design, certification, supplier authority, production configuration, airline operations, program accounting, and in-service support. Familiar words such as family, conformity, slot, repair, green, and margin carry precise meanings that change technical authority, schedule, and economics.

• Is this a type-design issue, a production nonconformance, or an in-service configuration issue?
• Which approval path applies: original TC change, amended TC, STC, approved repair, or service bulletin?
• What certification basis and amendment levels control, and are any issue papers or CRIs still open?
• What is the exact effectivity by model, MSN, line number, part number, dash number, and modification standard?
• Who holds the formal compliance finding or disposition authority: the regulator, ODA, DOA, TC holder, supplier, or production MRB?
• Is the cited evidence from a development article, a conforming certification article, or a production-representative configuration?
• Does the cost number include NRE, recurring cost, escalation, learning, and the assumed production rate?
• Is the requirement mandatory through the ALS or an AD, or recommended through the MPD or a service bulletin?
• For a production issue, is the disposition rework, repair, use-as-is, deviation, or concession?
• For a reliability metric, what event definition, delay threshold, fleet population, and reporting period are being used?
• For an engine conclusion, is the limiting factor EGT margin, LLP life, condition, workscope, or contractual return requirements?
• What block point, delivery slot, maintenance interval, or compliance date determines what must happen next?

Real fluency does not require memorizing every acronym. It comes from recognizing which design state, approval, configuration, metric, and economic assumption the acronym is quietly carrying into the conversation.