What to bring to the review
- Aircraft type and mission phases
- Payload and aircraft configuration
- Measured or estimated load profile
- Pack space, mass and connector constraints
- Operating environment and turnaround plan
- Aircraft validation and acceptance criteria
Separate the phases of flight
Describe takeoff, climb, cruise or hover, descent and landing as applicable to the aircraft. Include auxiliary loads and the basis of any estimated demand. Identify which conditions are representative and which require separate evaluation.
Energy storage and power delivery are different requirements. NASA’s aircraft battery research discusses both the energy available and the rate at which it can be delivered. In a project brief, record the mission demand rather than assuming one capacity label describes both.
Treat the pack as part of the aircraft
Document the allowed input range, connector arrangement, mounting, retention and service access. Explain how the host receives battery information and responds to warnings. Protocol support, message definitions and protection behavior must be agreed for the project.
Record the battery mass assumption alongside the aircraft and payload configuration. If that assumption changes, review the mission calculation and validation plan rather than simply substituting a larger pack.
Define the evidence needed before flight use
Agree on the ground evaluation, host integration checks and aircraft-level validation appropriate to the development stage. A bench result is not an aircraft endurance result. Record the pack revision and operating conditions with every evaluation.
Flight operations and safety decisions belong to the responsible aircraft team. This guide is a requirements checklist, not approval to operate an aircraft or a claim of flight qualification.