Page 1 of 1

icao conflicts

Posted: Sun Apr 27, 2008 7:16 am
by flightsimer
there is still the conflicts with icao codes for aircraft, both the 737-700/-700er/7et have the same code, i have an 7et and 700ER at kphx and wanted to use the 7et, but only the 700er came up when booking it...

Re: icao conflicts

Posted: Sun Apr 27, 2008 8:02 am
by hezza
I don't think it is a fault with ICAO codes, after all they are the same for the a/c you mention.
But you have to enter the correct FlyNET code into the flight plan for all of the a/c you want to fly on that route.

For example: the 700ER is id 41, but the 7ET is 23.

Hope this helps.

Graham

Re: icao conflicts

Posted: Sun Apr 27, 2008 8:27 am
by flightsimer
no, ok here is an example, i have the 737-700ER/7et/ and -700C all on the same route. when i book that flight, only the 700ER comes up as an option even though the other aircraft are there...

Re: icao conflicts

Posted: Sun Apr 27, 2008 9:24 am
by hezza
Yes I understand.
But do you have ....,B737 B737 B737,41 23 377,..... in the flight plan, or just ....,B737,41,....?
Plus of course type approval for them all?

Re: icao conflicts

Posted: Sun Apr 27, 2008 4:50 pm
by Quantum
Hi,

Your 7ET has one plan NEF2 KPHX-KBVI, your 700ER/800 only fly to KCGX and KPDX and your 700C only goes to KCGX. As Hezza says, several acft have same ICAO but you have to specify the aicraft code in FlyNET so it knows which version of the ICAO you wish to use on the route.

Regards

John

Re: icao conflicts

Posted: Sun Apr 27, 2008 8:29 pm
by flightsimer
no my 7et has two out of phx... kbvi which is my home base for all of my corporate aircraft and kcgz... all 737's are on the phx-cgz flight to and from... but when i went to book last night, the 7et did come up only the 700ER...

Re: icao conflicts

Posted: Sun Apr 27, 2008 8:39 pm
by flightsimer
well i dont know it must of been something last night, because i checked my route and it was assigned... and i just went to book a flight and to see if it would allow the 7et, and it was there... but it wasnt last night... :roll: