srcooke

Sent you a DM @Skydriver

Do you have Notepad++ installed ?

You have to re-format the FAA text yourself enclosing the NAT entries in brackets ( ) .As above add the following macro to Notepad++ which I updated: <Macros> <Macro name="PFPX FAA NAT" Ctrl="yes" Alt="no" Shift="yes" Key="78"> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-1" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-1" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-2" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-2" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-3" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-3" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART ONE OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART ONE OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART TWO OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART TWO OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART THREE OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART THREE OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART ONE OF TWO PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART ONE OF TWO PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART TWO OF TWO PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART TWO OF TWO PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> </Macro> </Macros>

There is now a mix of formatting on the FAA site Andrej, the macro still works but may become unnecessary.

Hi Andrej, NATS are now published on the new FAA site FAA NMS Unfortunately the format has changed slightly and requires sections encompassed in brackets eg (NAT-1/3 to END OF PART ONE OF THREE PARTS) repeated for each section. I have however created a Notepad++ macro, just paste into \AppData\Roaming\Notepad++\shortcuts.xml: <Macros> <Macro name="PFPX FAA NAT" Ctrl="yes" Alt="no" Shift="yes" Key="78"> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-1" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-1" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-2" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-2" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="NAT-3" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="(NAT-3" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART ONE OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART ONE OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART TWO OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART TWO OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="END OF PART THREE OF THREE PARTS" /> <Action type="3" message="1625" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="END OF PART THREE OF THREE PARTS)" /> <Action type="3" message="1702" wParam="0" lParam="513" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> </Macro> </Macros> Having pasted the complete NAT entry from the FAA into Notepad++ simply run the macro via the toolbar ( or shortcut CTRL+SHIFT+N ). This can then be copy/pasted to PFPX manual tracks. If necessary I'll increase this to four sections.

With NG 2603-rev3 there are no issues.

Have you installed city update 14 ? If so try without.

Correct. Unfortunately ActiveSky API access was never implemented in PFPX which could have returned the forecast over time.

That is correct Jakob, select the three hour period that best covers your flight.

Sorry Jakob, not even myself ☹️

Copy the whole page content from https://notams.aim.faa.gov/nat.html Paste that in the PFPX manual track entry for NAT. Save the data as a text file for future use if really required, the entry is however retained in PFPX until removed/overwritten. For the save function to work using the above link requires the tab formatting to be changed.

The AIP does not list or depict in the charts docking systems at T2, you have an official source for the information?

The last communication I had was that options were been considered.

Maybe further complicated by its links to the commercial product.

Not whilst it still remains the better route planning tool, at least for Europe.