Hi,
A small suggestion, adding a separate optional box for IATA flight number since not all airlines uses the flight number as a callsign, i.e BA1370 uses the callsign SHT2L and EK734 becomes UAE8J and so on. This will make easier for volanta for example to differentiate between what is a callsign and what is a flight number.
They have this already (“Airline” and “ATC Callsign” fields).
Hi,
I might be mistaken but I only see option for (Airline) and (Flight-No).
I was hoping for something similar to PFPX
You can enter (for example):
Airline: EK
Flight-No: 734
ATC Callsign: UAE8J
(The callsign is made up of the ICAO code and an (alpha)numeric combination)
This dose not work. I just tried generating a flight plan using IATA:FZ for FlyDubai Airlines which has an ICAO:FDB.
The ICAO code doesn’t show anywhere in the OFP or when prefiling the flight plan, you can see the ATC FPL blew, instead it’s showing with the abbreviation of FZ
261945 CYULSBFP
(FPL-FZ17-IS
-B738/M-SDE1E2E3FGHIJ1LM3ORVWXYZ/HB1
-OMDB2015
-N0434F260 NABIX3G NABIX P699 OXARI M430 BOVIP Q215 AFNAN AFNAN1R
-OTHH0036 OMDB
-PBN/A1B1C1D1L1O1S1T1 NAV/GPSRNAV REG/A6FEV SEL/DLFR CODE/8963B8 RMK/TCAS CALLSIGN SKYDUBAI PURPOSE SCHEDULED PAX FLIGHT)
as described above from @thepilot111 it works perfectly. I assume, you have entered it wrong.
What about a screenshot of your Simbrief dispatch system while filling it out?