/main
|-- perf_tests
| `-- eight
| |-- TD
| | |-- table_1_class.py
| | `-- table_2_class.py
| |-- TINF
| | |-- table_1_class.py
| | `-- table_2_class.py
| |-- LD
| | |-- table_1_class.py
| | `-- table_2_class.py
| `-- LINF
| |-- table_1_class.py
| `-- table_2_class.py
|-- main.py
Popular Engine option: CFM56-7B26
This repository inputs values that are found within the official 737NG series FCOM performance tables, calculates performance per phase (takeoff/landing), and outputs the recommended aircraft configuration.
Aviation performance data is typically consumed through static tables and manual cross-checking. While this works on paper, translating those procedures into software introduces additional complexity:
- Inputs may be incomplete, inconsistent, or out of expected bounds
- Assumptions embedded in tables must be made explicit in code
- Operational context (phase of flight, aircraft state) matters
- Errors must be detectable, explainable, and recoverable
This project reframes aircraft performance calculation as a systems problem, not just a numerical one—treating performance logic as something that must be robust, inspectable, and evolvable.
Through incremental modules and experiments, this project examines:
- How real-world procedural logic maps to software structures
- How flight-phase–dependent state influences outputs
- How to surface invalid or unsafe configurations clearly
- How domain rules can be separated from calculation mechanics
- How small architectural decisions impact correctness and trustworthiness
The goal is not to replace certified tools, but to better understand how safety-critical logic behaves when expressed as software.