@Richard Martinez good question, and honestly the right one to ask before you spin a test board.
The short answer is that the RF front-end on the MultiNav Pro+ already includes the PA and LNA with the matching done on-module — you're not expected to drop in external matching components. The 50km figure comes from a combination of the amplifier stack, the receiver sensitivity pushed well beyond what a stock BLE chip gives you, and the antenna being up in the air on both ends (drone-to-drone, where you eliminate ground reflections entirely). That last part is important — that number assumes line of sight at altitude, not two units sitting on a workbench.
For antenna, you want a 50-ohm load and a clean feedline. If you're using a U.FL connector and keeping the cable short, you're fine. Where people usually leave dB on the table is using a cheap coax run with a connector that wasn't torqued properly, or putting the antenna too close to a metal enclosure. The module itself won't be your weak point if you feed it correctly.
Honestly your best move before committing to a footprint is to ping the team directly through the Dev Hub — Moamen has done the RF work himself and can tell you exactly what antenna they validated against for those range tests. That'll save you a lot of guesswork on the integration side.
