Hi all.Below is a section from 0803 KSEA, what is missing is the MGNUM waypoint between ERYKA and ANVIL. This only affects the ILS and not the LOC or other sections for 16C.ie PAE ERYKA MGNUM ANVIL etcat the moment my app reads PAE ERYKA ANVIL etcIs this something that you can add or is there a reason it is not added here? I could add this myself but when I upload a beta of my app that uses this data then any user would have to manually add it too.I take it that there is no need to identify the FAF within these procedure files? ie SODOE is FAF in this case. I suppose I will create an external DB containing FAF for various airports.Is PAE the correct transition for this approach? According to another file it has as the only transition for this approach.Many thanksGrayANVILNormal47.618844-122.309628032000aboveSODOENormal47.536953-122.310347019000aboveRW16CRunway47.463808-122.31098604330atOTLIENormal47.397825-122.311561020000below(INTC)Intc47.435389-122.309611000at0158161AutoMILLTNormal47.252153-122.308003050000atMILLTHold47.252153-122.308003050000atInbd341RightDist3.0PAENormal47.919833-122.277833000atERYKANormal47.735608-122.308597050000above

Hi Gray,Thanks for bringing this to my attention.>Below is a section from 0803 KSEA, what is missing is the>MGNUM waypoint between ERYKA and ANVIL. >Is this something that you can add I have already overwritten my master 0803 database with the 0804 data so I don't know for sure if that waypoint was in there or not but I'd guess it was. Anyway, it is in the 0804 so I'll check to see if MGNUM shows up and will fix it if it does not.>I take it that there is no need to identify the FAF within>these procedure files? Not that I know of. The aircraft could care less about a FAF. All the FMC sees are the waypoints to follow.>Is PAE the correct transition for this approach? My FAA data has PAE, ERYKA and MGNUM as the transition. PAE is the IAF. You can always delete PAE from the flightplan if you do not need or want to use it.Regards,Terry