I finally had some time to sit down, add new features and smash some bugs (rather than bugs, most of the time, are references error with the reset scripts because I keep adding and moving cells and features).
External Data Sources
Rather than rely on sheets belonging only to the MDCG spreadsheet, the default tables not fetch data from a separate Spreadsheet.
This means that, going forward, updating the MDC with your will be very simple:
- Clone the spreadsheet linked above;
- Fill the sheets with your data;
- Copy the URL into the MDC Generator (C12:C15), respecting the scopes;
- Update the ranges, if you have changed them.
- The first time you import data from a separate spreadsheet, you need to allow the MDC access to them. Go through the four sheets (“airbases”, “waypoints”, “agencies”, “frequencies” – hidden by default) and click the relative button in the cell A1.
That’s it, now the MDCG uses your data and there is no need to replace the original tables every time I release a new MDCG.
Internal data sources are still available but are part of the MDCG spreadsheet itself, as usual.
BINGO is calculated as the sum of:
- Alternate fuel consumption (from HB to Divert AF);
- Egress fuel consumption (from TGT to HB), using one of the two profiles;
- Recovery, i.e. IFR usually requires more fuel than VFR. Note that CASE fuel requirements are placeholders.
- Minimum fuel at landing, because landing with engines running on fumes can cause serious issues, not to mention the fact that is dangerous.
Joker and Tiger can be defined as well (they are not part of Bingo).
The Model Tolerance parameter is a percentage-based increase (or decrease) of the values fetched from my fuel consumption model, in order to account for adverse weather conditions, and other variables. Remember that is better to land with more fuel than less, so I usually leave this value set to 10%.
The Start+Taxi+T/O parameter is a flat subtraction from the starting fuel. It is not usually considered because it is (at least partially) offset by other low-regime phases (e.g. descending) but for completeness’ sake I decided to add it.
Moving CV Distance Calculator
This is a small feature I made for fun to answer I question a viewer asked me about the recovery, specifically how the moving CV affects the fuel consumption over time. Well, the first answer is immediate: not much. Carriers don’t run at Mach 1.0 (yet) so the impact of their speed over time is fundamentally a non-factor. I decide nevertheless to write this simple tool that calculates the distance travelled over time and factors it in along speed and heading to calculate the final approximated latlongs of the CV.
It takes the departure time as Time Zero, then the last WP ETA plus a buffer to approximate the distance and the latlongs of the carrier.
It’s a tool that no one’s going to use but it took me only a few minutes to set it up. On the other hand, you can use with whatever flies straight (so not many things ¯\_(ツ)_/¯ ).