TMetzinger
Final Approach
Starting June 29th, if you want to get RNAV arrival/departure routes (RNAV SID/STARS), you need to start filing your IFR flight plans in ICAO format.
Details are at the AOPA website, and there's an FAA letter to airmen out about it. Also try http://faa.gov/ato?k=fpl
I'm still sorting it out, but I think that for my G1000 airplanes I file the equipment codes of SGZ/C (standard, GPS, Z "other" identifier for FAA / Mode C transponder - I know the G1000 is a mode S but I'm not sure what mode S info it's transmitting)
Then in the Other section (block 18) I put in NAV/RNVD1E2A1 to say I can do 1 NM precision in departures and arrivals and 2 NM precision enroute.
Other wrinkles include making sure that the airport identifiers are four digits.
I may try filing one via DUAT today just to see if it goes through correctly.
EDIT - DUAT (www.duat.com) makes it pretty straightforward. I'll have to remember to put the appropriate comments in when filing with FliteStar though.
Details are at the AOPA website, and there's an FAA letter to airmen out about it. Also try http://faa.gov/ato?k=fpl
I'm still sorting it out, but I think that for my G1000 airplanes I file the equipment codes of SGZ/C (standard, GPS, Z "other" identifier for FAA / Mode C transponder - I know the G1000 is a mode S but I'm not sure what mode S info it's transmitting)
Then in the Other section (block 18) I put in NAV/RNVD1E2A1 to say I can do 1 NM precision in departures and arrivals and 2 NM precision enroute.
Other wrinkles include making sure that the airport identifiers are four digits.
I may try filing one via DUAT today just to see if it goes through correctly.
EDIT - DUAT (www.duat.com) makes it pretty straightforward. I'll have to remember to put the appropriate comments in when filing with FliteStar though.
Last edited: