Key Aspects of the Mission Planning Environment
The MPE is the software workspace where an F-35 mission is built, validated, rehearsed, and loaded into the jet. Plan → Build → Rehearse → Load — one workspace that turns intent into a validated brief the jet can execute.
Inputs → MPE → Build → Validate → Rehearse → Load → Debrief
▸ Tip: click any build / rehearse / output node to jump to its detail card. Use the link icon on each card to copy a shareable deep link.
One stop per capability
Waypoints, ingress/egress corridors, tanker tracks, and recovery fields tied to authoritative geospatial data (DAFIF, FLIP, DTED, WGS-84).
Known IADS sites, SAM rings, EW emitters, and restricted operating zones overlaid on the route so planners can avoid or suppress them.
Match weapons to targets — JDAM, SDB, AIM-120, AIM-9X — with release parameters, fuzing, and collateral damage estimates.
APG-81 modes, EOTS tasking, DAS coverage, and ASQ-239 EW posture configured per phase of flight.
Fuel ladder by leg, tanker rendezvous windows, bingo and joker thresholds, and divert fields.
Radio nets, HAVE QUICK / SATCOM presets, EKMS-loaded crypto, Link-16 NPGs, and MADL participation lists.
Automated checks for airspace conflicts, ROE violations, terrain clearance, and platform performance envelopes before the plan is allowed to ship.
Same mission data file replayed in a SIL / HWIL or full simulator so crews fly the brief once on the ground before flying it for real.
All of the above compiled into a single MDF/MDL, signed, and transferred to the jet via the Data Transfer Cartridge through ALIS/ODIN.
Post-mission ADR data flows back in, feeding lessons learned and reprogramming labs (USRL/ACURL) for the next cycle.
Plan → Build → Rehearse → Load
A great jet with a bad plan is a great calculator with no idea what to solve. The MPE is the one workspace that turns commander's intent into a validated brief the jet can execute — no gaps, no rework, and a feedback loop from debrief back into the next mission.