How Aircraft Design Reviews Work: SRR, PDR, CDR and the Decisions That Shape an Aircraft
An aircraft may begin as a promising configuration, a set of performance targets or a response to a customerโs operational need.
Before it becomes a flying machine, however, the design must survive a long series of formal reviews.

These reviews are commonly identified by acronyms such as:
- SRR: System Requirements Review
- SFR: System Functional Review
- PDR: Preliminary Design Review
- CDR: Critical Design Review
- TRR: Test Readiness Review
- PRR: Production Readiness Review
- FRR: Flight Readiness Review
To an outsider, an aircraft design review may sound like a meeting in which engineers present drawings and managers decide whether they like the design.
That is not what is happening.
A major aerospace review is a structured examination of whether the program has enough evidence to justify its next commitment.
At different stages, reviewers may ask:
- Are the requirements complete, consistent and achievable?
- Does the proposed aircraft architecture satisfy the mission?
- Have major technical risks been identified?
- Are the structures, systems and interfaces sufficiently defined?
- Can the aircraft be manufactured?
- Can it be inspected, maintained and operated safely?
- Is the design mature enough to begin building expensive hardware?
- Is the test article configured correctly?
- Is the aircraft ready to fly?
A review can approve the program to proceed. It can approve the program with corrective actions. It can require additional analysis or testing. It can also reveal that part of the design must be changed before the program continues.
The purpose is not to prove that the aircraft is perfect.
It is to determine whether the design is mature enoughโand the remaining risk understood well enoughโto justify moving into the next, usually more expensive, phase.
Why Aerospace Programs Use Formal Design Reviews
Aircraft development involves thousands or millions of connected decisions.
A seemingly small change can affect:
- Weight
- Center of gravity
- Aerodynamics
- Structural loads
- Flutter
- Fuel capacity
- Electrical power
- Thermal performance
- Hydraulic capacity
- Software
- Maintainability
- Manufacturing
- Inspection
- Certification
- Cost
- Schedule
No single engineer can independently understand every consequence of every decision across the complete aircraft.
Formal design reviews bring together specialists from different disciplines so that the aircraft can be evaluated as a system rather than as a collection of individually successful parts.
A wing structure may satisfy its strength requirements but be too difficult to manufacture.
A flight-control system may perform correctly but consume more electrical power than the aircraft can reliably provide.
A maintenance panel may technically allow access to a component but require mechanics to remove several unrelated systems first.
A fuel-system change may resolve one problem while altering weight distribution or introducing a new failure mode.
Design reviews create deliberate points at which those interactions must be examined.
NASAโs systems engineering guidance describes major technical reviews as lifecycle assessments used to evaluate whether a project has met the objectives necessary to proceed to the next phase. The reviews are connected to decision points rather than treated as ceremonial presentations.
Aircraft Design Reviews Are Not All the Same
There is no single universal sequence used identically by every aircraft manufacturer, defense program, spacecraft project or supplier.
Names, timing and required deliverables vary according to:
- The company
- The customer
- The aircraft type
- Civil or military use
- Program size
- Contract requirements
- Certification basis
- Internal development processes
- Whether the review covers the entire aircraft, one system or one component
A large defense aircraft program may use an extensive sequence of formal systems engineering technical reviews.
A small unmanned aircraft company may use a simpler process while still applying the same underlying principles.
Subsystems can also hold their own reviews before the aircraft-level review. The landing gear, propulsion system, avionics, flight controls and other major systems may each pass through requirements, preliminary design and critical design reviews before their status is consolidated at the complete-aircraft level.
The names matter less than the decision being made:
Is the work sufficiently mature to commit more money, time, material and organizational confidence?
Before the Reviews: Defining the Mission
A design review process cannot begin with CAD geometry alone.
The program first needs to understand what the aircraft is expected to accomplish.
Depending on the aircraft, the initial mission definition may include:
- Passenger or payload capacity
- Range
- Cruise speed
- Takeoff and landing distance
- Operating altitude
- Runway requirements
- Fuel efficiency
- Survivability
- Signature requirements
- Endurance
- Maneuverability
- Noise limits
- Emissions
- Reliability
- Availability
- Maintainability
- Acquisition cost
- Operating cost
These goals may come from an airline, military customer, government agency, spacecraft mission, internal business case or anticipated market.
The earliest reviews test whether those goals have been translated into usable engineering requirements.
System Requirements Review: Are We Solving the Right Problem?
The System Requirements Review, or SRR, examines whether the programโs requirements adequately describe the aircraft that must be developed.
This occurs before the detailed aircraft design is mature.
At SRR, the team is not expected to present every rib, wire, valve or fastener. Instead, reviewers examine the foundation on which those later decisions will be built.
Questions may include:
- Is the mission clearly defined?
- Are customer needs translated into measurable requirements?
- Are regulatory and certification requirements identified?
- Are safety requirements included?
- Are performance targets realistic?
- Are requirements contradictory?
- Can each important requirement eventually be verified?
- Have major interfaces with external systems been identified?
- Are assumptions documented?
- Are the most serious technical risks understood?
A requirement such as โthe aircraft must be easy to maintainโ is not sufficiently precise by itself.
The program may need measurable requirements for:
- Component access
- Removal and replacement time
- Required tools
- Inspection intervals
- Fault detection
- Ground-support equipment
- Number of maintenance personnel
- Dispatch reliability
If the requirements are vague, incomplete or conflicting, the design team may spend years creating an aircraft that cannot satisfy the customer, operator or regulator.
What must be demonstrated at SRR?
The team generally needs to demonstrate that:
- The requirements provide a credible basis for design
- Major constraints are known
- Requirements can be traced to customer or mission needs
- Verification approaches are being considered
- The program understands its principal technical risks
- The next phase of architectural development can begin responsibly
Passing SRR does not mean the aircraft design is complete.
It means the program has enough confidence that it understands the problem it is trying to solve.
System Functional Review: What Must the Aircraft Do?
Some programs conduct a System Functional Review, often abbreviated SFR, after SRR and before PDR.
The terminology varies, but the purpose is generally to examine whether the aircraftโs required functions have been identified and allocated to systems.
For example, an aircraft must:
- Generate lift
- Produce or manage propulsion
- Maintain controllability
- Supply electrical power
- Manage fuel
- Control cabin pressure
- Detect failures
- Communicate
- Navigate
- Protect occupants
- Support maintenance
- Provide emergency functions
These high-level functions are decomposed and assigned to aircraft systems, subsystems, hardware and software.
The review asks whether the proposed functional architecture is coherent.
Questions may include:
- Which system performs each function?
- Are any required functions missing?
- Are multiple systems unknowingly responsible for the same task?
- How will failures be detected and isolated?
- What happens when a primary system becomes unavailable?
- Are redundancy and independence adequate?
- Are system boundaries and interfaces understood?
- Can the proposed architecture satisfy safety requirements?
At this stage, reviewers are increasingly concerned not only with what the aircraft must accomplish but with how its systems will work together to accomplish it.
Preliminary Design Review: Does the Proposed Design Make Sense?
The Preliminary Design Review, or PDR, is one of the most important points in aircraft development.
By PDR, the aircraft has moved beyond broad requirements and conceptual possibilities. The team should have a credible preliminary design showing how the requirements will be satisfied.
NASA describes PDR as an assessment of whether the preliminary design meets requirements with acceptable risk and whether the project is ready to proceed into detailed design.
At aircraft level, the review may examine:
- Overall configuration
- Aerodynamic performance
- Structural concepts
- Propulsion integration
- Flight controls
- Electrical architecture
- Hydraulic and pneumatic systems
- Avionics
- Landing gear
- Fuel systems
- Environmental controls
- Cabin or payload integration
- Weight and balance
- Safety assessments
- Manufacturing strategy
- Maintenance approach
- Certification planning
- Program cost and schedule
The preliminary design does not need every production detail finalized.
It must, however, be sufficiently complete to demonstrate that the proposed aircraft can work as an integrated system.
What reviewers ask at PDR
PDR questions may include:
- Does the aircraft configuration satisfy the mission?
- Are performance estimates supported by credible analysis?
- Are weight estimates realistic?
- Is there enough margin for expected weight growth?
- Are the principal structural load paths understood?
- Are major system interfaces defined?
- Have critical technologies been demonstrated sufficiently?
- Are safety analyses identifying credible hazards?
- Can the aircraft be manufactured using realistic processes?
- Can major components be installed and removed?
- Is the certification strategy credible?
- Are cost and schedule estimates still defensible?
The review may also examine whether the program has prematurely selected an attractive configuration that creates unacceptable problems elsewhere.
A design could meet range and speed targets while becoming:
- Too heavy
- Too expensive
- Too difficult to manufacture
- Too difficult to maintain
- Too dependent on immature technology
- Too risky to certify
- Too vulnerable to a single failure
PDR forces those tradeoffs into the open before the program becomes locked into detailed design.
What does passing PDR mean?
Passing PDR generally means that the program has a technically credible preliminary design and can proceed into detailed development.
It does not mean every uncertainty has disappeared.
It means:
- The architecture appears sound
- Major requirements have been allocated
- Key interfaces are sufficiently defined
- Major risks are identified and being managed
- The design appears capable of meeting its objectives
- Detailed design can proceed without relying on unsupported assumptions
PDR is often the point at which changing the basic aircraft architecture becomes much more expensive.
Before PDR, the team may still compare significantly different configurations.
After PDR, major architectural change can force extensive redesign across many systems.
Between PDR and CDR: The Aircraft Becomes Real
The work between PDR and CDR is where preliminary concepts become detailed engineering definitions.
Engineers develop:
- Production-intent geometry
- Detailed structural arrangements
- Material specifications
- Fastener selections
- Tolerances
- Wiring and harness definitions
- Hydraulic and fuel routing
- Software architecture
- Equipment installations
- Manufacturing plans
- Inspection requirements
- Maintenance access
- Test procedures
- Compliance evidence
This is also where the digital mockup becomes increasingly important.
Engineers must determine whether components:
- Physically fit
- Can be assembled
- Can be reached
- Can be removed
- Have adequate clearance
- Interfere during motion
- Can tolerate structural deflection
- Can be inspected
- Can be manufactured repeatedly
The design is not becoming merely more detailed.
It is becoming more difficult and costly to change.
Critical Design Review: Are We Ready to Build It?
The Critical Design Review, or CDR, determines whether the detailed design is mature enough to proceed toward fabrication, integration and testing.
NASA describes CDR as an assessment of whether the design is sufficiently mature to support full-scale fabrication, assembly, integration and testing while meeting requirements within acceptable risk.
The word โcriticalโ does not mean that PDR was unimportant.
It reflects the importance of the commitment being made.
After CDR, the program may authorize significant spending on:
- Production tooling
- Test articles
- Long-lead materials
- Flight hardware
- Manufacturing equipment
- Supplier production
- Software implementation
- Integration facilities
Errors discovered after this point can be extremely expensive.
What reviewers examine at CDR
CDR may assess whether:
- Detailed design requirements are satisfied
- Engineering analyses support the design
- Interfaces are defined and controlled
- Drawings and model-based definitions are sufficiently mature
- Materials and processes are selected
- Safety-critical features are adequately addressed
- Software and hardware development are synchronized
- Manufacturing planning is credible
- Inspection methods are defined
- Test plans can verify the requirements
- Certification compliance methods remain viable
- Configuration baselines are established
- Remaining risks are understood and acceptable
The team may need to present evidence from:
- Stress analysis
- Fatigue and damage-tolerance analysis
- Aerodynamic analysis
- Computational fluid dynamics
- Wind-tunnel testing
- Thermal analysis
- Electrical-load analysis
- Safety assessments
- Failure mode analysis
- Reliability analysis
- Human-factors studies
- Manufacturing simulations
- Tolerance analysis
- Maintainability assessments
Reviewers are not merely asking whether the CAD model looks complete.
They are asking whether the engineering evidence supports building and testing the design represented by that model.
Does CDR freeze the design?
CDR is sometimes described informally as a design freeze.
That description can be misleading.
Aircraft designs continue to change after CDR because testing, manufacturing and integration reveal new information. Suppliers may encounter production problems. Weight may continue to grow. Certification testing may expose deficiencies. Components may become unavailable.
What changes after CDR is not the physical possibility of change.
It is the degree of control required.
A post-CDR change may require:
- Engineering justification
- New analysis
- Updated drawings or models
- Revised safety assessments
- Retesting
- Supplier notification
- Configuration-board approval
- Certification coordination
- Cost and schedule evaluation
The design is not frozen in the sense that it can never move.
It is baselined so that movement is deliberate, traceable and authorized.
Manufacturing Readiness and Production Readiness Reviews
A design can be technically correct and still be extremely difficult to manufacture.
Production-focused reviews examine whether the organization, suppliers, tooling, processes and quality systems are ready to build the aircraft reliably.
A Production Readiness Review, or PRR, may examine:
- Manufacturing instructions
- Tooling readiness
- Supplier capability
- Material availability
- Process qualification
- Workforce training
- Quality planning
- Inspection equipment
- First article inspection
- Production capacity
- Configuration control
- Nonconformance processes
- Corrective-action systems
Reviewers may ask:
- Can the design be produced repeatedly?
- Are special processes qualified?
- Are suppliers working from the correct configuration?
- Can critical characteristics be measured?
- Are inspection methods capable of detecting unacceptable variation?
- Are production risks likely to disrupt schedule or quality?
- Is the manufacturing system ready for the intended production rate?
This review exposes a truth that appears repeatedly in aerospace:
A design is not mature merely because engineers have completed the geometry.
It must also be possible to manufacture, assemble, inspect and document the aircraft consistently.
Test Readiness Review: Is the Test Worth the Risk?
Before a major ground or flight test, the program may conduct a Test Readiness Review, or TRR.
The purpose is to determine whether:
- The test article is ready
- The facility is ready
- The instrumentation is ready
- The procedures are complete
- Safety hazards are controlled
- The expected data will answer the intended questions
A test can consume an expensive article, damage equipment or place people at risk. Even a physically safe test can waste time and money if the instrumentation or procedure cannot produce useful evidence.
Reviewers may examine:
- Test objectives
- Success and failure criteria
- Test configuration
- Instrumentation
- Sensor calibration
- Data acquisition
- Test limits
- Abort criteria
- Hazard controls
- Personnel roles
- Emergency procedures
- Weather limitations
- Hardware and software versions
- Required approvals
One of the most important questions is deceptively simple:
If the test produces an unexpected result, will we know whether the aircraft failed, the test setup failed or the measurement failed?
The test must be designed so that the evidence is trustworthy.
Flight Readiness Review: Is the Aircraft Ready to Leave the Ground?
The Flight Readiness Review, or FRR, is among the most consequential reviews in aircraft development.
It examines whether the aircraft, test team, operating procedures, range, support equipment and risk controls are ready for the planned flight.
The review may consider:
- Aircraft configuration
- Open discrepancies
- Ground-test results
- Structural clearance
- Flight-control functionality
- Software status
- Instrumentation
- Weight and balance
- Weather
- Airspace
- Chase aircraft
- Emergency response
- Pilot training
- Flight-test cards
- Abort procedures
- Safety limits
- Maintenance status
- Regulatory or organizational approvals
An aircraft does not become ready to fly merely because it can taxi and its engines operate.
The program must understand:
- What conditions will be tested
- Which limits must not be exceeded
- How the crew will respond to anomalies
- Whether required systems are functioning
- Whether unresolved problems are acceptable for this particular flight
- Whether the aircraft matches the configuration evaluated by the analysis
That last point connects flight readiness directly to configuration management.
Analysis of one configuration cannot safely justify flight of a different, undocumented configuration.
Operational Readiness Review
An Operational Readiness Review, or ORR, examines whether the complete system is ready to enter an intended operational environment.
For an aircraft program, the review may go beyond the aircraft itself and include:
- Maintenance
- Logistics
- Training
- Technical publications
- Ground equipment
- Spare parts
- Support facilities
- Operational procedures
- Cybersecurity
- Data systems
- Mission planning
- Supply-chain support
An aircraft can perform well in developmental testing and still be unready for operational service.
Operators must be able to:
- Prepare it
- Fly it
- Diagnose it
- Repair it
- Supply it
- Update it
- Train personnel to use it
- Sustain it over time
Operational readiness examines the aircraft as part of a functioning enterprise rather than as a test article.
Who Participates in an Aircraft Design Review?
A major design review may include representatives from:
- Systems engineering
- Aerodynamics
- Structures
- Propulsion
- Flight controls
- Avionics
- Electrical engineering
- Software
- Safety
- Human factors
- Manufacturing
- Quality
- Test engineering
- Certification
- Maintenance
- Supply chain
- Program management
- Customers
- Regulators
- Independent technical authorities
The exact group depends on the review.
Independent reviewers can be particularly valuable because people working daily on the program may become accustomed to its assumptions.
An outside expert may ask:
- Why was this requirement interpreted that way?
- What evidence supports this margin?
- What happens when these two failures occur together?
- How is this interface controlled?
- Who owns this unresolved risk?
- Has the manufacturing organization agreed that this can be built?
- Has maintenance verified that the component is truly accessible?
Those questions may feel disruptive.
That is partly their purpose.
What Happens During a Design Review?
The visible meeting is only one part of the process.
A formal review commonly involves:
- Defining review entrance criteria
- Preparing technical data
- Distributing documents in advance
- Allowing reviewers time to examine the evidence
- Presenting the design and unresolved risks
- Recording questions, concerns and action items
- Classifying findings
- Determining whether exit criteria have been met
- Assigning responsibility for corrective work
- Closing actions or granting formal waivers
Large reviews may last several days or be divided into many discipline-specific sessions.
The program may use review packages containing:
- Requirements
- Architecture descriptions
- CAD models
- Analysis reports
- Interface-control documents
- Risk registers
- Safety assessments
- Test plans
- Manufacturing plans
- Certification plans
- Configuration records
- Cost and schedule information
The presentation should summarize the evidence.
It should not substitute for evidence.
What Does It Mean to Pass a Design Review?
A design review rarely ends with a simple theatrical verdict of โpassโ or โfail.โ
Possible outcomes can include:
- Approved to proceed
- Approved with action items
- Conditionally approved
- Additional evidence required
- Partial re-review required
- Major corrective action required
- Not approved to proceed
An aircraft program may advance while still carrying unresolved items, provided those items are documented, assigned and judged not to invalidate the decision.
This is where engineering judgment becomes essential.
Waiting until every minor uncertainty disappears could paralyze development.
Proceeding with major unknowns could place the aircraft, program and people at unacceptable risk.
The review board must distinguish between:
- Ordinary work remaining
- Manageable technical risk
- Significant but containable concerns
- Fundamental evidence that the design is not ready
Review Action Items Are Not Administrative Clutter
A review finding may identify:
- Missing evidence
- Incomplete analysis
- Conflicting requirements
- Uncontrolled interfaces
- Unacceptable risk
- Weak verification planning
- Manufacturing concerns
- Safety issues
- Configuration inconsistencies
These findings must be recorded and tracked.
Each action should have:
- A responsible owner
- A required response
- A due date
- Objective closure evidence
- Approval by an authorized reviewer
Closing an action should not mean changing its status to green because the deadline arrived.
It means demonstrating that the underlying concern has been resolved or formally accepted by someone with authority to accept the risk.
Design Reviews and Aircraft Certification Are Related but Not Identical
Internal aircraft design reviews should not be confused with regulatory certification.
A manufacturer may conduct SRR, PDR and CDR as part of its own systems engineering and product-development process.
The FAAโs civil aircraft design-approval process follows its own structured phases, including conceptual design, requirements definition, compliance planning, implementation and post-certification activities. The applicant is responsible for showing that the aircraft complies with applicable regulations, while the FAA oversees and makes the required findings or approvals.
A successful internal CDR does not mean the FAA has certified the aircraft.
It means the company believes the design is mature enough to proceed according to its program criteria.
Certification requires evidence that the aircraft complies with the applicable airworthiness standards.
The two processes overlap because good design reviews examine many of the same requirements, analyses, tests and risks that ultimately support certification.
But one does not automatically replace the other.
Can a Design Review Catch Every Problem?
No.
Reviews reduce risk; they do not eliminate uncertainty.
Some problems emerge only when:
- Hardware is built
- Systems are integrated
- Manufacturing variation appears
- Software runs on the real aircraft
- Structures are physically loaded
- Environmental testing is conducted
- Pilots fly the aircraft
- Maintainers work on it
- The aircraft accumulates service experience
A review can examine whether the engineering process is credible and whether the available evidence supports proceeding.
It cannot produce knowledge that does not yet exist.
The danger arises when organizations treat passing a review as proof that the design can no longer contain serious problems.
A successful review means:
Based on the evidence available, the program has met the agreed criteria for the next phase.
It does not mean:
Nothing unexpected will happen from this point forward.
When Design Reviews Fail
A review fails in substance when the organization cannot demonstrate that it is ready for the next commitment.
Warning signs may include:
- Requirements that continue changing without control
- Analyses based on outdated configurations
- Important interfaces without clear ownership
- Risks repeatedly deferred
- Test plans that cannot verify requirements
- Manufacturing concerns dismissed as future problems
- Software and hardware developed against different assumptions
- Safety findings without credible mitigation
- Weight targets maintained through optimism rather than evidence
- Review materials delivered too late for meaningful examination
A program can also undermine the review process by creating pressure to reach a predetermined answer.
If schedule or executive expectations make it politically impossible for reviewers to say โnot ready,โ the review becomes a performance rather than a safety and engineering control.
The aircraft does not become mature because the calendar says the review must be successful.
Why Independent Judgment Matters
Design reviews exist partly because engineers and managers can become committed to their own decisions.
People naturally defend work in which they have invested:
- Time
- Reputation
- Budget
- Career advancement
- Public commitments
- Organizational identity
That does not make them dishonest.
It makes independence important.
A credible review process allows knowledgeable people to question:
- Assumptions
- Margins
- Evidence
- Interfaces
- Risks
- Readiness
The objective is not to embarrass the design team.
It is to discover weaknesses while there is still an opportunity to correct them.
In aerospace, a difficult question asked in a conference room may prevent a much more difficult discovery in manufacturing, testing or flight.
How Digital Engineering Is Changing Design Reviews
Modern aircraft reviews increasingly rely on digital engineering environments rather than isolated documents.
Reviewers may examine:
- Connected CAD assemblies
- Digital mockups
- Requirements databases
- Simulation models
- Digital threads
- Model-based systems engineering architectures
- Model-based definitions
- Configuration records
- Manufacturing simulations
- Virtual test results
- Digital twins
This can improve traceability.
A reviewer may be able to follow a requirement into:
- The system architecture
- The allocated subsystem
- The detailed design
- The verification method
- The test result
- The approved configuration
But digital tools do not automatically create a good review.
A large quantity of connected information can still conceal:
- Weak assumptions
- Incomplete evidence
- Conflicting models
- Outdated data
- Poor engineering judgment
Digital engineering improves access to evidence.
It does not remove the need to question that evidence.
Final Answer: How Do Aircraft Design Reviews Work?
Aircraft design reviews are formal decision points used to determine whether an aircraft program is sufficiently mature to proceed into its next phase.
The major reviews commonly include:
- SRR, which asks whether the requirements define the right aircraft
- SFR, which asks whether required functions have been allocated into a credible system architecture
- PDR, which asks whether the preliminary design can meet the mission with acceptable risk
- CDR, which asks whether the detailed design is mature enough for fabrication, integration and testing
- PRR, which asks whether the organization can manufacture and inspect the aircraft consistently
- TRR, which asks whether a planned test can be performed safely and produce meaningful evidence
- FRR, which asks whether the aircraft and test organization are ready for flight
- ORR, which asks whether the aircraft and its supporting systems are ready for operational use
These reviews do not merely inspect drawings.
They examine the evidence connecting requirements, engineering decisions, physical design, manufacturing, testing, certification and aircraft configuration.
A successful review does not declare the aircraft perfect.
It establishes that the remaining risk is understood well enough to justify taking the next step.
That distinction is essential.
Aircraft development does not advance because everyone has become certain.
It advances because the program has assembled enough credible evidence to make the next decision responsibly.
Frequently Asked Questions About Aircraft Design Reviews
What is an aircraft design review?
An aircraft design review is a structured evaluation of an aircraft programโs requirements, architecture, detailed design, risks, evidence or readiness. The purpose is to determine whether the program has met defined criteria for advancing to its next development phase.
What is the difference between PDR and CDR?
A Preliminary Design Review evaluates whether the proposed aircraft design and system architecture can satisfy the requirements with acceptable risk. A Critical Design Review evaluates whether the detailed design is mature enough to support fabrication, integration and testing.
Does passing CDR mean the aircraft design is finished?
No. The design continues to change as manufacturing, integration and testing reveal new information. Passing CDR generally means the design is sufficiently mature to establish a controlled baseline and authorize further implementation.
What happens if an aircraft fails a design review?
The program may be required to complete additional analysis, modify the design, resolve specific findings or repeat part of the review. The outcome depends on the seriousness of the deficiencies and whether they prevent the program from meeting the reviewโs exit criteria.
Is a design review the same as FAA certification?
No. Design reviews are generally part of an organizationโs engineering and program-management process. FAA certification is the regulatory process through which an applicant demonstrates compliance with applicable airworthiness requirements. The processes support one another but are not interchangeable.
Who attends an aircraft design review?
Participants may include systems, structures, aerodynamics, propulsion, avionics, software, safety, manufacturing, quality, certification, test, maintenance, supply-chain and program-management personnel. Customers, regulators and independent experts may also participate.
What is reviewed at a Flight Readiness Review?
A Flight Readiness Review examines the aircraft configuration, unresolved discrepancies, ground testing, software, instrumentation, weight and balance, flight limits, pilot preparation, emergency procedures, weather, airspace and organizational readiness for the planned flight.
