Aerospace — Good to Know: Rules of Thumb, Standards Mastery, and Veteran Knowledge — Study guide

Aerospace — Good to Know: Rules of Thumb, Standards Mastery, and Veteran Knowledge

This companion covers everything in the Aerospace catalogue that does not get a standalone study guide: the standard-practice and niche credentials, the flagship standards and regulations you must know cold, order-of-magnitude rules of thumb, and the things exams never test.

1. Standard-practice and niche credentials (no standalone guide)

INCOSE ASEP / CSEP / ESEP — the systems-engineering ladder

What: Three tiers from the International Council on Systems Engineering, built on the INCOSE Systems Engineering Handbook: ASEP (entry, knowledge exam, <5 years SE experience), CSEP (professional: technical bachelor's, 60 months SE experience with 12 months in each of 3 SE areas, knowledge exam, 3 references), ESEP (expert: ~20–25 years senior experience, leadership roles, community contribution, reference-based assessment).
Who needs it: Systems engineers in aerospace/defense, especially on programs run under ARP4754A-style development assurance where the credential signals you can own requirements, V&V, and interface management.
When: ASEP as a student/recent grad differentiator; CSEP when bidding systems roles at primes (it is frequently a preferred qualification in job postings); ESEP for recognized technical leaders. Renewal is 3-year cycles with fees and PDUs.
Veteran note: CSEP's real value is not the exam — it's forcing you to document 5 years of systems work across three areas, which becomes your program-management portfolio.

FAA Designated Engineering Representative (DER) — delegated authority, not a license

What: An individual engineer to whom the FAA delegates authority to find compliance with airworthiness regulations and approve technical data, under FAA Order 8110.37F. DERs exist by discipline: structures, systems and equipment, software, flight test, and others. The FAA confirmed in 2026 it has no plans to discontinue designees — DERs remain a critical component of the certification system.
Who needs it: Certification engineers at OEMs, STC houses, and consultancies who need their compliance findings accepted by the FAA without routing every finding through an ACO engineer.
When: After building deep, recognized expertise in a delegated discipline plus years of certification-program experience; appointment is by application demonstrating expertise, reviewed/reissued periodically by the managing FAA office. Company DERs act for their employer; consultant DERs serve clients.
Critical distinction: a DER is a delegation of FAA authority, not a license to practice — license_to_practice=false. The authority exists only within the delegated discipline and only as long as the FAA maintains the appointment. Engineers who confuse DER status with personal licensure misunderstand the entire delegation system.

ASQ Certified Quality Engineer (CQE) — the aerospace supply-chain quality credential

What: ASQ's quality-engineering body of knowledge: quality management, the quality system, product/process design, process control, continuous improvement, quantitative methods (SPC, DOE, reliability, acceptance sampling), risk management. First exam given 1968 — the oldest and most established quality credential.
Who needs it: Quality engineers, supplier quality engineers, and manufacturing engineers in AS9100 supply chains.
When: 8 years on-the-job experience (degree waivers: bachelor's waives 4, advanced degree waives 5), with 3 years in a decision-making role; exam is 175 questions computer-based, 550/750 to pass; recertification every 3 years (PDUs) or re-exam.
Veteran note: in aerospace, CQE pairs with AS9100D auditor knowledge; in automotive the analogous credential is different — know which industry you're in.

Covered by shared guides (linked, not duplicated)

PE license (aerospace-flavored): see ../shared/pe-license-study-guide.md. Aerospace reality check: the PE is rarely legally required for aircraft design work (the FAA type-certification system is the operative approval, not state licensure), but it is valuable for engineers doing structural analysis sign-off in adjacent civil work, expert-witness work, and some state-regulated roles.
Chartered Engineer (CEng) via RAeS: see ../shared/ceng-uk-chartered-engineer-study-guide.md. The flagship UK/European professional credential for aerospace engineers — competence-based (UK-SPEC A–E), not exam-based.
PMP: see ../shared/pmp-study-guide.md. The default program-management credential on aerospace/defense programs run under earned-value management.

2. Standards mastery — what a practitioner must know cold

DO-178C / ED-12C — airborne software

Know cold: the five Design Assurance Levels (A = catastrophic, B = hazardous, C = major, D = minor, E = no effect) and the 71 objectives distributed across them; the planning documents (PSAC — Plan for Software Aspects of Certification — is the contract with the authority); requirements-based testing with structural coverage: statement coverage (Level C+), decision coverage (B+), modified condition/decision coverage, MC/DC (Level A); end-to-end traceability from system requirements → high-level requirements → low-level requirements → code → test cases; tool qualification (TQL-1 through TQL-5) for tools whose output is not otherwise verified.
How compliance is demonstrated: to the FAA via AC 20-115D; Stage of Involvement (SOI) audits at planning, development, verification, and final; the Software Accomplishment Summary at the end.
Common violations/mistakes: treating unit testing as a substitute for requirements-based testing (coverage without traceability is worthless); claiming MC/DC on auto-generated code without understanding the masking rules; changing a qualified tool version mid-program without re-qualifying; deriving requirements from code instead of from system requirements.
Recent: DO-178C supplements (DO-330 tool qualification, DO-331 model-based, DO-332 object-oriented, DO-333 formal methods) are where modern programs live; the base document dates to 2011.

DO-254 / ED-80 — airborne electronic hardware

Know cold: hardware DALs A–E mirroring software; the hardware design lifecycle (conceptual design → detailed design → implementation → verification); the distinction between verification of requirements vs. verification of the implementation; configuration management of HDL and design data.
How compliance is demonstrated: Hardware Accomplishment Summary; PHAC (Plan for Hardware Aspects of Certification); audits by the authority or delegated DER.
Common mistakes: assuming an FPGA/ASIC is "just hardware" with no assurance process; reusing COTS IP cores without assessing their development assurance; confusing DO-254 (design assurance) with environmental qualification (DO-160).
Note: DO-254 was written for custom micro-coded devices; its application to complex COTS (multicore processors) is handled via companion guidance (CAST-32A / AC 20-193) — know this exists.

ARP4754A (→ ARP4754B, Dec 2023) — aircraft/systems development assurance

Know cold: the development-assurance workflow: aircraft/system functions → functional requirements → allocation to items → FDAL (Functional DAL, set by the safety assessment) vs. IDAL (Item DAL, what the item is actually developed to); validation (right requirements) vs. verification (requirements met); the certification liaison process.
How compliance is demonstrated: the system development plans, requirements traceability, and the safety-assessment hand-off to ARP4761; the applicant's certification plan references ARP4754A as the means of compliance to 25.1309.
Common mistakes: assigning DALs bottom-up from component criticality instead of top-down from functional hazard assessment; skipping the validation step (most program failures are wrong requirements, not wrong implementations); ARP4754B's new model-based provisions being ignored by teams still doing document-based development.

ARP4761 — safety assessment process

Know cold: the analysis chain — FHA (Functional Hazard Assessment) → PSSA (Preliminary System Safety Assessment) → SSA (System Safety Assessment); the methods — FTA (fault tree, top-down), FMEA/FMES (bottom-up), CCA (common-cause analysis: zonal analysis, particular-risk analysis, common-mode analysis); the quantitative targets: catastrophic failure conditions must be extremely improbable (on the order of 10⁻⁹ per flight hour for Part 25), hazardous 10⁻⁷, major 10⁻⁵.
How compliance is demonstrated: the System Safety Assessment document is the primary compliance artifact for 25.1309.
Common mistakes: fault trees with AND-gates fed by the same power supply (common-cause failure the analysis was supposed to catch); FMEAs that stop at the component instead of propagating to the functional effect; treating 10⁻⁹ as a number you can test to (you can't — it's demonstrated by architecture: redundancy, partitioning, dissimilarity, plus analysis).

AS9100D — aerospace quality management

Know cold: it's ISO 9001 plus aerospace extras: configuration management, risk management, counterfeit-parts prevention, FOD control, work transfer, special-process validation (NADCAP), first-article inspection (AS9102), human factors.
How compliance is demonstrated: third-party certification audits; customer flow-downs; PPAP-like production approval in some chains.
Common violations: counterfeit/used-suspect parts entering the chain (a criminal matter, not just a quality escape); FOD discipline breakdowns; treating AS9102 first-article as a paperwork exercise rather than a process-validation event.

NASA-STD-8719 series / NASA-STD-5001 — NASA safety and structures

Know cold: 5001's factors of safety for spaceflight hardware — the famous 1.4 ultimate / 1.25 yield (metallic structure, with test factors and knockdowns for buckling, composites, and joints spelled out in the standard); the distinction between proof (no detrimental yielding) and ultimate (no rupture) testing.
8719: the safety-standard series (pressure systems, lifting, explosives, range safety interfaces) — know it exists and which volume governs your hardware.
Common mistakes: applying aircraft factors (1.5 ultimate) to NASA hardware or vice versa; forgetting that composites and buckling get additional knockdowns; testing to ultimate without a separate proof cycle.

ECSS — European space standards

Know cold: the ECSS system is organized by discipline (ECSS-E engineering, ECSS-Q product assurance, ECSS-M management); ECSS-E-ST-10-03 testing, ECSS-Q-ST-70 materials/processes, ECSS-E-ST-32 structural factors.
How compliance is demonstrated: declared compliance in the project's compliance matrix, verified by the customer's product-assurance authority (ESA or prime).
Common mistakes: assuming ECSS and NASA standards are interchangeable (factors and margins philosophies differ); missing that ECSS tailoring is mandatory — you never apply ECSS unmodified.

MIL-STD-810 — environmental test tailoring

Know cold: 810 is a tailoring standard, not a fixed test list — the methods (vibration, shock, temperature, humidity, sand/dust, salt fog, altitude, icing, etc.) are selected and tailored to the life-cycle environment profile. The current revision is H.
Common mistakes: running "MIL-STD-810" as a checkbox battery without a life-cycle environmental profile; confusing qualification (design margins) with acceptance (workmanship screening).

MIL-STD-461 — EMI/EMC

Know cold: conducted/radiated emissions (CE/RE) and susceptibility (CS/RS) requirements; the equipment categories (Army/Navy/Air Force installations); RS103 radiated susceptibility levels by platform.
Common violations: failing RS103 at aircraft external levels because the box was designed to a lab bench; bonding/grounding schemes that defeat the filter design.

3. Regulations mastery

14 CFR Part 25 — transport-category airworthiness standards

Know cold: the structure — Subpart B (flight), C (structure), D (design and construction), E (powerplant), F (equipment), G (operating limitations/information). The crown jewel is 25.1309: equipment, systems, and installations must be designed so that catastrophic failure conditions are extremely improbable — this single paragraph drives the entire ARP4754A/4761/DO-178C/DO-254 compliance chain. Also 25.571 (damage tolerance), 25.561 (emergency landing), 25.853 (flammability), 25.981 (fuel-tank ignition prevention — the TWA 800 rule), 25.1529/25.1729 (Instructions for Continued Airworthiness).
How compliance is demonstrated: issue papers, certification plans, means-of-compliance documents, witnessed tests, DER findings — all procedurally through Part 21.
Recent: novel features (electric propulsion, autonomy) are handled via special conditions and issue papers because Part 25 predates them.

14 CFR Part 21 — certification procedures

Know cold: Subpart B (type certificates), Subpart D (changes — STCs live here), Subpart E (supplemental type certificates), Subpart K (PMAs), Subpart O (TSO authorizations). The TC/STC/PMA/TSO taxonomy is the vocabulary of the entire industry.
Common mistakes: confusing a PMA (approval to manufacture a part to approved design data) with design approval itself; assuming an STC on one serial number transfers to another.

EASA Part 21 — the European counterpart

Know cold: the DOA vs. POA distinction: the Design Organisation Approval holder owns the design and its design-assurance system (independent verification — the "four eyes" principle); the Production Organisation Approval holder builds to the approved design. Major vs. minor changes/repairs mirror the FAA's major/minor logic but are classified by the DOA.
Common mistakes: assuming FAA DER findings transfer directly to EASA (they don't — validation processes exist under bilateral agreements); underestimating the DOA handbook as the actual compliance document.

ITAR (22 CFR 120–130) / EAR (15 CFR 730–774) — export control

Know cold: ITAR covers defense articles/services/technical data on the USML (22 CFR 121.1) — presumption of denial, no commercial-interest balancing, State Department jurisdiction. EAR covers dual-use/commercial items on the Commerce Control List — Commerce Department, with licensing that weighs foreign availability and commercial objectives.
When it bites: military aircraft, missiles, and space technology with missile applicability (ITAR); civilian aircraft/components, commercial avionics, satellites not on the USML (EAR — including deemed-export rules for foreign nationals on your engineering team).
Common violations: emailing ITAR technical data to a foreign-national colleague (deemed export); carrying controlled design data on a laptop abroad; assuming "it's on the company server" means it's not an export. Violations are criminal, personal, and career-ending.
Veteran note: the single most expensive sentence in aerospace engineering is "I'll just send you the drawing." Know your jurisdiction determination before you share anything across a border.

14 CFR Part 450 — streamlined launch and reentry licensing

Know cold: the FAA's consolidated commercial launch/reentry licensing rule — single license, performance-based safety approach, flight-safety analysis requirements.
When it matters: engineers at launch providers live under Part 450; payload/spaceport engineers need to know its interfaces.

NASA NPR 8705.2 / 8715.x — human-rating and program safety

Know cold: NPR 8705.2 (human-rating requirements for space systems) sets the crew-survival, fault-tolerance, and abort requirements for crewed NASA missions; the 8715 series covers range/flight safety and payload safety.
When it matters: contractor engineers on NASA crewed programs — these are contractually flowed requirements, not optional guidance.

4. Rules of thumb

Performance and sizing:

Jet airliner L/D ≈ 15–20; a clean business jet ~15; a fighter ~8–10; a sailplane 40+.
Typical jet fuel fraction for long-haul ≈ 40–45% of MTOW; short-haul ≈ 20–25%.
Thrust-to-weight for airliners ≈ 0.25–0.35; fighters ≥ 1.0 with afterburner.
Wing loading: airliner ~600–800 kg/m² (120–160 lb/ft²); GA ~70–100 kg/m²; fighter ~400–600.
Specific fuel consumption: modern turbofan ~0.55–0.65 lb/lbf/hr cruise; turboprop ~0.5–0.6 lb/hp/hr; piston ~0.42–0.48 lb/hp/hr; helicopter turboshaft ~0.55–0.65.
Rule of thumb for range sanity: 1 lb of jet fuel ≈ 1 lb of thrust for ~1.5–1.8 hours at cruise (from SFC ~0.6).

Structures:

Aluminum aircraft structure: limit load = 1.0, ultimate = 1.5 × limit (Part 25). Fitting factor 1.15 on fittings whose strength isn't proven by test. Casting factor 1.25–2.0 depending on inspection level.
Bearing stress in aluminum joints: keep ≤ ~1.5 × F_tu for static sanity, then do the real analysis.
Fastener edge distance 2D minimum, spacing 3D–4D single row — memorize; it's on every structures exam and every shop floor.
Pressurized fuselage hoop stress: σ = p·r/t — a 3-m-radius fuselage at 8 psi Δp with 0.08-in. skin sees ~ σ = 8 × 118 / 0.08 ≈ 11,800 psi; sanity-checks skin gauges instantly.

Systems and electrical:

Aircraft electrical: 28 V DC (small), 115 V / 400 Hz AC 3-phase (large). Power: 3-phase P = √3 · V_L · I_L · cos φ.
Hydraulic systems: 3,000 psi standard; 5,000 psi on newer types (787, A350). Higher pressure = smaller actuators, but seal and fatigue life get harder.
Bleed air: ~30–40 psi, ~200°C from the compressor — that's why bleed ducts are insulated titanium/steel, not aluminum.

Reliability and safety numbers:

10⁻⁹/flight-hour (catastrophic), 10⁻⁷ (hazardous), 10⁻⁵ (major) — the Part 25 ladder.
Typical dispatch reliability target for a new airliner: ≥ 99%.
MTBF sanity: a "1 million hour MTBF" claim for a single LRU is meaningless without the failure-rate model behind it; ask for the prediction standard (MIL-HDBK-217, Telcordia, or field data) and the operating profile.

Unit-conversion reflexes:

1 knot = 1.6878 ft/s = 1.1508 mph; 1 ft = 0.3048 m — do not round to 0.3 in structural math.
Standard sea level: 14.696 psi, 29.92 inHg, 1013.25 hPa, 15°C, ρ = 0.002377 slug/ft³ (1.225 kg/m³). Lapse rate 1.98°C/1,000 ft.
1 g = 32.174 ft/s². Fuel: Jet A ≈ 6.7 lb/gal; 100LL ≈ 6.0 lb/gal; oil ≈ 7.5 lb/gal.

Safety factors and margins:

Aircraft 1.5 ultimate; NASA human-rated 1.4 ultimate / 1.25 yield; pressure vessels (PVHO/ASME) carry their own factors — never borrow factors across regimes.
Margin of safety: MS = (allowable / (f × applied)) − 1, must be ≥ 0; negative MS is not "close enough," it's a failed design.

5. Veteran knowledge — what exams don't test

The certification basis is a negotiation. New programs don't just "meet Part 25" — they establish a certification basis with the authority (amendment level, special conditions, equivalent safety findings). Engineers who treat regulations as fixed physics lose schedule; engineers who treat them as optional lose certificates.
The most expensive words in aerospace: "minor change." Misclassifying a major change as minor to dodge certification process is how programs end up with grounding ADs. When in doubt, write the classification rationale down and get the DER/authority to agree before cutting metal.
Traceability beats cleverness. Every failed audit the author has seen was a traceability failure, not a technical one. If you can't trace a requirement from the system spec to the test that verifies it, you don't have a requirement — you have a wish.
Weight is a program, not a parameter. Mass properties needs a named owner with authority to say no. Every kilogram added in detailed design was "only" a kilogram.
Call a specialist when: flutter/aeroelasticity appears (it's a specialty, not a chapter); lightning/HIRF protection zoning is needed; the failure condition involves software and hardware common cause; export-control jurisdiction is ambiguous (call the trade-compliance lawyer, not the senior engineer); human-rating fault tolerance is in play.
Beginner mistakes that cost real money: designing to ultimate loads instead of limit for fatigue/damage tolerance; forgetting thermal expansion in long duct runs; specifying a fastener the supply chain can't procure; writing a requirement without a verification method; assuming the simulation is the test article.

All content is original explanation. Public facts (exam structures, regulation numbers, standard designations) are as catalogued; verify current revisions against the issuing bodies before relying on them for program decisions.

Original ETS reference writing, verified against public sources on 2026-09-30. Thin sourcing is flagged inline. Not legal advice — confirm current editions with the issuing body.

Aerospace — Good to Know: Rules of Thumb, Standards Mastery, and Veteran Knowledge