Ops Added Support For Acmi Specific Configuration In The Integration With N Flight Planning

Leon-N-Flight Planning Integration Configuration for ACMI Flights

Previous Situation:

Operators who conduct a significant number of ACMI operations have needed a way to adapt the process of transferring data from Leon to the N-Flight Planning application. The main issue was that these operators, when specifying flight numbers or ATC callsigns, often used the ICAO or IATA codes of the operators they were flying for—not their own. Until now, NFP (N-Flight Planning) could only recognize the ICAO or IATA codes of the operator itself.

How the integration now works:

The process has been improved to address this issue:

- If the flight number starts with three characters, this is interpreted as an ICAO identifier. In this case, the three-letter code is sent to NFP in the ATCALC field, while the numeric part that follows is sent as the FNUM field.

- If the flight number starts with two letters, this is considered an IATA code. The system will now automatically convert the IATA code to the corresponding ICAO code before sending the data to N-Flight Planning application.

This update ensures that operators performing ACMI operations can seamlessly transfer their flight information from Leon to NFP, regardless of which operator’s codes are used in the flight number or callsign. It greatly improves compatibility and automation, reducing manual intervention and the risk of errors.