Skip to content
Blog

Rocket apogee prediction with machine learning

Estimate recorded rocket apogee

Fit measured apogee from the Rocket Flight Database using the saved Neural Designer model. This small approximation example has 25 flight records and five held-out testing rows.

25Source records
8Encoded input values
5Testing-role records
1Model outputs

1. Industrial challenge

Flight analysts can compare measured apogee with a small empirical model and inspect where errors occur. The example replaces the former mission-success classifier with a continuous-output task.

Continuous outcome

Estimate apogee in the source unit of feet.

Small-sample review

Inspect every held-out prediction.

Availability timing

Verify when each flight descriptor becomes available.

Flight analysisAerospace engineeringScientific modelling
A small recorded-flight regression example, not a flight-safety or launch-approval model.

2. Data set

The derived CSV retains motor, maximum and minimum diameter in inches, peak Mach number, launch-site altitude in feet and flight-data type, with apogee_real_ft as the target. Categorical expansion produces eight model inputs.

Source: Rocket Flight Database. Dataset license: CC-BY-4.0. The downloadable ZIP includes the adapted data and attribution notices.

Dataset measureSaved value
Analysis unitflight record
Records25
Raw variables6
Encoded model inputs8
Model outputs1
Training roles15
Validation / selection roles5
Testing roles5
Unused roles0
FieldRoleTypeCategories
maximum_diameter_inInputNumeric
minimum_diameter_inInputNumeric
peak_machInputNumeric
launch_site_alt_ftInputNumeric
flight_data_typeInputCategoricalBarometric Altimeter, GPS, Integrated Accelerometer, Optical Track
apogee_real_ftTargetNumeric
maximum_diameter_in distribution
maximum_diameter_in distribution. Native Neural Designer report for this project.
minimum_diameter_in distribution
minimum_diameter_in distribution. Native Neural Designer report for this project.
The saved project assigns rows to training, validation and testing as shown above. This is internal record-level evaluation; it does not demonstrate separation by subject, device, site or acquisition batch.

3. Model

The model has 8 encoded inputs and 1 outputs. No architecture-selection experiment is recorded in this project. The diagram shows the topology used by the saved model.

LayerInput shapeOutput shapeActivation
Scaling88
Dense83Tanh
Dense31Identity
Unscaling11
Clamping11
Rocket apogee prediction with machine learning — initial network architecture
Topology of the saved current model; no architecture selection is recorded.

4. Training strategy

The saved training configuration uses QuasiNewton with NormalizedSquaredError.

Quasi-Newton method results

MeasureValue
Epochs number18
Elapsed time00:00:00
Stopping criterionLoss goal
Training error0.002
Validation error0.001
Quasi-Newton method error history
Quasi-Newton method error history. Native Neural Designer report for this project.

5. Model selection

No model selection experiment is recorded for this version. The validation subset guides fitting where a training report is present; it is distinct from the held-out test rows.

6. Testing analysis

The figures and tables below refer to the current project’s saved testing analysis. The subset uses testing role 2; it contains 5 source records.

apogee_real_ft goodness-of-fit parameters

MeasureValue
Determination0.997
apogee_real_ft goodness-of-fit chart
apogee_real_ft goodness-of-fit chart. Native Neural Designer report for this project.

7. Model deployment

Open the downloaded project in Neural Designer, inspect the dataset roles and preprocessing, then review the saved task report. Use the same input schema and category order when calculating outputs. The ZIP contains the exact current .nd, its source data and the applicable dataset notices.

Workflow: source measurements → schema and availability checks → model output → domain review. Keep model versions, validation evidence and incoming-data monitoring together.

8. Scope and limitations

Five test flights provide very limited evidence. Peak Mach and other flight-condition descriptors must be available at the time of inference; this saved model is not necessarily a pre-launch predictor. Assess transfer across motors, sites and flight regimes before use.

References