So calling FlightInfoEx returns a field called “route” something like (for ANZ1):
PRCH9 FICKY B200 TONYS 2400N 13000W 1900N 13600W 1500N 14000W 1000N 14500W 0500N 14900W 0000N 15300W 0500S 15700W 1000S 16100W 1500S 16600W NU R327 VISIK 2500S 17500W INTIB SELKA
I want to know what each block represents. As far as I can tell FICKY, SELKA, etc are waypoints with a specific lat/long location.
What are the other items in the list? (for example PRCH9, 16600W, NU, etc)
Elements like “2400N 13000W” are latitude/longitude pairs, in this case 24 degrees N, 130 degrees W.
They would read like this
PRCH9 - Perch 9 Departure Sid out of LAX (204.108.4.16/d-tpp/1113/00237PERCH.PDF)
Direct to
FICKY (see the PERCH 9 Departure attached.
B200 - Lower ATS route designator
TONYS - Reporting Point at 19.51.00N 122.49.14W
Next are the lat long points to route to.
2400N 13000W
1900N 13600W
1500N 14000W
1000N 14500W
0500N 14900W
0000N 15300W
0500S 15700W
1000S 16100W
1500S 16600W
NU R327 - route to follow to
VISIK - New Zealand Nav point at S 21 21 17.8, W 171 46 18.3
2500S 17500W
INTIB New Zealand Nav point at S 30 00 00.0, W 179 05 54.0
SELKA - Aukland transistion Fix.
More than likely by the time they reach Selka they receive the Approach they are going to use or
receive Radar Vectors from SELKA to an ILS.
All of the numbers followed by a single letter are either latitude or longitude.
I think you’re off by one, they’re lat long pairs not long lat pairs.
Huh? Even your quote shows I say Next are the lat long points But Looking at them they are
Longitude then latitude 
. So we both goofed hehe.
No, the pairs in the route are lat long. You peeled off 2400N from the first pair and called it something else; this is also why you ended up with the extra “not sure what this is” long. The first lat long is 2400N 13000W and the last lat long is 1500S 16600W.
Thanks for the MOST excellent explanation of where I messed up.
Ill edit the original and fix my OOOPS
You may want to also try using the DecodeFlightRoute method, which handles parsing of those route strings into a list of lat/lon points. However, be aware that it is not able to handle all possible route strings, particularly for routes not entirely within US airspace.
you know the various things applied to air field is getting new nerves.